Page 6 of 6

Re: gargoyle-ispy 2016-May-12 09:22.torrent

Posted: Sun May 22, 2016 9:02 pm
by calculoso
For whatever reason, the 2.4GHz network crashed on me this evening. I was streaming a video on my local network (Computer with Plex to Smart TV), and when I went to go to the next video, the Smart TV couldn't connect to the Wifi. Sure enough my phone verified that my 2.4GHz network couldn't be found, but the 5 GHz network was still up (as was hardwired).

A logread doesn't show anything useful, I don't think. Here is the last half hour (approx)...

Sun May 22 20:27:11 2016 daemon.info dnsmasq-dhcp[16600]: DHCPREQUEST(br-lan) 192.168.1.12 xx:xx:xx:xx:xx:xx
Sun May 22 20:27:11 2016 daemon.info dnsmasq-dhcp[16600]: DHCPACK(br-lan) 192.168.1.12 xx:xx:xx:xx:xx:xx CanonPrint
Sun May 22 20:27:46 2016 daemon.info dnsmasq-dhcp[16600]: DHCPREQUEST(br-lan) 192.168.1.28 xx:xx:xx:xx:xx:xx
Sun May 22 20:27:46 2016 daemon.info dnsmasq-dhcp[16600]: DHCPACK(br-lan) 192.168.1.28 xx:xx:xx:xx:xx:xx e-iPhone
Sun May 22 20:28:17 2016 daemon.info dnsmasq-dhcp[16600]: DHCPREQUEST(br-lan) 192.168.1.20 xx:xx:xx:xx:xx:xx
Sun May 22 20:28:17 2016 daemon.info dnsmasq-dhcp[16600]: DHCPACK(br-lan) 192.168.1.20 xx:xx:xx:xx:xx:xx LG-TV
Sun May 22 20:28:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:28:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:28:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:28:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:28:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:29:52 2016 daemon.info dnsmasq-dhcp[16600]: DHCPREQUEST(br-lan) 192.168.1.17 xxxxxxxxxxxxxxxxx
Sun May 22 20:29:52 2016 daemon.info dnsmasq-dhcp[16600]: DHCPACK(br-lan) 192.168.1.17 xxxxxxxxxxxxxxxxx BLACKBERRY-832E
Sun May 22 20:32:18 2016 daemon.info dnsmasq-dhcp[16600]: DHCPREQUEST(br-lan) 192.168.1.66 xxxxxxxxxxxxxxxxx
Sun May 22 20:32:18 2016 daemon.info dnsmasq-dhcp[16600]: DHCPACK(br-lan) 192.168.1.66 xxxxxxxxxxxxxxxxx PS4
Sun May 22 20:38:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:38:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:38:22 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:38:23 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:38:23 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx WPA: group key handshake completed (RSN)
Sun May 22 20:48:31 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx IEEE 802.11: deauthenticated due to local deauth request
Sun May 22 20:48:31 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx IEEE 802.11: deauthenticated due to local deauth request
Sun May 22 20:48:31 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx IEEE 802.11: deauthenticated due to local deauth request
Sun May 22 20:48:31 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx IEEE 802.11: deauthenticated due to local deauth request
Sun May 22 20:48:31 2016 daemon.info hostapd: wlan1: STA xxxxxxxxxxxxxxxxx IEEE 802.11: deauthenticated due to local deauth request
Sun May 22 20:50:06 2016 daemon.info hostapd: wlan0: STA xxxxxxxxxxxxxxxxx IEEE 802.11: authenticated
Sun May 22 20:50:06 2016 daemon.info hostapd: wlan0: STA xxxxxxxxxxxxxxxxx IEEE 802.11: associated (aid 1)
Sun May 22 20:50:06 2016 daemon.info hostapd: wlan0: STA xxxxxxxxxxxxxxxxx RADIUS: starting accounting session 5741CDBF-00000001
Sun May 22 20:50:06 2016 daemon.info hostapd: wlan0: STA xxxxxxxxxxxxxxxxx WPA: pairwise key handshake completed (RSN)
Sun May 22 20:50:07 2016 daemon.info dnsmasq-dhcp[16600]: DHCPDISCOVER(br-lan) xxxxxxxxxxxxxxxxx
Sun May 22 20:50:07 2016 daemon.info dnsmasq-dhcp[16600]: DHCPOFFER(br-lan) 192.168.1.17 xxxxxxxxxxxxxxxxx
Sun May 22 20:50:07 2016 daemon.info dnsmasq-dhcp[16600]: DHCPREQUEST(br-lan) 192.168.1.17 xxxxxxxxxxxxxxxxx
Sun May 22 20:50:07 2016 daemon.info dnsmasq-dhcp[16600]: DHCPACK(br-lan) 192.168.1.17 xxxxxxxxxxxxxxxxx BLACKBERRY-832E
Sun May 22 20:51:55 2016 authpriv.info dropbear[28301]: Child connection from 192.168.1.9:50803

It appears that at approx 20:50:06 is when the 2.4 GHz crashed, as that is when my phone switched to the 5 GHz network.

Re: gargoyle-ispy 2016-May-12 09:22.torrent

Posted: Sun May 22, 2016 9:04 pm
by calculoso
Here is some other info as of right now, if it is useful...

Device Name:xxxxxxxx
Gargoyle Version:1.9.X (Built 20160522-0900 git@c570910)
Model:TP-Link Archer C7 v2
Device Configuration:Gateway
Memory Usage:36.4MB / 123.1MB (29.5%)
Connections:30/4096
CPU Load Averages:0.09 / 0.08 / 0.07 (1/5/15 minutes)
Uptime:0 days, 9 hours, 53 minutes
Current Date & Time:05/22/16 9:03 PM EDT

Re: gargoyle-ispy 2016-May-12 09:22.torrent

Posted: Sun May 22, 2016 9:10 pm
by Lantis
Mmmm nothing should have changed for 2.4.

Keep an eye on it. If you can get a closer logread possibly helpful. Also potentially a dmesg as well.

Re: gargoyle-ispy 2016-May-12 09:22.torrent

Posted: Sun May 22, 2016 9:14 pm
by calculoso
Will do. I don’t think the logread will show anything other than what was there, but I'll try a dmesg too

Re: gargoyle-ispy 2016-May-12 09:22.torrent

Posted: Mon May 23, 2016 5:40 pm
by nworbnhoj
nworbnhoj wrote:Enabling the Tor plugin results in a bootloop on my TL-WDR3600 for this build (and some prior builds).
I have narrowed this down a little. The tor plugin is stable when I use the default "Tor Data Drive: RAM Disk." but enters a boot loop when I use "Tor Data Drive: /dev/sda2".

Re: gargoyle-ispy 2016-May-12 09:22.torrent

Posted: Mon May 23, 2016 7:03 pm
by nworbnhoj
nworbnhoj wrote:Enabling the Tor plugin results in a bootloop on my TL-WDR3600 for this build (and some prior builds)

Sigh! So now I cannot replicate the instability :-(

And am starting to wonder again about those weird packets captured in my original post

Code: Select all

kern.debug kernel: [   62.590000] UDP: bad checksum. From 99.73.8.235:52605 to 103.25.181.95:53 ulen 41