DHCP Server fails to start in Access Point Mode

SteffenFri commented 1 year ago

Hi,

I followed the last developments of the openwifi project with high interest and tried to start the new release Notter 1.4.0 by using the "zed_fmcs2-board" and the "zcu102_fmcs2-board". However, there seems to be a problem with the dhcp server running on the access point, that it failing to start within the fosdem.sh startup script. I checked the dhcpd configs, but they seem fine and I did not change them in the first place.

Am I missing something?

I have successfully booted the image and started the script ./wgd.sh to enable the access point. I get the following output:

    usage:
        Script for load (or download+load) different driver and FPGA img without rebooting
        no  argument: Load .ko driver files and FPGA img (if system_top.bit.bin exist) in current dir with test_mode=0.
        1st argument: If it is a NUMBER, it will be assigned to test_mode. Then load everything from current dir.
        1st argument: If it is a string called "remote", it will download driver/FPGA and load everything.
        - 2nd argument (if exist) is the target directory name for downloading and reloading
        - 3rd argument (if exist) is the value for test_mode
        1st argument: neither NUMBER nor "remote" nor a .tar.gz file, it is regarded as a directory and load everything from it.
        - 2nd argument (if exist) is the value for test_mode
        1st argument: a .tar.gz file, it will be unpacked then load from that unpacked directory
        - 2nd argument (if exist) is the value for test_mode

    Module                  Size  Used by
    mac80211              565248  0
    libarc4                16384  1 mac80211
    xilinx_dma             28672  0
    ad9361_drv            163840  2
    cfg80211              319488  1 mac80211
    8021q                  24576  0
    ipv6                  397312  28
    TARGET_DIR ./
    DOWNLOAD_FLAG 0
    test_mode 0
    tx_offset_tuning_enable 0
    $TARGET_DIR is found!

    hostapd: no process found
    Failed to stop dhcpd.service: Unit dhcpd.service not loaded.
    dhcpd: no process found
    sdr0: ERROR while getting interface flags: No such device
    rmmod: ERROR: Module sdr is not currently loaded
    ./load_fpga_img.sh: line 14: warning: command substitution: ignored null byte in input
    xlnx,zynq-7000
    .//system_top.bit.bin
    system_top.bit.bin
    + ifconfig sdr0 down
    sdr0: ERROR while getting interface flags: No such device
    + rmmod sdr
    rmmod: ERROR: Module sdr is not currently loaded
    + rmmod openofdm_rx
    rmmod: ERROR: Module openofdm_rx is not currently loaded
    + rmmod openofdm_tx
    rmmod: ERROR: Module openofdm_tx is not currently loaded
    + rmmod rx_intf
    rmmod: ERROR: Module rx_intf is not currently loaded
    + rmmod tx_intf
    rmmod: ERROR: Module tx_intf is not currently loaded
    + rmmod xpu
    rmmod: ERROR: Module xpu is not currently loaded
    + sleep 1
    + '[' -f .//system_top.bit.bin ']'
    + echo 0
    + mkdir -p /lib/firmware
    + cp .//system_top.bit.bin /lib/firmware/ -rf
    + echo system_top.bit.bin
    + '[' xlnx,zynq-7000 '!=' xlnx,zynq-7000 ']'
    + SPI_DEVNAME=spi0.0
    + DDS_DEVNAME=79024000.cf-ad9361-dds-core-lpc
    + ADC_DEVNAME=79020000.cf-ad9361-lpc
    + '[' '!' -d /sys/bus/spi/drivers/ad9361/spi0.0 ']'
    + cd /sys/bus/spi/drivers/ad9361/
    + echo spi0.0
    + echo spi0.0
    + '[' '!' -d /sys/bus/platform/drivers/cf_axi_adc/79020000.cf-ad9361-lpc ']'
    + cd /sys/bus/platform/drivers/cf_axi_adc/
    + echo 79020000.cf-ad9361-lpc
    + echo 79020000.cf-ad9361-lpc
    + set +x
    tx_offset_tuning_enable 0
    openwifi_ad9361_fir_tx_0MHz_11n.ftr tx_fir_enable 1
    Found openwifi_ad9361_fir_tx_0MHz_11n.ftr
    + test -f /sys/bus/iio/devices/iio:device0/in_voltage_rf_bandwidth
    + test -f /sys/bus/iio/devices/iio:device1/in_voltage_rf_bandwidth
    + test -f /sys/bus/iio/devices/iio:device2/in_voltage_rf_bandwidth
    + cd /sys/bus/iio/devices/iio:device2/
    + set +x
    FIR Rx: 48,1 Tx: 48,1
    1
    1
    rx0 agc fast_attack
    slow_attack
    fast_attack
    rx1 agc fast_attack
    slow_attack
    fast_attack
    40000000
    25215513
    40000000
    25215414
    rssi
    113.75 dB
    114.00 dB
    rx0 gain to 70
    72.000000 dB
    ./rf_init_11n.sh: 101: echo: echo: I/O error
    72.000000 dB
    rx1 gain to 70
    73.000000 dB
    ./rf_init_11n.sh: 106: echo: echo: I/O error
    73.000000 dB
    tx0 gain -89dB
    -10.000000 dB
    -89.000000 dB
    tx1 gain 0dB
    -10.000000 dB
    0.000000 dB
    rmmod: ERROR: Module tx_intf is not currently loaded
    + insmod .//tx_intf.ko
    tx_intf is loaded!
    rmmod: ERROR: Module rx_intf is not currently loaded
    + insmod .//rx_intf.ko
    rx_intf is loaded!
    rmmod: ERROR: Module openofdm_tx is not currently loaded
    + insmod .//openofdm_tx.ko
    openofdm_tx is loaded!
    rmmod: ERROR: Module openofdm_rx is not currently loaded
    + insmod .//openofdm_rx.ko
    openofdm_rx is loaded!
    rmmod: ERROR: Module xpu is not currently loaded
    + insmod .//xpu.ko
    xpu is loaded!
    rmmod: ERROR: Module sdr is not currently loaded
    + insmod .//sdr.ko test_mode=0
    sdr is loaded!
    the end

