Posted: Tue Feb 08, 2011 9:12 Post subject: both bcmrobo.c and switch-robo.c need to be patche?
cron2 wrote:
OK, patching switch-bcmrobo.c works, and I can get my vlans 920+930+940 that way - but it's somewhat ugly (/proc/switch/eth0/vlan is prepopulated with 1024 subdirectories now), and of course I'd need to recomple the run-time environment to make it "compatible".
Posted: Tue Feb 08, 2011 10:19 Post subject: Re: both bcmrobo.c and switch-robo.c need to be patche?
tangsoft wrote:
so, both bcmrobo.c and switch-robo.c need to be patched as you posted above to break the vlan number limit, right?
"Yes and no" :-)
If you only want runtime configuration, on DD-WRT, and have a switch that is controlled by switch-robo.c (which seems to be true for most/all? broadcom gear, but see phuzi0n's comment about non-broadcom), then it is sufficient to only patch switch-robo.c - for the E3000, that's all I need.
If you want the kernel driver to configure the switch properly on boot, based on NVRAM settings, with "high VLANs", then you need to patch bcmrobo.c
Since patching switch-robo.c only requires putting the newly compiled .ko on a jffs or usb filesystem and load that instead of the default module, it's way easier to get started than patching bcmrobo.c, recompiling the whole kernel, rebuilding the image, and wondering why it's not booting...
phuzi0n wrote:
... if the VLAN boardflag is enabled...
what sort of flag is this, and where is it set? Is it a NVRAM setting, or somethign specific to a certain architecture / board?
Posted: Wed Feb 09, 2011 5:22 Post subject: Re: both bcmrobo.c and switch-robo.c need to be patche?
cron2 wrote:
tangsoft wrote:
so, both bcmrobo.c and switch-robo.c need to be patched as you posted above to break the vlan number limit, right?
"Yes and no" :-)
If you only want runtime configuration, on DD-WRT, and have a switch that is controlled by switch-robo.c (which seems to be true for most/all? broadcom gear, but see phuzi0n's comment about non-broadcom), then it is sufficient to only patch switch-robo.c - for the E3000, that's all I need.
If you want the kernel driver to configure the switch properly on boot, based on NVRAM settings, with "high VLANs", then you need to patch bcmrobo.c
Since patching switch-robo.c only requires putting the newly compiled .ko on a jffs or usb filesystem and load that instead of the default module, it's way easier to get started than patching bcmrobo.c, recompiling the whole kernel, rebuilding the image, and wondering why it's not booting...
hi,gert, are you sure you can tag 3 vlans simutaneously over trunk port?
here i can load the revised module: switch-robo,and get 128 vlans propagate under the /proc/switch/eth0/vlan/.
when i try to tag my iptv vlan85 over wan port and get iptv streaming, the internet connection over vlan2 through wan port dropped. Or the reverse.
by the way, my router is wrt160nv3, should be brcm5325e switch chips. and my isp provides iptv/internet access over 1 single uplink through multiple vlans(iptv tagged vlan85, internet no tagged).
So i also need to figure out how to put tagged and untagged traffic together over wan port.
cron2 wrote:
phuzi0n wrote:
... if the VLAN boardflag is enabled...
what sort of flag is this, and where is it set? Is it a NVRAM setting, or somethign specific to a certain architecture / board?
it looks like only for BCM4704, for my WRT160n V3, it is:
nvram get boardflags
0x710
if i set the boardflags like 0x810, the router will be half bricked.
looks like no need to set boardflag for wrt160n v3.
by the way, Gurus there, any clues for put 802.1Q tagged and untagged traffic together through wan port?
it looks like only for BCM4704, for my WRT160n V3, it is:
nvram get boardflags
0x710
if i set the boardflags like 0x810, the router will be half bricked.
looks like no need to set boardflag for wrt160n v3.
Where did you get the idea of adding 0x100 ?
The wiki article clearly says that you should OR 0x100 to your current value, not ADD. _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Wed Feb 09, 2011 8:39 Post subject: Re: both bcmrobo.c and switch-robo.c need to be patche?
tangsoft wrote:
it looks like only for BCM4704, for my WRT160n V3, it is:
nvram get boardflags
0x710
if i set the boardflags like 0x810, the router will be half bricked.
looks like no need to set boardflag for wrt160n v3.
by the way, Gurus there, any clues for put 802.1Q tagged and untagged traffic together through wan port?
You just don't understand binary math and tried to do it without a hexadecimal calculator. Your 0x100 bit was already set as it will be on any model that has VLAN's already enabled. You actually unset 3 bits and set another. _________________ 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: Wed Feb 09, 2011 8:47 Post subject: Re: both bcmrobo.c and switch-robo.c need to be patche?
tangsoft wrote:
hi,gert, are you sure you can tag 3 vlans simutaneously over trunk port?
Yes, I've tried 2 + 920 + 930 + 940 at the same time and it worked. All of them tagged, though.
tangsoft wrote:
here i can load the revised module: switch-robo,and get 128 vlans propagate under the /proc/switch/eth0/vlan/.
when i try to tag my iptv vlan85 over wan port and get iptv streaming, the internet connection over vlan2 through wan port dropped. Or the reverse.
by the way, my router is wrt160nv3, should be brcm5325e switch chips. and my isp provides iptv/internet access over 1 single uplink through multiple vlans(iptv tagged vlan85, internet no tagged).
So i also need to figure out how to put tagged and untagged traffic together over wan port.
There's special letters for "untagged native vlan" in the switch config. You could try:
that should give you "vlan 2 untagged, vlan 85 tagged" on the port 0 (WAN). I think the "*" specifies "if untagged packets come in, they go to this particular VLAN".
What I do to make sure packets are tagged as I want them is to hook up a linux laptop to the port in question and run "tcpdump -n -e" there - "-e" will show ethernet headers and will display "vlan 85" for a tagged packet. Untagged packets won't show "vlan" info.
Posted: Wed Feb 09, 2011 9:30 Post subject: Re: both bcmrobo.c and switch-robo.c need to be patche?
phuzi0n wrote:
tangsoft wrote:
it looks like only for BCM4704, for my WRT160n V3, it is:
nvram get boardflags
0x710
if i set the boardflags like 0x810, the router will be half bricked.
looks like no need to set boardflag for wrt160n v3.
by the way, Gurus there, any clues for put 802.1Q tagged and untagged traffic together through wan port?
You just don't understand binary math and tried to do it without a hexadecimal calculator. Your 0x100 bit was already set as it will be on any model that has VLAN's already enabled. You actually unset 3 bits and set another.
i really made a mess up with the bits...
anyway, thanks Guru.
Posted: Wed Feb 09, 2011 9:53 Post subject: Re: both bcmrobo.c and switch-robo.c need to be patche?
cron2 wrote:
tangsoft wrote:
hi,gert, are you sure you can tag 3 vlans simutaneously over trunk port?
Yes, I've tried 2 + 920 + 930 + 940 at the same time and it worked. All of them tagged, though.
tangsoft wrote:
here i can load the revised module: switch-robo,and get 128 vlans propagate under the /proc/switch/eth0/vlan/.
when i try to tag my iptv vlan85 over wan port and get iptv streaming, the internet connection over vlan2 through wan port dropped. Or the reverse.
by the way, my router is wrt160nv3, should be brcm5325e switch chips. and my isp provides iptv/internet access over 1 single uplink through multiple vlans(iptv tagged vlan85, internet no tagged).
So i also need to figure out how to put tagged and untagged traffic together over wan port.
There's special letters for "untagged native vlan" in the switch config. You could try:
that should give you "vlan 2 untagged, vlan 85 tagged" on the port 0 (WAN). I think the "*" specifies "if untagged packets come in, they go to this particular VLAN".
What I do to make sure packets are tagged as I want them is to hook up a linux laptop to the port in question and run "tcpdump -n -e" there - "-e" will show ethernet headers and will display "vlan 85" for a tagged packet. Untagged packets won't show "vlan" info.
gert
hmm,thanks gert, it may be 5325E behaves in another way? when I did echo "0* 5" >vlans/2/ports, the output of cat vlans/2/ports just like: 0 5t. not like 0* 5t. And the echo "0t 5" >vlans/85/ports will make internet connection through vlan2 dropped.
its very appreciated if you can do a test on E3000.
I do agree the "*" specifies "if untagged packets come in, they go to this particular VLAN", but maybe it does not mean the outgoing packets will be untagged through the * port.
Not sure, i maybe make another mess. I will try to do a tcpdump.