Appearance of unnecessary tabs with VLANs in the bandwidth monitor

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Adding any additional bridge (br1 for example).
2. Assigning any VLAN to new bridge (vlan3 to br1 for example).
3. Assigning any port to new bridge (port3 and port4 to br1 for example)
4. Router reboot.

In general problem arise when you change the VLAN/bridge configuration.

What is the expected output? What do you see instead?
Unnecessary tabs with VLANs (all 16 VLANs) appear in the bandwidth monitor 
instead only 3 tabs with VLANs (vlan1, vlan2, vlan3 for example). In addition 
tabs are placed in the wrong order (vlan0, vlan1, vlan10, vlan11, vlan12, …, 
vlan15, vlan2, vlan3…).

What version of the product are you using? On what operating system?
Tomato Firmware v1.28.4493 MIPSR2-Toastman-VLAN-RT K26 USB VPN

Please provide any additional information below.

Original issue reported on code.google.com by epas...@yandex.ru on 22 Dec 2011 at 7:00

GoogleCodeExporter commented 9 years ago

On which particular HW/device/router/model are you getting those errors?
When running 'ifconfig' via shell/terminal, are any of those 'extra' interfaces 
active/up? Do they show with 'ifconfig -a'?

Original comment by augu...@bott.com.br on 24 Dec 2011 at 6:23

Changed state: WaitingForUser

GoogleCodeExporter commented 9 years ago

Router model is Netgear WNR3500L. There is thread on the forum 
(http://tomatousb.org/forum/t-420225/appearance-of-unnecessary-vlan-s-in-the-ban
dwidth-monitor#post-1334052) where e2000 is mentioned with the same issue.

ifconfig and ifconfig -a give the same output:

-------------------------------------------------
...
vlan10     Link encap:Ethernet  HWaddr 00:90:4C:09:00:01   
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
           collisions:0 txqueuelen:0  
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B) 

vlan11     Link encap:Ethernet  HWaddr 00:90:4C:09:00:01   
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
           collisions:0 txqueuelen:0  
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
...
etc. (all 16 VLANs)
-------------------------------------------------

Original comment by epas...@yandex.ru on 30 Dec 2011 at 3:43

GoogleCodeExporter commented 9 years ago

Please provide more details about this issue, such as runtime and NVRAM 
settings, etc... Thanks.

Original comment by augu...@bott.com.br on 5 Jan 2012 at 4:22

Changed state: PendingDetails
Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

What kind of NVRAM settings are needed?

I encountered the same problem in previous versions of Tomato.
I have cleared NVRAM (30-30-30) before and after upgrade to version v1.28.4493 
(or to any other). The issue remained.

The problem can be solved temporarily by hitting the "Save" on the 
"Basic->Network" page, but issue arises again after router reboot.

I compared the output of commands "nvram show" before and after hitting the 
"Save" on the "Basic->Network" page - nothing has changed except WAN IP address 
everywhere where it is required in NVRAM settings (ddnsx0_cache, ppp_get_ip, 
etc...). Comparison was done carefully.

Original comment by epas...@yandex.ru on 5 Jan 2012 at 2:14

GoogleCodeExporter commented 9 years ago

I confirm this issue on a wrt160nv3.
The problem goes away when we restart the network service, but comes back after 
changes in vlan page or a reboot.

Original comment by a...@netvps.ca on 25 Jan 2012 at 8:21

GoogleCodeExporter commented 9 years ago

So it looks like several VLAN interfaces are being created and brought online 
at boot time for some reason - even if just some of them are actually 
configured (relating to WAN and/or some LAN bridge). However, when the 'net' 
service is restarted those 'unused' VLAN/interfaces just go away?

How many network interfaces are up once your device boots? How many are 'up'? 
Any particular interface seems to be 'missing' or looks sorta 'out of place'?

When the 'net' service restarts, what happens with those unexpected/additional 
interfaces? Just taken offline? Vanished/destroyed? Which interfaces you get on 
/proc/net/dev?

It might be helpful if we could take a look at some of your NVRAM settings 
(please do review/sanitize/clean-up any passwords that might be in there before 
posting anything):

nvram show | egrep 'lan|wan|hwname|port|macaddr|ifname' | egrep -v 
'^vpn|^qos|^portforward|^script|^multicast|^sshd|^dr|^http|^telnet'

Thanks!

Original comment by augu...@bott.com.br on 26 Jan 2012 at 2:07

Changed state: WorkInProgress
Added labels: Priority-Medium
Removed labels: Priority-Low

GoogleCodeExporter commented 9 years ago

Yes, this is exactly what happens. Interface are created for some reasons at 
boot time.

I've attached a text file showing what happens after a fresh boot and after a 
'service net restart'

And another showing the requested nvram values.

Original comment by a...@netvps.ca on 3 Feb 2012 at 8:46

Attachments:

