Netgear 3500L with DD-WRT v24-sp2 (08/07/10) mega (SVN revision 14896)
Can somebody please explain, why tagged VLAN's from a trunk are discarded at the switchports? I replaced a simple Linksys L2 Switch where trunks are transparently forwarded. All tagged networks reach the core router/dhcp no more.
Ok, I think. I configure Trunks like I do in CISCO Networks for example. VLAN1 native untagged and all others tagged on incoming and outgoing port. With GUI impossible, in cli setable but not working. And yes, I am aware, that the port numbering is inverted. I do not even need the VLANS on dd-wrt, but I need that it passes the trunks. Last hint: I do not even require L3 functions on this (simple) dd-wrt configuration.
Netgear 3500L with DD-WRT v24-sp2 (08/07/10) mega (SVN revision 14896)
Can somebody please explain, why tagged VLAN's from a trunk are discarded at the switchports? I replaced a simple Linksys L2 Switch where trunks are transparently forwarded. All tagged networks reach the core router/dhcp no more.
Ok, I think. I configure Trunks like I do in CISCO Networks for example. VLAN1 native untagged and all others tagged on incoming and outgoing port. With GUI impossible, in cli setable but not working. And yes, I am aware, that the port numbering is inverted. I do not even need the VLANS on dd-wrt, but I need that it passes the trunks. Last hint: I do not even require L3 functions on this (simple) dd-wrt configuration.
I think you're referring to Dynamic Trunking Protocol which configures trunks automatically and is a piece of Cisco's vast proprietary technology...
Did you see the switched ports page recently? I changed it a few days ago to explain more of the nvram variables and how to set them.
I haven't finished revamping it so the trunking usage examples are still missing and it's probably still really confusing for configuring trunks... However, I gave a good example of all my variables from a working trunk on two different models here:
If you can't get it working with the new information then post the defaults from the three nvram commands, all the VLAN's you're trying to trunk, and what ports you're trying to use. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I think you're referring to Dynamic Trunking Protocol which configures trunks automatically and is a piece of Cisco's vast proprietary technology...
No,no nothing dynamic. But Trunk is the correct term. Usually You have exactly one untagged VLAN and n tagged
VLANS between two switches. My last observations show, that tagging on dd-wrt means tag all VLANs or nothing.
Quote:
Did you see the switched ports page recently? I changed it a few days ago to explain more of the nvram variables and how to set them.
The one and only intention behind this is to tap dd-wrt in a existing trunk. And serving bridged wireless in default VLAN.
I was surprised, that indeed all devices in VLAN3 on my network reached the firewall now. But all other connectivity in the untagged VLAN is gone. The GUI is also no more reachable. Only via fixed IP over port 2 or 3.
I think you're referring to Dynamic Trunking Protocol which configures trunks automatically and is a piece of Cisco's vast proprietary technology...
No,no nothing dynamic. But Trunk is the correct term. Usually You have exactly one untagged VLAN and n tagged
VLANS between two switches. My last observations show, that tagging on dd-wrt means tag all VLANs or nothing.
Trunks don't magically configure themselves without some help, so either the old switch had a dynamic protocol running to configure the trunking or it wasn't VLAN capable at all and you were just using it to pass the trunk from another device that was VLAN capable?
netsigi wrote:
Quote:
Did you see the switched ports page recently? I changed it a few days ago to explain more of the nvram variables and how to set them.
VLAN's in DD-WRT are exposed as interfaces named vlan# which you can do everything you normally would with an interface (assign it an address, bridge it, run a DHCP server for it, etc.). You can find more info about how to use the interface in other wiki guides, the switched ports page is just about how to configure the nvram variables to get VLAN's functional on layer 2.
netsigi wrote:
My last test:
nvram set vlan3ports="4t 1t"
The one and only intention behind this is to tap dd-wrt in a existing trunk. And serving bridged wireless in default VLAN.
I was surprised, that indeed all devices in VLAN3 on my network reached the firewall now. But all other connectivity in the untagged VLAN is gone. The GUI is also no more reachable. Only via fixed IP over port 2 or 3.
If you want the GUI to be accessible from VLAN 3 then you need to assign the interface an IP within the subnet that VLAN 3 is using which you can do on the networking page. You should have the CPU internal port included in the vlan3ports also, see the explanation on the switched ports page. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Trunks don't magically configure themselves without some help
How true. But You search explanations much too far. Like You I am trying hard to understand dd-wrt concepts. Or in Other words: With the concepts of many other Companies I earn my money And therefore I have a quite good knowledge of them.
I made some quick drawings:
I put a simple Netgear, D-Link switch into the trunk. All ethernet packets are switched. Tagged or not. All VLAN's going thru. All Networks between "some" and "another" work.
Here dd-wrt comes into the game. Default settings.
The untagged traffic is still forwarded, tagged packets are lost, dropped whatever, VLAN3 from "some" to "another" does not work.
I try do do what I do with any other network gear in this case: configuring the trunk. And minimalistic as needed. I tell port4 and port1, they have also capability to forward tagged VLAN3:
Now the VLAN3 is indeed forwarded between "some" and "another" but the untagged, let's say VLAN1 is now blocked. And also the management is no more reachable. I can connect my client PC to port2 or port3, set manually a address in the management lan (the untagged one) and then I can reach dd-wrt's address again and change the mess back. It is because DHCP for all Networks are behind "some"
It's no Voodoo, no dynamic stuff. Just simple network basics ;-)
There is support for the "u" attribute, the opposite of the "t", did you test the example above?
I think it should work. _________________ Kernel panic: Aiee, killing interrupt handler!
I put a simple Netgear, D-Link switch into the trunk. All ethernet packets are switched. Tagged or not. All VLAN's going thru. All Networks between "some" and "another" work.
I'm asking if those switches are VLAN capable or not?
I understand now that you're trying to get the untagged vlan1 to still function along with the trunk. During my test earlier in this thread I said that these settings allow both VLAN's to work between two routers:
Those settings worked fine using my two 100mbit models, but similar settings (adjusted for gigabit numbering VLAN's 1-3) between a gigabit model (wrt320n) and a 100mbit model (wrt300n v1.1) resulted in the tagged VLAN 3 working but the default VLAN 1 not working. ie. it may be a problem specific to the gigabit switches. I hadn't ever heard about the "u" option until now, so I'll play around with it and see if it makes any difference for me. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
That thread talks about how to configure the GUI which doesn't work on gigabit models as I explained at the start of this thread.
I just got done adding examples to the switched ports page for how to configure nvram variables for trunks.
http://www.dd-wrt.com/wiki/index.php/Switched_Ports _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Yes, it is very near. It works because all VLAN's on the uplink ports of the switches are tagged.
It is very common, that there are "grown" networks out there, where later VLAN's where implemented. And mostly there is still a untagged, default VLAN for legacy devices. And I do not understand where the limitations are. Is it broadcom, is it xx-wrt or is it some proprietary driver thing?
Ok, one thing that still narrows the usability is the limitations of VLAN-Tags from 0 to 16 instead of 0 to 4096.
How is this under x86? For example pfSense under pcengines WRAP and ALIX works perfect with trunks AND native VLAN that can be any number between one and 4k.
And therefore I have a quite good knowledge of them.
