SOLVED: Avoiding delay in boot connecting to wifi

[Brian MasinickModerator]

Back a couple of hours later, after attending a high intensity Water Aerobics class.
Again, good news: from a USB instance, the Connman/cmst network management combination
continues to work as expected, no loss of WiFi signal while in xlock mode, promptly
resumed when I returned, so I maintain my position regarding this:

If you have a single operating system installed or at least a single Linux system
installed, you will probably have good results with the Connman network management
daemon and the Connman System Tray (cmst).

IF, on the other hand you have only Ethernet, you can save a few MB of actively
running images by using Ceni instead of Connman; it’s GREAT for that scenario.
Ceni is also a reliable way to connect to WiFi services, but I’ve not come up
with an automatic way to maintain it; I tried preconfiguring /etc/network/interfaces
and I still didn’t see it automatically connect (but MAYBE there’s a way to convince
it to read that file and automatically connect to a pre-configured WiFi service.

As far as 100% manually using the wpa_supplicant to configure a service, I’ve not
tried every possibility, but the one or two experiments I tried did not yield me
a reliable solution. Therefore, in the general case I still recommend using
the Connman/cmst solution; only try something else if you can’t get it working.

--
Brian Masinick
Alternate "Search B":
This search page

[stevesr0Member]

UPDATE: After “futzing” with the cost settings did nothing, I commented out the eth0 lines in the /etc/network/interfaces file and the next boot connected to wifi with no delay. I have NOt tried leaving both Ethernet and wifi powered “on” in cmst, yet. For another night.

Thanks.

—————————————————————

Hi all,

Reopening this question, for my “minimalistic” Sid install running sysvinit. I recently added a wifi dongle (the internal card stopped working) and now have a slow boot time when I don’t have Ethernet attached.

I am using connman and am attaching a scan of the details screen.

In the “Status” page, I set Ethernet to off and in Preferences/Interface, I checked Retain State and from Program Control Enable Autostart.

As the attached image shows, connman identifies “Ethernet” as wlan3. Since /etc/network/interfaces doesn’t list wlan3, in accord with abc-nix’s comment in 2023, connman should be working with it wlan3. However, it still tries to first launch an eth0 connection, in spite of my turning Ethernet OFF in cmst (see image).

• This reply was modified 1 year, 7 months ago by stevesr0.
• This reply was modified 1 year, 7 months ago by stevesr0.
• This reply was modified 1 year, 7 months ago by stevesr0.

Attachments:

1. Scanned-Document-2-26-25-at-20.35.06.pdf

[emmaMember]

Hi stevesr0,
had the same boot delay issue with “DHCPDISCOVER on eth0” with my antiX 23.2 installation running sysVinit.
In connman cmst I have both ethernet and wifi powered on.

With help of this thread (thank you) in /etc/network/interfaces I tried commenting out only the following:
#iface eth0 inet dhcp
and the boot delay was gone.

Hope this would not bore you, steves0. I just started with antiX and don’t quite understand everything,
but wanted to share the solution that worked for me on the same issue.

[stevesr0Member]

Hi emma,

Not boring at all! I am a permanent noobie, so welcome from one noobie to another.

The credit for the fix belongs to abc-nix, when I originally raised the issue in 2023.

I don’t understand the relationship of cmst/connman and the /etc/network/interfaces and why, but that is above my paygrade <g>.

Glad that it resolved your issue.

[paulcrrMember]

The solution posted by Emma worked for me on 23.2 Thank you Emma!

[Author]

Posts