Bridge: br-lan Wireless: wlan0 with hostapd smartphone (wlan) can talk to tv (ethernet) smartphone (wlan) can talk to internet smartphone (wlan) can talk to host smartphone (wlan) can *no longer* talk to avr (wlan) smartphone (lwan) can *no longer* talk to blueray-player (wlan) no connection from yamaha AVR app to RX-A880 receiver no ping from smartphone to RX-A880 receiver from the host running the bridge and hostapd i can ping and connect to any other device no matter if it's wlan or ethernet in mordern networks with only smartphones and notebooks this would be a showstopper 5.14.7-200.fc34.x86_64 -------------------------- reboot with 5.13.19 and all works as the years before, every device can talk to any other device no matter if it's connected to the ethernet bridge or via wlan on the same hostapd access point -------------------------- [root@srv-rhsoft:~]$ cat /etc/hostapd/hostapd.conf bssid=02:ab:cd:ef:12:30 driver=nl80211 hw_mode=g country_code=AT channel=acs_survey ctrl_interface=/run/hostapd ctrl_interface_group=0 ################################################################ # wlan0 # ################################################################ interface=wlan0 ssid=rhsoft-hardened wpa_passphrase=****** bridge=br-lan wpa=2 rsn_pairwise=CCMP logger_syslog=-1 logger_syslog_level=2 ieee80211ac=1 ieee80211d=1 ieee80211h=1 ieee80211n=1 wme_enabled=1 wmm_enabled=1 require_ht=1 ht_capab=[HT20][HT40][SHORT-GI-40][DSSS_CCK-40][MAX-AMSDU-3839] ################################################################ # wlan1 # ################################################################ bss=wlan1 ssid=rhsoft-guest wpa_passphrase=****** bridge=br-guest wpa=2 rsn_pairwise=CCMP logger_syslog=-1 logger_syslog_level=2 ieee80211ac=1 ieee80211d=1 ieee80211h=1 ieee80211n=1 wme_enabled=1 wmm_enabled=1 require_ht=1 ht_capab=[HT20][HT40][SHORT-GI-40][DSSS_CCK-40][MAX-AMSDU-3839] -------------------------- [root@srv-rhsoft:~]$ /usr/sbin/ip link show master br-lan 2: poe-spare: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master br-lan state DOWN mode DEFAULT group default qlen 1000 link/ether 00:e0:4c:80:5c:ca brd ff:ff:ff:ff:ff:ff altname enp5s0 3: poe-phone: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP mode DEFAULT group default qlen 1000 link/ether 00:e0:4c:80:5c:cb brd ff:ff:ff:ff:ff:ff altname enp6s0 6: lan-spare2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan state DOWN mode DEFAULT group default qlen 1000 link/ether ac:16:2d:a1:74:ed brd ff:ff:ff:ff:ff:ff altname enp1s0f1 7: lan-spare1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan state DOWN mode DEFAULT group default qlen 1000 link/ether ac:16:2d:a1:74:ee brd ff:ff:ff:ff:ff:ff altname enp1s0f2 8: lan-tv: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan state DOWN mode DEFAULT group default qlen 1000 link/ether ac:16:2d:a1:74:ef brd ff:ff:ff:ff:ff:ff altname enp1s0f3 9: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP mode DEFAULT group default qlen 1000 link/ether 02:ab:cd:ef:12:30 brd ff:ff:ff:ff:ff:ff permaddr 28:10:7b:ca:be:51 altname wlp2s0
02:00.0 Network controller: Qualcomm Atheros AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01) Subsystem: D-Link System Inc DWA-556 Xtreme N PCI Express Desktop Adapter Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f7b00000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Kernel driver in use: ath9k Kernel modules: ath9k
upstream bugreport: https://bugzilla.kernel.org/show_bug.cgi?id=214531
5.14.11-200.fc34.x86_64 seems to fix the problem, maybe it's one of the mac80211 relevant changes in 5.14.10 but none of the changelogs at kernel.org from 5.14.9 to 5.14.11 really explains the fix - at least for me
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.