Setting up Guest WLAN

EvilGrin

EvilGrin

EvilGrin

Associate
Joined
12 Oct 2004
Posts
1,432
Location
Aberdeen, Scotland
Hi guys,

I'm trying to set up a Guest WLAN to be completetly separate from our network and only allow internet access. The line I want to use has a Draytek Vigor 2800 router, and I have a Ruckus 2942 wireless AP. Both units support VLANs, but I have no clue how to configure them - have never needed to mess with VLANs before!

Draytek have this on their support site: http://www.draytek.co.uk/support/kb_vigor_vlan.html

It sounds great in principle, but how to set it up in practice? I understand that those options there will set for example switch port 1 as VLAN1, and port 2 as VLAN2, but how does it work, I can't see a way to configure VLAN1 to be on say 192.168.0.x and VLAN2 to be on 192.168.1.x, or am I completely missing the point?

For our main network, our file server is the DHCP server, so ideally I'd like our wireless AP to sit on VLAN 2 and serve DHCP, to have a subnet of 192.168.1.x.

The Ruckus unit states that it supports VLANs in much the same way as the Draytek, I can't see a way of separating the IP addressing.

I'm confused. :confused: Any help would be much appreciated!
 
The IP addressing is separated by using different scopes for each VLAN. (or indeed different servers). Then all you do is configure the Interface with an IP in that subnet for that VLAN. Depending on the kit this can either be the router port itself or a virtual VLAN interface.

Stuff to think about:

Both VLAN address ranges will need to be included in any NAT rules to get internet access.
Access control lists need adding to the router interfaces to stop the guest network getting access to the production network.
Configuring VLANs on the router is fine if everything plugs into it directly, but of there's a switch in the middle you will need that to support VLANs too. In which case you'll need to go off and read about 802.1Q vlan tagging and how that works, else you'll get yourself in a right muddle.
 
Skidilliplop said:
The IP addressing is separated by using different scopes for each VLAN. (or indeed different servers). Then all you do is configure the Interface with an IP in that subnet for that VLAN. Depending on the kit this can either be the router port itself or a virtual VLAN interface.

Stuff to think about:

Both VLAN address ranges will need to be included in any NAT rules to get internet access.
Access control lists need adding to the router interfaces to stop the guest network getting access to the production network.
Configuring VLANs on the router is fine if everything plugs into it directly, but of there's a switch in the middle you will need that to support VLANs too. In which case you'll need to go off and read about 802.1Q vlan tagging and how that works, else you'll get yourself in a right muddle.
Click to expand...

Thanks for the quick reply.

Yeah this is where I'm getting confused; all that I can see for configuring the VLAN is Vlan1 - P1, Vlan2 - P2 etc., there's nothing that I can see in any of the settings windows for configuring/defining the scope of Vlan 1 and 2... In addition to this, I can't see any way of turning on DHCP for one specific VLAN either. Urgh.

My plan was to keep things simple by plugging the AP in directly to the appropriate router port (although I do have layer 3 switches which I know will complicate things ad infinatum).
 
The Draytek routes aren't proper VLANs like your traditional switches. They just segment ports so that traffic on P1 will not communicate with P2.

Are you trying to use your own wireless solution or the wireless on the Draytek?
 
Layer 3 switches should make this easier. If you do all the DHCP/DHCP Relay, VLANs and Access lists on those you'll find you have more tools at your disposal.
 
Yeah, problem I have is that I have no idea where to start with configuring VLANs on the poweredge 6224/6248 switches, I can see all the settings in OpenManage, but without knowing what I'm doing, it's pretty damn confusing.

Any tips/pointers?
 
Not really, I could spend all day telling you how to configure VLANs, and routing but you wouldn't understand it any more than you do now.
I'd just jump on wikipedia and read up on them, then look up the relevant areas in the Powerconnect manual. Also look at some Cisco Examples for CCNA/CCNP, the powerconnect CLI is very similar to Cisco IOS.

Once you get your head around how the switches process and separate the traffic then it's really very straight forward.
 
Last edited:
There's plenty of nice VLAN basics videos on YouTube. As above telling you how to configure your network is quite a bit of work I doubt most people want to go into.

Maybe play with Cisco Packet Tracer to get a working version of your project?
 
You must log in or register to reply here.
Back
Top Bottom