On Wed, 2015-12-02 at 10:36 +0100, Guus Sliepen wrote:
> /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
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
On Tue, 2015-12-01 at 22:28 +0100, Guus Sliepen wrote:
> Ok, finally reproduced it. The problem is that apparently, the Linux
> kernel waits with assigning an IPv6 link-local address until the
> interface sees a "carrier". For wireless interfaces, that means it
> waits
> until it has associated wit
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
> >
On Mon, Nov 30, 2015 at 12:34:40AM +0100, Christoph Anton Mitterer wrote:
> On Sun, 2015-11-29 at 23:21 +0100, Guus Sliepen wrote:
>
> > This is not a bug in ifupdown. In both cases, you have instructed
> > ifupdown to start only a DHCPv4 client. It could be that, in the
> > first case, the kerne
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 ro
6 matches
Mail list logo