After starting the file "./fosdem.sh" I get the following output:

    hostapd: no process found
    rm: cannot remove '/var/run/dhcpd.pid': No such file or directory
    Job for isc-dhcp-server.service failed because the control process exited with error code.
    See "systemctl status isc-dhcp-server.service" and "journalctl -xe" for details.
    Configuration file: hostapd-openwifi.conf
    sdr0: interface state UNINITIALIZED->COUNTRY_UPDATE
    Using interface sdr0 with hwaddr a2:02:d6:13:6b:17 and ssid "openwifi"
    sdr0: interface state COUNTRY_UPDATE->ENABLED
    sdr0: AP-ENABLED

The access point has ssucessfully started, the interface "sdr0" is up and the openwifi is visible for other devices but it is not possible to connect to the access point and ip-adress via DHCP.

After executing the command "systemctl status isc-dhcp-server.service" I get the following output:

    ● isc-dhcp-server.service - LSB: DHCP server
        Loaded: loaded (/etc/init.d/isc-dhcp-server; generated)
        Active: failed (Result: exit-code) since Tue 2023-03-21 14:01:44 GMT; 6min ago
            Docs: man:systemd-sysv-generator(8)
        Process: 25118 ExecStart=/etc/init.d/isc-dhcp-server start (code=exited, status=1/FAILURE)
            CPU: 357ms
        CGroup: /system.slice/isc-dhcp-server.service
                └─25136 /usr/sbin/dhcpd -4 -q -cf /etc/dhcp/dhcpd.conf

    Mar 21 14:01:44 analog isc-dhcp-server[25209]:  failed!
    Mar 21 14:01:44 analog systemd[1]: isc-dhcp-server.service: Control process exited, code=exited, status=1/FAILURE
    Mar 21 14:01:44 analog systemd[1]: isc-dhcp-server.service: Failed with result 'exit-code'.
    Mar 21 14:01:44 analog systemd[1]: isc-dhcp-server.service: Unit process 25136 (dhcpd) remains running after unit stopped.
    Mar 21 14:01:44 analog systemd[1]: Failed to start LSB: DHCP server.
    Mar 21 14:01:44 analog dhcpd[25136]: receive_packet failed on sdr0: Network is down
    Mar 21 14:01:46 analog dhcpd[25136]: DHCPDISCOVER from a2:02:d6:13:6b:17 via sdr0
    Mar 21 14:01:47 analog dhcpd[25136]: DHCPOFFER on 192.168.13.6 to a2:02:d6:13:6b:17 (analog) via sdr0
    Mar 21 14:01:47 analog dhcpd[25136]: DHCPREQUEST for 192.168.13.6 (192.168.13.1) from a2:02:d6:13:6b:17 (analog) via sdr0
    Mar 21 14:01:47 analog dhcpd[25136]: DHCPACK on 192.168.13.6 to a2:02:d6:13:6b:17 (analog) via sdr0

