Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm just getting my head around VLANs and have been through the tutorials by danscourses on youtube which have been incredibly helpful.

I recently picked up a netgear managed switch (FSM726-300) which I think can do layer 2 vlans. I would like to set up 2 or more vlans on my network. The would simply be the netgear switch (that everything would be plugged into) which is then plugged into the router connected to the internet.

I want to have one connection from a port on the switch to a port on the router and make it a trunk for all the vlans. If I have 2 vlans then I'd probably make the addressing something like

  • 192.168.21.1-192.168.21.255 for vlan 1 with 192.168.21.1 being the router
  • 192.168.22.1-192.168.22.255 for vlan 2 with 192.168.22.1 being the router

The problem is I'm not sure how I would set up the router so create the sub interfaces and make it work. The router is a EchoLife HG532. I don't think it's possible to telnet into it. If there was I probably would be able to figure it out. Originally I thought that maybe the router didn't support VLANS but there are several places where options for it come up.

1)

If I go to the advanced->vlan page I can set the mode to LANVLAN (the only mode) and then I get the configuration screen shown below. (The help button actually contains no help on this!)

1 2

I'm not too sure but I presume if I checked LAN1 next to PVID then this means anything coming in on LAN1 will be assigned to the vlan with the id in the "VLAN ID" box. It lets you either just set a pvid, or just one of tag or untag, or both, a tag or untag and pvid for each port.

Can someone explain what tagging and untagging would do in this case? Given that it only lets you enter one vlan id does this mean it doesn't support trunking? I guess I could just use a port for each vlan.

2)

In the basic->wan settings section you can create several connections but you can also create a connection and check the vlan box and enter a VLAN id (in the range of 0-4094, I thought vlans started at 1?!)

3

If I create a second connection and set the vlan id to 1 I get something like this:

4

From the dot in the name "nas0.1" it kind of looks like it's created a sub interface. There is nowhere I can find though where I can set a secondary IP address for the second interface (e.g. 192.168.22.1).

Please can someone try and explain what's going on. Why would it let you specify a wan connection for a vlan but not allow a seperate ip so that it can be accessed from the vlan?

I realise this is a really long question. This is the first time I've ever looked into vlans so it would be great if someone has some time to try and explain parts of this.

Thanks!

share|improve this question
add comment

migrated from serverfault.com Apr 2 '13 at 8:43

This question came from our site for professional system and network administrators.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.