Report wireless and/or network connectivity problems in this forum.
Moderator: Moderators
ViBE
Posts: 194 Joined: Sun Apr 19, 2015 6:58 pm
Post
by ViBE Fri Jul 14, 2017 4:34 am
I already noticed this but now I'm sure that after 5-7 days of run my Nexx WT3020 does not let my devices to connect. Not sure what should I check to figure out the problem but I only see this when a device tries to connect on wifi:
Code: Select all
Fri Jul 14 08:58:15 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x IEEE 802.11: authenticated
Fri Jul 14 08:58:15 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x IEEE 802.11: associated (aid 2)
Fri Jul 14 08:58:15 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x RADIUS: starting accounting session 5960AD33-00000040
Fri Jul 14 08:58:15 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x WPA: pairwise key handshake completed (RSN)
Fri Jul 14 08:58:15 2017 daemon.info dnsmasq-dhcp[3144]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Fri Jul 14 08:58:15 2017 daemon.info dnsmasq-dhcp[3144]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Fri Jul 14 08:58:18 2017 daemon.info dnsmasq-dhcp[3144]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Fri Jul 14 08:58:18 2017 daemon.info dnsmasq-dhcp[3144]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Fri Jul 14 08:58:22 2017 daemon.info dnsmasq-dhcp[3144]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Fri Jul 14 08:58:22 2017 daemon.info dnsmasq-dhcp[3144]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Fri Jul 14 08:58:29 2017 daemon.info dnsmasq-dhcp[3144]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Fri Jul 14 08:58:29 2017 daemon.info dnsmasq-dhcp[3144]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
I'm on 1.9.2. The devices see the network but cannot access.
Last edited by
ViBE on Fri Jul 14, 2017 5:18 am, edited 1 time in total.
ispyisail
Moderator
Posts: 5185 Joined: Mon Apr 06, 2009 3:15 amLocation: New Zealand
Post
by ispyisail Fri Jul 14, 2017 5:03 am
What is the flash size for that router?
ViBE
Posts: 194 Joined: Sun Apr 19, 2015 6:58 pm
Post
by ViBE Fri Jul 14, 2017 5:10 am
ispyisail wrote: What is the flash size for that router?
8 MB
ViBE
Posts: 194 Joined: Sun Apr 19, 2015 6:58 pm
Post
by ViBE Wed Sep 13, 2017 2:59 pm
Now after a restart it drops down every devices flooding the log with these continuously
Code: Select all
Wed Sep 13 20:40:14 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x IEEE 802.11: authenticated
Wed Sep 13 20:40:14 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x IEEE 802.11: associated (aid 2)
Wed Sep 13 20:40:14 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x RADIUS: starting accounting session 59B93DCD-00000007
Wed Sep 13 20:40:14 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x WPA: pairwise key handshake completed (RSN)
Wed Sep 13 20:40:14 2017 daemon.info dnsmasq-dhcp[2008]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:14 2017 daemon.info dnsmasq-dhcp[2008]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:19 2017 daemon.info dnsmasq-dhcp[2008]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:19 2017 daemon.info dnsmasq-dhcp[2008]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:24 2017 daemon.info dnsmasq-dhcp[2008]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:24 2017 daemon.info dnsmasq-dhcp[2008]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:32 2017 daemon.info dnsmasq-dhcp[2008]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:32 2017 daemon.info dnsmasq-dhcp[2008]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:47 2017 daemon.info dnsmasq-dhcp[2008]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:47 2017 daemon.info dnsmasq-dhcp[2008]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:51 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x IEEE 802.11: authenticated
Wed Sep 13 20:40:51 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x IEEE 802.11: associated (aid 2)
Wed Sep 13 20:40:51 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x RADIUS: starting accounting session 59B93DCD-00000008
Wed Sep 13 20:40:51 2017 daemon.info hostapd: wlan0: STA 3x:ax:ex:7x:2x:7x WPA: pairwise key handshake completed (RSN)
Wed Sep 13 20:40:51 2017 daemon.info dnsmasq-dhcp[2008]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:51 2017 daemon.info dnsmasq-dhcp[2008]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:56 2017 daemon.info dnsmasq-dhcp[2008]: DHCPDISCOVER(br-lan) 3x:ax:ex:7x:2x:7x
Wed Sep 13 20:40:56 2017 daemon.info dnsmasq-dhcp[2008]: DHCPOFFER(br-lan) 192.168.1.115 3x:ax:ex:7x:2x:7x
Meanwhile I found something different:
Code: Select all
Wed Sep 13 20:49:46 2017 kern.err kernel: [ 190.570000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:49:46 2017 kern.err kernel: [ 190.590000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:49:46 2017 kern.err kernel: [ 190.610000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:49:46 2017 kern.err kernel: [ 190.630000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:49:46 2017 kern.err kernel: [ 190.640000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:49:46 2017 kern.err kernel: [ 190.660000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:49:46 2017 kern.err kernel: [ 190.680000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:50:41 2017 kern.err kernel: [ 246.070000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:50:41 2017 kern.err kernel: [ 246.090000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:50:41 2017 kern.err kernel: [ 246.110000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Wed Sep 13 20:51:17 2017 kern.err kernel: [ 281.910000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
One last thing but I guess it's not related:
Code: Select all
Wed Sep 13 21:13:15 2017 daemon.warn miniupnpd[7858]: SSDP packet sender 169.254.198.51:51292 not from a LAN, ignoring
Wed Sep 13 21:13:16 2017 daemon.warn miniupnpd[7858]: SSDP packet sender 169.254.198.51:51292 not from a LAN, ignoring
Wed Sep 13 21:13:17 2017 daemon.warn miniupnpd[7858]: SSDP packet sender 169.254.198.51:51292 not from a LAN, ignoring
Wed Sep 13 21:13:18 2017 daemon.warn miniupnpd[7858]: SSDP packet sender 169.254.198.51:51292 not from a LAN, ignoring
ispyisail
Moderator
Posts: 5185 Joined: Mon Apr 06, 2009 3:15 amLocation: New Zealand
Post
by ispyisail Wed Sep 13, 2017 4:42 pm
Does the problem still occur after a re-flash?
ViBE
Posts: 194 Joined: Sun Apr 19, 2015 6:58 pm
Post
by ViBE Wed Sep 13, 2017 4:48 pm
ispyisail wrote: Does the problem still occur after a re-flash?
No.
ispyisail
Moderator
Posts: 5185 Joined: Mon Apr 06, 2009 3:15 amLocation: New Zealand
Post
by ispyisail Wed Sep 13, 2017 7:05 pm
ViBE wrote: ispyisail wrote: Does the problem still occur after a re-flash?
No.
No, you have fixed the problem with a reflash
or
No, you haven't tired a re-flash
??
ViBE
Posts: 194 Joined: Sun Apr 19, 2015 6:58 pm
Post
by ViBE Fri Sep 15, 2017 7:32 am
ispyisail wrote: ViBE wrote: ispyisail wrote: Does the problem still occur after a re-flash?
No.
No, you have fixed the problem with a reflash
or
No, you haven't tired a re-flash
??
Oh, so. I already did in the past. This installation is about 7 months old. I also noticed this problem on my other router (I have two of this model) but I didn't care too much cause I restarted the system frequently before. This is the first time when restarts cannot fix this problem.
ispyisail
Moderator
Posts: 5185 Joined: Mon Apr 06, 2009 3:15 amLocation: New Zealand
Post
by ispyisail Fri Sep 15, 2017 4:24 pm
hardware fail?
ViBE
Posts: 194 Joined: Sun Apr 19, 2015 6:58 pm
Post
by ViBE Sat Sep 16, 2017 3:13 pm
ispyisail wrote: hardware fail?
I guess not. No sign of that. It starts and runs well. On LAN the connection works but wifi devices stucks when try to get IP. After a few restarts the issue disappeared but as I said above the wifi problem come back around 7 days uptime.
