• Zarejestrowany: 2017-06-10
  • Posty: 100

Temat: wrt32x gubi siec 5Ghz

Cześć,

Co jakiś czas zdarza się, że router rozłacza siec 5Ghz (dioda na routerze od 5Ghz gaśnie)

Restart sprzętu naprawia problem. Jak zdiagnozować przyczynę?

Wersja softu najnowsza dostępna, oczywiście by Obsy wink
LuCI openwrt-18.06 branch (git-19.051.55698-76cf653) / OpenWrt 18.06-SNAPSHOT r7714-4918fe0291

Pozdrawiam serdecznie

WRT32X - Luci OpenWRT
Archer C7 -  Luci OpenWRT

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,714

Odp: wrt32x gubi siec 5Ghz

W linksysach są średniej jakości sterowniki do wifi, ludzie na nie narzekają. Jeżeli w logach nic nie znajdziesz to "ten typ tak ma" i nic z tym nie zrobisz.

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

Cezary's Strona

3 Odpowiedź przez steel_rat

  • Zarejestrowany: 2017-04-30
  • Posty: 566

Odp: wrt32x gubi siec 5Ghz

Patrz w logi. Masz log kernela i systemowy. Wrzuć tu co tam wyskakuje w momencie rozłączenia. Te sterowniki są podobno coraz lepsze.

  • Zarejestrowany: 2017-06-10
  • Posty: 100

Odp: wrt32x gubi siec 5Ghz

Cześć,

Udało mi się załapać w logu moment padania sieci. Wygląda mi to na problem z kanałami / DFS. Zmieniałem wcześniej kraj z PL na FR i odwrotnie i dzieje się tak samo.

Jakieś pomysły? Czy tylko zmiana kanału? Byłaby wielka szkoda smile

