NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GS105PE VLAN trunking not working
I’m trying to set up a GS105PE in the garage. I intend to add an Orbi Pro Wifi6 satellite there and we already have a POE camera in position. The GS105PE connects to a GS324TP switch, which also po...
- Thanks, got it working! Tagging the uplink for VLAN ID 1 didn’t work, but setting the IP to manual did the trick. I’d used a reserved IP before and for some reason that messed things up
Retired_Member wrote:
I’m trying to set up a GS105PE in the garage. I intend to add an Orbi Pro Wifi6 satellite there and we already have a POE camera in position.
The GS105PE connects to a GS324TP switch, which also powers it.
Is this an extension from a wired backhaul?
Retired_Member wrote:
The GS105 has port 5 as its uplink. It’s connected to port 17 on the GS324.
GS324 port config:
VLAN 1 untagged
VLANs 10-40: tagged
GS105: same configuration for the uplink port.
Assuming the PVID on the ports used for the trunk are set to PVID 1 - this makes perfect sense.
The Retired_Member proposal also tagging the VLAN 1 on the trunk is philosophical - untagged it is much easier to just connect a system to access the VLAN 1.
Retired_Member wrote:
According to the insight app, it gets an apparently self-assigned IP in the .66 range. That range doesn’t exist on the Orbi pro and has never been configured.
All the Plus switches (except a few models which allow the config of a real management VLAN) can pick-up IP configs by DHCP from any connected VLAN.
Some confusion what is a "self-assigned IP" - that would be some ZeroConf 169.254.x.x/16 address. However, the Netgear switches don't support self-assigning address spaces. Remains the question what address that ".66" rage should reflect? Some public IP leaking over for example?
Yes it is (an extension from a wired backhaul).
I got the setup working using a fixed IP. The DHCP reservation was ignored for some reason once the uplink port was tagged for the 20-40 VLAN IDs. Now I’m trying to figure out where that .66 network is coming from. Our WAN hookup is a shared medium (cable internet), so I guess it’s theoretically possible this is bleeding in. But tbh I don’t like the idea of that.
I got the setup working using a fixed IP. The DHCP reservation was ignored for some reason once the uplink port was tagged for the 20-40 VLAN IDs. Now I’m trying to figure out where that .66 network is coming from. Our WAN hookup is a shared medium (cable internet), so I guess it’s theoretically possible this is bleeding in. But tbh I don’t like the idea of that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
