Page 1 of 1

WR841 v8 - Request timed out

Posted: Wed Apr 10, 2013 4:39 pm
by woxy
Hello,
I'm running PL Gargoyle 1.5.9.7 on TP-LINK WR-841N v8.
On first ewertyhing looked fine, bu the I've observed
that my Internet is choking or something.
Then Gargoyle webUI takes long time to load, and secend after it loads without problem.
I'm strugling with this for a week or so, and here what it looks like.

1. WR841 as AP + Client to WiFi AP
2. PC connected to LAN of WR841
3. pinging from PC to WR841 LAN IP.

Whet AP WIFI is off, so WR841 is not connected to WiFi, ping from PC to LAN goes as it should.
After turning on WiFi AP, after WR841 connects to it, I'm geting something like that:

[img]http://woxy_ivanhoee.republika.pl/wr841/ping_lan.jpg[/img]

And in the same moment, if I disconnect WR841 from LAN PC, and connect PC to otherrouter as AP Client, so WR841 is WiFi bridged with WiFi AP, and PC is WiFi bridged with AP, ping's from PC to WR841 through WiFi goes as it should.

So for me it looks like the WiFi connection on WR841, makes some problem with LAN connection on WR841.
What can I do with it.

Here is logread:

Apr 6 17:23:43 Gargoyle user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Apr 6 17:23:43 Gargoyle kern.info kernel: [ 653.220000] eth1: link up (1000Mbps/Full duplex)
Apr 6 17:23:43 Gargoyle kern.info kernel: [ 653.220000] br-lan: port 1(eth1) entered forwarding state
Apr 6 17:23:43 Gargoyle kern.info kernel: [ 653.230000] br-lan: port 1(eth1) entered forwarding state
Apr 6 17:23:45 Gargoyle kern.info kernel: [ 655.230000] br-lan: port 1(eth1) entered forwarding state
Apr 6 17:23:48 Gargoyle kern.info kernel: [ 658.240000] device wlan0 entered promiscuous mode
Apr 6 17:23:48 Gargoyle kern.info kernel: [ 658.530000] br-lan: port 2(wlan0) entered forwarding state
Apr 6 17:23:48 Gargoyle kern.info kernel: [ 658.540000] br-lan: port 2(wlan0) entered forwarding state
Apr 6 17:23:50 Gargoyle kern.info kernel: [ 660.540000] br-lan: port 2(wlan0) entered forwarding state
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.010000] br-lan: port 2(wlan0) entered disabled state
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.340000] device wlan0-1 entered promiscuous mode
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.570000] wlan0-1: authenticate with 00:1f:3f:d7:37:4b
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.590000] wlan0-1: send auth to 00:1f:3f:d7:37:4b (try 1/3)
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.600000] wlan0-1: authenticated
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.610000] wlan0-1: associate with 00:1f:3f:d7:37:4b (try 1/3)
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.620000] wlan0-1: RX AssocResp from 00:1f:3f:d7:37:4b (capab=0x431 status=0 aid=1)
Apr 6 17:23:52 Gargoyle kern.info kernel: [ 662.630000] wlan0-1: associated

