Forum Discussion
Solved
ProSAFE XS728T, DHCP on trunk port?
Is it possible to do DHCP on trunk ports?
On my Netgear switch, I have VLANs 128 and 192. I've made port 23 and 24 trunk ports. I'm connecting an access poing to the trunk ports because the S...
tantony wrote:
The AP is connected to trunk port 24, and I tagged it with VLANS 128 and 192 because the AP SSIDs are using those VLANS. The port PVID is 1. So if I change the port PVID to 128, the AP will get DHCP from that VLAN?
Yes, untagged traffic will be associated to the VLAN 128 then.
tantony wrote:
I'm assuming the SSIDs will still work?
Of corse, yes. Not sure why you intend to expose the management VLAN to the wireless, up to you...
tantony wrote:
The AP is connected to trunk port 24, and I tagged it with VLANS 128 and 192 because the AP SSIDs are using those VLANS. The port PVID is 1. So if I change the port PVID to 128, the AP will get DHCP from that VLAN? I'm assuming the SSIDs will still work?
I guess it makes sense why the AP is not getting a dhcp now because the PVID is 1 no ports are members of VLAN 1.
Yep - no DHCP server on the VLAN, too.
The trunk port does not have to know...
Either the undefined WLAN AP does the BOOTP/DHCP untagged (so the switch PVID does define the VLAN these packets are associated to), or the WLAN AP has a tagged management VLAN configured.
tantony wrote:
The WLAN AP is a Ubiquity AP AC PRO.
Unless they changed or there is something well hidden, the UAP management is untagged, so see the PVID approach above.
The AP is connected to trunk port 24, and I tagged it with VLANS 128 and 192 because the AP SSIDs are using those VLANS. The port PVID is 1. So if I change the port PVID to 128, the AP will get DHCP from that VLAN? I'm assuming the SSIDs will still work?
I guess it makes sense why the AP is not getting a dhcp now because the PVID is 1 no ports are members of VLAN 1.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