JiaoXianjun commented 1 year ago

That dhcp failure won't affect the system. You can live with it as long as your client can get IP from openwifi AP automatically.

https://github.com/open-sdr/openwifi/blob/master/doc/known_issue/notter.md

SteffenFri commented 1 year ago

Actually, that is the problem 🙂 the clients can associate with the access point on mac layer, but do not get an IP address. I also tried to configure a static IP for my client in the dhcpd config, but this did also not work. It did however work with the older release wilsele.

JiaoXianjun commented 1 year ago

Did you try the method in the known issue page? (The link I gave). Are you using the official zed/zcu102 and ADI fmcomms board? When did you download the img? We updated recently. Maybe you can download again? We don't have ip fetching issue on zed/zcu102 + fmcomms board.

SteffenFri commented 1 year ago

I have downloaded the image on the main website on Monday and for a new trial today again. There are two different versions of the image available on your website . Which one should be used?

https://github.com/open-sdr/openwifi: openwifi-1.4.0-notter.img.xz
https://github.com/open-sdr/openwifi/blob/master/doc/known_issue/notter.md: openwifi-1.4.0-pre1-notter.img.xz I have tested both images where I have once configured the zed board as access point and once the zcu board. I have also tried to connect the client by using a static ip. Furthermore I have tried to restart the dhcp-server before trying to connect the client again. I am using the official zed/zcu102 (Revision 1.1) and ADI fmcomms boards.

Once below I have also listed the output of the ./openwifi/setup_once.sh which I have executed after flashing the image:


