Gargoyle Forum

Hi, Recently upgraded finding out that this is based on CC. ON wndr3800ch, with no big issues. However now networx does not work with this through upnp, despite upnp ports working fine to map. I see gargoyle router in gateway name, but nothing in wan interface. I tried the fix described in past vers...

If you connect a laptop or desktop directly, do you get a 178 or 10. address? If 178 maybe try this on the laptop before connecting the gargoyle router: open command prompt as admin ipconfig /release Unplug laptop and plug the gargoyle router in. I've had issues with my ISP giving odd IP addresses d...

Any way to read the upnp variable in order to use a cron to restart the service if the data gets up high enough to kill reporting?

It gives a codel queue for the interfaces themselves, not touching the QOS queues. My friend has 150 mbit fiber, so he doesn't use qos. But if he leaves stock queues (fifo?) he can get spikes to 200 ms. With codel, the latency never goes above 120ms. It's just smarter about how it handles traffic, e...

You don't need bwmon... I always disable it and chmod -x it to be sure.

You can't use codel for the qos in gargoyle, but hsfc/ sfq is much better because like mentioned, you can use caps. sqm_scripts was not too good in balancing out load- like torrents would still saturate the connection because of many multiple connections! But you can change the eth0 eth1 wlan1 wlan0...

I've since changed my setup. Now, gargoyle is used to do download QOS, as it's much better in sharing bandwith, limiting torrents, and keeping ping low than the old school QOS of the actiontec rev. I. The actiontec is still handling upload QOS though because gargoyle or openwrt on 800 mhz overclocke...

Any idea if this was fixed in the newer build?
I see something regarding iptables on github late Feb, but not sure... I could care less about the guest networks- so I'd rather not recompile if not needed

You need to lower your upload limit a bit more. Some lines need more "space" to do this. Also set a rule in upload (and download) to prioritize packets less than 86 bytes or so. That helps ack/ping/etc

The only workaround is a bit hacky: Set a rule in download qos for that ip range using a subnet in cidr notation (eg: 192.168.1.128/26). The quotas are easier because they can take ip ranges, where qos tab cannot. Another unrelated issue is with dnscrypt-proxy http://wiki.openwrt.org/inbox/dnscrypt ...