Re: NM Shutting Down



On Mon, 2012-08-20 at 07:59 -0700, CACook quantum-sci com wrote:
> On Monday, 20 August, 2012 07:48:59 you wrote:
> > > Aug 19 10:44:34 hex NetworkManager[17362]: <info> Auto-activating
> > > connection 'Sirius'.
> > > Aug 19 10:44:34 hex NetworkManager[17362]: <info> Activation (wlan0)
> > > starting connection 'Sirius'
> > > Aug 19 10:44:34 hex NetworkManager[17362]: <info> (wlan0): device
> > > state change: disconnected -> prepare (reason 'none') [30 40 0]
> > 
> > This is probably not enough. By the way, do you have IPv6 in your network?
> 
> Not enough of the log?  I wonder what a reason 4 is?  

"disassociated due to inactivity"

That can be any number of reasons, if there's any way to get AP logs,
that would help.  Otherwise it could be a driver problem.  But it's
pretty clear that it's an issue lower than NetworkManager.  To figure
that out, we need detailed supplicant debugging logs.  You can do this
via the instructions here:

https://live.gnome.org/NetworkManager/Debugging

Then we'll get more information about why.

Dan

> 
> Notice I'm using 5.2GHz 'n'.  NM's icon shows only two bars out of four, but no idea whether that's Tx or Rx, and there doesn't seem to be a way to adjust power or sensitivity in NM.
> 
> I have IPV6 absolutely disabled in sysctl.conf.
> 
>  
> > > Yeah, it only allows one cloned MAC address.  I want random MACs
> > > every boot, which I used to have.
> > 
> > On every boot or on every connection start?
> 
> Ideally on every connection start.  That's what I had before NM, when I could use if-pre-up.d.
> 
> 
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> https://mail.gnome.org/mailman/listinfo/networkmanager-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]