DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Cannot connect to pi configured with Hostapd (bridged AP)

Tue Jun 08, 2021 7:13 pm

Following this guide: https://www.raspberrypi.org/documentati ... bridged.md

Windows laptop always displays "Unable to connect to network"
Android always displays "incorrect password"

Diagnostic Data:

Code: Select all

pi@raspberrypi:~ $ sudo iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

br0       no wireless extensions.

wlan0     IEEE 802.11  Mode:Master  Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

pi@raspberrypi:~ $ sudo ip route show
default via 192.168.16.1 dev eth0 proto dhcp src 192.168.16.153 metric 100
192.168.16.0/24 dev eth0 proto kernel scope link src 192.168.16.153
192.168.16.1 dev eth0 proto dhcp scope link src 192.168.16.153 metric 100
Files:

Code: Select all

\etc\network\interfaces

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# interfaces(5) file used by ifup(8) and ifdown(8)
# Better use netplan.io or systemd-networkd to configure additional interface stanzas.

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

Code: Select all

/etc/network/interfaces.d:

(no files, directories - empty)

Code: Select all

/etc/dhcpcd.conf 

denyinterfaces wlan0 eth0

interface br0

Code: Select all

/etc/systemd/network/br0-member-eth0.network

[Match]
Name=eth0

[Network]
Bridge=br0

Code: Select all

/etc/systemd/network/bridge-br0.netdev

[NetDev]
Name=br0
Kind=bridge

Code: Select all

/etc/hostapd/hostapd.conf

country_code=US
interface=wlan0
bridge=br0
ssid=Myssid
hw_mode=g
channel=10
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=Mypassword
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

epoch1970
Posts: 6511
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Tue Jun 08, 2021 8:19 pm

eth0 appears to be missing from the bridge interface br0. Systemd-networkd doesn’t seem to be working, that was his job.

Eth0 seems to be managed outside dhcpcd because you disabled its configuration in dhcpcd.conf but somehow it has been configured via DHCP.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

nick59
Posts: 10
Joined: Thu Apr 15, 2021 2:57 pm

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Wed Jun 09, 2021 12:24 am

A quick look makes he think the following files are being processed in the wrong order:

/etc/systemd/network/br0-member-eth0.network
/etc/systemd/network/bridge-br0.netdev

The files are processed in alphabetical order by filename. It appears you are trying to bind eth0 before br0 is created.

Here is a link to a guide that I have available. Note the filenames that I use to make sure they process in the right order:

https://github.com/morrownr/7612u/blob/ ... s_Point.md

If you decide to use a usb adapter at some point, the following site has information:

https://github.com/morrownr/USB-WiFi

DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Wed Jun 09, 2021 2:02 am

It is a Pi 4B 4Gb and all I have done prior initially to the Pi s used ethernet cable to connect Pi LAN port to router LAN port and followed this guide:
https://pimylifeup.com/raspberry-pi-openmediavault/ to install Open Media Vault.

Now I have just added HOSTAPD in an attempt to enable the internal Pi radio serving as bridged AP for AP wifi clients to receive DHCP info and gateway access via main router over ethernet (no DHCP server in PI if that is an option). Thanks!

