Hi,
I have two Debian laptops at home: a Dell E7440 running testing/sid and
a Lenovo T400 running stable with LibreBoot, both with Gnome and
NetworkManager.
I think I always had the same issue with the Dell (I had it in 2017 I
think), while Wi-Fi reconnects immediately with the T400. So in
>> Somehow NM is convinced that it should try an Ethernet connection
>> first. You need a way to disabuse it of that notion.
> Not necessarily. My netbook (stretch with NM) normally uses wires, and
> that is the priority. I occasionally use wifi at home, and usually when
> out, and use sleep quite
>> Also, why does it wait 10s before it tries to connect to anything?
> Perhaps because it's got to detect that it's actually lost network
> connection in the first place? When the computer comes back from
> hibernate or suspend a running program probably doesn't know anything's
> happened other
>> Indeed I have a
>>
>> iface eth0 inet dhcp
>>
>> in there. But removing it doesn't seem to make any difference in this
>> respect (even after `systemctl restart NetworkManager`).
> In view of the fact that I haven't seen an "eth0" string for quite a
> while, might it be worth checking
On Wed, 22 Jul 2020 17:23:25 -0600
Charles Curley wrote:
> On Wed, 22 Jul 2020 15:04:44 -0400
> Stefan Monnier wrote:
>
> >
> > IOW, while it takes about 5s to connect to the wifi network, it
> > takes about 20 additional seconds for NM to decide that it should
> > try to connect.
>
>
On Wed, 22 Jul 2020 16:05:04 -0400
Stefan Monnier wrote:
Hello Stefan,
>Are you saying that you suffer from the same problem?
No.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
The deadbeats and the dispossessed, the
On Wed, 2020-07-22 at 22:51 -0400, Stefan Monnier wrote:
> > > Somehow NM is convinced that it should try an Ethernet connection
> > > first. You need a way to disabuse it of that notion.
>
> Why doesn't it start with the last active connection?
> I suspect that for 99% of the users this will be
On Wed 22 Jul 2020 at 22:51:00 (-0400), Stefan Monnier wrote:
> >> Somehow NM is convinced that it should try an Ethernet connection
> >> first. You need a way to disabuse it of that notion.
>
> Why doesn't it start with the last active connection?
> I suspect that for 99% of the users this will
>> Somehow NM is convinced that it should try an Ethernet connection
>> first. You need a way to disabuse it of that notion.
Why doesn't it start with the last active connection?
I suspect that for 99% of the users this will be the most common case.
Also, why does it wait 10s before it tries to
> I have no idea how to fix your problem. I do use NM though, and my wifi
> is already connected in the time I unlock after my laptop has been
> sleeping overnight.
Right, that's what I remember it doing a couple years ago for me as well.
Thanks for confirming!
Stefan
Stefan Monnier writes:
>> You could set up networkmanager so that it ignores the ethernet port.
>> That should save you some time.
>>
>> See;
>> https://developer.gnome.org/NetworkManager/stable/NetworkManager.conf.html
>>
>> In particular the 'keyfile section' and 'ifupdown section', which
On Wed, 22 Jul 2020 17:23:25 -0600
Charles Curley wrote:
> Somehow NM is convinced that it should try an Ethernet connection
> first. You need a way to disabuse it of that notion.
Also check the priorities of your WiFi and Ethernet connections. Mine
are: Ethernet, -999; all WiFi, 0.
Right
On Wed, 22 Jul 2020 15:04:44 -0400
Stefan Monnier wrote:
> When I wake up from suspend, my Debian machines take a "long" time to
> reconnect to the wifi. Looking at the `nm-applet` icon in my XFCE4
> panel, I see:
> - for about 10s the icon is "two computers" (which IIUC represents
> just
> Presumably the logs (daemon.log, syslog) should give details of
> what's going on.
Nothing I can see there seems relevant, no. I just see the messages
about when the connection is done.
> But I'm not clear about how it should determine that it woke up in the
> same place,
It doesn't need to.
On Wed 22 Jul 2020 at 15:04:44 (-0400), Stefan Monnier wrote:
> When I wake up from suspend, my Debian machines take a "long" time to
> reconnect to the wifi. Looking at the `nm-applet` icon in my XFCE4
> panel, I see:
> - for about 10s the icon is "two computers" (which IIUC represents
> just
> You could set up networkmanager so that it ignores the ethernet port.
> That should save you some time.
>
> See;
> https://developer.gnome.org/NetworkManager/stable/NetworkManager.conf.html
>
> In particular the 'keyfile section' and 'ifupdown section', which detail
> methods by which network
>> When I wake up from suspend,
> My current laptop is nice and fast, with an nvme boot drive, so I've
> been doing some investigations into speeding up boot times as well.
Notice the apple-vs-oranges here.
I'm talking about the time to reconnect to wifi after wake-up
from suspend.
Time to boot
On Wed, 22 Jul 2020 15:04:44 -0400
Stefan Monnier wrote:
Hello Stefan,
>Any idea what might be going on and how to make it quicker?
You could set up networkmanager so that it ignores the ethernet port.
That should save you some time.
See;
On 22/07/2020 20:04, Stefan Monnier wrote:
> When I wake up from suspend, my Debian machines take a "long" time to
> reconnect to the wifi. Looking at the `nm-applet` icon in my XFCE4
> panel, I see:
> - for about 10s the icon is "two computers" (which IIUC represents
> just NetworkManager).
>
Stefan Monnier wrote:
> When I wake up from suspend, my Debian machines take a "long" time to
> reconnect to the wifi. Looking at the `nm-applet` icon in my XFCE4
> panel, I see:
> - for about 10s the icon is "two computers" (which IIUC represents
> just NetworkManager).
> - then the icon
20 matches
Mail list logo
