WiFi Woes
Frederick Bambrough (1372) 837 posts |
Update to ROS 5.30 a doddle. WiFi however… This is on a RPi 4B which has been used with WiFi successfully with RaspberryPi OS. With ROS the router (Fritz!Box 7530) shows a brief connection before disconnect but that’s all. No network access. I’ve tried both configuring via DHCP & manually. Checking the details; WiFi menu bar menu Interfaces-SDIO Slot 2 BCM43 WIFI Status Activity shows: Activity ticked, Active ticked, Full duplex X, Polarity ?. Slowly increasing transmit frames, receive frames ditto (over a very long period). No errors either way. Hopefully I’ve done something stupid, easy to correct. |
Steve Pampling (1551) 8172 posts |
That 169.254.×.x is an APIPA address, which means your client device has not seen, or not properly processed the response from your DHCP server (in the router) Netmask of 255.255.0.0 is consistent with APIPA settings, and the gateway isn’t set as APIPA addresses are expected to only be used in the local net |
Frederick Bambrough (1372) 837 posts |
APIPA – had to look that up! So that still leaves why & what to do. Edit: Noticed my neighbour’s Wi-Fi pops up occasionally in the icon bar menu. Info looks sensible. |
Frederick Bambrough (1372) 837 posts |
Frustrating! I managed to get the RPi connected via Wi-Fi. Unfortunately it was via my android phone, not the router. Grrr! So what’s different with the router??? |
Martin Avison (27) 1494 posts |
I have managed to connect my Pi4B to my FritzBox 5730AX router, but… But it does work! @Frederick: is there no sign of it in the router event logs? |
Doug Webb (190) 1180 posts |
Get the same here with my WiFi extenders. It works as you say though. |
Frederick Bambrough (1372) 837 posts |
No, nothing.
Yes. I’ve not had any issues connecting other devices on either the main or guest network. … and what’s the WEP stuff about? The router doesn’t do that. I disabled my powerline Wi-Fi extenders while testing. Edit: Made false assumption. |
Frederick Bambrough (1372) 837 posts |
We have ignition…of sorts. It appears to have been an encryption problem. The router has three options – WPA+WPA2, WPA2 (CCMP) and WPA2+WPA3. Whilst I normally use the last, ROS will only connect if one of the first two is set. Even then it depends on me selecting the router’s AP and not one of the extenders which is fun given that they bear the same name. Ah, well. It’s progress. Edit: The extenders are also set to WPA2/WPA3 so that’s consistent. Still don’t get the WEP bit. |
Martin Avison (27) 1494 posts |
Strange. My router is also set to use WPA2+WPA3, and it connects ok … though WiFi Manager claims it used WEP and the router WPA2. What it actually uses, I am not sure! |
Norman Lawrence (3005) 172 posts |
I am experiencing all of the above on both a Pi3B and Pi4B using a clean 5.30 image. For some reason WiFi Manager claims my router and my neighbours are all WEP whereas they are all WPA2. I get an invalid argument error when I try to connect using WiFi manager. I have connected using Connect on the menu but it does not connect automatically on next boot up so it is necessary to enter SSID and password every time. However, I have not experienced any difficulties in connecting and automatically reconnecting using Elesar’s WiFi hat or similar alternatives. All that said, it is a tremendous achievement and well done to all involved. PS Would it be possible for a show password option on the next release? |
Raik (463) 2061 posts |
I have also any problems with Pi4B. No connection, double entrys in the netlist… It was a good idea to delete the old WifiMgr folder in Choices. Than I get a clean list but an unstable connection. |
Frederick Bambrough (1372) 837 posts |
Resolved for me with 16 May release. Now announces WPA2+WPA3 and connects. |