1 Temat przez dawidt

  • dawidt
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2015-11-09
  • Posty: 17

Temat: WDR3600 'radio0' is now down

Cześć,

mam problem z WDR3600, a mianowicie w losowych momentach urządzenie pracujące w trybie AP wyłącza obie karty wifi.
Mam na nim wgrane "OpenWrt 23.05-SNAPSHOT (r23310-680a4c7e12)", ale problem w takim samym stopniu występował na "luci-21.02-SNAPSHOT (r16847-f8282da11e)".
Żeby było ciekawiej mam dwa Archery C7 v5, pracujące w identycznej konfiguracji na "OpenWrt 22.03-SNAPSHOT r20060-f7541aecdc" i tutaj problem nie występuje. Dodam jeszcze, że sieć LAN działa na problematycznym urządzeniu bez najmniejszych kłopotów.
Poniżej część logów z System log.

Tue Aug  8 07:08:01 2023 kern.info kernel: [31632.489515] br-lan: port 2(phy0-ap0) entered blocking state
Tue Aug  8 07:08:01 2023 kern.info kernel: [31632.495233] br-lan: port 2(phy0-ap0) entered disabled state
Tue Aug  8 07:08:01 2023 kern.info kernel: [31632.501275] device phy0-ap0 entered promiscuous mode
Tue Aug  8 07:08:01 2023 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Aug  8 07:08:01 2023 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Tue Aug  8 07:08:01 2023 daemon.notice hostapd: phy0-ap0: interface state COUNTRY_UPDATE->ACS
Tue Aug  8 07:08:01 2023 daemon.notice hostapd: phy0-ap0: ACS-STARTED
Tue Aug  8 07:08:01 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy phy1-ap0) --> new PHY
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.194070] br-lan: port 3(phy1-ap0) entered blocking state
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.199807] br-lan: port 3(phy1-ap0) entered disabled state
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.205809] device phy1-ap0 entered promiscuous mode
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.211025] br-lan: port 3(phy1-ap0) entered blocking state
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.216767] br-lan: port 3(phy1-ap0) entered forwarding state
Tue Aug  8 07:08:01 2023 daemon.notice hostapd: phy1-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.415450] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.446842] vlan10: port 2(phy1-ap1) entered blocking state
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.452727] vlan10: port 2(phy1-ap1) entered disabled state
Tue Aug  8 07:08:01 2023 kern.info kernel: [31633.458893] device phy1-ap1 entered promiscuous mode
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.476683] vlan10: port 2(phy1-ap1) entered blocking state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.482369] vlan10: port 2(phy1-ap1) entered forwarding state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.488570] vlan10: port 2(phy1-ap1) entered disabled state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.665335] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap1: link becomes ready
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.672447] vlan10: port 2(phy1-ap1) entered blocking state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.678193] vlan10: port 2(phy1-ap1) entered forwarding state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.706671] vlan20: port 2(phy1-ap2) entered blocking state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.712386] vlan20: port 2(phy1-ap2) entered disabled state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.718463] device phy1-ap2 entered promiscuous mode
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.737894] vlan20: port 2(phy1-ap2) entered blocking state
Tue Aug  8 07:08:02 2023 kern.info kernel: [31633.743615] vlan20: port 2(phy1-ap2) entered forwarding state
Tue Aug  8 07:08:02 2023 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->ENABLED
Tue Aug  8 07:08:02 2023 kern.info kernel: [31634.019833] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap2: link becomes ready
Tue Aug  8 07:08:02 2023 daemon.notice hostapd: phy1-ap0: AP-ENABLED
Tue Aug  8 07:08:02 2023 daemon.notice netifd: Wireless device 'radio0' is now up
Tue Aug  8 07:08:03 2023 daemon.notice netifd: lan (5647): udhcpc: sending renew to server 192.168.1.1
Tue Aug  8 07:08:03 2023 daemon.notice netifd: lan (5647): udhcpc: lease of 192.168.1.50 obtained from 192.168.1.1, lease time 32400
Tue Aug  8 07:08:04 2023 daemon.notice netifd: Wireless device 'radio1' is now up
Tue Aug  8 07:08:04 2023 daemon.notice netifd: Network device 'phy1-ap0' link is up
Tue Aug  8 07:08:04 2023 daemon.notice netifd: Network device 'phy1-ap1' link is up
Tue Aug  8 07:08:04 2023 daemon.notice netifd: Network device 'phy1-ap2' link is up
Tue Aug  8 07:08:04 2023 daemon.notice netifd: lan (5647): udhcpc: sending renew to server 192.168.1.1
Tue Aug  8 07:08:04 2023 daemon.notice netifd: lan (5647): udhcpc: lease of 192.168.1.50 obtained from 192.168.1.1, lease time 32400
Tue Aug  8 07:08:04 2023 daemon.notice netifd: vlan10 (5565): udhcpc: sending renew to server 192.168.10.1
Tue Aug  8 07:08:04 2023 daemon.notice netifd: vlan10 (5565): udhcpc: lease of 192.168.10.9 obtained from 192.168.10.1, lease time 86400
Tue Aug  8 07:08:04 2023 daemon.notice netifd: vlan20 (5655): udhcpc: sending renew to server 192.168.20.1
Tue Aug  8 07:08:04 2023 daemon.notice netifd: vlan20 (5655): udhcpc: lease of 192.168.20.6 obtained from 192.168.20.1, lease time 86400
Tue Aug  8 07:08:08 2023 daemon.notice hostapd: phy0-ap0: ACS-COMPLETED freq=2472 channel=13
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.488411] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.495412] br-lan: port 2(phy0-ap0) entered blocking state
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.501148] br-lan: port 2(phy0-ap0) entered forwarding state
Tue Aug  8 07:08:09 2023 daemon.notice netifd: Network device 'phy0-ap0' link is up
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.520561] vlan10: port 3(phy0-ap1) entered blocking state
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.526323] vlan10: port 3(phy0-ap1) entered disabled state
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.532337] device phy0-ap1 entered promiscuous mode
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.547474] vlan10: port 3(phy0-ap1) entered blocking state
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.553160] vlan10: port 3(phy0-ap1) entered forwarding state
Tue Aug  8 07:08:09 2023 daemon.notice netifd: Network device 'phy0-ap1' link is up
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.835948] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap1: link becomes ready
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.864110] vlan20: port 3(phy0-ap2) entered blocking state
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.869894] vlan20: port 3(phy0-ap2) entered disabled state
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.875859] device phy0-ap2 entered promiscuous mode
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.889058] vlan20: port 3(phy0-ap2) entered blocking state
Tue Aug  8 07:08:09 2023 kern.info kernel: [31640.894776] vlan20: port 3(phy0-ap2) entered forwarding state
Tue Aug  8 07:08:09 2023 daemon.notice netifd: vlan10 (5565): udhcpc: sending renew to server 192.168.10.1
Tue Aug  8 07:08:09 2023 daemon.notice netifd: vlan10 (5565): udhcpc: lease of 192.168.10.9 obtained from 192.168.10.1, lease time 86400
Tue Aug  8 07:08:09 2023 daemon.notice netifd: Network device 'phy0-ap2' link is up
Tue Aug  8 07:08:09 2023 kern.info kernel: [31641.286637] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap2: link becomes ready
Tue Aug  8 07:08:09 2023 daemon.notice hostapd: phy0-ap0: interface state ACS->ENABLED
Tue Aug  8 07:08:09 2023 daemon.notice hostapd: phy0-ap0: AP-ENABLED
Tue Aug  8 07:08:09 2023 daemon.notice netifd: vlan20 (5655): udhcpc: sending renew to server 192.168.20.1
Tue Aug  8 07:08:09 2023 daemon.notice netifd: vlan20 (5655): udhcpc: lease of 192.168.20.6 obtained from 192.168.20.1, lease time 86400
Tue Aug  8 07:08:25 2023 daemon.info hostapd: phy0-ap2: STA 28:9c:6e:88:27:40 IEEE 802.11: authenticated
Tue Aug  8 07:08:25 2023 daemon.info hostapd: phy0-ap2: STA 28:9c:6e:88:27:40 IEEE 802.11: associated (aid 1)
Tue Aug  8 07:08:25 2023 daemon.notice hostapd: phy0-ap2: AP-STA-CONNECTED 28:9c:6e:88:27:40 auth_alg=open
Tue Aug  8 07:08:25 2023 daemon.info hostapd: phy0-ap2: STA 28:9c:6e:88:27:40 WPA: pairwise key handshake completed (RSN)
Tue Aug  8 07:08:25 2023 daemon.notice hostapd: phy0-ap2: EAPOL-4WAY-HS-COMPLETED 28:9c:6e:88:27:40
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: Remove interface 'phy1-ap0'
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy1-ap0: interface state ENABLED->DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy1-ap2: AP-DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy1-ap2: CTRL-EVENT-TERMINATING
Tue Aug  8 07:12:26 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Aug  8 07:12:26 2023 daemon.notice netifd: Network device 'phy1-ap2' link is down
Tue Aug  8 07:12:26 2023 kern.info kernel: [31897.639293] vlan20: port 2(phy1-ap2) entered disabled state
Tue Aug  8 07:12:26 2023 kern.info kernel: [31897.649980] device phy1-ap2 left promiscuous mode
Tue Aug  8 07:12:26 2023 kern.info kernel: [31897.654846] vlan20: port 2(phy1-ap2) entered disabled state
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap2 from bridge vlan20: No such device
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy1-ap1: AP-DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy1-ap1: CTRL-EVENT-TERMINATING
Tue Aug  8 07:12:26 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Aug  8 07:12:26 2023 daemon.notice netifd: Network device 'phy1-ap1' link is down
Tue Aug  8 07:12:26 2023 kern.info kernel: [31897.814474] vlan10: port 2(phy1-ap1) entered disabled state
Tue Aug  8 07:12:26 2023 kern.info kernel: [31897.828632] device phy1-ap1 left promiscuous mode
Tue Aug  8 07:12:26 2023 kern.info kernel: [31897.833562] vlan10: port 2(phy1-ap1) entered disabled state
Tue Aug  8 07:12:26 2023 daemon.notice netifd: vlan20 (5655): udhcpc: sending renew to server 192.168.20.1
Tue Aug  8 07:12:26 2023 daemon.notice netifd: vlan20 (5655): udhcpc: lease of 192.168.20.6 obtained from 192.168.20.1, lease time 86400
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap1 from bridge vlan10: No such device
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Tue Aug  8 07:12:26 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.060266] device phy1-ap0 left promiscuous mode
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.065216] br-lan: port 3(phy1-ap0) entered disabled state
Tue Aug  8 07:12:26 2023 daemon.notice netifd: Network device 'phy1-ap0' link is down
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: Remove interface 'phy0-ap0'
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap0: interface state ENABLED->DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap2: AP-STA-DISCONNECTED 28:9c:6e:88:27:40
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap2: AP-DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap2: CTRL-EVENT-TERMINATING
Tue Aug  8 07:12:26 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Aug  8 07:12:26 2023 daemon.notice netifd: Network device 'phy0-ap2' link is down
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.172506] vlan20: port 3(phy0-ap2) entered disabled state
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.193311] device phy0-ap2 left promiscuous mode
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.198114] vlan20: port 3(phy0-ap2) entered disabled state
Tue Aug  8 07:12:26 2023 daemon.notice netifd: vlan10 (5565): udhcpc: sending renew to server 192.168.10.1
Tue Aug  8 07:12:26 2023 daemon.notice netifd: vlan10 (5565): udhcpc: lease of 192.168.10.9 obtained from 192.168.10.1, lease time 86400
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap1: AP-DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap1: CTRL-EVENT-TERMINATING
Tue Aug  8 07:12:26 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Aug  8 07:12:26 2023 daemon.notice netifd: Network device 'phy0-ap1' link is down
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.295990] vlan10: port 3(phy0-ap1) entered disabled state
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.334320] device phy0-ap1 left promiscuous mode
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.339126] vlan10: port 3(phy0-ap1) entered disabled state
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Tue Aug  8 07:12:26 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Aug  8 07:12:26 2023 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.454749] device phy0-ap0 left promiscuous mode
Tue Aug  8 07:12:26 2023 kern.info kernel: [31898.459717] br-lan: port 2(phy0-ap0) entered disabled state
Tue Aug  8 07:12:27 2023 daemon.notice netifd: Wireless device 'radio1' is now down
Tue Aug  8 07:12:27 2023 daemon.notice netifd: Network device 'phy0-ap0' link is down
Tue Aug  8 07:12:27 2023 daemon.notice netifd: vlan20 (5655): udhcpc: sending renew to server 192.168.20.1
Tue Aug  8 07:12:27 2023 daemon.notice netifd: vlan20 (5655): udhcpc: lease of 192.168.20.6 obtained from 192.168.20.1, lease time 86400
Tue Aug  8 07:12:27 2023 daemon.notice netifd: lan (5647): udhcpc: sending renew to server 192.168.1.1
Tue Aug  8 07:12:27 2023 daemon.notice netifd: lan (5647): udhcpc: lease of 192.168.1.50 obtained from 192.168.1.1, lease time 32400
Tue Aug  8 07:12:27 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Tue Aug  8 07:12:27 2023 daemon.notice netifd: vlan10 (5565): udhcpc: sending renew to server 192.168.10.1
Tue Aug  8 07:12:27 2023 daemon.notice netifd: vlan10 (5565): udhcpc: lease of 192.168.10.9 obtained from 192.168.10.1, lease time 86400
Tue Aug  8 07:12:28 2023 daemon.notice netifd: lan (5647): udhcpc: sending renew to server 192.168.1.1
Tue Aug  8 07:12:28 2023 daemon.notice netifd: lan (5647): udhcpc: lease of 192.168.1.50 obtained from 192.168.1.1, lease time 32400
Tue Aug  8 08:23:58 2023 daemon.err uhttpd[2092]: [info] luci: accepted login on /admin/dashboard for root from 192.168.1.204

