Wifi not consistently connected

[mkozlows]

I'm using the latest release on a Kobo Sage. I'm using Progress Sync, and want for it to always sync, but sometimes the Wifi will be disabled, and will stay disabled, for no obvious reason.

I have the following settings set:

Disable Wi-Fi connection when inactive: Unchecked
Restore Wi-Fi connection on resume: Checked
Action when Wi-Fi is off: turn on
Action when done with Wi-Fi: leave on

But still, and not infrequently, the Wi-Fi is off.

What am I missing?

[bald]

I am just trying to setup progress sync, i was able to register via my kobo device but using the same credentials I am unable to login via Android device using the same credentials... I get "unauthorized" I've tried reinstalling koreader but no joy, anything I'm missing?

[NiLuJe]

@bald: Entirely different issue, please create a separate thread .

@mkozlows: Check the logs, my wild guess would be poor connectivity making the initial connection attempt fail, as there's no retry in these cases.

[bald]

[QUOTE=NiLuJe;4238948]@bald: Entirely different issue, please create a separate thread .

Fairplay... was a little cheeky of me!

[mkozlows]

Originally Posted by NiLuJe

@mkozlows: Check the logs, my wild guess would be poor connectivity making the initial connection attempt fail, as there's no retry in these cases.

When you say "no retry", do you mean "no retry after fail until Wifi is manually connected"? Because that matches what I see: On 7/6, when I went on a trip, I see a "restore-wifi-async.sh: Failed to connect to preferred AP!" message (which makes sense, there was no Wi-Fi enabled on the airplane), and then it never tries to connect on wake-up from there on out:

07/13/22-18:00:57 INFO  Kobo suspend: ZzZ ZzZ ZzZ... And woke up!
07/13/22-18:00:57 INFO  Kobo resume: clean up after wakeup
07/13/22-18:00:57 INFO  Kobo resume: successfully asked the kernel to resume subsystems
07/13/22-18:00:57 INFO  Restoring user input handling
GET https://sync.koreader.rocks:443/syncs/progress/54255d2149fbf92b1341a73db2265c3c
host or service not provided, or not known
PUT https://sync.koreader.rocks:443/syncs/progress
host or service not provided, or not known
07/13/22-18:04:25 INFO  WakeupMgr: scheduling wakeup in 259200
07/13/22-18:04:25 INFO  Inhibiting user input
07/13/22-18:04:41 INFO  Kobo suspend: going to sleep . . .

... until I manually connect the network, and then it automatically reconnects on wake from then on.

This behavior surprises me. Is there a reason it doesn't try on every wake, regardless of prior failures?

[pazos]

Originally Posted by mkozlows

This behavior surprises me. Is there a reason it doesn't try on every wake, regardless of prior failures?

Yes

Restore Wi-Fi connection on resume will only attempt to restore if there was a Wi-Fi connection at suspend time.

The behaviour you describe would be called Turn on wifi connection on resume

[NiLuJe]

That, too .

But I was initially talking about the simple fact that if the connection attempt fails to succeed within 15s, it just gives up .

(That's the "restore-wifi-async.sh: Failed to connect to preferred AP!" error).

[mkozlows]

Originally Posted by pazos

Restore Wi-Fi connection on resume will only attempt to restore if there was a Wi-Fi connection at suspend time.

The behaviour you describe would be called Turn on wifi connection on resume

Fair enough. Is there a way to get that "turn on wifi connection on resume" behavior? Because "try to connect every session, regardless of whether you failed to connect last session" really is what I want.

[mkozlows]

And I guess relatedly, I'm trying to make sense of this series of log entries. I think what I'm seeing is that I turned the device on, it started trying to make a connection. I then turned the device off quickly again, and it canceled the Wifi connection attempt midway through, such that it shows all that failure and error, and the next time I started the device up it didn't attempt to restore the connection. Yes?

(I've tried to trim it to the relevant context, but this section doesn't start with one of those "ZzZ ZzZ ZzZ... And woke up!" logs, so it's possible that there's another wake-up a minute before this that's relevant.)

07/14/22-18:07:08 INFO  WakeupMgr: scheduling wakeup in 259200
07/14/22-18:07:08 INFO  Inhibiting user input
07/14/22-18:07:09 INFO  Kobo resume: clean up after wakeup
07/14/22-18:07:09 INFO  Kobo resume: successfully asked the kernel to resume subsystems
[Thu Jul 14 18:07:09 EDT 2022] restore-wifi-async.sh: Restarting Wi-Fi
07/14/22-18:07:09 INFO  Restoring user input handling
dhcpcd[21266]: sending signal ARLM to pid 21212
dhcpcd[21266]: waiting for pid 21212 to exit
dhcpcd[21293]: dhcpcd not running
07/14/22-18:07:09 INFO  Kobo Wi-Fi: disabling Wi-Fi
dhcpcd[21305]: dhcpcd not running
Selected interface 'wlan0'
OK
ifconfig: SIOCGIFFLAGS: No such device
Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory [EDIT: this line repeats a bunch of times, trimming for space]
[Thu Jul 14 18:07:27 EDT 2022] restore-wifi-async.sh: Failed to connect to preferred AP!
dhcpcd[21537]: dhcpcd not running
Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
ifconfig: SIOCGIFFLAGS: No such device
07/14/22-18:08:01 INFO  Failed to restore Wi-Fi (after 26 iterations)!
dhcpcd[21558]: dhcpcd not running
07/14/22-18:08:01 INFO  Kobo Wi-Fi: disabling Wi-Fi
dhcpcd[21570]: dhcpcd not running
Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
ifconfig: SIOCGIFFLAGS: No such device
PUT https://sync.koreader.rocks:443/syncs/progress
host or service not provided, or not known
07/14/22-18:08:15 INFO  WakeupMgr: scheduling wakeup in 259200
07/14/22-18:08:15 INFO  Inhibiting user input
07/14/22-18:08:31 INFO  Kobo suspend: going to sleep . . .
07/14/22-18:08:31 INFO  Kobo suspend: successfully asked the kernel to put subsystems to sleep
07/14/22-18:08:33 INFO  Kobo suspend: waited for 2s because of reasons...
07/14/22-18:08:33 INFO  Kobo suspend: synced FS
07/14/22-18:08:33 INFO  Kobo suspend: asking for a suspend to RAM . . .

[pazos]

Originally Posted by mkozlows

Fair enough. Is there a way to get that "turn on wifi connection on resume" behavior? Because "try to connect every session, regardless of whether you failed to connect last session" really is what I want.

Nope. But you can setup a gesture to activate wifi and use it once each time you arrive home after one of the travels.

[NiLuJe]

Trimming logs generally ends up ruining any chance of figuring out what actually happened, FWIW .

That's a personal pet peeves of mine: don't trim logs, kthxplz .