Bug#808719: isc-dhcp-client: does not set a default route for ipv6

[Martin Sillence]

Package: isc-dhcp-client
Version: 4.3.3-5
Severity: important
Tags: ipv6

Dear Maintainer,

* What led up to the situation?
I have recently enabled IPv6 on my Draytek router

* What exactly did you do (or not do) that was effective (or
ineffective)?
Using the network manager gui I connected to the wifi network

* What was the outcome of this action?
It successfully gets both a IPv4 and IPv6 address, IPv4 has a default route,
IPv6 does not.
IPv6 works on my phone but on my debian machines is unable to route, it can
only see the local network

* What outcome did you expect instead?
I expected an IPv6 default route as seems to happen on my android phone.
My routing table has no next hop
If I manually add a default route to my router it works until the dhcp lease is
renewed and the route is removed.


Technical notes from my provider:

/64 Neighbour Discovery (ND) Prefix. This is used to automatically address the
WAN
interface of your Router, or if you are directly connected without a router,
the WAN
interface of that device.

/48 Delegation Prefix. This is usually provided over DHCPv6, and requires that
your
router acts as a requesting router for the purpose of IPv6 delegation RFC3633 -
(https://tools.ietf.org/html/rfc3633). Subnets of this prefix are used by the
CPE to
address devices on the LAN. If prefix delegation is not supported on the
router, a
suggested interface ID and static route is available, which should allow
routing to
take place.


We also have an IPv6 enabled DNS Resolver the IPv6
Address of this will be automatically advertised to supporting routers RFC3646
(https://tools.ietf.org/html/rfc3646). It can also be configured manually if
required.

Routers supporting RFC7084 (https://tools.ietf.org/html/rfc7084) are expected
to
work without issue. Older routers, or ones that do not fully implement RFC7084
may
experience issues.



-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages isc-dhcp-client depends on:
ii debianutils 4.5.1
ii iproute2 4.3.0-1
ii libc6 2.21-4
ii libdns-export100 1:9.9.5.dfsg-12.1
ii libisc-export95 1:9.9.5.dfsg-12.1

Versions of packages isc-dhcp-client recommends:
ii isc-dhcp-common 4.3.3-5

Versions of packages isc-dhcp-client suggests:
ii avahi-autoipd 0.6.32~rc+dfsg-1
pn isc-dhcp-client-ddns <none>
pn resolvconf <none>

-- no debconf information

[Martin]

Please close, turns out that I was getting two ipv6 addresses one served
by my draytek router and the other by a dlink I was using as a wireless
access point, turns out that turning off dhcp on ipv4 on the dlink doesn't
turn off ipv6 nor does it seem possible to turn off.

Anyway there is no issue with the dhcp client.

Sorry about the false alarm.

M