asked on DHCP Broadcasts across WAN
I am bringing up a new WLAN environment and all site LWAP's will receive their DHCP address from the main site that houses the WLAN controllers. I have setup a /24 for the controllers and the LWAP's.
I need some verification and or advice on how I can ensure when a new AP is plugged in that it's DHCP broadcast is sent over the WAN link to the DHCP server here. Seeing as how Routers break up broadcast domains that is a problem, but we have ip helper-address for this.
As it is now, I can ping across the WAN link to the /24 and DHCP server. Now if I create a new vlan interface on the core switch at the other location and set the ip helper-address on it, ping dies and I can no longer reach the /24
I somehow need this because once I start plugging in AP's and trunking ports to the native /24 vlan in question they will need to know how to reach their intended DHCP server.
I am somehow missing something
I need some verification and or advice on how I can ensure when a new AP is plugged in that it's DHCP broadcast is sent over the WAN link to the DHCP server here. Seeing as how Routers break up broadcast domains that is a problem, but we have ip helper-address for this.
As it is now, I can ping across the WAN link to the /24 and DHCP server. Now if I create a new vlan interface on the core switch at the other location and set the ip helper-address on it, ping dies and I can no longer reach the /24
I somehow need this because once I start plugging in AP's and trunking ports to the native /24 vlan in question they will need to know how to reach their intended DHCP server.
I am somehow missing something
RoutersDHCPNetwork Architecture
Last Comment
dswope79
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Sounds good. If you get sick of waiting on TAC, feel free to post configs and "show ip route" on the devices in question.
ASKER
Created L2 network for each site for the AP's and the controller, got all the L2 and L3 issues out of the way. This question can be deleted.
If all pings stopped when you created the new vlan, I would guess that there is some type of IP overlap - This could be a duplicated subnet or even two subnets with overlapping host ranges such as 192.168.1.0/24 overlapping 192.168.0.0/23.