This repository was archived by the owner on Sep 30, 2021. It is now read-only.
Clarify options, and make backups when installing create_ap.conf file#434
Open
dlenski wants to merge 46 commits into
Open
Clarify options, and make backups when installing create_ap.conf file#434dlenski wants to merge 46 commits into
dlenski wants to merge 46 commits into
Conversation
…plain default non-bridged network in a little more detail
May help with battery life, throughput, and signal retention depending on network environment
Uses the /lib/systemd/system-sleep mechanism. See https://www.freedesktop.org/software/systemd/man/systemd-suspend.service.html for how this works. For unclear reasons, this only works in /lib/systemd/system-sleep, not in /usr/lib/systemd/system-sleep. (ping oblique#153, oblique#167)
dlenski
force-pushed
the
master
branch
2 times, most recently
from
2af7132 to
b14e6a1
Compare
…ate_ap.conf comments Also makes it *possible* to set ADDN_HOSTS via create_ap.conf
Use 'sudo create_ap --wps-pbc <id>' to simulate the button being pushed, or 'sudo create_ap --wps-pin <id>,<pin>' to enroll a specific PIN requested by a device.
I added WPS push-button and PIN modes in 86a3d60, but now they don't work for me. Apparently: 1. hostapd's built in EAP server *must* be enabled in order for WPS to complete. (Did this ever actually work for me previously, without this??) 2. Also, the 'push_button' method seems to have been replaced with 'virtual_push_button', per the following warning message from hostapd (v2.9): ``` WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance ```
These were needed because of an annoying bug in old versions of
'hostapd', where the kernel's entropy pool was used incorrectly, and 'hostapd'
would decide that there wasn't enough randomness available, e.g.:
random: Only 9/20 bytes of strong random data available from /dev/random
random: Not enough entropy pool available for secure operations
WPA: Not enough entropy in random pool for secure operations - update keys later when the first station connects
That issue has been fixed since hostapd v2.6, released in 2016
(https://packetstormsecurity.com/files/156573/Hostapd-Insufficient-Entropy.html),
so there's really no reason for 'create_ap' to have an entropy-checking
watchdog or to encourage users to install 'haveged'.
…tem-sleep For unclear reasons, this only worked for me on Ubuntu 16.04 if it was put in `/lib/systemd/system-sleep`, and NOT in `/usr/lib/systemd/system-sleep`. I'm unsure if this was a systemd bug, a distro bug, or what… but it's probably no longer applicable on modern distros. Fix it, and leave behind a warning comment. Thanks to @exuvo for bringing this up in #1.
This feature is specified in 802.11v-2011 7.3.2.87. The timezone is supposed to be specified via beacon tag 98 (0x62) as a string in "POSIX format" (https://developer.ibm.com/articles/au-aix-posix/#understanding-the-posix-format3). Happily, the POSIX format timezone is easily extracted from the tzfile format (https://stackoverflow.com/a/67045287), and /etc/localtime is a symlink to such a file. I'm not sure what OSes, if any, will detect these tags and use them to set timezone. Most likely it would only be used as a fallback from some "location-based" timezone determination algorithm. - Android 5.x source alludes to knowledge of this 802.11 feature in `DateTimeSettings.java`: https://android.googlesource.com/platform/packages/apps/Settings/+/android-5.0.1_r1/src/com/android/settings/DateTimeSettings.java#113 - … but more recent versions of Android don't appear to mention it at all: https://android.googlesource.com/platform/packages/apps/Settings/+/main/src/com/android/settings/datetime/DateTimeSettings.java FIXME: The capability of advertising local timezoney was added to hostapd in https://chromium.googlesource.com/external/w1.fi/cgit/hostap/+/39b97072b2a45551e6f20e6251eeaca269f22a2d%5E%21/#F1 with the 'time_zone' variable, but appears to be broken in hostapd v2.9.
The format is defined in this French legislative document specifying how UAVs/drones should broadcast their GPS position and heading via vendor elemnts in WiFi beacons: https://www.legifrance.gouv.fr/eli/arrete/2019/12/27/ECOI1934044A/jo/texte Wireshark dissector shows how the sub-fields are decoded: https://gitlab.com/wireshark/wireshark/commit/7ed3180 There are other fields such as "takeoff" coordinates, takeoff-relative altitude, heading, and aircraft serial numbers; these seem pointless for a non-aircraft application.
While WPA3 is "mostly" a pure-software feature, it requires 802.11w (protected management frames) which require hardware support. Detect adapters that don't support this and prevent them from attempting WPA3.
The /run directory is writable only by root, so we should be able to use the
directory `/run/create_ap.${VWIFI_IFACE}.conf/` in all cases.
Instead of relying on a "static" `create_ap.resume` script (added in 8bb9068), just create one on-the-fly. If the AP isn't working after resume-from-suspend, it will disable and re-enable it via `hostapd_cli`. (ping #1, oblique#153, oblique#167)
It doesn't make any sense to use both.
Obviously, WEP (https://en.wikipedia.org/wiki/Wired_Equivalent_Privacy) is thoroughly insecure and has been crackable for decades, but it can be useful for research or testing purposes.
[ Cherry picked from lakinduakash/linux-wifi-hotspot@50cf12c ] Since iw 6.7, which adds 802.11ah support, iw may print fractional frequencies (e.g. 917.4 MHz). The change in the formatting code can also affect frequencies in the 2.4 and 5 GHz bands, so a frequency that used to be shown as "2412 MHz" may now be shown as "2412.0 MHz". This breaks the parsing logic in `can_transmit_to_channel`, `ieee80211_frequency_to_channel` and `is_5ghz_frequency`. The problem in `can_transmit_to_channel` causes an error when creating an AP, due the frequency not being detected as supported ("ERROR: Your adapter can not transmit to channel 1, frequency band 2.4GHz."). Fix this by changing the parsing logic to accept a trailing ".0" (or even ".00", etc.) suffix for the existing 2.4 and 5 GHz bands. See also: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/commit/?id=f2d9f5b52677f5414dc194be94b5916d2b080eab https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/commit/?id=e2224c729840cc33c6ea89ba5e91b69f79c88e85 https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/commit/?id=1bc6ab0abbb6f26f35d826d166d06bc28ae47b6b
Setting this to zero should disable it.
No need to spam log files with this
I should have done this back in 4664f05 ("Remove the 'haveged' options and entropy watchdog")
It's old and incomplete, and only needed as a workaround for old and buggy hardware drivers that don't support iw/nl80211.
Both brcmfmac and old Realtek drivers only support very old hardware: I don't have any to test it with. Instead of attempting various heroic workarounds for them, just warn about them.
[ Cherry picked from lakinduakash/linux-wifi-hotspot@bae89da ]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
create_ap.confwhen installing a newer version