On Wed, Dec 02, 2015 at 03:58:19AM +0100, Christoph Anton Mitterer wrote: > > DHCPv6 requires a link-local address. Unfortunately, the ISC DHCP > > client immediately bails out if the interface doesn't have a > > link-local address. It would have been nice if it would just go to > > the background and wait until one appears. I'll work around it by > > having ifup wait for a link-local address right before starting the > > DHCP client. > > Did you report that upstream (i.e. that it doesn't bail out)?
Not yet, there might be some other solution I've overlooked.
> /u/s/d/ifupdown/examples/network-interfaces.gz seems to be rather
> limited and perhaps in some places even outdated, for example it says:
> - "The loopback interface isn't really required any longer"
> That shouls perhaps rather be something like "it doesn't need to be set
> up by ifupdown anymore [as it's already set up by xyz]".
Yes, it could use a makeover.
> > In general, if you run "ifup foo", it will act as if it runs all
> > "iface foo" stanzas in /etc/network/interfaces in sequence. So if
> > will first try to bring up your inet stanza, which in turn will
> > configure wpa-supplicant. Then it brings up the inet6 stanza, but
> > you don't need to repeat the wpa-* options.
>
> Ah.... good to know... so it does some kind of "merging".
> I think that should be more clearly explained like you did it just here
> in the manpage... AFAICS, there is no section which really describes
> that thoroughly.
Yes.
> And perhaps additionally in the example interfaces file using one as I
> did with wifi + v4/v6 + wpa-*.
> Maybe even one with eth, like:
> iface eth0 inet dhcp
> iface eth0 inet6 dhcp
> iface eth0 inet manual
> up vpnc foo
>
> And tell people:
> First it will bring v4 and v6 DHCP up... afterwards it will do the
> vpnc.
Well, there is only so much you can do with examples. You would like to
see that example because it matches your needs, but everyone has
different requirements. Too many examples or very complex examples also
won't help. But I'll try to remove some outdated stuff and ensure the
more common situations have a proper example.
> And perhaps it would be cleaner (in terms of config file language) to
> have a pseudo family for shared options so that one can e.g. specify
> something like that:
>
> iface wlan0-bar all
> wpa-ssid bar
> wpa-key-mgmt WPA-PSK
> wpa-psk foo
>
> iface wlan0-bar inet dhcp
> iface wlan0-bar inet6 dhcp
If anything, I'd rather have ifupdown automatically detect the address
type from the address option, and allow multiple ones, so you could do:
iface wlan0-bar
wpa-ssid bar
wpa-psk foo
address 1.2.3.4/24
gateway 1.2.3.1
address 2000::1234/24
gateway 2000::1
...
And maybe have dhcp and dhcp6 as options below the iface line. But
that's all cosmetic, and people don't like needless changes, so this
would be low priority.
Thanks for all your comments by the way, it's always good to hear what
other people think :) I'll try to address them in future versions.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
