May 18, 2010 6:38 AM

Nope as far as I know this hasn't been fixed upstream and I'll first add a few more features to my image before I can check that.

Yesterday I compiled and tested an optimized version of my firmware which increases read/write performance by 10%.

The next few days I'm going to finish the services part so samba gets restarted if config has been changed via webinterface.

I have already compiled in ntfs-3g support yesterday, but it's not yet automounting.

So I got lots of things to work on:-)

June 7, 2010 5:50 PM

Hi warwagon,

I have identified the problem. The vlan setup page is more of a placebo, there is no code to actually setup vlanports correctly. Some folks over at the dd-wrt forum claim vlan setup is not working for gigabit routers, but this is not true. You can manually set it up if you use nvram set and nvram commit.

According to ticket:

http://svn.dd-wrt.com:8000/dd-wrt/ticket/1365

This feature is not coming shortly. It is not easy to implement since some of the code is not flexible enough to fully enable the setup without breaking other things.

Here is a little explanation on how to set this up manually:

1. logon via telnet, ssh
2. remove port1 (which is in fact port4 on wnr) from vlan1ports:

nvram set vlan1ports='4 3 2 8*'

3. add port 1 to vlan3

nvram set vlan3ports='1'

4. commit changes:

nvram commit

5. Go to Setup->Networking, setup vlan3 "Unbridged" add IP etc.
6. Setup DHCP and use vlan3 as interface, save changes
7. Go to Administration Commands enter:

insmod /lib/modules/2.6.24.111/kernel/drivers/net/switch/switch-core.ko
insmod /lib/modules/2.6.24.111/kernel/drivers/net/switch/switch-robo.ko

Press Save Startup. Now reboot and connect your device to the 4th ethernet port on your wnr3500l. If you want to make sure there is no communication between your vlans you need to add some iptables rules and save them again under commands "Save Firewall"

August 15, 2010 2:45 PM

This shed some light.
Working day for day with VLAN's but dd-wrt has his own rules. Found many tutorials, but there is never described the philosophy behind it. By the way You can found such top informations like that the ports are in reverse order opposite to the configuration. What's that? Even in such descriptions like http://www.dd-wrt.com/wiki/index.php/Default_Configuration_Diagram there is a complete lack of according standards or even OSI-Layers. When I work with VLAN's in terms of 802.1q there is only layer 2. Why should I need a VLAN Interface in L3, when the routing does happen in a FW or a Core?

For the moment I do not even understand, why the unconfigured switch (ports 1-4) do not forward tagged VLAN's like every other L2 devices. No problem I think. Then I make a trunk on incoming and outgoing port (I do not need termination of this VLAN on dd-wrt). Adding 'set nvram vlan3ports="4t 3t 2t 1t"' bricks the router instead of simply adding tagged vlan3.

Are here some networkers who can translate between IEEE/OSI and dd-wrt? ;-)