ifup bridge devices does not work with inet6

Bug #1021398 reported by Jay R. Wren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

using a bridge device configured like this:

auto br0
iface br0 inet6 auto
iface br0 inet static
        address 10.8.10.192
        netmask 255.255.254.0
        gateway 10.8.10.1
        dns-nameservers 10.1.1.11 10.1.0.11
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0

auto eth0
iface eth0 inet manual

yields an error when bringing up with ifup

error: "net.ipv6.conf.br0.accept_ra" is an unknown key
Failed to bring up br0.

commenting the inet6 line solves the problem.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ifupdown 0.7~beta2ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Thu Jul 5 13:22:48 2012
ProcEnviron:
 TERM=screen
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ifupdown
UpgradeStatus: Upgraded to precise on 2012-04-09 (87 days ago)

Revision history for this message
Jay R. Wren (evarlast) wrote :
Revision history for this message
Stéphane Graber (stgraber) wrote :

ifupdown works sequentially, so in this case you're asking it to configure an ipv6 address on an interface you haven't defined yet.

Move the "iface br0 inet6 auto" after the "iface br0 inet static" section, that should fix it.

Also, I don't think you actually need that line at all as the kernel's default behaviour is to accept router advertisement.

Marking the bug invalid as that syntax is indeed invalid. Fell free to move it back to new if the bug still happens after fixing the ordering.

Changed in ifupdown (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.