Package: ifupdown
Version: 0.7.48.1
Severity: important
Tags: ipv6

Dear Maintainer,

An upgrade in the last few days has broken my dual IPv4/IPv6 configuration.
I have v0.7.48.1 of ifupdown as a result of the upgrade.

/etc/network/interfaces looks like this:

==QUOTE==
auto eth0
iface eth0 inet static
        address 192.168.1.1
        netmask 255.255.255.0
        gateway 192.168.1.254
        dns-nameservers 0.0.0.0
        dns-search adsb.org.uk

iface eth0 inet6 static
        address 2001:8b0:9d7:6b00::1/64
        gateway 2001:8b0:9d7:6b00:9e97:26ff:fe77:4cfa
==UNQUOTE==

Prior to the upgrade, this resulted in the networking being configured
as expected.

After the upgrade, the IPv6 static config is ignored - instead I get
a temporary IPv6 address assigned by DHCP6 from my router, which isn't
the same as the static address everything else expects.

If I reverse the order of the IPv4 and IPv6 stanzas, then I get the
right IPv6 config but no IPv4 networking is configured AT ALL.

I suspect that only the first stanza is being processed, and the second
stanza is silently ignored.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ifupdown depends on:
ii  adduser      3.113+nmu3
ii  initscripts  2.88dsf-53
ii  iproute      1:3.14.0-1
ii  iproute2     3.14.0-1
ii  libc6        2.18-5
ii  lsb-base     4.1+Debian12

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.2.4-7

Versions of packages ifupdown suggests:
ii  net-tools  1.60-25
ii  ppp        2.4.6-2
pn  rdnssd     <none>

-- no debconf information

-- 
Andrew Benham     Southgate, London N14, United Kingdom

The gates in my computer are AND OR and NOT, not "Bill"


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to