Gargoyle IPv6 Testing

[BJReplay]

Just reporting back that since upgrading on the 9th, this is running nicely on my Linksys EA8500 (ipq806x).

It took some playing around to get QOS working the way I wanted (which is primarily limiting one user who is incapable of reasonably limiting himself ).

Running with adblock, dark-one, spectrum plug ins.

[Lantis]

Thanks for reporting back.
Are you running IPv6 or just IPv4?

Was the QoS trouble with the new functionality or just QoS in general?

[BJReplay]

Are you running IPv6 or just IPv4?

IPv6 LAN
IPv4 WAN (Optus)

Was the QoS trouble with the new functionality or just QoS in general?

Just in general: was trying to use ACC to further limit the class associated with the errant users if the link was under pressure, but it appeared to reduce the Fair Link Limit but it wouldn't appear to climb back up again without hitting "Reset Fair Link Limit".

Given WAN is IPv4, didn't try setting a download class based on source IP or upload class based on destination IP with IPv6.

[Lantis]

Fair enough. Thanks for that.

I think it would have created the ipv6 rules ok for you, they just wouldn't have had any effect (obviously). At least that would be the intent.
We could maybe be smarter about even letting you do that in the first place...

[BJReplay]

I see new builds (23rd May) for ipq086x in https://lantisproject.com/gargoyle_cust ... st_builds/

Are these ready for testing?

If already on the ipq806x builds from
https://lantisproject.com/gargoyle_custom/ipv6/ipq806x/ should these be preserve settings or clean installs?

[Lantis]

You can try it if you like. Preserve settings should be ok.
The only change is updated Tor, and I've reworked ewget to understand IPv6. This is a stepping stone for DDNS supporting IPv6.

[BJReplay]

Sweet, will try it after work hours and report back.

[BJReplay]

Smooth update.

Nothing (specific to this release, IPv6) to report.

Had hoped that perhaps the changes to ewget might have worked around the problem with DDNS being reporting that it is unable to get the remote IP for my DDNS hosted on zoneedit.com - it logs "remote IP cannot be determined" which looks like it is a result of a NULL return from lookup_domain_ip:

Code: Select all

Tue Jun  2 17:49:11 2020 daemon.info ddns_gargoyle[5848]: Forcing update:
Tue Jun  2 17:49:11 2020 daemon.info ddns_gargoyle[5848]:       service provider=zonedit.com
Tue Jun  2 17:49:11 2020 daemon.info ddns_gargoyle[5848]:       domain=xxxx.xxxx.com.au
Tue Jun  2 17:49:12 2020 daemon.info ddns_gargoyle[5848]:               Successfully retrieved local ip from url: https://aruljohn.com/ip/
Tue Jun  2 17:49:12 2020 daemon.info ddns_gargoyle[5848]:       local IP  = 175.nnn.nnn.151
Tue Jun  2 17:49:12 2020 daemon.info ddns_gargoyle[5848]:       remote IP cannot be determined
Tue Jun  2 17:49:13 2020 daemon.info ddns_gargoyle[5848]:       Update failed

I've had this problem (reported failure of update) since at least 1.12.0.

It should be noted that the update attempt still occurs after logging "remote IP cannot be determined", and, as far as I can tell from the update info on ZoneEdit, succeeds, but Gartgoyle thinks it has failed.

[BJReplay]

Another smooth update.

Just upgraded to 20200607-0310 git@8755fb93 with preserve settings, added in plugin sources, installed and enabled adblock and logread and dark one theme.

Now installing other favourite plugins.

[Lantis]

So problem with zoneedit is they've gone to a paid model.
viewtopic.php?f=6&t=10947&p=45008&hilit=zoneedit#p45008

I haven't got a way to test it.
I will need to rely on community members (yourself?) To figure out what is wrong.