(That's certainly a brain-full of info that it will take me some time to sift through - THANK YOU.) If the info I now share from this post regarding the Pi connected via Ethernet changes my needed strategy to enable AP, please let me know.

DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Wed Jun 09, 2021 3:07 am

@nick99 My gateway and DNS is at 192.168.16.1. The OMV server is already acquiring an address for the OMV server, do I need to set another address for the AP? I want people who sign into the AP to still negotiate via DHCP with the main router and not via a service on the Pi if that is possible. THANKS!!!

Reference:

Code: Select all

sudo nano /etc/systemd/network/21-bridge-br0-config.network

Note: The contents of the Network block below should reflect the needs of your network.

File contents

[Match]
Name=br0

[Network]
Address=192.168.1.100/24
Gateway=192.168.1.1
DNS=8.8.8.8

DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Wed Jun 09, 2021 4:26 pm

Log file is just looping the error (grown to 700Mb in 24 hrs)

Code: Select all

random: getrandom() support available
Configuration file: /etc/hostapd/hostapd-5g.conf
ctrl_interface_group=0
Configuration file: /etc/hostapd/hostapd-2g.conf
ctrl_interface_group=0
nl80211: Using driver-based roaming
nl80211: TDLS supported
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Using driver-based off-channel TX
nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: Enable multi-channel concurrent (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0xe23778 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=0501
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=0503
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=0504
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=08
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=12
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xe23778 match=7f
nl80211: Enable Probe Request reporting nl_preq=0xe1f898
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0xe1f898 match=
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 3 (ifidx_reason 4)
nl80211: if_indices[16]: 3(4)
nl80211: Add own interface ifindex 4 (ifidx_reason -1)
nl80211: if_indices[16]: 3(4) 4(-1)
nl80211: Adding interface wlan0 into bridge br0
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code US, new country code US 
nl80211: Regulatory information - country=US (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 30 mBm
nl80211: 5170-5250 @ 80 MHz 23 mBm
nl80211: 5250-5330 @ 80 MHz 23 mBm (DFS)
nl80211: 5490-5730 @ 160 MHz 23 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 30 mBm
nl80211: 57240-63720 @ 2160 MHz 40 mBm
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[DISABLED] 2472[DISABLED] 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5170[DISABLED] 5180 5190[DISABLED] 5200 5210[DISABLED] 5220 5230[DISABLED] 5240 5260[NO_IR][RADAR] 5280[NO_IR][RADAR] 5300[NO_IR][RADAR] 5320[NO_IR][RADAR] 5500[NO_IR][RADAR] 5520[NO_IR][RADAR]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[DISABLED] 2472[DISABLED] 2484[DISABLED]
Driver does not support configured HT capability [GF]
wlan0: interface state COUNTRY_UPDATE->DISABLED
wlan0: AP-DISABLED 
wlan0: Unable to setup interface.
hostapd_interface_deinit_free(0xe1dc40)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0xe1dc40)
wlan0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> 0 (Success)
nl80211: bridge FDB entry delete for ff:ff:ff:ff:ff:ff ifindex=4 failed: Object not found
wlan0: AP-DISABLED 
hostapd_cleanup(hapd=0xe20510 (wlan0))
wlan0: CTRL-EVENT-TERMINATING 
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_deinit_free: driver=0x54436c drv_priv=0xe236f8 -> hapd_deinit
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Disable Probe Request reporting nl_preq=0x88697011
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=4)
netlink: Operstate: ifindex=4 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 4 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Unsubscribe mgmt frames handle 0x886abff1 (AP teardown (dev SME))
hostapd_interface_free(0xe1dc40)
hostapd_interface_free: free hapd 0xe20510
hostapd_cleanup_iface(0xe1dc40)
hostapd_cleanup_iface_partial(0xe1dc40)
hostapd_cleanup_iface: free iface=0xe1dc40
hostapd_interface_deinit_free(0xe1eb20)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0xe1eb20)
wlan1: interface state UNINITIALIZED->DISABLED
hostapd_bss_deinit: deinit bss wlan1
wlan1: AP-DISABLED 
hostapd_cleanup(hapd=0xe21590 (wlan1))
wlan1: CTRL-EVENT-TERMINATING 
hostapd_free_hapd_data: Interface wlan1 wasn't started
hostapd_interface_deinit_free: driver=0x54436c drv_priv=(nil) -> hapd_deinit
hostapd_interface_free(0xe1eb20)
hostapd_interface_free: free hapd 0xe21590
hostapd_cleanup_iface(0xe1eb20)
hostapd_cleanup_iface_partial(0xe1eb20)
hostapd_cleanup_iface: free iface=0xe1eb20
random: getrandom() support available
Configuration file: /etc/hostapd/hostapd-5g.conf
ctrl_interface_group=0
Configuration file: /etc/hostapd/hostapd-2g.conf
ctrl_interface_group=0
nl80211: Using driver-based roaming
nl80211: TDLS supported
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Using driver-based off-channel TX
nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: Enable multi-channel concurrent (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x1077778 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=0501
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=0503
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=0504
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=08
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=12
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1077778 match=7f
nl80211: Enable Probe Request reporting nl_preq=0x1073898
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x1073898 match=
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 3 (ifidx_reason 4)
nl80211: if_indices[16]: 3(4)
nl80211: Add own interface ifindex 4 (ifidx_reason -1)
nl80211: if_indices[16]: 3(4) 4(-1)
nl80211: Adding interface wlan0 into bridge br0
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code US, new country code US 
nl80211: Regulatory information - country=US (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 30 mBm
nl80211: 5170-5250 @ 80 MHz 23 mBm
nl80211: 5250-5330 @ 80 MHz 23 mBm (DFS)
nl80211: 5490-5730 @ 160 MHz 23 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 30 mBm
nl80211: 57240-63720 @ 2160 MHz 40 mBm
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[DISABLED] 2472[DISABLED] 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5170[DISABLED] 5180 5190[DISABLED] 5200 5210[DISABLED] 5220 5230[DISABLED] 5240 5260[NO_IR][RADAR] 5280[NO_IR][RADAR] 5300[NO_IR][RADAR] 5320[NO_IR][RADAR] 5500[NO_IR][RADAR] 5520[NO_IR][RADAR]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[DISABLED] 2472[DISABLED] 2484[DISABLED]
Driver does not support configured HT capability [GF]
wlan0: interface state COUNTRY_UPDATE->DISABLED
wlan0: AP-DISABLED 
wlan0: Unable to setup interface.
hostapd_interface_deinit_free(0x1071c40)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x1071c40)
wlan0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> 0 (Success)
nl80211: bridge FDB entry delete for ff:ff:ff:ff:ff:ff ifindex=4 failed: Object not found
wlan0: AP-DISABLED 
hostapd_cleanup(hapd=0x1074510 (wlan0))
wlan0: CTRL-EVENT-TERMINATING 
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_deinit_free: driver=0x58436c drv_priv=0x10776f8 -> hapd_deinit
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Disable Probe Request reporting nl_preq=0x898fb011
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=4)
netlink: Operstate: ifindex=4 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 4 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Unsubscribe mgmt frames handle 0x898ffff1 (AP teardown (dev SME))
hostapd_interface_free(0x1071c40)
hostapd_interface_free: free hapd 0x1074510
hostapd_cleanup_iface(0x1071c40)
hostapd_cleanup_iface_partial(0x1071c40)
hostapd_cleanup_iface: free iface=0x1071c40
hostapd_interface_deinit_free(0x1072b20)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x1072b20)
wlan1: interface state UNINITIALIZED->DISABLED
hostapd_bss_deinit: deinit bss wlan1
wlan1: AP-DISABLED 
hostapd_cleanup(hapd=0x1075590 (wlan1))
wlan1: CTRL-EVENT-TERMINATING 
hostapd_free_hapd_data: Interface wlan1 wasn't started
hostapd_interface_deinit_free: driver=0x58436c drv_priv=(nil) -> hapd_deinit
hostapd_interface_free(0x1072b20)
hostapd_interface_free: free hapd 0x1075590
hostapd_cleanup_iface(0x1072b20)
hostapd_cleanup_iface_partial(0x1072b20)
hostapd_cleanup_iface: free iface=0x1072b20
random: getrandom() support available
Configuration file: /etc/hostapd/hostapd-5g.conf
ctrl_interface_group=0
Configuration file: /etc/hostapd/hostapd-2g.conf
ctrl_interface_group=0
nl80211: Using driver-based roaming
nl80211: TDLS supported
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Using driver-based off-channel TX
nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: Enable multi-channel concurrent (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x12bf778 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=0501
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=0503
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=0504
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=08
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=12
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x12bf778 match=7f
nl80211: Enable Probe Request reporting nl_preq=0x12bb898
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x12bb898 match=
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 3 (ifidx_reason 4)
nl80211: if_indices[16]: 3(4)
nl80211: Add own interface ifindex 4 (ifidx_reason -1)
nl80211: if_indices[16]: 3(4) 4(-1)
nl80211: Adding interface wlan0 into bridge br0
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code US, new country code US 
nl80211: Regulatory information - country=US (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 30 mBm
nl80211: 5170-5250 @ 80 MHz 23 mBm
nl80211: 5250-5330 @ 80 MHz 23 mBm (DFS)
nl80211: 5490-5730 @ 160 MHz 23 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 30 mBm
nl80211: 57240-63720 @ 2160 MHz 40 mBm
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[DISABLED] 2472[DISABLED] 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5170[DISABLED] 5180 5190[DISABLED] 5200 5210[DISABLED] 5220 5230[DISABLED] 5240 5260[NO_IR][RADAR] 5280[NO_IR][RADAR] 5300[NO_IR][RADAR] 5320[NO_IR][RADAR] 5500[NO_IR][RADAR] 5520[NO_IR][RADAR]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[DISABLED] 2472[DISABLED] 2484[DISABLED]
Driver does not support configured HT capability [GF]
wlan0: interface state COUNTRY_UPDATE->DISABLED
wlan0: AP-DISABLED 
wlan0: Unable to setup interface.
hostapd_interface_deinit_free(0x12b9c40)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x12b9c40)
wlan0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> 0 (Success)
nl80211: bridge FDB entry delete for ff:ff:ff:ff:ff:ff ifindex=4 failed: Object not found
wlan0: AP-DISABLED 
hostapd_cleanup(hapd=0x12bc510 (wlan0))
wlan0: CTRL-EVENT-TERMINATING 
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_deinit_free: driver=0x5d436c drv_priv=0x12bf6f8 -> hapd_deinit
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Disable Probe Request reporting nl_preq=0x89a33011
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=4)
netlink: Operstate: ifindex=4 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 4 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Unsubscribe mgmt frames handle 0x89a37ff1 (AP teardown (dev SME))
hostapd_interface_free(0x12b9c40)
hostapd_interface_free: free hapd 0x12bc510
hostapd_cleanup_iface(0x12b9c40)
hostapd_cleanup_iface_partial(0x12b9c40)
hostapd_cleanup_iface: free iface=0x12b9c40
hostapd_interface_deinit_free(0x12bab20)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x12bab20)
wlan1: interface state UNINITIALIZED->DISABLED
hostapd_bss_deinit: deinit bss wlan1
wlan1: AP-DISABLED 
hostapd_cleanup(hapd=0x12bd590 (wlan1))
wlan1: CTRL-EVENT-TERMINATING 
hostapd_free_hapd_data: Interface wlan1 wasn't started
hostapd_interface_deinit_free: driver=0x5d436c drv_priv=(nil) -> hapd_deinit
hostapd_interface_free(0x12bab20)
hostapd_interface_free: free hapd 0x12bd590
hostapd_cleanup_iface(0x12bab20)
hostapd_cleanup_iface_partial(0x12bab20)
hostapd_cleanup_iface: free iface=0x12bab20
random: getrandom() support available
Configuration file: /etc/hostapd/hostapd-5g.conf
ctrl_interface_group=0
Configuration file: /etc/hostapd/hostapd-2g.conf
ctrl_interface_group=0
nl80211: Using driver-based roaming
nl80211: TDLS supported
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Using driver-based off-channel TX
nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: Enable multi-channel concurrent (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x1e89778 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=0501
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=0503
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=0504
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=08
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=12
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1e89778 match=7f
nl80211: Enable Probe Request reporting nl_preq=0x1e85898
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x1e85898 match=
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 3 (ifidx_reason 4)
nl80211: if_indices[16]: 3(4)
nl80211: Add own interface ifindex 4 (ifidx_reason -1)
nl80211: if_indices[16]: 3(4) 4(-1)
nl80211: Adding interface wlan0 into bridge br0
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code US, new country code US 
nl80211: Regulatory information - country=US (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 30 mBm
nl80211: 5170-5250 @ 80 MHz 23 mBm
Hardware Version:

Raspberry Pi 4 Model B 2019 Quad Core 64 Bit WiFi Bluetooth (4GB)

Software Version:

Linux raspberrypi 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l

epoch1970
Posts: 6511
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Wed Jun 09, 2021 4:50 pm

How many config files do you use for hostapd?
Does the bridge interface fare better and has eth0 in it?
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Wed Jun 09, 2021 6:59 pm

I am in general just a follower of setup guides and don't have a large networking background (very simple understanding of the operation) and the guide I followed after the official guide failed has been here https://github.com/morrownr/7612u/blob/ ... s_Point.md by the suggestion of @nick59 . All I know is I started with the standard Pi no-monitor/keyboard setup, I installed OMV using the Ethernet cable and I have been using OMV for about 6 months. I am just trying to enable the internal radio as an AP.

This guide gives the option of two config files which is the option I chose.

What is the process for displaying this information "Does the bridge interface fare better and has eth0 in it?"

Thank you.

epoch1970
Posts: 6511
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Wed Jun 09, 2021 7:21 pm

Run "ip link show"
You should see eth0 with "master br0" mentioned in the description. The link should be up.
You should see br0 up as well.

Run "ip route show" and "ip address show" to verify eth0 has no IP address and br0 has acquired an IP address (through eth0)


I would also recommend you use a single hostapd config file to begin, and a simple one at that.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Thu Jun 10, 2021 9:24 pm

Notes: **:*A, **:*B, *** changed for privacy

Linux raspberrypi 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jun 9 11:29:38 2021 from 192.168.16.174

Code: Select all

pi@raspberrypi:~ $ sudo ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether dc:a6:32:96:**:*A brd ff:ff:ff:ff:ff:ff
3: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether dc:a6:32:96:**:*B brd ff:ff:ff:ff:ff:ff

Code: Select all

pi@raspberrypi:~ $ sudo ip route show
default via 192.168.16.1 dev eth0 proto dhcp src 192.168.16.153 metric 100
192.168.16.0/24 dev eth0 proto kernel scope link src 192.168.16.153
192.168.16.1 dev eth0 proto dhcp scope link src 192.168.16.153 metric 100

Code: Select all

pi@raspberrypi:~ $ sudo ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether dc:a6:32:96:**:*A brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.153/24 brd 192.168.16.255 scope global dynamic eth0
       valid_lft 524sec preferred_lft 524sec
    inet6 fd42:e3e8:79ee::f96/128 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fd42:e3e8:79ee:0:dea6:32ff:fe96:***4/64 scope global mngtmpaddr noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::dea6:32ff:fe96:***4/64 scope link
       valid_lft forever preferred_lft forever
3: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6029:bcff:fe36:c089/64 scope link
       valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether dc:a6:32:96:**:*B brd ff:ff:ff:ff:ff:ff
pi@raspberrypi:~ $

epoch1970
Posts: 6511
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Thu Jun 10, 2021 10:19 pm

So, the networkd part of your network setup doesn’t work. You should try to fix that.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Fri Jun 11, 2021 5:32 am

What steps would I take to "fix" this? All I did is the following:
- download headless install & burn to SSD card
- alter boot image using Linux desktop to give SSH access
- use Ethernet client option to connect
- install OMV (works well - ethernet cable to router and shared on local LAN)
- attempt to install Hostapd (failed)

I have not changed anything on the system other than just install OMV.

DonJuane
Posts: 13
Joined: Tue Dec 15, 2020 1:15 am

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Fri Jun 11, 2021 4:23 pm

Another curiosity I have is where is the default hostname set up? I can TTY into my Pi using the address of "raspberrypi" which means something has have established that for my LAN network access, yet before I started the hostapd install the file /etc/dhcp.conf/ was completely empty (not even any comments in it) Of course it now looks like:

Code: Select all

denyinterfaces eth0 wlan0 wlan1



interface br0

epoch1970
Posts: 6511
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Cannot connect to pi configured with Hostapd (bridged AP)

Fri Jun 11, 2021 5:24 pm

Try this:
- download headless install & burn to SSD card
- alter boot image using Linux desktop to give SSH access
- use Ethernet client option to connectconnect the Pi to your router via Ethernet
- attempt to install Hostapd using the official guide.

Once your AP works, and it will unless you refuse to follow the guide,

- install OMV and try to find out what it breaks along the way
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Return to “Networking and servers”