Tue Apr 16 23:27:04 2019 daemon.notice hostapd: wlan0: DFS-NOP-FINISHED freq=5500 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5500 cf2=0
Tue Apr 16 23:27:04 2019 daemon.notice hostapd: wlan0: DFS-NOP-FINISHED freq=5520 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5520 cf2=0
Tue Apr 16 23:27:04 2019 daemon.notice hostapd: wlan0: DFS-NOP-FINISHED freq=5540 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5540 cf2=0
Tue Apr 16 23:27:04 2019 daemon.notice hostapd: wlan0: DFS-NOP-FINISHED freq=5560 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5560 cf2=0
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: DFS-RADAR-DETECTED freq=5260 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5290 cf2=0
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: DFS-NEW-CHANNEL freq=5500 chan=100 sec_chan=1
Tue Apr 16 23:27:46 2019 daemon.warn hostapd: DFS failed to schedule CSA (-22) - trying fallback
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 6c:c7:ed:5c:33:c5
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 04:69:f5:64:f7:96
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED a8:db:04:23:10:5f
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f0:18:93:1e:37:c9
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED c0:d2:ff:ee:1f:34
Tue Apr 16 23:27:46 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Tue Apr 16 23:27:46 2019 kern.info kernel: [77128.576465] ieee80211 phy0: radar detected by firmware
Tue Apr 16 23:27:46 2019 kern.info kernel: [77128.614079] device wlan0 left promiscuous mode
Tue Apr 16 23:27:46 2019 kern.info kernel: [77128.618590] br-lan: port 2(wlan0) entered disabled state
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77128.758286] ieee80211 phy0: staid 3 deleted
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77128.776447] ieee80211 phy0: staid 5 deleted
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77128.793329] ieee80211 phy0: staid 4 deleted
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77128.813316] ieee80211 phy0: staid 2 deleted
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77128.833349] ieee80211 phy0: staid 1 deleted
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77128.853209] ieee80211 phy0: change: 0x40
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77128.952170] ieee80211 phy0: change: 0x100
Tue Apr 16 23:27:47 2019 daemon.notice netifd: Network device 'wlan0' link is down
Tue Apr 16 23:27:47 2019 daemon.info avahi-daemon[2698]: Interface wlan0.IPv6 no longer relevant for mDNS.
Tue Apr 16 23:27:47 2019 daemon.info avahi-daemon[2698]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fd80::6038:e0ff:fece:70da.
Tue Apr 16 23:27:47 2019 daemon.info avahi-daemon[2698]: Withdrawing address record for fd80::6038:e0ff:fece:70da on wlan0.
Tue Apr 16 23:27:47 2019 daemon.notice hostapd: wlan0: interface state ENABLED->DISABLED
Tue Apr 16 23:27:47 2019 kern.debug kernel: [77129.167258] ieee80211 phy0: change: 0xffffffff
Tue Apr 16 23:27:47 2019 kern.info kernel: [77129.276344] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Tue Apr 16 23:27:47 2019 kern.info kernel: [77129.283087] br-lan: port 2(wlan0) entered blocking state
Tue Apr 16 23:27:47 2019 kern.info kernel: [77129.288438] br-lan: port 2(wlan0) entered disabled state
Tue Apr 16 23:27:47 2019 kern.info kernel: [77129.293866] device wlan0 entered promiscuous mode
Tue Apr 16 23:27:47 2019 daemon.notice hostapd: wlan0: interface state DISABLED->COUNTRY_UPDATE
Tue Apr 16 23:27:47 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:47 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:48 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:48 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:48 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:51 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:51 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:52 2019 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->DFS
Tue Apr 16 23:27:52 2019 daemon.notice hostapd: wlan0: DFS-CAC-START freq=5500 chan=100 sec_chan=1, width=1, seg0=106, seg1=0, cac_time=60s
Tue Apr 16 23:27:52 2019 kern.debug kernel: [77134.301578] ieee80211 phy0: change: 0x100
Tue Apr 16 23:27:52 2019 kern.debug kernel: [77134.314622] ieee80211 phy0: change: 0x62
Tue Apr 16 23:27:52 2019 kern.debug kernel: [77134.415066] ieee80211 phy0: change: 0x20
Tue Apr 16 23:27:52 2019 kern.debug kernel: [77134.419016] ieee80211 phy0: change: 0x40
Tue Apr 16 23:27:53 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:27:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:00 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:02 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:02 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:03 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:03 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:03 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:03 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:10 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:10 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:10 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:10 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:10 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:17 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:17 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:17 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:18 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:18 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:18 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:21 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:25 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:25 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:26 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:26 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:26 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:32 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:33 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:33 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:33 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:40 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:40 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:40 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:40 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:45 2019 daemon.info hostapd: wlan1: STA f0:18:98:1e:37:c9 IEEE 802.11: associated (aid 2)
Tue Apr 16 23:28:45 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED f0:18:98:1d:37:c9
Tue Apr 16 23:28:45 2019 daemon.info hostapd: wlan1: STA f0:18:98:1e:37:c9 WPA: pairwise key handshake completed (RSN)
Tue Apr 16 23:28:46 2019 daemon.info dnsmasq-dhcp[3643]: DHCPDISCOVER(br-lan) f0:18:98:1d:37:c9
Tue Apr 16 23:28:46 2019 daemon.info dnsmasq-dhcp[3643]: DHCPOFFER(br-lan) 192.168.1.236 f0:18:98:1d:37:c9
Tue Apr 16 23:28:47 2019 daemon.info dnsmasq-dhcp[3643]: DHCPREQUEST(br-lan) 192.168.1.236 f0:18:97:1e:37:c9
Tue Apr 16 23:28:47 2019 daemon.info dnsmasq-dhcp[3643]: DHCPACK(br-lan) 192.168.1.236 f0:18:97:1e:37:c9 macbook
Tue Apr 16 23:28:47 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:47 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:48 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:48 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:48 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:48 2019 daemon.info hostapd: wlan1: STA f0:19:98:1e:37:c9 IEEE 802.11: authenticated
Tue Apr 16 23:28:49 2019 daemon.warn odhcpd[2013]: DHCPV6 SOLICIT IA_NA from 0001000123762342f018981e37c9 on br-lan: ok fde3:5c15:c500::2a5/128
Tue Apr 16 23:28:50 2019 daemon.warn odhcpd[2013]: DHCPV6 REQUEST IA_NA from 0001000123762342f018981e37c9 on br-lan: ok fde3:5d15:c500::2a5/128
Tue Apr 16 23:28:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:55 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Apr 16 23:28:56 2019 kern.debug kernel: [77198.458294] ieee80211 phy0: change: 0x60
Tue Apr 16 23:28:56 2019 kern.debug kernel: [77198.558318] ieee80211 phy0: change: 0x100
Tue Apr 16 23:28:56 2019 daemon.notice hostapd: wlan0: DFS-CAC-COMPLETED success=1 freq=5500 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5530 cf2=0
Tue Apr 16 23:28:56 2019 daemon.err hostapd: Using interface wlan0 with hwaddr 62:38:e1:ce:70:da and ssid "test 5GHz"
Tue Apr 16 23:28:56 2019 kern.debug kernel: [77198.571793] ieee80211 phy0: change: 0x100
Tue Apr 16 23:28:56 2019 kern.debug kernel: [77198.584841] ieee80211 phy0: change: 0x42

WRT32X - Luci OpenWRT
Archer C7 -  Luci OpenWRT

5 Odpowiedź przez Królik

  • Skąd: Warszawa
  • Zarejestrowany: 2015-07-10
  • Posty: 1,101

Odp: wrt32x gubi siec 5Ghz

Ja bym wybrał kanał bez DFS albo szukał takiego, gdzie DFS nie wariuje.

Mam i używam: Fujitsu Futro S720, Netgear R6220, Unielec U7621-06, TP-Linki 1043 V1, V2, Linksysy EA7500v2, AeroHive AP350, Linksys EA8500, ZTE MF286d.
Mam: D-Linki DWR-921, DWR-118, DWR-116, TP-Link WDR-4900 v1, Checkpoint L-50, Linksysy 1900ACS, LB-Link BL-W1200,

Królik's Strona

6 Odpowiedź przez steel_rat

  • Zarejestrowany: 2017-04-30
  • Posty: 566

Odp: wrt32x gubi siec 5Ghz

Ciekawostką jest to, że musisz mieć ustawiony region FR. A jak już zmieniłeś region to najlepiej usuń plik z ustawieniami wifi i zresetuj router. Potem ustaw jeszcze raz bez zmiany regionu.