2504 WLC with External Hotspot

[petenixon]

Hi all,

I have a problem with my configuration that I hope someone can help with.

I have a 2504 WLC configured for guest internet access, which points to a default gateway which is a GIS internet hotspot gateway. DHCP is controlled by the WLC and the guest interface (port 4) connects directly to the hotspot. 

When connecting a device directly into the hotspot, everything works fine. When connecting the controller to the hotspot, I get a DHCP address ok, but when attempting to browse to a webpage (when I should be prompted to enter an authentication code) the webpage eventually times out.

Any ideas or suggestions are most welcome.

Thanks.

[Scott Fella]

I'm assuming that the GIS gateway is doing the portal page?  If so, is it also doing the dhcp and the NAT?  If the GIS unit is performing most or all these task, all you need to do is have an open ssid which places the traffic on port 4 of the controller.  From there, the GIS unit would take over.

-Scott

[petenixon]

Hi Scott,

Thanks for the reply. Yep, the GIS gateway is doing the NAT and is now doing DHCP although i'm not getting an address from the gateway. I'm guessing this may be due to the fact that it has an internal 'firewall' and therefore does not respond to proxied requests?

Cheers,
Pete.

[petenixon]

Just to give a bit more detail:

Topology:
WLC connects direct to hotspot on port 4, port 1 connects to the switch for AP management. 

WLC:

Code version: 7.2

VLAN 4 - Mapped to port 4.
IP: 192.168.1.1/24
Gateway: 192.168.1.254

VLAN 2 - ap management interface
IP 192.168.0.1/27

Virtual interface 1.1.1.1

Two further vlans have been configured for other wireless networks.

GIS LAN IP: 192.168.1.254/24
DHCP Scope: 192.168.1.3 - 253

I enabled an ACL on the controller to see what traffic was hitting, traffic is entering the interface but not leaving, have confirmed this as well on the controller where I can see discovers going out but no response. Not sure why the hotspot box isn't responding, I think possibly an ARP issue from my troubleshooting.