root@analog:~# ./openwifi/setup_once.sh 
+ cd /root/
++ uname -m
+ MACHINE_TYPE=aarch64
+ rm -rf kernel_modules
+ mkdir -p kernel_modules
+ '[' aarch64 == aarch64 ']'
+ cp /root/kernel_modules64/8021q.ko /root/kernel_modules64/a8293.ko /root/kernel_modules64/af9013.ko /root/kernel_modules64/af9033.ko /root/kernel_modules64/ascot2e.ko /root/kernel_modules64/atbm8830.ko /root/kernel_modules64/au8522_common.ko /root/kernel_modules64/au8522_decoder.ko /root/kernel_modules64/au8522_dig.ko /root/kernel_modules64/axidmatest.ko /root/kernel_modules64/bcm3510.ko /root/kernel_modules64/bpfilter.ko /root/kernel_modules64/cx22700.ko /root/kernel_modules64/cx22702.ko /root/kernel_modules64/cx24110.ko /root/kernel_modules64/cx24113.ko /root/kernel_modules64/cx24116.ko /root/kernel_modules64/cx24117.ko /root/kernel_modules64/cx24120.ko /root/kernel_modules64/cx24123.ko /root/kernel_modules64/cxd2099.ko /root/kernel_modules64/cxd2820r.ko /root/kernel_modules64/cxd2841er.ko /root/kernel_modules64/cxd2880.ko /root/kernel_modules64/cxd2880-spi.ko /root/kernel_modules64/dib0070.ko /root/kernel_modules64/dib0090.ko /root/kernel_modules64/dib3000mb.ko /root/kernel_modules64/dib3000mc.ko /root/kernel_modules64/dib7000m.ko /root/kernel_modules64/dib7000p.ko /root/kernel_modules64/dib8000.ko /root/kernel_modules64/dib9000.ko /root/kernel_modules64/dibx000_common.ko /root/kernel_modules64/dma-axi-dmac.ko /root/kernel_modules64/dmatest.ko /root/kernel_modules64/drx39xyj.ko /root/kernel_modules64/drxd.ko /root/kernel_modules64/drxk.ko /root/kernel_modules64/ds3000.ko /root/kernel_modules64/dvb-pll.ko /root/kernel_modules64/e4000.ko /root/kernel_modules64/ec100.ko /root/kernel_modules64/efivarfs.ko /root/kernel_modules64/fc0011.ko /root/kernel_modules64/fc0012.ko /root/kernel_modules64/fc0013.ko /root/kernel_modules64/fc2580.ko /root/kernel_modules64/fou6.ko /root/kernel_modules64/fou.ko /root/kernel_modules64/gspca_main.ko /root/kernel_modules64/helene.ko /root/kernel_modules64/horus3a.ko /root/kernel_modules64/ip6_tunnel.ko /root/kernel_modules64/ip6_udp_tunnel.ko /root/kernel_modules64/ip6_vti.ko /root/kernel_modules64/ipip.ko /root/kernel_modules64/ip_tunnel.ko /root/kernel_modules64/ip_vti.ko /root/kernel_modules64/isl6405.ko /root/kernel_modules64/isl6421.ko /root/kernel_modules64/isl6423.ko /root/kernel_modules64/it913x.ko /root/kernel_modules64/itd1000.ko /root/kernel_modules64/ix2505v.ko /root/kernel_modules64/l64781.ko /root/kernel_modules64/lg2160.ko /root/kernel_modules64/lgdt3305.ko /root/kernel_modules64/lgdt3306a.ko /root/kernel_modules64/lgdt330x.ko /root/kernel_modules64/lgs8gl5.ko /root/kernel_modules64/lgs8gxx.ko /root/kernel_modules64/lnbh25.ko /root/kernel_modules64/lnbh29.ko /root/kernel_modules64/lnbp21.ko /root/kernel_modules64/lnbp22.ko /root/kernel_modules64/m88ds3103.ko /root/kernel_modules64/m88rs2000.ko /root/kernel_modules64/m88rs6000t.ko /root/kernel_modules64/max2165.ko /root/kernel_modules64/mb86a16.ko /root/kernel_modules64/mb86a20s.ko /root/kernel_modules64/mc44s803.ko /root/kernel_modules64/mn88443x.ko /root/kernel_modules64/mn88472.ko /root/kernel_modules64/mn88473.ko /root/kernel_modules64/modules.builtin /root/kernel_modules64/modules.builtin.modinfo /root/kernel_modules64/modules.order /root/kernel_modules64/Module.symvers /root/kernel_modules64/mpls_gso.ko /root/kernel_modules64/msi001.ko /root/kernel_modules64/mt2060.ko /root/kernel_modules64/mt2063.ko /root/kernel_modules64/mt20xx.ko /root/kernel_modules64/mt2131.ko /root/kernel_modules64/mt2266.ko /root/kernel_modules64/mt312.ko /root/kernel_modules64/mt352.ko /root/kernel_modules64/mtd_nandbiterrs.ko /root/kernel_modules64/mtd_nandecctest.ko /root/kernel_modules64/mtd_oobtest.ko /root/kernel_modules64/mtd_pagetest.ko /root/kernel_modules64/mtd_readtest.ko /root/kernel_modules64/mtd_speedtest.ko /root/kernel_modules64/mtd_stresstest.ko /root/kernel_modules64/mtd_subpagetest.ko /root/kernel_modules64/mtd_torturetest.ko /root/kernel_modules64/mxl301rf.ko /root/kernel_modules64/mxl5005s.ko /root/kernel_modules64/mxl5007t.ko /root/kernel_modules64/mxl5xx.ko /root/kernel_modules64/netlink_diag.ko /root/kernel_modules64/nf_conntrack.ko /root/kernel_modules64/nf_conntrack_netlink.ko /root/kernel_modules64/nf_defrag_ipv4.ko /root/kernel_modules64/nf_defrag_ipv6.ko /root/kernel_modules64/nfs_layout_flexfiles.ko /root/kernel_modules64/nsh.ko /root/kernel_modules64/nxt200x.ko /root/kernel_modules64/nxt6000.ko /root/kernel_modules64/openvswitch.ko /root/kernel_modules64/or51132.ko /root/kernel_modules64/or51211.ko /root/kernel_modules64/qm1d1b0004.ko /root/kernel_modules64/qm1d1c0042.ko /root/kernel_modules64/qt1010.ko /root/kernel_modules64/r820t.ko /root/kernel_modules64/raw_diag.ko /root/kernel_modules64/rpmsg_core.ko /root/kernel_modules64/rtl2830.ko /root/kernel_modules64/rtl2832.ko /root/kernel_modules64/rtl2832_sdr.ko /root/kernel_modules64/s5h1409.ko /root/kernel_modules64/s5h1411.ko /root/kernel_modules64/s5h1420.ko /root/kernel_modules64/s5h1432.ko /root/kernel_modules64/s921.ko /root/kernel_modules64/si2157.ko /root/kernel_modules64/si2165.ko /root/kernel_modules64/si2168.ko /root/kernel_modules64/si21xx.ko /root/kernel_modules64/sit.ko /root/kernel_modules64/sp2.ko /root/kernel_modules64/sp8870.ko /root/kernel_modules64/sp887x.ko /root/kernel_modules64/stb0899.ko /root/kernel_modules64/stb6000.ko /root/kernel_modules64/stb6100.ko /root/kernel_modules64/stv0288.ko /root/kernel_modules64/stv0297.ko /root/kernel_modules64/stv0299.ko /root/kernel_modules64/stv0367.ko /root/kernel_modules64/stv0900.ko /root/kernel_modules64/stv090x.ko /root/kernel_modules64/stv0910.ko /root/kernel_modules64/stv6110.ko /root/kernel_modules64/stv6110x.ko /root/kernel_modules64/stv6111.ko /root/kernel_modules64/tc90522.ko /root/kernel_modules64/tcp_bic.ko /root/kernel_modules64/tcp_htcp.ko /root/kernel_modules64/tcp_westwood.ko /root/kernel_modules64/tda10021.ko /root/kernel_modules64/tda10023.ko /root/kernel_modules64/tda10048.ko /root/kernel_modules64/tda1004x.ko /root/kernel_modules64/tda10071.ko /root/kernel_modules64/tda10086.ko /root/kernel_modules64/tda18212.ko /root/kernel_modules64/tda18218.ko /root/kernel_modules64/tda18250.ko /root/kernel_modules64/tda18271c2dd.ko /root/kernel_modules64/tda18271.ko /root/kernel_modules64/tda665x.ko /root/kernel_modules64/tda8083.ko /root/kernel_modules64/tda8261.ko /root/kernel_modules64/tda826x.ko /root/kernel_modules64/tda827x.ko /root/kernel_modules64/tda8290.ko /root/kernel_modules64/tda9887.ko /root/kernel_modules64/tea5761.ko /root/kernel_modules64/tea5767.ko /root/kernel_modules64/ts2020.ko /root/kernel_modules64/tua6100.ko /root/kernel_modules64/tua9001.ko /root/kernel_modules64/tuner-simple.ko /root/kernel_modules64/tuner-types.ko /root/kernel_modules64/tuner-xc2028.ko /root/kernel_modules64/tunnel4.ko /root/kernel_modules64/tunnel6.ko /root/kernel_modules64/udp_diag.ko /root/kernel_modules64/udp_tunnel.ko /root/kernel_modules64/uio_dmem_genirq.ko /root/kernel_modules64/uio_pdrv_genirq.ko /root/kernel_modules64/ves1820.ko /root/kernel_modules64/ves1x93.ko /root/kernel_modules64/virtio_rpmsg_bus.ko /root/kernel_modules64/xc4000.ko /root/kernel_modules64/xc5000.ko /root/kernel_modules64/xilinx_dma.ko /root/kernel_modules64/xlnx_vcu.ko /root/kernel_modules64/xt_connmark.ko /root/kernel_modules64/xt_conntrack.ko /root/kernel_modules64/xt_state.ko /root/kernel_modules64/zd1301_demod.ko /root/kernel_modules64/zl10036.ko /root/kernel_modules64/zl10039.ko /root/kernel_modules64/zl10353.ko /root/kernel_modules64/zynqmp_r5_remoteproc.ko /root/kernel_modules/
+ cp /root/openwifi64/openofdm_rx.ko /root/openwifi64/openofdm_tx.ko /root/openwifi64/rx_intf.ko /root/openwifi64/sdr.ko /root/openwifi64/side_ch.ko /root/openwifi64/tx_intf.ko /root/openwifi64/xpu.ko /root/openwifi/
+ mv /root/kernel_modules/ad9361_drv.ko /root/openwifi/ -f
mv: cannot stat '/root/kernel_modules/ad9361_drv.ko': No such file or directory
+ true
+ mv /root/kernel_modules/adi_axi_hdmi.ko /root/openwifi/ -f
mv: cannot stat '/root/kernel_modules/adi_axi_hdmi.ko': No such file or directory
+ true
+ mv /root/kernel_modules/axidmatest.ko /root/openwifi/ -f
+ mv /root/kernel_modules/lcd.ko /root/openwifi/ -f
mv: cannot stat '/root/kernel_modules/lcd.ko': No such file or directory
+ true
+ mv /root/kernel_modules/xilinx_dma.ko /root/openwifi/ -f
++ uname -r
+ rm -rf /lib/modules/5.10.0-98248-g1bbe32fa5182-dirty
++ uname -r
+ ln -s /root/kernel_modules /lib/modules/5.10.0-98248-g1bbe32fa5182-dirty
+ sync
+ depmod
+ cd /root/openwifi/sdrctl_src
+ make clean
+ make
 CC   sdrctl.o
 CC   cmd.o
 GEN  version.c
 CC   version.o
 CC   sections.o
 CC   sdrctl