Konfiguracja wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/ahb/18100000.wmac'
        option band '2g'
        option htmode 'HT20'
        option country 'PL'
        option channel 'auto'
        option cell_density '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'SSID'
        option encryption 'psk2+ccmp'
        option key 'pass'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'pci0000:00/0000:00:00.0'
        option channel '36'
        option band '5g'
        option htmode 'HT20'
        option country 'PL'
        option cell_density '0'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'SSID'
        option encryption 'psk2'
        option key 'pass'

config wifi-iface 'wifinet3'
        option device 'radio0'
        option mode 'ap'
        option encryption 'psk2+ccmp'
        option ssid 'SSID-Guest'
        option key 'pass'
        option network 'vlan10'

config wifi-iface 'wifinet4'
        option device 'radio0'
        option mode 'ap'
        option ssid 'SSID-IoT'
        option encryption 'psk2+ccmp'
        option key 'pass'
        option network 'vlan20'

config wifi-iface 'wifinet5'
        option device 'radio1'
        option mode 'ap'
        option ssid 'SSID-Guest'
        option key 'pass'
        option network 'vlan10'
        option encryption 'psk2+ccmp'


config wifi-iface 'wifinet6'
        option device 'radio1'
        option mode 'ap'
        option ssid 'SSID-IoT'
        option encryption 'psk2+ccmp'
        option key 'pass'
        option network 'vlan20'

