Connection Start/End Logging

[cwswpl]

Hi, I have a TP-Link TL-WR1043N/ND v2 running Gargoyle 1.8.1 that I bought a few months ago preloaded.

Love the ability to monitor and restrict bandwidth usage.

Finding lately that we are getting frequent disconnections from the ISP, always followed a minute or two later with a reliable reconnect. When I find the internet is not working, I check the router and it is always sitting on 0 minutes uptime.

No idea whether the router or the ISP or something else is to blame, but what diagnostics does Gargoyle provide here?

I assume there must be a log of WAN connect/disconnect, with maybe some reason for the disconnect? But can't find this in the Gargoyle interface.

If I'm going to take this up with the ISP, want to be well armed with data.

Any suggestions appreciated.

[Lantis]

You want to do a "logread" and "dmesg" at the command line just after a disconnect to find out why.

[cwswpl]

Thanks Lantis. It just happened again, here's what I got


FROM logread (relevant time entries only)

Fri Apr 28 11:12:55 2017 authpriv.info dropbear[2223]: Child connection from 192.168.1.109:61756
Fri Apr 28 11:12:58 2017 kern.info kernel: [ 43.120000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Fri Apr 28 11:13:01 2017 authpriv.notice dropbear[2223]: Password auth succeeded for 'root' from 192.168.1.109:61756
Fri Apr 28 11:13:10 2017 user.notice root: vsftpd init: mounted = 0
Fri Apr 28 11:13:10 2017 user.emerg syslog: ERROR: No drives attached, no directories to share!
Fri Apr 28 11:13:10 2017 user.emerg syslog: setting up led USB
Fri Apr 28 11:13:10 2017 user.emerg syslog: setting up led WLAN
Fri Apr 28 11:13:10 2017 user.emerg syslog: - init complete -
Fri Apr 28 11:13:19 2017 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Fri Apr 28 11:13:24 2017 user.err syslog: module is already loaded - sch_prio
Fri Apr 28 11:13:24 2017 user.err syslog: module is already loaded - sch_tbf
Fri Apr 28 11:13:24 2017 user.err syslog: module is already loaded - cls_fw
Fri Apr 28 11:13:24 2017 kern.info kernel: [ 68.490000] IMQ driver unloaded successfully.
Fri Apr 28 11:13:24 2017 kern.info kernel: [ 68.520000] Hooked IMQ after mangle on INPUT
Fri Apr 28 11:13:24 2017 kern.info kernel: [ 68.520000] Hooked IMQ after mangle on FORWARD
Fri Apr 28 11:13:24 2017 kern.info kernel: [ 68.530000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1)
Fri Apr 28 11:13:24 2017 kern.info kernel: [ 68.530000] Hooking IMQ before NAT on PREROUTING.
Fri Apr 28 11:13:24 2017 kern.info kernel: [ 68.540000] Hooking IMQ after NAT on POSTROUTING.
Fri Apr 28 11:13:47 2017 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0)

FROM dmesg (also only the latest entries, not sure what format the timestamp is in)

[ 68.490000] IMQ driver unloaded successfully.
[ 68.520000] Hooked IMQ after mangle on INPUT
[ 68.520000] Hooked IMQ after mangle on FORWARD
[ 68.530000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1)
[ 68.530000] Hooking IMQ before NAT on PREROUTING.
[ 68.540000] Hooking IMQ after NAT on POSTROUTING.

Does this shed any light?

[Lantis]

Nothing out of the ordinary there. Doesn't really even show the disconnect, just the reconnect afterwards.

[cwswpl]

Thanks, that's what it looked like to me too.

Is there no way of even logging the times when a disconnect/reconnect happens, so I can hand it as a list to the ISP?

What's the timestamp format on dmesg, is it minutes/hours/days since boot?

[pbix]

"0 Uptime" on the router status page means your router rebooted. The cause of your reboot could be power interruption, hardware issue or software issue on your router.

A reboot is consistent with everything you reported.