2016-09-01 07:05:40 +00:00
|
|
|
#!/bin/sh
|
|
|
|
|
2024-06-18 19:20:14 +00:00
|
|
|
# NOTE: Close any non-standard fds, so that it doesn't come back to bite us in the ass with USBMS (or sockets) later...
|
2020-08-25 00:00:59 +00:00
|
|
|
for fd in /proc/"$$"/fd/*; do
|
2024-06-18 19:20:14 +00:00
|
|
|
close_me="false"
|
2020-08-25 00:00:59 +00:00
|
|
|
fd_id="$(basename "${fd}")"
|
2024-06-18 19:20:14 +00:00
|
|
|
fd_path="$(readlink -f "${fd}")"
|
|
|
|
|
2020-08-25 00:00:59 +00:00
|
|
|
if [ -e "${fd}" ] && [ "${fd_id}" -gt 2 ]; then
|
2024-06-18 19:20:14 +00:00
|
|
|
if [ -S "${fd}" ]; then
|
|
|
|
# Close any and all sockets
|
|
|
|
# NOTE: Old busybox builds do something stupid when attempting to canonicalize pipes/sockets...
|
|
|
|
# (i.e., they'll spit out ${fd} as-is, losing any and all mention of a socket/pipe).
|
|
|
|
fd_path="$(readlink "${fd}")"
|
|
|
|
close_me="true"
|
|
|
|
elif [ -p "${fd}" ]; then
|
|
|
|
# We *might* be catching temporary pipes created by this very test, se we have to leave pipes alone...
|
|
|
|
# Although it would take extremely unlucky timing, as by the time we go through the top-level -e test,
|
|
|
|
# said temporary pipe is already gone, and as such we *should* never really enter this branch for temporary pipes ;).
|
|
|
|
fd_path="$(readlink "${fd}")"
|
|
|
|
close_me="false"
|
|
|
|
else
|
|
|
|
# NOTE: dash (meaning, in turn, busybox's ash) uses fd 10+ open to /dev/tty or $0 (w/ CLOEXEC)
|
|
|
|
# NOTE: The last fd != fd_path check is there to (potentially) whitelist non-regular files we might have failed to handle,
|
|
|
|
# it's designed to match the unhelpful result from old buysbox's readlink -f on non-regular files (c.f., previous notes).
|
|
|
|
if [ "${fd_path}" != "/dev/tty" ] && [ "${fd_path}" != "$(readlink -f "${0}")" ] && [ "${fd}" != "${fd_path}" ]; then
|
|
|
|
close_me="true"
|
|
|
|
else
|
|
|
|
close_me="false"
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
|
|
|
if [ "${fd_id}" -gt 2 ]; then
|
|
|
|
if [ "${close_me}" = "true" ]; then
|
2020-08-25 00:00:59 +00:00
|
|
|
eval "exec ${fd_id}>&-"
|
|
|
|
echo "[obtain-ip.sh] Closed fd ${fd_id} -> ${fd_path}"
|
2024-06-18 19:20:14 +00:00
|
|
|
else
|
|
|
|
# Try to log something more helpful when old busybox's readlink -f mangled it...
|
|
|
|
if [ "${fd}" = "${fd_path}" ]; then
|
|
|
|
fd_path="${fd_path} => $(readlink "${fd}")"
|
|
|
|
if [ ! -e "${fd}" ]; then
|
|
|
|
# Flag (potentially?) temporary items as such
|
|
|
|
fd_path="${fd_path} (temporary?)"
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
echo "[obtain-ip.sh] Left fd ${fd_id} -> ${fd_path} open"
|
2020-08-25 00:00:59 +00:00
|
|
|
fi
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
|
2016-09-24 08:10:45 +00:00
|
|
|
./release-ip.sh
|
|
|
|
|
Various Wi-Fi QoL improvements (#6424)
* Revamped most actions that require an internet connection to a new/fixed backend that allows forwarding the initial action and running it automatically once connected. (i.e., it'll allow you to set "Action when Wi-Fi is off" to "turn_on", and whatch stuff connect and do what you wanted automatically without having to re-click anywhere instead of showing you a Wi-Fi prompt and then not doing anything without any other feedback).
* Speaking of, fixed the "turn_on" beforeWifi action to, well, actually work. It's no longer marked as experimental.
* Consistently use "Wi-Fi" everywhere.
* On Kobo/Cervantes/Sony, implemented a "Kill Wi-Fi connection when inactive" system that will automatically disconnect from Wi-Fi after sustained *network* inactivity (i.e., you can keep reading, it'll eventually turn off on its own). This should be smart and flexible enough not to murder Wi-Fi while you need it, while still not keeping it uselessly on and murdering your battery.
(i.e., enable that + turn Wi-Fi on when off and enjoy never having to bother about Wi-Fi ever again).
* Made sending `NetworkConnected` / `NetworkDisconnected` events consistent (they were only being sent... sometimes, which made relying on 'em somewhat problematic).
* restoreWifiAsync is now only run when really needed (i.e., we no longer stomp on an existing working connection just for the hell of it).
* We no longer attempt to kill a bogus non-existent Wi-Fi connection when going to suspend, we only do it when it's actually needed.
* Every method of enabling Wi-Fi will now properly tear down Wi-Fi on failure, instead of leaving it in an undefined state.
* Fixed an issue in the fancy crash screen on Kobo/reMarkable that could sometime lead to the log excerpt being missing.
* Worked-around a number of sneaky issues related to low-level Wi-Fi/DHCP/DNS handling on Kobo (see the lengthy comments [below](https://github.com/koreader/koreader/pull/6424#issuecomment-663881059) for details). Fix #6421
Incidentally, this should also fix the inconsistencies experienced re: Wi-Fi behavior in Nickel when toggling between KOReader and Nickel (use NM/KFMon, and run a current FW for best results).
* For developers, this involves various cleanups around NetworkMgr and NetworkListener. Documentation is in-line, above the concerned functions.
2020-07-27 01:39:06 +00:00
|
|
|
# NOTE: Prefer dhcpcd over udhcpc if available. That's what Nickel uses,
|
|
|
|
# and udhcpc appears to trip some insanely wonky corner cases on current FW (#6421)
|
|
|
|
if [ -x "/sbin/dhcpcd" ]; then
|
2023-07-16 01:51:57 +00:00
|
|
|
dhcpcd -d -t 30 -w "${INTERFACE}"
|
Various Wi-Fi QoL improvements (#6424)
* Revamped most actions that require an internet connection to a new/fixed backend that allows forwarding the initial action and running it automatically once connected. (i.e., it'll allow you to set "Action when Wi-Fi is off" to "turn_on", and whatch stuff connect and do what you wanted automatically without having to re-click anywhere instead of showing you a Wi-Fi prompt and then not doing anything without any other feedback).
* Speaking of, fixed the "turn_on" beforeWifi action to, well, actually work. It's no longer marked as experimental.
* Consistently use "Wi-Fi" everywhere.
* On Kobo/Cervantes/Sony, implemented a "Kill Wi-Fi connection when inactive" system that will automatically disconnect from Wi-Fi after sustained *network* inactivity (i.e., you can keep reading, it'll eventually turn off on its own). This should be smart and flexible enough not to murder Wi-Fi while you need it, while still not keeping it uselessly on and murdering your battery.
(i.e., enable that + turn Wi-Fi on when off and enjoy never having to bother about Wi-Fi ever again).
* Made sending `NetworkConnected` / `NetworkDisconnected` events consistent (they were only being sent... sometimes, which made relying on 'em somewhat problematic).
* restoreWifiAsync is now only run when really needed (i.e., we no longer stomp on an existing working connection just for the hell of it).
* We no longer attempt to kill a bogus non-existent Wi-Fi connection when going to suspend, we only do it when it's actually needed.
* Every method of enabling Wi-Fi will now properly tear down Wi-Fi on failure, instead of leaving it in an undefined state.
* Fixed an issue in the fancy crash screen on Kobo/reMarkable that could sometime lead to the log excerpt being missing.
* Worked-around a number of sneaky issues related to low-level Wi-Fi/DHCP/DNS handling on Kobo (see the lengthy comments [below](https://github.com/koreader/koreader/pull/6424#issuecomment-663881059) for details). Fix #6421
Incidentally, this should also fix the inconsistencies experienced re: Wi-Fi behavior in Nickel when toggling between KOReader and Nickel (use NM/KFMon, and run a current FW for best results).
* For developers, this involves various cleanups around NetworkMgr and NetworkListener. Documentation is in-line, above the concerned functions.
2020-07-27 01:39:06 +00:00
|
|
|
else
|
2023-07-16 01:51:57 +00:00
|
|
|
udhcpc -S -i "${INTERFACE}" -s /etc/udhcpc.d/default.script -b -q
|
Various Wi-Fi QoL improvements (#6424)
* Revamped most actions that require an internet connection to a new/fixed backend that allows forwarding the initial action and running it automatically once connected. (i.e., it'll allow you to set "Action when Wi-Fi is off" to "turn_on", and whatch stuff connect and do what you wanted automatically without having to re-click anywhere instead of showing you a Wi-Fi prompt and then not doing anything without any other feedback).
* Speaking of, fixed the "turn_on" beforeWifi action to, well, actually work. It's no longer marked as experimental.
* Consistently use "Wi-Fi" everywhere.
* On Kobo/Cervantes/Sony, implemented a "Kill Wi-Fi connection when inactive" system that will automatically disconnect from Wi-Fi after sustained *network* inactivity (i.e., you can keep reading, it'll eventually turn off on its own). This should be smart and flexible enough not to murder Wi-Fi while you need it, while still not keeping it uselessly on and murdering your battery.
(i.e., enable that + turn Wi-Fi on when off and enjoy never having to bother about Wi-Fi ever again).
* Made sending `NetworkConnected` / `NetworkDisconnected` events consistent (they were only being sent... sometimes, which made relying on 'em somewhat problematic).
* restoreWifiAsync is now only run when really needed (i.e., we no longer stomp on an existing working connection just for the hell of it).
* We no longer attempt to kill a bogus non-existent Wi-Fi connection when going to suspend, we only do it when it's actually needed.
* Every method of enabling Wi-Fi will now properly tear down Wi-Fi on failure, instead of leaving it in an undefined state.
* Fixed an issue in the fancy crash screen on Kobo/reMarkable that could sometime lead to the log excerpt being missing.
* Worked-around a number of sneaky issues related to low-level Wi-Fi/DHCP/DNS handling on Kobo (see the lengthy comments [below](https://github.com/koreader/koreader/pull/6424#issuecomment-663881059) for details). Fix #6421
Incidentally, this should also fix the inconsistencies experienced re: Wi-Fi behavior in Nickel when toggling between KOReader and Nickel (use NM/KFMon, and run a current FW for best results).
* For developers, this involves various cleanups around NetworkMgr and NetworkListener. Documentation is in-line, above the concerned functions.
2020-07-27 01:39:06 +00:00
|
|
|
fi
|