Konfiguracja network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fda5:aa8f:4fa2::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'
        option ipv6 '0'

config interface 'lan'
        option device 'br-lan'
        option proto 'dhcp'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option vid '1'
        option ports '0t 2 3 4 5 1'

config switch_vlan
        option device 'switch0'
        option vlan '3'
        option vid '20'
        option ports '0t 2t 1t'

config switch_vlan
        option device 'switch0'
        option vlan '4'
        option vid '10'
        option ports '0t 2t 1t'

config device
        option type 'bridge'
        option name 'vlan10'
        list ports 'eth0.10'
        option ipv6 '0'

config device
        option name 'vlan20'
        option type 'bridge'
        list ports 'eth0.20'
        option ipv6 '0'

config interface 'vlan10'
        option proto 'dhcp'
        option device 'vlan10'

config interface 'vlan20'
        option proto 'dhcp'
        option device 'vlan20'

Proszę o pomoc. ;-)

Pozdrawiam
Dawid

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,074

Odp: WDR3600 'radio0' is now down

Na początek to wywal to auto z radio0 i ustaw na stałe kanał, zmeń tego dhcp w lanie i vlan10 na stałe adresy. Zrestartuj i zobacz jak się będzie tak zachowywał.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

3 Odpowiedź przez pepino

  • pepino
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2010-05-01
  • Posty: 137

