102.7 Alpha Builds available

[dave14305]

I have mine turned off when goes to Adaptive Qos page and hit any of tabs when crashing and reboot.

When you click Adaptive QoS in the menu, does the Bandwidth Monitor page load without causing a crash? What happens if you browse directly to the Speedtest URL without visiting the Bandwidth Monitor page first?

So very little has changed in this Alpha for WiFi6 that I can’t imagine how this would induce a crash (I.e. disabling AiCloud, updating dnsmasq, nettle, dropbear, OpenVPN, and a small DNS Director fix).

 

[octopus]

When you click Adaptive QoS in the menu, does the Bandwidth Monitor page load without causing a crash? What happens if you browse directly to the Speedtest URL without visiting the Bandwidth Monitor page first?

So very little has changed in this Alpha for WiFi6 that I can’t imagine how this would induce a crash (I.e. disabling AiCloud, updating dnsmasq, nettle, dropbear, OpenVPN, and a small DNS Director fix).

I can display QoS - WAN/LAN Bandwidth Monitor page and when click on Adaptive QoS it's crashing.
After playing around with Chrome/Firefox and Edge it's suddenly start to working, can run speed test.
it must have been something with chachade stuff, i don't really don't know.

Thanks for your support.

 

[MDM]

Something new since Alpha, a DNSSEC error that I newer had before (and my DNSSEC settings didn't change in quite a while). But of course it might just be a coincidental timing of an Cloudflare issue or my ISP misbehaving...
And it didn't happen with just limetorrents.cc but with others including Google! It is intermittent in nature and not too often.

dnsmasq[5235]: Insecure DS reply received for limetorrents.cc, check domain configuration and upstream DNS server DNSSEC support

 

[Ripshod]

Something new since Alpha, a DNSSEC error that I newer had before (and my DNSSEC settings didn't change in quite a while). But of course it might just be a coincidental timing of an Cloudflare issue or my ISP misbehaving...
And it didn't happen with just limetorrents.cc but with others including Google! It is intermittent in nature and not too often.

Can't remember the specifics but I've also seen this message.

 

[dave14305]

Something new since Alpha, a DNSSEC error that I newer had before (and my DNSSEC settings didn't change in quite a while). But of course it might just be a coincidental timing of an Cloudflare issue or my ISP misbehaving...
And it didn't happen with just limetorrents.cc but with others including Google! It is intermittent in nature and not too often.

dnsmasq 2.92 has multiple DNSSEC changes, and even some DNSSEC patches post-2.92, so maybe it's valid, or maybe it's a bug in dnsmasq. But it does seem like that domain has a bad DS.

DNSSEC Debugger - limetorrents.cc

The DNSSEC Debugger from VeriSign Labs is an on-line tool to assist with diagnosing problems with DNSSEC-signed names and zones.

dnssec-analyzer.verisignlabs.com

Quite possibly this fix:

thekelleys.org.uk Git - dnsmasq.git/commitdiff

 

[MDM]

dnsmasq 2.92 has multiple DNSSEC changes, and even some DNSSEC patches post-2.92, so maybe it's valid, or maybe it's a bug in dnsmasq. But it does seem like that domain has a bad DS.

DNSSEC Debugger - limetorrents.cc

The DNSSEC Debugger from VeriSign Labs is an on-line tool to assist with diagnosing problems with DNSSEC-signed names and zones.

dnssec-analyzer.verisignlabs.com

Quite possibly this fix:

thekelleys.org.uk Git - dnsmasq.git/commitdiff

Might be the case with dnsmasq being the cause, well will get fixed then in a future release (dnsmasq and then Merlin FW).
Yes the torrent link probably isn't expected to be correct, but the Google one...

Just for reference my DNSSEC settings (since the introduction of DNSSEC and DOT in the FW):

 

[lgkahn]

gt-axe16000 running in ap mode with 2.5gbe connected to 10gbe port.. 3 of 4 wifi bands used (not using 5gz1 as that is reservered for upstairs router)
(backbone to upstairs main router is fiber 10gb connection). iperf perfect at 2.38gb/sec

dirty upgrade from release... no issues at all.. good job.

 

[Tech9]

Just for reference my DNSSEC settings (since the introduction of DNSSEC and DOT in the FW):

This is not needed. I see it very often as example configuration on SNB Forums. You have trusted DNS providers upstream and encrypted communication. They do DNSSEC validation for you.

 

[MDM]

This is not needed. I see it very often as example configuration on SNB Forums. You have trusted DNS providers upstream and encrypted communication. They do DNSSEC validation for you.

Oh but it is needed (in my country), because otherwise ISP sniffs all to government before it gets to trusted DNS providers...

 

[Tech9]

They eventually see encrypted packets and may cut off your DoT if they want to. They can't alter the packets. You basically run DNSSEC on Quad9 and Cloudflare.

 

[MDM]

I know, but better than nothing! Doubt they will cut DoT, but who knows...
+ VPN when needed.

 

[KevTech]

because otherwise ISP sniffs all to government before it gets to trusted DNS providers

ISP can still see your traffic even though you use dnssec.
Only way to hide traffic from ISP is VPN and Tor.

 

[MDM]

ISP can still see your traffic even though you use dnssec.
Only way to hide traffic from ISP is VPN and Tor.

I know, but that's why I use DNSSEC, DoT and VPN.
Better make it harder! AND safer - multiple reasons...

 

[Tech9]

You do whatever you like with your router. The configuration shown in post #86 is unrelated to specific location and ISP history collection. It just doesn't make sense. Same about the comment someone is "sniffing to the government" (whatever it means) encrypted packets between you and your DNS provider. If they can do it the encrypted packets between you and your VPN provider are busted as well.

 

[Bob575]

Something new since Alpha, a DNSSEC error that I newer had before (and my DNSSEC settings didn't change in quite a while). But of course it might just be a coincidental timing of an Cloudflare issue or my ISP misbehaving...
And it didn't happen with just limetorrents.cc but with others including Google! It is intermittent in nature and not too often.

I reported this earlier in this thread, but with Quad9 throwing the errors. Changing to Cloudflare "Security" (1.1.1.2) cleared the errors reported in my logs, but seems to be very unusual behavior.