Skip to main content

Wed, Apr 30, 2014 6:36 PM

Same SSID at two different locations and different DHCP relay

I am trying to create the same SSID with multiple VLANs and different DHCP relay. Trying to setup same SSID at two different sites with different firewalls. I would like to have the SSID go to the corresponding DHCP server based on their location. is this possible to do?

Responses

37 Messages

 • 

854 Points

7 years ago

Yes this works quite nicely with an organization with multiple sites. The dhcp server location isn't determined by the SSID, it's determined by the device that's doing DHCP relay for you, which can be the switch or firewall at each site. The DHCP server is smart enough to see which subnet the request came from and respond accordingly.

One thing to be aware of... if the locations are close to each other, make sure the DHCP lease time is less than the time it takes to get between locations. Windows 7 has this 'helpful' feature where if it sees the same SSID it tries to keep using the same address without going through a full DHCP cycle. That one puzzled us for a very long time....

824 Messages

 • 

13.2K Points

7 years ago

Hello FluxCapMalfunction,

I wonder if you found a workaround or solution to what you are trying to achieve.

With regards

MS

3 Messages

 • 

92 Points

7 years ago

Yup. I have the same SSID at two different sites with the same VLAN ID. They both go to the FW for DHCP for Guest/Corp.

824 Messages

 • 

13.2K Points

7 years ago

ok. Is it doable to have same SSID with different VLAN ID in different sites?
Use case - Central Office with ZD with its own FW and VLAN scheme and branch with its own. AP is connecting to ZD from remote.

3 Messages

 • 

92 Points

7 years ago

In my case I actually made it the same VLANID at both sites for easier management. But i believe you can specify the VLANID on the WAPs as well.

1 Message

 • 

60 Points

4 years ago

Makes no sense - 7 AP's at once location with tagged vlan - 2 AP's at remote location with no vlan needed - DHCP comes from the firewall all on same subnet, no separate WLAN IP scheme. Should be completely transparent and automatic. Nothing more needed. So, why can't remote wireless clients see the local DHCP server out of the gate?