Gargoyle Forum

Greetings.

I am new to Gargoyle. Thank you all for all you have done. I found out about it trying to solve TL-WA850RE v1.2 stability problems. Installed Gargoyle 1.80 and it worked great (client bridge repeater).

Installed 1.81 fine with preserve settings/reboot. Radio internet started to cut out after a couple of hours. Entered echo '0' > '/sys/kernel/debug/ieee80211/phy0/ath9k/ani' on the fly at the CLI and rock solid again.

Compared to Tomato Broadcom the ath9k / hostapd processes seems to decrease cell phone battery life ~20%/day more during sleep. Battery life is great when awake (e.g. playing music). Any pointers appreciated.

1.8.1: This may be related to cell phone power usage - group key handshake was coincident with deauth and the phone would then authenticate; repeat every 10 minutes. Some Android phones do not play well with wmm. Setting wmm to 0 cleaned up the logs. With 1x1 phones 54 Mb/s is not that bad. The 2x2 router/extender link remains > 117 Mb/s.

WDR3600 v1 fixed wireless stability issues with 1.8.1. I no longer have to reboot on a daily basis to fix wireless. Not sure what the change was maybe ANI?

1.8.1: The TL-WA850RE v1.2 (client bridge repeater) connected Andriod phone sleeps well with wmm=0. Re-enabled ANI and the stats are good (stable). It appears ANI was trying to adapt to the dropped(?) WMM traffic and it was a no-win scenario.

mwCT wrote:1.8.1: The TL-WA850RE v1.2 (client bridge repeater) connected Andriod phone sleeps well with wmm=0. Re-enabled ANI and the stats are good (stable). It appears ANI was trying to adapt to the dropped(?) WMM traffic and it was a no-win scenario.

Hi how are your wifi speeds?
http://www.smallnetbuilder.com/wireless ... s-with-wmm

root@TL-WA850RE:~# iwinfo wlan0 assoclist
XX:XX:XX:XX:0B -53 dBm / -95 dBm (SNR 42) 10 ms ago
RX: 117.0 MBit/s, MCS 14, 20MHz 220877 Pkts.
TX: 117.0 MBit/s, MCS 14, 20MHz 100483 Pkts.

root@TL-WA850RE:~# iwinfo wlan0-1 assoclist
XX:XX:XX:XX:51 -63 dBm / -95 dBm (SNR 32) 2050 ms ago
RX: 54.0 MBit/s, MCS 0, 20MHz 11187 Pkts.
TX: 54.0 MBit/s, MCS 0, 20MHz 10475 Pkts.

XX:XX:XX:XX:9B -56 dBm / -95 dBm (SNR 39) 46080 ms ago
RX: 24.0 MBit/s, MCS 0, 20MHz 34004 Pkts.
TX: 48.0 MBit/s, MCS 0, 20MHz 41202 Pkts.

I am confused. Without WMM you should get g-speeds. The wireless-N phones get g-speeds but a netbook with a 2x2 TL-WDN3200 gets n-speed. Looks like it still does 2 streams. Since it's an extender throughput is much lower than the connection. Speed test with the netbook is 11MB/sec (half) with the sirq ~20%. Latency is <20 ms (same).

root@TL-WA850RE:~# iwinfo wlan0-1 assoclist
XX:XX:XX:XX:XX:F1 -69 dBm / -95 dBm (SNR 26) 250 ms ago
RX: 117.0 MBit/s, MCS 14, 20MHz 31667 Pkts.
TX: 104.0 MBit/s, MCS 13, 20MHz 49362 Pkts.

XX:XX:XX:XX:XX:51 -62 dBm / -95 dBm (SNR 33) 1640 ms ago
RX: 54.0 MBit/s, MCS 0, 20MHz 29327 Pkts.
TX: 54.0 MBit/s, MCS 0, 20MHz 33339 Pkts.

XX:XX:XX:XX:XX:9B -46 dBm / -95 dBm (SNR 49) 1900 ms ago
RX: 24.0 MBit/s, MCS 0, 20MHz 34156 Pkts.
TX: 48.0 MBit/s, MCS 0, 20MHz 41242 Pkts.

Just installed in a WDR 3600

Seems to be working fin, gona test on the next few days.

Noticed already that the "option rfc1918_filter '1'"

Isn't around to be disabled causing some problems from who wants to access insde as outside.

This option needs to be a part of the Gui configuration.

Swimmer wrote:Just installed in a WDR 3600

Seems to be working fin, gona test on the next few days.

Noticed already that the "option rfc1918_filter '1'"

Isn't around to be disabled causing some problems from who wants to access insde as outside.

This option needs to be a part of the Gui configuration.

Can you give me a specific use case that would justify it needing to be part of the UI?

You can certainly disable it if you would prefer.

nworbnhoj wrote:

emukim wrote:THE MODERM is not working correctly.
it has critical faults, 5~6 times a day.

Can you provide some more detail about the errors when if you see them again please

it's on MODEM side.
MODEM can't get IP from ISP.
and sometime Gargoyle got DNS(ISP) error.(by using google dns will fix that)

Maybe DNS error is also MODEM side problem.

after reset MODEM to default setting,and plug-off MODEM's power for 60 seconds.
everything runs well. so far so good.