Device that's bridging eth0 to wlan0 does not have its own IP

[tarikaltuncu]

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:

sudo su
apt update 
apt upgrade --yes
apt install --yes hostapd
apt install --yes dnsmasq
apt install --yes git
apt install --yes make
apt install --yes net-tools
apt install --yes wireless-tools

mkdir rpi_network
cd rpi_network/
git clone https://github.com/oblique/create_ap.git
cd create_ap/
make install

create_ap -m bridge --freq-band 2.4 -w 2 --country US wlan0 eth0 ssid_name wifi_pass --mkconfig /etc/create_ap.conf

systemctl daemon-reload
systemctl enable create_ap.service
systemctl start create_ap.service

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

[yogesa]

you can use "rfkill list "to skim,
if soft blocked is yes , the question maybe cause it.