NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Simple VLAN without VLAN-aware router and DHCP aka Port-based VLAN
I did manage to get the tagged VLANs (802.1Q) working with DHCP, mutiple switches AND VLAN-aware router - the whole shebang. However, I tried to poke around with the simple setup with not vlan-aware ...
Thanx a lot for the time and effort. Looks like, I'm ending up as that guy I mentioned before, who got it working...somehow :O
Actually, I tried all kinds of combinations and...eneded up with exactly the same setup I began with...and this time it was working! With DHCP and everyting!
So the approach the Asymmetric VLAN is very simple:E.g.
- define VLAN 10 + 20
- define the trunk/gateway - VLAN50 (or keep the default VLAN1)
- make ports 2+3 only members of VLAN10 and VLAN 20 respectively
- make all ports needing access to the outside network (extra switch of router) members of VLAN50
- set port 1 to PVID50
- set port 2+3 to PVID10 and PVID20 respectively
And the setup works as intended - port 2+3 are online, but cannot talk to each other as they are on different VLANs.
Now, the biggest question still remains - Why the #¤%# didn't it work before ???!!!!!A few reboots were made, yes, but otherwise, nothing else!
Additional question:- What exactly are Tagged VLANs needed for then comparing the Untagged if the asymmetric VLANs support the network segmentation and DHCP ?
Kindly try the steps below:
1. On VLAN 1, all ports are set to untagged.
2. On VLAN 10, port members would be ports 1 and 4. Set port 1 as untagged with PVID of 1. Then, set port 4 as untagged with PVID of 10.
3. Create VLAN 100. The port members would be ports 1, 4 and 8.
4. On VLAN 100, set port 1 as untagged with PVID of 1. Then, set port 4 as untagged with PVID of 10. Then, set port 8 as untagged with PVID 100.
5. Connect the router on port 8.
6. Check if the PC connected on port 4 that has a static IP address will be able to get replies when you ping the IP address of the router. Also, check if it will acquire an IP address from the router.
What we've tried to setup from the steps above is called Asymmetric VLAN.
Let us know the results.
Regards,
DaneA
NETGEAR Community Team
Thanx a lot for the time and effort. Looks like, I'm ending up as that guy I mentioned before, who got it working...somehow :O
Actually, I tried all kinds of combinations and...eneded up with exactly the same setup I began with...and this time it was working! With DHCP and everyting!
So the approach the Asymmetric VLAN is very simple:
E.g.
- define VLAN 10 + 20
- define the trunk/gateway - VLAN50 (or keep the default VLAN1)
- make ports 2+3 only members of VLAN10 and VLAN 20 respectively
- make all ports needing access to the outside network (extra switch of router) members of VLAN50
- set port 1 to PVID50
- set port 2+3 to PVID10 and PVID20 respectively
And the setup works as intended - port 2+3 are online, but cannot talk to each other as they are on different VLANs.
Now, the biggest question still remains - Why the #¤%# didn't it work before ???!!!!!
A few reboots were made, yes, but otherwise, nothing else!
Additional question:
- What exactly are Tagged VLANs needed for then comparing the Untagged if the asymmetric VLANs support the network segmentation and DHCP ?
I'm glad that its now working. :) I have just read your feedback 14 hrs ago and I was wondering why it didn't work instantly.
As you can observed, no tagging is involved and as far as I know, all VLANs should be in the same subnet in implementing asymmetric VLANs.
On the other hand, the usual VLAN configuration wherein tagging is needed, you can have each VLAN on their own subnet. You could also set inter-VLAN routing when needed as long as the switch supports the inter-VLAN routing feature or if not, you could use a VLAN-aware router that supports inter-VLAN routing.
Regards,
DaneA
NETGEAR Community Team
Anyway, thanx again for the effort.
Although, the solution is - there's no solution if it's not working as described. My best advice to others would be - try setting up the simple setup first, try different routers, make a few reboots and factory defaults and make sure you follow the correct instructions - and hopefully it will work.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
