I use it in bridge mode on a Raspberry pi 4 running headless on a clean Ubuntu Server 20.04.
Below is the all script that I run on the clean OS. It runs good as a bridging wi-fi. But on reboot, although Wi-Fi still serves well and assigns IP to other wireless devices, the Raspberry pi does not get its own IP. It should be assigned the same IP by its MAC address on eth0, but It's not there. I checked arp -a and it's not listed there as well.
Btw, if I run more or less the same script on Raspbian Lite OS, it works well first. But starting from the first reboot, it neither can get its own IP nor assign the other wifi clients trying to connect.
Since I run these on headless, I can't debug at the moment but I can soon try getting a monitor to access it offline hopefully.
Do you have any idea to fix this?
Best
Hey, thanks for maintaining this.
I use it in bridge mode on a Raspberry pi 4 running headless on a clean Ubuntu Server 20.04. Below is the all script that I run on the clean OS. It runs good as a bridging wi-fi. But on reboot, although Wi-Fi still serves well and assigns IP to other wireless devices, the Raspberry pi does not get its own IP. It should be assigned the same IP by its MAC address on eth0, but It's not there. I checked
arp -a
and it's not listed there as well.Here is how I run it on headless ssh:
Btw, if I run more or less the same script on Raspbian Lite OS, it works well first. But starting from the first reboot, it neither can get its own IP nor assign the other wifi clients trying to connect.
Since I run these on headless, I can't debug at the moment but I can soon try getting a monitor to access it offline hopefully. Do you have any idea to fix this? Best