IPv6 Forwarding node does not autoconf

Bug #1260241 reported by Sargun Dhillon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

If, in /etc/network/interfaces, you configure a network interface to be IPv6 autoconfigured, it sets accept_ra to 1. If, you also enable IPv6 forwarding on your machine, the kernel doesn't actually autoconf if accept_ra is only set to 1, you must set it to 2. The details are outlined here about how the kernel changed behaviour: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/

Ideally, ifupdown would either enable you to manually override accept_ra (and set it to 2), or always set it to 2, as opposed to 1.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ifupdown - 0.7.48.1ubuntu1

---------------
ifupdown (0.7.48.1ubuntu1) utopic; urgency=medium

  [ Stéphane Graber ]
  * Merge from Debian. Remaining changes:
    - Add transition code for moving /etc/init.d/networking from netbase
      to ifupdown.
    - On upgrade from 0.7.5ubuntu4, handle the fact that our unmodified
      conffile may have a mismatch in the dpkg database and manually
      shuffle the file around on upgrade. LP: #1217263.
    - Always call dhclient with -1, Ubuntu carries a patch so that renewal
      won't time out.
    - Allow setting the MTU and HWADDR on manual interfaces. (LP: #1294807)
    - The above change also means that manual interfaces will now be
      brought up and down (ias many users expected until now).
    - Disable link.defn as it's not covering all the cases supported by
      the vlan and bridge hooks and so causes more harm than good at this
      point. (LP: #1295304)
    - Also enable network-interface-container for OpenVZ. (LP: #1294155)
    - Update networking.init to exit 1 on reload when on an upstart system.
    - Pass --force to ifdown in network-interface to silence errors on
      non-existing interfaces. (LP: #1295620)
    - Prevent the ability to stop or restart networking service
      interactively. As that is not supported. Networking job is only stopped
      during shutdown sequence. (LP: #1072518)
  * Dropped NetworkManager.conf support, the NetworkManager
    ifupdown:managed mode was never really supported and this causes quite a
    massive delta on ifupdown's side.
    If you do use that option at the moment, you will need to decide
    between managing the interface with NetworkManager (removing it from
    interfaces) or managing it with ifupdown (removing ifupdown:managed=true
    and the interface from NM).
  * Stopped removing /etc/default/networking. The file still won't be
    used as the upstart jobs don't parse it but there wasn't a good reason
    to carry this as a delta.

  [ Benjamin Drung ]
  * Fix network-interface upstart job to bring up allow-hotplug devices.
    (LP: #1307429)

ifupdown (0.7.48.1) unstable; urgency=low

  * Add --ignore-errors option.
  * Handle errors correctly during interface deconfiguration.

ifupdown (0.7.48) unstable; urgency=low

  * Ignore statuses on down, don't ignore them on up.
      When configuring an interface, it's important for all commands
      to succeed, so if anything fails, interface isn't marked as
      configured. When deconfiguring it, however, we should do our
      best we can to deconfigure it, so if something fails, that's
      not the reason to stop trying.
      Closes: #360806, #547587, #562962, #700811.
  * Disable tests for DAD.
  * Fix hurd static script with IPv6 support (Closes: #737084).
  * Support preferred lifetime setting for tunnels (Closes: #735534).
  * Provide an alternative iproute dependency to make backporting easier.
  * Default to accept_ra=2 for inet6/auto (Closes: #739993, LP: #1260241)
 -- Stephane Graber <email address hidden> Thu, 01 May 2014 19:01:35 -0400

Changed in ifupdown (Ubuntu):
status: New → Fix Released
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.