#18106: Assigning interface to physical VLAN-interface causes 100% cpu
------------------------------+-----------------------------------
Reporter: martin.priv@… | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Barrier Breaker 14.07
Component: base system | Version: Barrier Breaker 14.07
Keywords: VLAN, Interface, |
------------------------------+-----------------------------------
{{{
Hardware: DIR-825 B1 with switch RTL8366S.
Switch (eth0):
VLAN 1:ports : 0 1 2 5t
VLAN 2:ports : 3 5t
VLAN 845:ports : 0t 3t 5t
(0 is LAN4, 3 is LAN1, 5 is CPU)
Interfaces:
WAN: eth0.2
LAN: br-lan, including eth0.1
}}}
I use switch port 3 (LAN1) as WAN port, as I have Internet untagged and
IPTV tagged on VLAN 845 on it.
Interface WAN uses eth0.2.
IPTV is passed to port 0 (LAN4) tagged, together with my local LAN
(untagged).
When addning a new interface linked to eth0.845 my syslog fills upp with a
lot of interface up/down and the router becomes unusable:
{{{
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is setting
up now
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now up
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity loss
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is
disabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is enabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is up
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is setting
up now
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now up
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity loss
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is
disabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is enabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is up
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is setting
up now
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now up
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity loss
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is
disabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is enabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is up
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is setting
up now
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now up
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' has link
connectivity loss
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is now
down
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is
disabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: Interface 'test' is enabled
Sun Oct 12 14:11:23 2014 daemon.notice netifd: VLAN 'eth0.845' link is up
}}}
This was fully working in 12.09 and I could monitor traffic for eth0.845
with iftop.
It works OK to create a new interface and assign it to eth1 (original WAN-
port), but assigning a new interface to any physical interface that is
VLAN-tagged result in this problem.
Nothing shows up in the kernel-log.
--
Ticket URL: <https://dev.openwrt.org/ticket/18106>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