Odp: WDR3600 'radio0' is now down

Na moim WDR3600 z OpenWrt 23.05-SNAPSHOT (r24016-f791ec1f6d) jest dokładnie to samo. Zmiana kanału na sztywno na najmniej oblegany nic nie dała. Ustawienie najmniejszej, możliwej szerokości - również. Aba radia się składają, chociaż na 5GHz jest czysto w okolicy

Fri Aug  9 00:40:45 2024 kern.info kernel: [142111.427096] br-lan: port 3(phy0-ap0) entered disabled state
Fri Aug  9 00:40:45 2024 kern.info kernel: [142111.486633] br-lan: port 3(phy0-ap0) entered disabled state
Fri Aug  9 00:40:45 2024 kern.info kernel: [142111.499333] br-lan: port 3(phy0-ap0) entered disabled state
Fri Aug  9 00:40:45 2024 kern.info kernel: [142112.091206] br-lan: port 3(phy0-ap0) entered blocking state
Fri Aug  9 00:40:45 2024 kern.info kernel: [142112.097098] br-lan: port 3(phy0-ap0) entered disabled state
Fri Aug  9 00:40:45 2024 kern.info kernel: [142112.103356] device phy0-ap0 entered promiscuous mode
Fri Aug  9 00:40:45 2024 kern.info kernel: [142112.175237] br-lan: port 3(phy0-ap0) entered blocking state
Fri Aug  9 00:40:45 2024 kern.info kernel: [142112.181049] br-lan: port 3(phy0-ap0) entered forwarding state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142112.197246] br-lan: port 3(phy0-ap0) entered disabled state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142112.263723] br-lan: port 3(phy0-ap0) entered blocking state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142112.269539] br-lan: port 3(phy0-ap0) entered disabled state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142112.275805] device phy0-ap0 entered promiscuous mode
Fri Aug  9 00:40:46 2024 kern.info kernel: [142112.281203] br-lan: port 3(phy0-ap0) entered blocking state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142112.287023] br-lan: port 3(phy0-ap0) entered forwarding state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142112.431507] br-lan: port 3(phy0-ap0) entered disabled state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142113.114561] br-lan: port 3(phy0-ap0) entered blocking state
Fri Aug  9 00:40:46 2024 kern.info kernel: [142113.120376] br-lan: port 3(phy0-ap0) entered forwarding state
Fri Aug  9 00:43:25 2024 kern.info kernel: [142271.316306] br-lan: port 2(phy1-ap0) entered disabled state
Fri Aug  9 00:43:25 2024 kern.info kernel: [142271.349664] br-lan: port 2(phy1-ap0) entered disabled state
Fri Aug  9 00:43:25 2024 kern.info kernel: [142271.363073] br-lan: port 2(phy1-ap0) entered disabled state
Fri Aug  9 00:43:25 2024 kern.info kernel: [142271.393214] br-lan: port 2(phy1-ap0) entered blocking state
Fri Aug  9 00:43:25 2024 kern.info kernel: [142271.399110] br-lan: port 2(phy1-ap0) entered disabled state
Fri Aug  9 00:43:25 2024 kern.info kernel: [142271.405321] device phy1-ap0 entered promiscuous mode

4 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,074

Odp: WDR3600 'radio0' is now down

entered promiscuous mode ? Masz jakiś program który przestawia radio w tryb skanowania/monitora? tcdump, travelmater?

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

5 Odpowiedź przez pepino (edytowany przez pepino 2024-08-09 12:24:04)

  • pepino
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2010-05-01
  • Posty: 137

Odp: WDR3600 'radio0' is now down

Nie mam. Właściwie to nie doinstalowywałem czegokolwiek, bo to co jest w twoim buildzie wystarcza do wszystkiego.
Jedyne, co by to skanowanie mogło wywołać to moje klikanie w analiza kanałów via www, które faktycznie miało miejsce ale nie w tym momencie. Robiłem je kilka-kilkanaście godzin wcześniej w celu wybrania właściwego kanału. Dla 2.4GHz mam option noscan '1', ale to już raczej zbędne, bo wróciłem testowo do option htmode 'HT20' (wcześniej było 40).
Dla 5Ghz dalej używam agregacji, brak noscan.

Z mniej typowych rzeczy to używam tam wireguarda w trybie klienta + forwardowanie z lan do wg, no ale to raczej nic wspólnego z radiem nie ma.

Edit:
Mój model to 4300, a nie jak wcześniej napisałem 3600.

6 Odpowiedź przez pepino

  • pepino
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2010-05-01
  • Posty: 137

Odp: WDR3600 'radio0' is now down

To tylko tak uzupełnie - dla 2.4Ghz wyłączenie agregacji pasm rozwiązało problem. Dla 5GHz musiałem przenieść się na kanał 48 i mimo włączonej agregacji problemu nie ma. Wcześniej używałem kanałów powyżej 100 i widać jakieś stacje meteo/radary musiały to powodować.