Package: ifupdown Version: 0.7.54 Severity: important
Hi. Since NM is more or less forced upon people I usually us that for daily network configuration... so I don't know when the following problem started. When I configure a iface like this: > iface eth0 inet dhcp then I get (from the same router) both, v4 and v6 addresses. However, when having something similar for a wlan: >iface wlan0-bar inet dhcp > wpa-ssid bar > > wpa-key-mgmt WPA-PSK > wpa-psk foo I only get v4 addresses. It works with NM, so I don't think it's a misconfiguration of the router or dhclient.conf. Now there is obviously the address family inet6 in /e/n/interfaces. I never understood how that is actually used/needed for. E.g. as above with eth0, inet already configures v6. How would one configure e.g. a wlan to also have inet6... does one really have to duplicate all the wpa-* stanzas for both inet and inet6? Or, is in the case of dhcp, inet vs. inet6 rather the family over which DHCP is tried (i.e. DHCPv4 vs. DHCPv6) and not the addresses that are configured in the end? Cheers, Chris. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59.2 ii iproute2 4.3.0-1 ii libc6 2.19-22 ii lsb-base 9.20150917 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.3-5 Versions of packages ifupdown suggests: ii ppp 2.4.6-3.1 pn rdnssd <none> -- debconf information: ifupdown/convert-interfaces: true
