Timeline for Raspberry Pi 3 wireless access point from Enterprise Network ethernet not working (hostapd)
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2019 at 7:30 | vote | accept | myraspberrypiscripts | ||
| Apr 8, 2019 at 7:29 | vote | accept | myraspberrypiscripts | ||
| Apr 8, 2019 at 7:30 | |||||
| Apr 8, 2019 at 7:22 | comment | added | myraspberrypiscripts | However I was using this frequency earlier with all other settings as is in the currently working RasPi and it was not working (same authentication issue). And I was definitely rebooting after every change in the wpa_supplicant-wlan0.conf file. So I'm honestly unsure what the issue was and what caused it to fix after the 2 days, but nonetheless it is now fully working with the "with NAT (recommended)" configuration from your tutorial. Thanks! | |
| Apr 8, 2019 at 7:19 | comment | added | myraspberrypiscripts |
Interesting (and final!) update: So I haven't worked on this in about 2 days but I plugged my pi back in today and spun it up (with the previous settings I was testing, which was exactly your configuration but with key_mgmt=WPA-EAP and frequency=2437. And RasPi network appeared and my devices could successfully connect to it! I then reverted the key_mgmt to the previous WPA-PSK and used my own password, and everything still continued to work. The only significant difference is that I am now using frequency 2437.
|
|
| Apr 6, 2019 at 12:16 | comment | added | Ingo |
@myraspberrypiscripts If you set key_mgmt=WPA-EAP then you need pre shared key files for authentication. This is not used for the access point. It is set to key_mgmt=WPA-PSK, that means only simple password authentication.
|
|
| Apr 6, 2019 at 11:08 | comment | added | myraspberrypiscripts |
None of the alternative frequencies or encryption protocols worked. I'm testing with default password right now ("password"), at least until I can verify that it works. An interesting update (hopefully this will help): When I set key_mgmt=WPA-EAP in the wpa_supplicant-wlan0.conf file and reboot, in the journalctl log I see 3 lines: wpa_supplicant[362]: wlan0: AP-STA-CONNECTED XXX, wpa_supplicant[362]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0, and wpa_supplicant[362]: wlan0: AP-STA-DISCONNECTED XXX where XXX is my phone's MAC Address. So perhaps it's not authentication?
|
|
| Apr 5, 2019 at 11:38 | comment | added | Ingo |
@myraspberrypiscripts You can also try to explicitly define encryption protocol RSN(WPA2) or older WPA. In wpa_supplicant-wlan0.conf change line proto=RSN WPA to proto=RSN or proto=WPA.
|
|
| Apr 5, 2019 at 9:35 | comment | added | Ingo | @myraspberrypiscripts Weird... There must be any difference between yours and mine setup. What could it be? Try to use a simple password, at least 8 chars and only chars and numbers without space, between double quotes. Try another frequency, one of 2412 (channel 1), 2437 (channel 6), 2462 ( channel 11), en.wikipedia.org/wiki/List_of_WLAN_channels#2.4_GHz_(802.11b/g/…. You may try to run wpa_supplicant in debug mode. | |
| Apr 5, 2019 at 8:44 | comment | added | myraspberrypiscripts |
After starting with a freshly updated Raspbian, I followed General Setup and then the Setting up an access point and with eth0, with NAT (recommended) section. After rebooting the SSID is being broadcast but I still have an authentication error, regardless of attempting to connect from my laptop or phone. In journalctl --boot --follow, I get the message raspberrypi wpa_supplicant[356]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 after every failed connection.
|
|
| Apr 4, 2019 at 23:41 | comment | added | Ingo | @myraspberrypiscripts I have checked the setup as described for you and it works. I can connect to the access point. To be clearer I have split the routing section in the tutorial into two sections with NAT and routing. You can follow now section Setting up an access point and with eth0, with NAT (recommended) in Setting up a Raspberry Pi as an access point - the easy way. | |
| Apr 4, 2019 at 9:51 | comment | added | Ingo | @myraspberrypiscripts I will look at it but I'm a bit busy today. You are right, the authentication has nothing to do with the enterprise network. You may have a look at the Troubleshooting section of the tutorial and maybe use the debug option? If you like you can check setup step by step and tell me what Checkpoint fails. | |
| Apr 4, 2019 at 9:09 | comment | added | myraspberrypiscripts | So it looks like regardless of whether I use a bridge or routing, and regardless of whether I use the NAT solution or not, the problem I consistently have is authentication with the broadcasted network from the pi. | |
| Apr 3, 2019 at 23:41 | comment | added | myraspberrypiscripts | Ok so I followed the routing tutorial, including replacing the DNS win 08-wlan0.network with the DNS used in my enterprise network. However, when the SSID is broadcast and I attempt to connect to it with my phone, I get an Authentication Error, even though I am copying and pasting the password and have triple checked that it is the correct one as the one I put in wpa_supplicant-wlan0.conf. I have tried it both with iptables and without, but I have the same issue regardless | |
| Apr 3, 2019 at 13:22 | comment | added | Ingo | @myraspberrypiscripts As I see you should better use routing. It is safer for your enterprise ;-) And you can fake it with NAT that all traffic is only coming from the RasPi. I have updated the answer with modifications for you to use routing. | |
| Apr 3, 2019 at 13:20 | history | edited | Ingo | CC BY-SA 4.0 |
Added info to use routing.
|
| Apr 3, 2019 at 12:49 | comment | added | Ingo | @myraspberrypiscripts Please don't use dnsmasq on your RasPi! You should immediately shut it down. Now you have two DHCP server running on the enterprise network and this is out of specification and may violate the enterprise network by assigning ip addresses. Your network manager will not like it. Btw. there is an easier way to enable a DHCP server with systemd-networkd. | |
| Apr 3, 2019 at 12:41 | comment | added | myraspberrypiscripts | I'm fairly certain there is a DHCP server running on the network. When I run ipconfig /all on my laptop I can see the address of the DHCP server. However when my phone connects to the raspberry pi bridge (without the dnsmasq DHCP server on it), it still fails to obtain an IP Address. The same phone successfully obtains one by directly connecting to the network. | |
| Apr 3, 2019 at 12:27 | comment | added | Ingo | @myraspberrypiscripts As already said: responsible for assigning ip addresses is a DHCP server running on the enterprise network. Is there one running? How does phones connecting to the access point of the enterprise get their ip address? Have you tried it with your phone? | |
| Apr 3, 2019 at 12:20 | comment | added | myraspberrypiscripts | I'm thinking maybe this is due to restrictions set by the network admin, since I had to register the MAC Address of the raspberry pi for the wired Ethernet connection to even work. I would like to avoid using static IP Addresses but need to get this bridge working. Thanks. | |
| Apr 3, 2019 at 12:16 | comment | added | myraspberrypiscripts | Thanks for the link. I started with a freshly updated Raspbian OS and followed the general setup and then the bridge guide, and upon rebooting my phone could see the network being broadcast. However, after attempting to connect it said "Failed to obtain IP Address." I then started again with a freshly updated Raspbian OS with the same process, but this time also followed the dnsmasq section too. After rebooting, this time my phone would get stuck in a loop of attempting to connect to the network, with no error message. Any further advice on how to proceed? | |
| Apr 3, 2019 at 9:59 | history | answered | Ingo | CC BY-SA 4.0 |