"start_ap" command bug

[khaledsherkawi]

Starting access point command (start_ap) is freeing the WiFi but not starting the access point.
Please find the logs attached.

syslog.log

netconnectd.log

[andywerner]

Today when I tested this, I found the AP was not present (checks on Mac and Pixel 4a with a Wifi Analyser App)

iwconfig confirms that AP is not running but ifconfig shows the expected IP on the wlan0 interface.

iwconfig:

wlan0     IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

ifconfig:

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:10:19:77
          inet addr:10.250.250.1  Bcast:10.250.250.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:2737 errors:0 dropped:2 overruns:0 frame:0
          TX packets:255 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:372816 (364.0 KiB)  TX bytes:88177 (86.1 KiB)