Another VLAN question...soz

[Simcfc73]

Hi,

 

I've been putting off doing VLANS for a while now but I think I need to now I am doing BYOD. I have a vlan setup but no intervlan routing yet which works fine as I don't need it but have hit a snag with VLANs and Ruckus controllers. When I use a VLAN and the ruckus sign in page it doesn't load up... which I imagine is because the controller is not on the right VLAN... so my question is, will this ever work without intervlan routing setup???

 

I am all netgear and struggle getting the vlans routing working in the GUI and hate CLI stuff. I have the routing setup in the GUI but its not working yet

[Boredguy]

Here is how our Ruckus and Netgear switches are configured

 

vLan 1 = Main network (10.x.x.x), vLan 30 = BYoD network (172.x.x.x)

 

All switches have the ports linking them together tagged for vLan 1 and vLan 30 and a pVID of 1

Ports where the access points are connected have vLan 1 Untagged and vLan 30 Tagged and a pVID of 1

The port from the switch to the Zone Directory has vLan 1 untagged and vLan 30 Tagged and a pVID of 1

 

We do not have any layer 3 capabilities on our switches, but it seems to work nicely.

 

We have purchased on signed SSL certificate for our ruckus box, so on our BYoD DHCP/DNS server we create a new zone for our domain and put the new FQDN of the Zone director in it with the 10.x.x.x address and clients are happily getting the portal page with their 172.x.x.x address