Apr 6 17:25:26 Gargoyle kern.info kernel: [ 756.180000] device wlan0 left promiscuous mode
Apr 6 17:25:26 Gargoyle kern.info kernel: [ 756.190000] br-lan: port 2(wlan0) entered disabled state
Apr 6 17:25:26 Gargoyle kern.info kernel: [ 756.240000] wlan0-1: deauthenticating from 00:1f:3f:d7:37:4b by local choice (reason=3)
Apr 6 17:25:26 Gargoyle kern.info kernel: [ 756.370000] br-lan: port 3(wlan0-1) entered disabled state
Apr 6 17:25:26 Gargoyle kern.info kernel: [ 756.450000] br-lan: port 3(wlan0-1) entered disabled state
Apr 6 17:25:26 Gargoyle kern.info kernel: [ 756.470000] device wlan0-1 left promiscuous mode
Apr 6 17:25:26 Gargoyle kern.info kernel: [ 756.470000] br-lan: port 3(wlan0-1) entered disabled state
Apr 6 17:25:28 Gargoyle kern.info kernel: [ 757.720000] eth1: link down
Apr 6 17:25:28 Gargoyle kern.info kernel: [ 758.190000] br-lan: port 1(eth1) entered disabled state
Apr 6 17:25:28 Gargoyle kern.info kernel: [ 758.200000] device eth1 left promiscuous mode
Apr 6 17:25:28 Gargoyle kern.info kernel: [ 758.210000] br-lan: port 1(eth1) entered disabled state
Apr 6 17:25:29 Gargoyle daemon.notice netifd: Interface 'lan' is now up
Apr 6 17:25:29 Gargoyle kern.info kernel: [ 759.270000] device eth1 entered promiscuous mode
Apr 6 17:25:29 Gargoyle daemon.notice netifd: Interface 'loopback' is now up
Apr 6 17:25:30 Gargoyle user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Apr 6 17:25:30 Gargoyle kern.info kernel: [ 759.870000] eth1: link up (1000Mbps/Full duplex)
Apr 6 17:25:30 Gargoyle kern.info kernel: [ 759.870000] br-lan: port 1(eth1) entered forwarding state
Apr 6 17:25:30 Gargoyle kern.info kernel: [ 759.880000] br-lan: port 1(eth1) entered forwarding state
Apr 6 17:25:32 Gargoyle kern.info kernel: [ 761.880000] br-lan: port 1(eth1) entered forwarding state
Apr 6 17:25:35 Gargoyle kern.info kernel: [ 765.430000] device wlan0 entered promiscuous mode
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.910000] wlan0: authenticate with 00:1f:3f:d7:37:4b
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.920000] wlan0: send auth to 00:1f:3f:d7:37:4b (try 1/3)
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.930000] wlan0: authenticated
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.950000] wlan0: associate with 00:1f:3f:d7:37:4b (try 1/3)
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.950000] wlan0: RX AssocResp from 00:1f:3f:d7:37:4b (capab=0x431 status=0 aid=1)
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.960000] wlan0: associated
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.970000] br-lan: port 2(wlan0) entered forwarding state
Apr 6 17:25:36 Gargoyle kern.info kernel: [ 765.970000] br-lan: port 2(wlan0) entered forwarding state
Apr 6 17:25:38 Gargoyle kern.info kernel: [ 767.970000] br-lan: port 2(wlan0) entered forwarding state
Apr 6 17:25:39 Gargoyle user.info firewall: adding lan (br-lan) to zone lan
Apr 6 17:26:32 Gargoyle user.notice ifup: Enabling Router Solicitations on loopback (lo)

As I can see eth1 goes in forwarding state, wlan also, and then goes in disabled state.

Re: WR841 v8 - Request timed out

Posted: Wed Apr 10, 2013 5:12 pm
by woxy
Justo for the record.
I've setup WR841 as Gateway and problems gone.
But returning to Wireless bridge, starts problems again.

Re: WR841 v8 - Request timed out

Posted: Fri Apr 26, 2013 7:23 am
by chente
Dear
which gargoyle version are you using with your v8 ?
I mean ... which file you downloaded for your v8 ?
thanks

Re: WR841 v8 - Request timed out

Posted: Sun Apr 28, 2013 4:45 pm
by woxy
I'm using :

http://ecco.selfip.net/gargoyle-pl/atti ... nt/ar71xx/

gargoyle-1.5.9.9-ar71xx-tl-wr841n-v8-squashfs-factory.bin

Re: WR841 v8 - Request timed out

Posted: Sun Apr 28, 2013 6:12 pm
by i_bounce
I Beleve this problem the same i am having even when i am using the router as gateway too, the wifi problem only happening from the same router which have installed Gargoyle system in it, hope some one help us with this problem because i have to reboot the router every 4 hours to get my Wifi connection up and running with full internet speed

Re: WR841 v8 - Request timed out

Posted: Mon Apr 29, 2013 8:15 am
by woxy
As for now, You can use DD-WRT instead.
At least there's no problems with WiFi stability or LAN pings.

http://dd-wrt.com/dd-wrtv2/downloads/ot ... -ddwrt.bin

Flash it from TP-LINK firmware.