Update access-point.md #859
Conversation
This setup tutorial requires RFKILL to be disabled in order to allow hostapd to bring up and control the wlan0 interface. I've added the line following the installation and stop of hostapd and dnsmasq to reflect this.
|
You'd only need to run rfkill manually if you havent' set the wifi country using raspi-config or rc_gui and only on a pi3 b+ or if you've blocked wifi yourself. In the former case, rfkill would block wifi again after restart, unless you've manually set the country in wpa_supplicant.conf. In other words, this step would only be required if you've done something wrong before. If this is merged as is, it would create more confusion when people find that wifi is getting blocked again after they reboot. |
|
Using the latest Raspbian image and going through the tutorial line-by-line, it does not work. I had not done anything "wrong" as you state. If you disable RFKILL it does work. Therefore the tutorial requires an update, either to set the wifi country as you point out, or as I solved it, by disabling RFKILL. |
|
That solution will last you until you reboot. I agree that the documentation should maybe take into account that people would be following the steps without setting the wifi country first. |
|
Happy to accept a PR on this...
…On 19 March 2018 at 15:40, XECDesign ***@***.***> wrote:
That solution will last you until you reboot. I agree that the
documentation should maybe take into account that people would be following
the steps without setting the wifi country first.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#859 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADqrHa5601dhM1JJBWejw-1snup154-4ks5tf9FPgaJpZM4Sv8xE>
.
--
James Hughes
Principal Software Engineer,
Raspberry Pi (Trading) Ltd
|
|
My solution is to disable RFKILL (not just stop it) that does work perpetually after reboot. |
|
Apologies, you're right. I thought you ran |
|
If setting the Wi-Fi country also fixes the issue, would that be the better solution to add in the documentation? |
|
I believe RFKILL remains in control of wifi and bluetooth unless permanently disabled i.e. it isn't as simple as just setting the wifi country as an alternative to disabling RFKILL. |
|
For full context of how it's disabled in the first place: |
|
So that doesn't work as I was able to connect to wifi on first boot, even without the country set. Only after having done that, loading the tutorial in front of an audience of 20, did I go through the tutorial and at the end find that it didn't work as an access point. |
|
This needs to be fixed, there's no clear answer on the forums, everyone is coming up with different "solutions" that doesn't work for the most part. |
|
Understood, it's a matter of finding the time to do it. TBH, I have no idea what needs to change, so I'm in the same boat as everyone else. If anyone DOES know what needs to be fixed, and can update the docs and send in a PR< that would save a load of time. |
|
@XECDesign Do you have any recommendations on what to change and where? Would like to clear this one up with a change to the docs, but not sure exactly what needs to change. |
|
Set the wifi country using the GUI or raspi-config. Some users may also need to run |
|
Sorry about delay in getting back to this. I'm still not sure what is actually required, and to why only some users might need to use |
|
When wifi is first disabled, a file is created in /run to tell raspi-config whether or not the user disabled wifi or if it was disabled automatically. After rebooting, there's no way to know. To stay on the safe side and avoid radiating rf, it doesn't run rfkill unblock. So, if you boot up and set wifi country, it will work. If you boot up, reboot, and then set wifi country, you'll need to unblock wifi as well. Having a requirement not to radiate unless the user intentionally enables that option results in nonsense like this. Instructions should be - if you're on a 3B+, set wifi country and run unblock all. Alternatively, use OP's approach of disabling rfkill alltogether, but add the unblock all command instead of requiring a reboot. |
|
Is this still relevant, given the changes to Raspbian that have been made since this issue was opened, and given the recent big changes to the access-point documentation? |
|
Don't know - I thought I had got rid of all the related PR's. @epoch1970 Any thoughts? |
|
I've never seen this. I only have 3Bs to play with. Last test I ran was w/ Raspbian Full (I always use Lite): fresh SD, boot, wizard, update, reboot (because it asked for it), apply guides. Worked "100%". I didn't try telling the wizard not to update, and reboot anyways. I will try that, but in years using Lite on Pi3B, I don't think I've every had rfkill causing an issue. Again, I only have 3Bs to test with. |
|
Some of the information here is no longer relevant, but rfkill is still used by default on pis with 5ghz wlan. If there's nothing in the latest version of the docs about rfkill, then I'd suggest adding |
There is nothing about rfkill in the latest versions (routed or bridged). Looking at https://www.raspberrypi.org/documentation/configuration/wireless/access-point-routed.md, Do you want me to try? |
|
@epoch1970 If you can supply another PR, we can review it and go from there. Thanks! |
|
In light of #1911 is this PR still relevant? If there is supporting third-party documentation outside of this repo, and there hasn't been much recent progress I'd be inclined to close it? |
|
This should be closed as obsolete. The AP docs have been improved to include topics rfkill and WiFi country long ago. |
Closing as obsolete! |
This setup tutorial requires RFKILL to be disabled in order to allow hostapd to bring up and control the wlan0 interface. I've added the line following the installation and stop of hostapd and dnsmasq to reflect this.