I have been using the GL-AR750S for about 1 month now. I love it except it disconnects every 30 mins. On the dot. Every 30 mins. I’ve tried many suggestions in this forum and to no avail. I’ve upgraded the router to the latest beta firmware and I’ve downgraded back to 3.009. I’ve killed and deleted gl_health and installed travelmate and luci-app-travelmate.
I’m connecting to a wireless router which has a captive portal however they allow you to register a MAC address and the device will be permanently connected. I’ve registered the MAC of the router and it successfully connects.
I typically use OpenVPN but I’ve tested both with a
nd without and it’s still the same every 30 mins. See the log below for the last two occurrences. I’m really hoping someone can provide some assistance…
Thank you!!
EDIT: Upon further review of these two I’m noticing one is referencing wlan1-1 link is down affecting trm_wwam for travelmate and the second one is referencing wlan-sta…
Occurrence 1:
Tue Jun 18 07:17:54 2019 daemon.notice netifd: Network device ‘wlan1-1’ link is down
Tue Jun 18 07:17:54 2019 daemon.notice netifd: Interface ‘trm_wwan’ has link connectivity loss
Tue Jun 18 07:17:54 2019 daemon.notice netifd: trm_wwan (20762): udhcpc: received SIGTERM
Tue Jun 18 07:17:54 2019 kern.info kernel: [38811.944405] wlan1-1: authenticate with 6c:b2:ae:31:3a:b2
Tue Jun 18 07:17:54 2019 kern.info kernel: [38811.950207] wlan1-1: send auth to 6c:b2:ae:31:3a:b2 (try 1/3)
Tue Jun 18 07:17:54 2019 kern.info kernel: [38811.957563] wlan1-1: authenticated
Tue Jun 18 07:17:54 2019 kern.info kernel: [38811.985943] wlan1-1: associate with 6c:b2:ae:31:3a:b2 (try 1/3)
Tue Jun 18 07:17:54 2019 kern.info kernel: [38811.996083] wlan1-1: RX AssocResp from 6c:b2:ae:31:3a:b2 (capab=0x421 status=0 aid=5)
Tue Jun 18 07:17:54 2019 kern.info kernel: [38812.004521] wlan1-1: associated
Tue Jun 18 07:17:54 2019 daemon.notice netifd: Network device ‘wlan1-1’ link is up
Tue Jun 18 07:17:54 2019 daemon.notice netifd: Interface ‘trm_wwan’ has link connectivity
Tue Jun 18 07:17:54 2019 daemon.notice netifd: Interface ‘trm_wwan’ is setting up now
Tue Jun 18 07:17:54 2019 kern.debug kernel: [38812.061709] wlan1-1: Limiting TX power to 23 dBm as advertised by 6c:b2:ae:31:3a:b2
Tue Jun 18 07:17:55 2019 daemon.notice netifd: trm_wwan (22684): udhcpc: started, v1.28.3
Tue Jun 18 07:17:55 2019 daemon.notice netifd: Network device ‘wlan1’ link is down
Tue Jun 18 07:17:55 2019 kern.info kernel: [38812.395944] br-lan: port 3(wlan1) entered disabled state
Tue Jun 18 07:17:55 2019 daemon.notice netifd: trm_wwan (22684): udhcpc: sending discover
Tue Jun 18 07:17:55 2019 kern.info kernel: [38812.979772] br-lan: port 3(wlan1) entered blocking state
Tue Jun 18 07:17:55 2019 kern.info kernel: [38812.985273] br-lan: port 3(wlan1) entered forwarding state
Tue Jun 18 07:17:55 2019 daemon.notice netifd: Network device ‘wlan1’ link is up
Tue Jun 18 07:17:56 2019 daemon.notice netifd: trm_wwan (22684): udhcpc: sending select for 10.0.0.17
Tue Jun 18 07:17:56 2019 daemon.notice netifd: trm_wwan (22684): udhcpc: lease of 10.0.0.17 obtained, lease time 900
Tue Jun 18 07:17:56 2019 daemon.notice netifd: Interface ‘trm_wwan’ is now up
Tue Jun 18 07:17:58 2019 user.notice firewall: Reloading firewall due to ifup of trm_wwan (wlan1-1)
Then 30 mins later:
Tue Jun 18 07:37:36 2019 daemon.notice netifd: wwan (15533): udhcpc: sending renew to 10.0.0.1
Tue Jun 18 07:37:36 2019 daemon.notice netifd: wwan (15533): udhcpc: lease of 10.0.0.245 obtained, lease time 900
Tue Jun 18 07:37:45 2019 kern.info kernel: [40002.655812] wlan-sta: disassociated from 6c:b2:ae:31:3a:b2 (Reason: 1=UNSPECIFIED)
Tue Jun 18 07:37:45 2019 daemon.notice netifd: Network device ‘wlan-sta’ link is down
Tue Jun 18 07:37:45 2019 daemon.notice netifd: Interface ‘wwan’ has link connectivity loss
Tue Jun 18 07:37:45 2019 daemon.notice netifd: wwan (15533): udhcpc: received SIGTERM
Tue Jun 18 07:37:46 2019 daemon.notice netifd: Network device ‘wlan1’ link is down
Tue Jun 18 07:37:46 2019 kern.info kernel: [40003.704733] br-lan: port 3(wlan1) entered disabled state
Tue Jun 18 07:37:48 2019 kern.info kernel: [40006.182656] wlan-sta: authenticate with 6c:b2:ae:31:3a:b2
Tue Jun 18 07:37:48 2019 kern.info kernel: [40006.188587] wlan-sta: send auth to 6c:b2:ae:31:3a:b2 (try 1/3)
Tue Jun 18 07:37:48 2019 kern.info kernel: [40006.197171] wlan-sta: authenticated
Tue Jun 18 07:37:49 2019 kern.info kernel: [40006.204811] wlan-sta: associate with 6c:b2:ae:31:3a:b2 (try 1/3)
Tue Jun 18 07:37:49 2019 kern.info kernel: [40006.215843] wlan-sta: RX AssocResp from 6c:b2:ae:31:3a:b2 (capab=0x421 status=0 aid=9)
Tue Jun 18 07:37:49 2019 kern.info kernel: [40006.224352] wlan-sta: associated
Tue Jun 18 07:37:49 2019 daemon.notice netifd: Network device ‘wlan-sta’ link is up
Tue Jun 18 07:37:49 2019 daemon.notice netifd: Interface ‘wwan’ has link connectivity
Tue Jun 18 07:37:49 2019 daemon.notice netifd: Interface ‘wwan’ is setting up now
Tue Jun 18 07:37:49 2019 kern.debug kernel: [40006.285717] wlan-sta: Limiting TX power to 23 dBm as advertised by 6c:b2:ae:31:3a:b2
Tue Jun 18 07:37:49 2019 daemon.notice netifd: wwan (1019): udhcpc: started, v1.28.3
Tue Jun 18 07:37:49 2019 daemon.notice netifd: wwan (1019): udhcpc: sending discover
Tue Jun 18 07:37:49 2019 daemon.notice netifd: wwan (1019): udhcpc: sending select for 10.0.0.245
Tue Jun 18 07:37:49 2019 kern.info kernel: [40006.717405] br-lan: port 3(wlan1) entered blocking state
Tue Jun 18 07:37:49 2019 kern.info kernel: [40006.722901] br-lan: port 3(wlan1) entered forwarding state
Tue Jun 18 07:37:49 2019 daemon.notice netifd: Network device ‘wlan1’ link is up
Tue Jun 18 07:37:49 2019 daemon.notice netifd: wwan (1019): udhcpc: lease of 10.0.0.245 obtained, lease time 900
Tue Jun 18 07:37:49 2019 daemon.notice netifd: Interface ‘wwan’ is now up
I’m guessing that, for some reason, your upstream provider is dropping your connection when you renew your DHCP lease. DHCP is on a “timer” based on the lease parameters sent to you by the server (900 seconds = 15 minutes), so “exactly 30 minutes” wouldn’t be surprising.
The first two lines are the lease renewal, the next three are the wireless disconnecting.
If you really want to track it down, installing tcpdump-mini and some command-line work would be involved the way I would approach it.
I’ve installed tcpdump-mini as suggested and this is the result dump during my latest outage. I’m hoping there’s someone on here more knowledgeable then me who can read this and provide further details…
Note my logfile states link goes down at 13:40:34…
@stibbo
From the log, I think it is a restriction on the upper level DHCP Server. The authentication can only be connected for up to 30 minutes（I guess the DHCP lease can be renewed at most once.）. I saw that the IP address has changed after connecting again.
Also，what version of the latest firmware are you using?
Please use the firmware version 3.025 to test .
the firmware download address:GL.iNet download center
note:
Please do not remove the gl_health package, I have optimized it for connecting to portal wifi.If the 3.025 version of the software still has problems, please provide me with logread and dmesg information.
Let me refresh and restart and re-implement gl_health
Note that to combat the problem, I’ve implemented a static IP address. This has not solved the problem rather it reduces my downtime. What was previously 40-60 seconds of downtime is now 1-2 seconds but the link still drops every 30 mins.
Let me start fresh with gl_health installed and DHCP enabled for the interface and I’ll post my logs if there are issues.
OK, completely refreshed box with gl_health enabled. No other options configured. Everything is default except admin password and the WAN connection. Here is the recent drop:
System Log:
Wed Jun 19 08:27:14 2019 daemon.notice netifd: wwan (8158): udhcpc: sending renew to 10.0.0.1
Wed Jun 19 08:27:14 2019 daemon.notice netifd: wwan (8158): udhcpc: lease of 10.0.0.233 obtained, lease time 900
Wed Jun 19 08:27:20 2019 daemon.notice netifd: Network device ‘wlan-sta’ link is down
Wed Jun 19 08:27:20 2019 daemon.notice netifd: Interface ‘wwan’ has link connectivity loss
Wed Jun 19 08:27:20 2019 kern.info kernel: [ 2301.582206] wlan-sta: disassociated from 6c:b2:ae:31:3a:b2 (Reason: 1=UNSPECIFIED)
Wed Jun 19 08:27:20 2019 daemon.notice netifd: wwan (8158): udhcpc: received SIGTERM
Wed Jun 19 08:27:21 2019 kern.info kernel: [ 2302.598582] wlan-sta: authenticate with 6c:b2:ae:31:3a:b2
Wed Jun 19 08:27:21 2019 kern.info kernel: [ 2302.616987] wlan-sta: send auth to 6c:b2:ae:31:3a:b2 (try 1/3)
Wed Jun 19 08:27:21 2019 kern.info kernel: [ 2302.625597] br-lan: port 2(wlan1) entered disabled state
Wed Jun 19 08:27:21 2019 daemon.notice netifd: Network device ‘wlan1’ link is down
Wed Jun 19 08:27:21 2019 kern.info kernel: [ 2302.634263] wlan-sta: authenticated
Wed Jun 19 08:27:21 2019 kern.info kernel: [ 2302.709166] wlan-sta: associate with 6c:b2:ae:31:3a:b2 (try 1/3)
Wed Jun 19 08:27:21 2019 kern.info kernel: [ 2302.724567] wlan-sta: RX AssocResp from 6c:b2:ae:31:3a:b2 (capab=0x421 status=0 aid=5)
Wed Jun 19 08:27:21 2019 kern.info kernel: [ 2302.733902] wlan-sta: associated
Wed Jun 19 08:27:21 2019 daemon.notice netifd: Network device ‘wlan-sta’ link is up
Wed Jun 19 08:27:21 2019 daemon.notice netifd: Interface ‘wwan’ has link connectivity
Wed Jun 19 08:27:21 2019 daemon.notice netifd: Interface ‘wwan’ is setting up now
Wed Jun 19 08:27:21 2019 kern.debug kernel: [ 2302.810267] wlan-sta: Limiting TX power to 23 dBm as advertised by 6c:b2:ae:31:3a:b2
Wed Jun 19 08:27:21 2019 daemon.notice netifd: wwan (15924): udhcpc: started, v1.28.3
Wed Jun 19 08:27:22 2019 daemon.notice netifd: wwan (15924): udhcpc: sending discover
Wed Jun 19 08:27:22 2019 daemon.notice netifd: wwan (15924): udhcpc: sending select for 10.0.0.233
Wed Jun 19 08:27:22 2019 daemon.notice netifd: wwan (15924): udhcpc: lease of 10.0.0.233 obtained, lease time 900
Wed Jun 19 08:27:22 2019 daemon.notice netifd: Network device ‘wlan1’ link is up
Wed Jun 19 08:27:22 2019 kern.info kernel: [ 2304.155589] br-lan: port 2(wlan1) entered blocking state
Wed Jun 19 08:27:22 2019 kern.info kernel: [ 2304.161143] br-lan: port 2(wlan1) entered forwarding state
Wed Jun 19 08:27:22 2019 daemon.warn dnsmasq[2999]: no servers found in /tmp/resolv.conf.auto, will retry
Wed Jun 19 08:27:22 2019 daemon.notice netifd: Interface ‘wwan’ is now up
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: reading /tmp/resolv.conf.auto
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using local addresses only for domain test
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using local addresses only for domain onion
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using local addresses only for domain localhost
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using local addresses only for domain local
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using local addresses only for domain invalid
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using local addresses only for domain bind
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using local addresses only for domain lan
Wed Jun 19 08:27:22 2019 daemon.info dnsmasq[2999]: using nameserver 203.83.22.22#53
Wed Jun 19 08:27:27 2019 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta)
I didn’t see the log before and after the disconnection. Is your current problem still dropped every 30 minutes? After opening gl_health, the problem still exists?
Yes. Same problem and still disconnecting every 30 mins. When you say open gl_health, I’ve made sure it’s installed and I can confirm the process is running. Is there anything else I’m supposed to do?
stibbo:
Can I look at your device remotely, I need to confirm whether it is a problem with the superior DHCP Server or portal wifi, or you can use tcpdump to grab the data packet of the wlan-sta interface, the operation method is as follows (refer to this link https: / /docs.gl-inet.com/en/3/app/ssh/):
1.ssh login to the route (make sure the route can access the network)
2.opkg update
3.opkg install tcpdump
4. Use the following instructions to fetch:
tcpdump -i wlan-sta -s 0 -w wlan_sta.pcap
5. Give the wlan_sta.pcap packet to me, pay attention to the process of disconnecting the connection.
