On Mon, 2015-11-30 at 09:09 +0100, Guus Sliepen wrote: > > Well but why wouldn't it get the RAs for v4 and not for v6? > There is no RA for IPv4, only DHCP. Argl... that's why I shouldn't write mails so late in the evening.
I meant: why would it get the RAs via ethernet, but not via Wifi :D
> > > And if I have just:
> > > iface wlan0-bar inet6 dhcp|auto
> > > wpa-ssid bar
> > >
> > > wpa-key-mgmt WPA-PSK
> > > wpa-psk foo
> > I even get:
> > # ifup wlan0
> > wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
> > run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with
> > return code 1
> > Failed to bring up wlan0-bar.
>
> Ah, I'll try to reproduce this problem.
Thanks. :)
I also don't yet understand the basic idea of how especially dual
stacked ifaces (and basically most network connections are dual stacked
these days) should be properly described in /e/n/interfaces.
For lo, people typically just use:
iface lo inet loopback
and no second
iface lo inet6 loopback
For others, typically eth/wlan I wonder a bit what's the way of doing
it correctly:
a) like you said
iface wlan0-bar inet dhcp
wpa-ssid bar
wpa-key-mgmt WPA-PSK
wpa-psk foo
iface wlan0-bar inet6 dhcp|auto
=> what if v4 would become disabled there? would it still apply the
wpa-settings to the connection?
b) or doubling everything:
iface wlan0-bar inet dhcp
wpa-ssid bar
wpa-key-mgmt WPA-PSK
wpa-psk foo
iface wlan0-bar inet6 dhcp|auto
wpa-ssid bar
wpa-key-mgmt WPA-PSK
wpa-psk foo
=> which leads to the question, what happens if I do that with scripts:
iface eth0 inet dhcp
post-up vpnc something
pre-down vpnc-disconnect
iface eth0 inet6 dhcp
post-up vpnc something
pre-down vpnc-disconnect
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
