Modify

Opened 6 years ago

Closed 5 years ago

Last modified 4 years ago

#10777 closed defect (too_vague)

kmod-ipv6 breaks functionality in Backfire 10.03.1

Reported by: openwrt@… Owned by: developers
Priority: response-needed Milestone: Barrier Breaker 14.07
Component: packages Version: 10.03.1
Keywords: backfire ipv6 Cc:

Description

Tried adding support for ipv6 in Backfire 10.03.1 on a Linksys WRT350n V2. When installing the kmod-ipv6 package errors start appearing in logread:
The errors that come up are the ones that reads like:
"Jan 12 18:38:47 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan4: link is not ready"

This in return breaks some of the hotplug functionalities.

{{{Jan 12 18:38:45 kil-n001 user.notice ifup: Enabling Router Solicitations on loopback (lo)
Jan 12 18:38:45 kil-n001 user.info kernel: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Jan 12 18:38:47 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan4: link is not ready
Jan 12 18:38:47 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan4: link is not ready
Jan 12 18:38:47 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan4: link is not ready
Jan 12 18:38:47 kil-n001 user.info kernel: lan4: link up, 1000 Mb/s, full duplex, flow control disabled
Jan 12 18:38:47 kil-n001 user.info kernel: ADDRCONF(NETDEV_CHANGE): lan4: link becomes ready
Jan 12 18:38:48 kil-n001 user.notice ifup: Enabling Router Solicitations on servers (lan4)
Jan 12 18:38:50 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan3: link is not ready
Jan 12 18:38:50 kil-n001 user.info firewall: adding servers (lan4) to zone servers
Jan 12 18:38:50 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan3: link is not ready
Jan 12 18:38:50 kil-n001 user.info kernel: lan3: link up, 1000 Mb/s, full duplex, flow control disabled
Jan 12 18:38:50 kil-n001 user.info kernel: ADDRCONF(NETDEV_CHANGE): lan3: link becomes ready
Jan 12 18:38:50 kil-n001 user.info kernel: device lan3 entered promiscuous mode
Jan 12 18:38:50 kil-n001 user.info kernel: device eth0 entered promiscuous mode
Jan 12 18:38:50 kil-n001 user.info kernel: br-clients: port 1(lan3) entering forwarding state
Jan 12 18:38:52 kil-n001 user.info kernel: br-clients: port 1(lan3) entering disabled state
Jan 12 18:38:52 kil-n001 user.info kernel: br-clients: port 1(lan3) entering forwarding state
Jan 12 18:38:53 kil-n001 user.notice ifup: Enabling Router Solicitations on clients (br-clients)
Jan 12 18:38:55 kil-n001 user.notice ifup: Enabling Router Solicitations on clientvpn (tap0)
Jan 12 18:38:56 kil-n001 user.debug kernel: eth0: no IPv6 routers present
Jan 12 18:38:56 kil-n001 user.info firewall: adding clients (br-clients) to zone clients
Jan 12 18:38:59 kil-n001 user.info firewall: adding clientvpn (tap0) to zone clientvpn
Jan 12 18:39:02 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan1: link is not ready
Jan 12 18:39:03 kil-n001 user.info firewall: adding guests (guests) to zone guests
Jan 12 18:39:03 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan1: link is not ready
Jan 12 18:39:03 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan1: link is not ready
Jan 12 18:39:03 kil-n001 user.info kernel: lan1: link up, 1000 Mb/s, full duplex, flow control disabled
Jan 12 18:39:03 kil-n001 user.info kernel: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
Jan 12 18:39:04 kil-n001 user.notice ifup: Enabling Router Solicitations on dmz (lan1)
Jan 12 18:39:06 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan2: link is not ready
Jan 12 18:39:07 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan2: link is not ready
Jan 12 18:39:07 kil-n001 user.info firewall: adding dmz (lan1) to zone dmz
Jan 12 18:39:07 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): lan2: link is not ready
Jan 12 18:39:07 kil-n001 user.info kernel: lan2: link up, 1000 Mb/s, full duplex, flow control disabled
Jan 12 18:39:07 kil-n001 user.info kernel: ADDRCONF(NETDEV_CHANGE): lan2: link becomes ready
Jan 12 18:39:08 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): wan: link is not ready
Jan 12 18:39:08 kil-n001 user.notice ifup: Enabling Router Solicitations on securenet (lan2)
Jan 12 18:39:09 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): wan: link is not ready
Jan 12 18:39:09 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): wan: link is not ready
Jan 12 18:39:09 kil-n001 user.info kernel: wan: link up, 100 Mb/s, full duplex, flow control disabled
Jan 12 18:39:09 kil-n001 user.info kernel: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready
Jan 12 18:39:13 kil-n001 user.info firewall: adding securenet (lan2) to zone securenet
Jan 12 18:39:14 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 12 18:39:14 kil-n001 user.info kernel: device wlan0 entered promiscuous mode
Jan 12 18:39:14 kil-n001 user.info kernel: br-clients: port 2(wlan0) entering forwarding state
Jan 12 18:39:16 kil-n001 user.info kernel: device wlan0-1 entered promiscuous mode
Jan 12 18:39:18 kil-n001 user.notice ifup: Allowing Router Advertisements on wan (wan)
}}}

Attachments (0)

Change History (6)

comment:1 Changed 6 years ago by jow

  • Priority changed from normal to response-needed

Those messages are normal, you get them on a desktop linux as well. Are there any actual problems?

comment:2 Changed 6 years ago by openwrt@…

Yup,
They break the scripts in the 6to4 package in /lib/network. This results in a "Segmentation fault" and the ip address for the WAN-iface will not work.

comment:3 Changed 6 years ago by nbd

Segmentation fault where? And how can kernel messages break the network scripts?

comment:4 Changed 6 years ago by openwrt@…

Hi,
What happens is that the 6to4 package tries to get info about the wan interface using the ip command. And since the wan interface is not ready, this results in a segmentation fault and the script breaks all network functionality.
I suspect that this fault was due to the kmod-ipv6 package. Since all messages like below disappears when i remove the kmod-ipv6 package this was my suspicion. I guess that the script is initiated at the first ADDRCON(NETDEV_UP) but that the interface is not really available, and hence the ip command results in a Segmentation fault and breaks network functionality.
This might be wrong, but this is the connection that I saw.

Jan 12 18:39:09 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): wan: link is not ready
 Jan 12 18:39:09 kil-n001 user.info kernel: ADDRCONF(NETDEV_UP): wan: link is not ready
 Jan 12 18:39:09 kil-n001 user.info kernel: wan: link up, 100 Mb/s, full duplex, flow control disabled
 Jan 12 18:39:09 kil-n001 user.info kernel: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready

Best regards
D

comment:5 Changed 5 years ago by nbd

  • Resolution set to too_vague
  • Status changed from new to closed

no idea what that means, but in my tests 6to4 is working just fine

comment:6 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.