[fresh boot.txt](https://storage.googleapis.com/google-code-attachments/tomato-sdhc-vlan/issue-2/comment-7/fresh boot.txt)
nvram.txt

GoogleCodeExporter commented 9 years ago

Except for the fact you seem to have enabled Spanning Tree Protocol on only one 
of your LAN bridges - br1, from your NVRAM dump (lan1_stp=1), everything else 
looks... just fine. Any particular reason for enabling STP on that one? Could 
you please try/check/see what happens when STP is either disabled or enabled on 
all your LAN bridges simultaneously?

Also, it might be interesting checking out which is the current 
membership/status of your LAN bridges at startup, then after network gets 
restarted (try "brctl show").

To be honest, I'm unable to think about any possible/plausible reason and/or 
link between all those things - but then, I got myself thinking... /what if/!? 

So, please let us know how it goes when you get a chance.

Thanks.

Original comment by augu...@bott.com.br on 4 Feb 2012 at 7:36

GoogleCodeExporter commented 9 years ago

I use STP on that particular bridge because it's linked to two juniper switches 
(one as a failback) that are used for my "lan room" and to do network 
experiments.

I've tried disabling STP altogether and nothing changed.

Nothing changes when I do brctl show before and after restarting the network.

bridge name     bridge id               STP enabled     interfaces
br0             8000.00259c2e629b       no              vlan1
                                                        eth1
br1             8000.00259c2e629b       yes             vlan3
                                                        wl0.1
br2             8000.000000000000       no

Original comment by a...@netvps.ca on 9 Feb 2012 at 4:39

GoogleCodeExporter commented 9 years ago

Note:

There is no problem after initial flashing the router and unnecessary tabs and 
their corresponding variables in the NVRAM do not appear after a reboot. The 
problem arises only when the VLAN/bridge configuration changes, and remains 
until the next re-flashing (or reset) the router.

Original comment by epas...@yandex.ru on 14 Feb 2012 at 11:37

GoogleCodeExporter commented 9 years ago

Interesting thing you mentioned: so right after wiping NVRAM (i.e. default 
settings), there's no noticeable problem and the issue only starts to happen 
once VLAN settings change.

Would it be possible to post some sort of 'NVRAM diff' between this 'working' 
and 'broken' config settings?

Thanks!

Original comment by augu...@bott.com.br on 17 Feb 2012 at 10:38

GoogleCodeExporter commented 9 years ago

Working configuration before VLAN/bridge configuration changing:

----------------------------------
nvram show | egrep vlan | egrep 'hwname|ports'

vlan1hwname=et0 
vlan1ports=1 2 3 4 8* 
vlan2hwname=et0 
vlan2ports=0 8 
----------------------------------

Additional empty variables appear after VLAN/bridge configuration changes:
----------------------------------
nvram show | egrep vlan | egrep 'hwname|ports'

vlan0hwname= 
vlan0ports= 
vlan10hwname= 
vlan10ports= 
vlan11hwname= 
vlan11ports= 
vlan12hwname= 
vlan12ports= 
vlan13hwname= 
vlan13ports= 
vlan14hwname= 
vlan14ports= 
vlan15hwname= 
vlan15ports= 
vlan1hwname=et0 
vlan1ports=1 2 3 4 8* 
vlan2hwname=et0 
vlan2ports=0 8 
vlan3hwname= 
vlan3ports= 
vlan4hwname= 
vlan4ports= 
vlan5hwname= 
vlan5ports= 
vlan6hwname= 
vlan6ports= 
vlan7hwname= 
vlan7ports= 
vlan8hwname= 
vlan8ports= 
vlan9hwname= 
vlan9ports=
----------------------------------

These variables remain after hitting the "Save" on the "Basic->Network" page 
and they are still empty, but the problem is temporarily resolved (tabs 
disappear) until the next reboot.

Finally after removal (by the "nvram unset" and "nvram commit" commands) of 
these variables the problem is solved until next VLAN/bridge configuration 
changing.

Original comment by epas...@yandex.ru on 28 Feb 2012 at 12:43

GoogleCodeExporter commented 9 years ago

Teaman, is there any progress in solving the problem?

Original comment by epas...@yandex.ru on 22 Apr 2012 at 5:58

GoogleCodeExporter commented 9 years ago

Unfortunately, no news here (simply can't reproduce/verify this problem). Does 
it still happen on recent builds?

Original comment by augu...@bott.com.br on 15 Jun 2012 at 7:12

Changed state: PendingFeedback
Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

Yes, it still happen on recent Shibby, Toastman builds. I think it is not 
necessary for you to reproduce this problem. All that is needed - to prevent 
the appearance of empty variables (see above) after changing the router 
configuration. IMHO.

Original comment by epas...@yandex.ru on 29 Jun 2012 at 11:42

totalizator / tomato-sdhc-vlan

Appearance of unnecessary tabs with VLANs in the bandwidth monitor #2