-
Hello together, since I've trouble with my Wifi connection on my old setup (the box is not connection to my local wifi). I've tried a setup from scratch. The OS (bullseye on RPi 3B+) is installing fine and I'm able to connect to my Wifi without issues. I was running the installation commandline and used the interactive configuration. I tried following combinations:
In all cases I end up that the Pi is not connecting to my Wifi after the phoniebox installation. Just the Auto-Hot-Spot is kicking in (if configured). The wpa_supplicant.conf seems fine. I've tried to set the Wifi again in the raspi-config without luck. I also tried changing between dhcpcd and NetworkManager and edited the dhcpcd.conf for static ip. Nothing worked out at the end. Has anyone else faced similar issues? I'd be very happy if someone could help me out on this. I just like to know a way to get the phoniebox to my local wifi and use the hotspot anywhere else. Regards, Robert |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Hi, I messed around with the installation of yesterday so I tried a fresh one again. The Raspberry Pi OS is "bullseye" Version: 2023-12-05. It seems that after the phoniebox installation the Pi has some issues with my hidden Wifi. The Wifi connection with the hidden wifi worked before the installation. The syslog gave me the hint on the issue
The following log now shows that the wifi connection could be established successfully. Another trap was the reboot of my router. The configuration interface gave me the option to enable/disable SSID hide on-the-fly. Didn't worked out until the router restart.
|
Beta Was this translation helpful? Give feedback.
Hi,
I messed around with the installation of yesterday so I tried a fresh one again. The Raspberry Pi OS is "bullseye" Version: 2023-12-05. It seems that after the phoniebox installation the Pi has some issues with my hidden Wifi. The Wifi connection with the hidden wifi worked before the installation. The syslog gave me the hint on the issue
Thx @AlvinSchiller for the hint with the syslog :-)