[ifupdown] ipv6 refuse vlan interfaces

Bug #905660 reported by Vivien GUEANT
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Package: ifupdown
Version: ifupdown 0.7~alpha5.1ubuntu5
Severity: normal

ifupdown (0.7~beta1) correct this bug :
    * Accept VLAN interface names (Closes: #632902).

The interfaces file: (/etc/network/interfaces)
auto eth0.77
iface eth0.77 inet static
        address 192.168.1.50
        netmask 255.255.255.0
        gateway 192.168.1.1
iface eth0.77 inet6 static
        address 2a01:6e00:1111:1111::2
        netmask 64
        gateway 2a01:6e00:1111:1111::1

=> IPv4 is OK with VLAN77
=> IPv6 not mont with VLAN77 (IPv6 ok without VLAN)

Bug with IPv6 auto : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632902

Revision history for this message
Vivien GUEANT (vivienfr) wrote :

Affect Ubuntu 11.10 (Oneiric Ocelot)

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.2 KiB)

This bug was fixed in the package ifupdown - 0.7~beta2ubuntu1

---------------
ifupdown (0.7~beta2ubuntu1) precise; urgency=low

  * Resynchronise with Debian experimental. Remaining changes
    (LP: #905660, LP: #850566, LP: #611877, LP: #678425):
    - ifupdown.nw: Use 100 as default route metric unless an explicit metric
      parameter is set in /etc/network/interface.
    - Add iniparser3.0b sources (dictionary.c, dictionary.h, iniparser.c,
      iniparser.h), to let ifupdown avoid auto-up/down of interfaces if
      network-manager's ifupdown plugin is in managed=true mode.
    - Add a new query interface, 'ifquery', that can be used by upstart
      hooks to ask for the list of possible interfaces that they might need
      to bring up.
    - debian/ifupdown.network-interface.upstart: Replace the init scripts
      with a per-interface Upstart job.
    - debian/ifupdown.networking.upstart: Add a "networking" job that
      partially replaces the networking init script from netbase.
    - debian/control: Bump build-dependency on debhelper for Upstart-aware
      dh_installinit.
    - debian/rules: Due to debhelper always adding /etc/init.d symlinks, we
      must manually remove /etc/init.d/networking for as long as netbase
      still provides it.
    - Add if-up and if-down scripts to emit Upstart events when interfaces
      come up and go down.
    - debian/ifupdown.network-interface-security.upstart: Ensure apport is
      started before interfaces are brought up by either ifupdown or
      network-manager.
    - debian/postinst: If the loopback interface is missing from the config
      in /etc/network/interfaces, add it on upgrade.
    - debian/ifupdown.preinst: Since files in /etc were not conffiles in
      lucid, and /etc/network/if-up.d/upstart and
      /etc/init/network-interface.conf changed between lucid final and
      maverick, add extra handling to avoid spurious conffile prompts.
    - invoke dhclient3 with '-1', meaning it should exit failure if it does
      not receive a response in 60 seconds. (LP: #838968)
    - contrib/ifstate-check: Use /run/ntework/ifstate instead of
      /etc/network/run/ifstate
    - ifup.8: Update man page to indicate that Ubuntu uses /run
      and that it's always writable as it's a temporary filesystem
  * ifupdown.nw: When calling dhclient3, also use /var/lib/dhcp as
    dhclient3 is now a symlink to dhclient and /var/lib/dhcp3 no longer
    exists. (LP: #900234)
  * Mark ifupdown as Multi-Arch foreign
  * Replace remaining references to /var/run/network by /run/network
    (LP: #885506)

ifupdown (0.7~beta2) experimental; urgency=low

  * Put interfaces down in the reverse order than they were
    brought up (Closes: #477650).
  * Fix postinst issues with loopback interface naming
    (Closes: #572396, #545250).
  * Remove old .dpkg-old symlink (Closes: #639612).
  * Document some details on processing /etc/network/if-*.d directories.
  * Terminate ifup if it's still running when doing ifdown.
  * Finally migrate to /run/network.
  * Use FHS names for wvdial pid files (Closes: #255222).
  * Stop on run-parts failure (Closes: #547587).
  * Execute scripts before interface options on *...

Read more...

Changed in ifupdown (Ubuntu):
status: New → Fix Released
Revision history for this message
Sebastian Unger (sebunger44) wrote :

Is there any chance to get this fixed in oneiric? Pulling 0.7~beta2ubuntu1 from precise also pulls in libc6 2.15 and some other libs.

Revision history for this message
Sebastian Unger (sebunger44) wrote :

Could this be fixed in oneiric as well? I cannot use the precise version in oneiric because it pulls in libc V2.15 which is broken (see https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/932621 )

Revision history for this message
Vivien GUEANT (vivienfr) wrote :

The bug if not fixed in oneiric.
IPv6 not mont with VLAN.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Vivien: As stated above, the bug was fixed in Precise, not in Oneiric.

Whether we backport it to Oneiric will depend on how critical it's and if it can be bundled with other fixes.
I'd at least wait for beta3 to land in Precise before considering more fixes for Oneiric.

Revision history for this message
Sebastian Unger (sebunger44) wrote :

I thought IPv6 not working would be reasonably critical? I know it only happens if you run IPv6 over a VLAN, but I think that is a reasonably common occurrence.

Unfortunately, I can't even work around this by pulling beta2 from precise into oneiric due to the problem with libc (which has been closed as invalid for reasons not entirely clear to me)

Revision history for this message
Robert Sander (gurubert) wrote :

It looks like ifupdown tries to configure the VLAN a second time when it comes across the inet6 definition in /etc/network/interfaces.

This fails as the VLAN interface was already setup in the inet definition of the same interface. It looks like a conceptual error in the interfaces(5) syntax.

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.