Mailinglist Archive: opensuse-bugs (5295 mails)

< Previous Next >
[Bug 851953] New: Network start insists on assigning addresses to bridge ports, breaking IPv6 on bridges
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 22 Nov 2013 22:52:42 +0000
  • Message-id: <>

Summary: Network start insists on assigning addresses to bridge
ports, breaking IPv6 on bridges
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: jfunk@xxxxxxxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/30.0.1599.66 Safari/537.36 SUSE/30.0.1599.66

I upgraded a pair of 12.3 systems with bridge configurations to 13.1. However,
it seems that IPv6 gets broken on boot because autoconfiguration is occurring
on the bridge ports. For example, say I have a br0 bridge containing eth0 as a
port. I have ifcfg-eth0 set up like this:

ETHTOOL_OPTIONS="-K eth1 rx off tx off"

And I have ifcfg-br0 set up like this:


When networking comes up, I end up with local IPv6 routes on eth0 and br0,
which totally breaks IPv6:

2001:x:x:x::/64 dev eth0 proto kernel metric 256 expires 2591382sec
2001:x:x:x::/64 dev br0 proto kernel metric 256

There is also an automatic IPv6 address on eth0 in the local range, along with
an automatic ipv4 address.

I have to remove the route and address from eth0 in order to get IPv6 working
after boot, which is very annoying as I have to ssh -4 into it and fix it after
every boot.

Reproducible: Always

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups