On Thu, 2015-03-12 at 09:28 -0500, Dan Williams wrote:
> On Thu, 2015-03-12 at 13:30 +0100, Thomas Haller wrote:
> > On Thu, 2015-03-12 at 07:32 -0400, Pavel Simerda wrote:
> > > - Original Message -
> > >
> > > What about my original suggestion of "onboot" as a separate option
> > > from
, "Pavel Simerda"
> > >
> > > Sent: Thursday, March 12, 2015 11:54:49 AM
> > > Subject: Re: No more IPv4 address after boot up since NM 0.9.10
> > >
> > > On Thu, 2015-03-12 at 10:32 +0100, Harald Dunkel wrote:
> > > > On Wed, 0
On Thu, 2015-03-12 at 07:32 -0400, Pavel Simerda wrote:
> - Original Message -
> > From: "Thomas Haller"
> > To: "Harald Dunkel"
> > Cc: "networkmanager." , "Pavel Simerda"
> >
> > Sent: Thursday, March 12, 2015
- Original Message -
> From: "Thomas Haller"
> To: "Harald Dunkel"
> Cc: "networkmanager." , "Pavel Simerda"
>
> Sent: Thursday, March 12, 2015 11:54:49 AM
> Subject: Re: No more IPv4 address after boot up since NM 0.9.10
&
On Thu, 2015-03-12 at 10:32 +0100, Harald Dunkel wrote:
> On Wed, 04 Mar 2015 18:15:43 +0100
> Frederik Himpe wrote:
>
> >
> > I still think that NM's behaviour not to touch the interface when it's
> > up already is counter-intuitive. If I start up NM with a configuration
> > for eth0, then I _d
On Wed, 04 Mar 2015 18:15:43 +0100
Frederik Himpe wrote:
>
> I still think that NM's behaviour not to touch the interface when it's
> up already is counter-intuitive. If I start up NM with a configuration
> for eth0, then I _do_ want this configuration to be applied, just like
> the distro speci
On ma, 2015-03-02 at 16:04 -0600, Dan Williams wrote:
> > I am not sure whether this is a really satisfying solution though: what
> > if I would want to debug potential kernel errors during boot, then NM
> > will cause your these kind of troubles?
>
> Well, I don't think NM is causing any kind of
On Mon, 2015-03-02 at 22:03 +0100, Frederik Himpe wrote:
> On ma, 2015-03-02 at 14:22 -0600, Dan Williams wrote:
>
> > > I also have netconsole activated via this line in a file
> > > in /etc/modprobe.d:
> > >
> > > options netconsole
> > > netconsole=@192.168.5.205/eth0,@192.168.5.128/2
On ma, 2015-03-02 at 14:22 -0600, Dan Williams wrote:
> > I also have netconsole activated via this line in a file
> > in /etc/modprobe.d:
> >
> > options netconsole
> > netconsole=@192.168.5.205/eth0,@192.168.5.128/24:77:03:f0:16:64
> >
> > Could this be related in some way?
>
> Yes,
On Mon, 2015-03-02 at 20:54 +0100, Frederik Himpe wrote:
> On ma, 2015-03-02 at 20:43 +0100, Thomas Haller wrote:
>
> > The question is, who configures that interface? Don't do that if you
> > don't want it. Maybe some script that ups the interface and enables
> > SLAAC?
>
> I have no idea. Does
On ma, 2015-03-02 at 20:43 +0100, Thomas Haller wrote:
> The question is, who configures that interface? Don't do that if you
> don't want it. Maybe some script that ups the interface and enables
> SLAAC?
I have no idea. Does not the kernel automatically configure the IPv6
using SLAAC without any
On Mon, 2015-03-02 at 20:22 +0100, Frederik Himpe wrote:
> Since Network Manager 0.9.10, up to current version 1.0, I have the
> problem that I don't get an IPv4 address on my Debian Jessie system. I
> only have an IPv6 address which I receive through SLAAC. Network Manager
> appears to create a br
Since Network Manager 0.9.10, up to current version 1.0, I have the
problem that I don't get an IPv4 address on my Debian Jessie system. I
only have an IPv6 address which I receive through SLAAC. Network Manager
appears to create a broken connection "eth0" every time I boot up my
system, and select
13 matches
Mail list logo