+ cp sdrctl /root/openwifi/
+ cd /root/openwifi/side_ch_ctl_src/
+ gcc -o side_ch_ctl side_ch_ctl.c
+ cp side_ch_ctl /root/openwifi/
+ cd /root/openwifi/inject_80211/
+ make clean
rm -f inject_80211 analyze_80211
+ make
gcc  -Wall -Werror inject_80211.c -o inject_80211 -lpcap
gcc  -Wall -Werror radiotap.c analyze_80211.c -o analyze_80211 -lpcap
+ cd ..
+ sync
``

JiaoXianjun commented 1 year ago

Do you still have the dhcp issue?

SteffenFri commented 1 year ago

Yes, I still have the problem that the dhcp service fails and the client will not get an IP address.

JiaoXianjun commented 1 year ago

Did you try the method in our known issue page? Can you paste the openwifi AP command line output during the client connecting?

SteffenFri commented 1 year ago

Yes, I have tried the method on your known issue page where I have restarted the dhcp-server and tried to connect the client again. While I a trying to connect the client to the AP by executing the command " wpa_supplicant -i sdr0 -c wpa-openwifi.conf " at the client I will get the following output for the client:

Successfully initialized wpa_supplicant
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
sdr0: SME: Trying to authenticate with 52:aa:69:c1:c3:79 (SSID='openwifi' freq=5220 MHz)
sdr0: Trying to associate with 52:aa:69:c1:c3:79 (SSID='openwifi' freq=5220 MHz)
sdr0: Associated with 52:aa:69:c1:c3:79
sdr0: CTRL-EVENT-CONNECTED - Connection to 52:aa:69:c1:c3:79 completed [id=0 id_str=]
sdr0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
^Csdr0: CTRL-EVENT-DISCONNECTED bssid=52:aa:69:c1:c3:79 reason=3 locally_generated=1
nl80211: deinit ifname=sdr0 disabled_11b_rates=0
sdr0: CTRL-EVENT-TERMINATING

