4 replies to this topic

[armorenets]

Shave a wr54g with coovaap configured with hotspotsystems. The wireless is turned off in the router as I have a trucks systems providing the WiFi network. Everything is configured to 192.168.10.
When a wired machine tries to connect u get all three pages ending in the layout instruction page and all works well. If you try to use the wireless with the same machine you get the terms page then the logging in page then it times out with the browser cannot find or display error and you do not complete the login process. This is a free access requiring only terms acceptance. Any ideas where to look to resolve this issue.

[Marko]

Please copy and send us the URL from the last screen that you reach.

[armorenets]

ok tested further problem seems to lie between router and ruckus ap's. and mostlikely has to do with the changing of ips from the 192.168.10.x set to the 192.168.182.0 the router and managed switches and the ruckus zone director all reside on 192,168.10.x but after joining the hotspot your ip is pushedto192.168.182.x so i believe afterthisoccurs the aps will no longer route you back to the router. tested this theory by moving router to a simple wifi net work were the ap gets its ip through dhcp and no problems but in the more complicated enviroment the problem returns not sure if i need to set up another network with the 192,168,182.x and haveall management on 192.168.10.x. if so how do you split the ports on the router.

[winkleburyctr]

I have no knowledge of the ruckus system and how it works, but ideally the access points should not be accessible from the 192.168.182.0/24 network due to security concerns and the limited number of addresses available imposing an upper bound to the number of access points and users that can be supported. All addresses in this network apart from 192.168.182.1/255 should be used by clients. The limiting factor in this instance would appear to be your ruckus gear firewalling this ip range used by chillispot. You will need to contact ruckus-knowledgeable people to find out if and how to alter the ruckus setup to allow the ip range through the APs onto the LAN.

Regarding your question of "how do you split the ports on the router", if you have your wrt54g running dd-wrt or openwrt then the matter is as simple as using the inbuilt vlan technology of the broadcom chipset which is supported by both of these OS. NOTE: there are two methods of vlans using broadcom, being port-based and 802.1q-based. If your ruckus gear can use 802.1q vlans and you insist on the equipment being on the same segment as your clients then you can use this method. However, the alternative, port-based vlans, does not require the additional implementation requirement on connected equipment, and therefore is easier to setup. Port-based essentially removes one or more of the LAN ports from the switching hub on your wrt54g router and designates it/them as a separate network segment allowing for multiple IP ranges to be utilised by the router on the various LAN ports without requiring 802.1q.

I hope you find some of this information helpful, and I am sorry I can't help more with your main problem between the ruckus ap(s) and chillispot, which I would guess is down to an inbuilt firewalling mechanism in the APs.

[armorenets]

Thanks winkleburyctr, although your answer did not directly help me it did remind me about some settings in Ruckus wireless networks. Turns out i had all clients firewalled from all other clients. This included the router after the ip was changed to the 192.168.182.x  client network just before authentication. A simple one click fix.