Posted: Mon Feb 21, 2011 21:58 Post subject: Re: give up 5325E, and get 802.1q successed on 53115 switch
Sleipnir wrote:
FW: dd-wrt.v24-14929_NEWD-2_K2.6_big.bin
On builds older than 15508 you need to run this first:
insmod switch-core _________________ 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)
Posted: Tue Feb 22, 2011 11:33 Post subject: Re: cleaned up patch
cron2 wrote:
Hi,
a cleaned-up patch that doesn't print so much debug info but still works is attached. Functionally, it's the same changes (but with the arl_entry[] stuff fixed).
I've also tested vlan ID 4022 now (random VID >1024), and that also works (pinging from router, and adding vlan4022 to bridge groups).
I just tried it on my wrt300n v1.1 with a BCM5325E switch and it seems to work alright as long as I don't exceed the 16 VLAN limit. I didn't test too thoroughly though so there could still be problems. When I exceeded the 16 VLAN limit nothing happened right away and cat'ing the /proc/switch entries showed the port configs all being there, but a few minutes later after doing some stuff with vconfig all the port configs were wiped, the switch was unresponsive, but I still had access through wireless which is how you should connect when playing with VLAN's.
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=540247#540247 _________________ 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)
Posted: Thu Feb 24, 2011 6:45 Post subject: good news!
phuzi0n wrote:
I just tried it on my wrt300n v1.1 with a BCM5325E switch and it seems to work alright as long as I don't exceed the 16 VLAN limit. I didn't test too thoroughly though so there could still be problems. When I exceeded the 16 VLAN limit nothing happened right away and cat'ing the /proc/switch entries showed the port configs all being there, but a few minutes later after doing some stuff with vconfig all the port configs were wiped, the switch was unresponsive, but I still had access through wireless which is how you should connect when playing with VLAN's.
Posted: Fri Feb 25, 2011 1:13 Post subject: Re: good news!
tangsoft wrote:
so there is no need to create vlan by vconfig?
There was, I just forgot to put it in the example. _________________ 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've been trying to get this patch to work and I'm running into a problem.
I have an e2000 running dd-wrt.v24-15508_NEWD-2_K2.6_std_usb_nas-e2k-e3k.bin. I think this has the same switch as the e3000 so it should be the same process right?
So I was able to run these commands:
rmmod switch-robo
insmod /jffs/switch-robo.ko
I did an ls on /proc/switch/eth0/vlan and it showed all the extra vlans so I think the patch worked. The problem comes in when I try to echo my configs to the ports file in the vlans.
For example I did:
echo "2t 8" > /proc/switch/eth0/vlan/40/ports
No error was thrown and it looked like it worked. I did a cat /proc/switch/eth0/vlan/40/ports to double check that the config worked, but the file was empty. I even tried to edit the 40/ports file with vi. I was able to add the config lines, write the file and close it with no errors, but then as soon as I looked in it it was blank again!
Does anyone have any idea why I can't write to the ports files and have it stay?
I did a cat /proc/switch/eth0/vlan/40/ports to double check that the config worked, but the file was empty.
I see the same thing - reading the "ports" file always results in "empty" output. It does this for me for the stock driver and vlan 1..15 as well, so it's an independent problem.
The VLAN should still work, though, even if you can't see it in the config.
Reading the ports files has never worked for gigabit models, you can only write to them. On 100mbps models you can read them though. _________________ 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)
The VLAN should still work, though, even if you can't see it in the config.
I got it working! I just wanted one of the ports to tag vlan40 and it's now working. Here are the commands I used and added to a startup script in /jffs/etc/config:
For anyone with an e2000, here are how the ports are numbered (stumped me for a minute):
WAN = 0
Port 4 = 1
Port 3 = 2
Port 2 = 3
Port 1 = 4
So in my example I set port 4 to be tagged with vlan 40.
Thank you so much to cron2 for this patch and to phuzi0n for all your good comments and insights. This will be great when it's incorporated into the builds.
Since I just start playing with vlan, I'm quite new here, so got quite a numbers of stuffs still unsure.
First, by using this method to set vlan in realtime, it does not reflect on the nvram parameters right?
Let say I use:
nvram show | grep vlan.*ports
nvram show | grep port.*vlans
nvram show | grep vlan.*hwname
It does not reflect the configuration you made to vlan this way right?
Next, If i use command such as:
echo "0t 4t" > /proc/switch/eth0/vlan/20/ports
echo "0t 4t" > /proc/switch/eth0/vlan/30/ports
By not adding the port 5 or 8, wan port and port 4 would act as data forwarder without any routing just like a ordinary switch right? What other thing I need to set for wan & port4 to behave like a switch?
You're not changing any nvram variables by echoing to /proc/switch, only the running configuration of the switch is changed.
I don't know if you can leave the CPU interface (5 or 8) out of the VLAN or not so just try it and find out. If you have to use it then it's okay, you can just not assign any IP address to the VLAN interface to prevent anything from being routed to it. _________________ 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)