At the access point I will get the following output:

sdr0: STA 2a:1c:47:ad:f9:ac IEEE 802.11: authenticated
sdr0: STA 2a:1c:47:ad:f9:ac IEEE 802.11: associated (aid 1)
sdr0: AP-STA-CONNECTED 2a:1c:47:ad:f9:ac
sdr0: STA 2a:1c:47:ad:f9:ac RADIUS: starting accounting session 6FA675B3DFB6CD1B
sdr0: AP-STA-DISCONNECTED 2a:1c:47:ad:f9:ac
sdr0: INTERFACE-DISABLED 
sdr0: INTERFACE-ENABLED 
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed
handle_probe_req: send failed

When I try to connect the client by executing the command " iwconfig sdr0 essid openwifi " I will get the following output at the access point :

sdr0: STA 7e:04:66:10:7d:63 IEEE 802.11: authenticated
sdr0: STA 7e:04:66:10:7d:63 IEEE 802.11: associated (aid 1)
sdr0: AP-STA-CONNECTED 7e:04:66:10:7d:63
sdr0: STA 7e:04:66:10:7d:63 RADIUS: starting accounting session 38161E73D463CDFD
sdr0: AP-STA-DISCONNECTED 7e:04:66:10:7d:63

There is no additional output at the client.

