View Single Post
Old 10-18-2022, 11:08 AM   #16
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
You could simply check if wpa_supplicant managed to associate with an AP via wpa_cli, that should work just as well, will only block as long as necessary, and doesn't require actual WAN connectivity.

c.f., https://github.com/koreader/koreader...sync.sh#L8-L20

Or, in a similar fashion, poke sysfs until the network IF is up:

c.f., https://github.com/koreader/koreader...ce.lua#L15-L27

(Except don't hardcode the IF name, use the ${INTERFACE} env var).
NiLuJe is offline   Reply With Quote