After trying to connect the client by executing the commands "wpa_supplicant -i sdr0 -c wpa-openwifi.conf" or "iwconfig sdr0 essid openwifi" I have used the command "dhclient sdr0" to get an ip address from the access point. This command terminates after a timeout without additional command line output.

JiaoXianjun commented 1 year ago

Can you use cellphone or computer to act as client? If they can get IP automatically, then there is no issue with dhcp server in AP.

On the other hand:

While you use wpa_supplicant on client, could you please update your onboard file in onboard openwifi directory: https://github.com/open-sdr/openwifi/blob/master/user_space/hostapd-openwifi.conf remove following password settings from it:

wpa=1
wpa_passphrase=openwifi
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP
wpa_ptk_rekey=600

SteffenFri commented 1 year ago

For me it was possible to connect my smartphone and my computer but after some time i get the following output:

sdr0: INTERFACE-DISABLED sdr0: INTERFACE-ENABLED handle_probe_req: send failed handle_probe_req: send failed

The settings you have mentioned from "hostapd-openwifi.conf " are already commented.

JiaoXianjun commented 1 year ago

please follow this. https://github.com/open-sdr/openwifi/blob/master/doc/app_notes/ap-client-two-sdr.md

Did you run dhclient?

open-sdr / openwifi

DHCP Server fails to start in Access Point Mode #289