By contrast, Firmware Download site implies that 8.2.0 is only good for Balance 20s with HW rev of 7 or 8, and that for rev 6 or earlier, 8.1.3 is the most current firmware option.
Thanks for the clarification. With that explained, it does seem to me that there are two bugs:
The “Devices Supported” table in the Release Notes for 8.2.0 is misleading in this regard (it should make it clear there that the support for Balance 20 does not apply to revs 6 or earlier); and
The Firmware Upgrade function of firmware 8.1.1 does correctly identify 8.1.3 as the most current (supported) firmware version for this hardware. A device should never explicitly encourage a user to upgrade to unsupported firmware.
It seems the firmware update feature is indeed flawed. I tested a Balance 20 hardware version 1 (yes 1, used to belong to Abraham Lincoln) running firmware 6.something and it too said that version 8.2 was the latest and greatest. Obvious conclusion is that the router phones home with the model number but not with the hardware version, when checking for new firmware. Pretty surprising since hardware versions have been around for quite a while.
HI all. MAX Transit CAT 18 here . is it my imagination or did 8.2 fix an issue with broadcasting the local Wifi SSID when the device is under USB power? Whenever I powered my CAT 18 with USB power (both ports 20w total available power) I found that my devices could not see the local Wifi SSID. So this morning I installed 8.2 and voiila the SSID is now broadcast under USB power.
I didn’t actually test to see if the original problem was SSID broadcast or if the Wifi itself was actually inoperable, under USB power, but in any case its working now under 8.2.
This update looks wrong. There are two flavors of DNS: old insecure DNS (UDP port 53) and new secure DNS (DoH or DoT). Old DNS is specified with IP addresses, new DNS is always specified with a server/host name.
And, there is the arm wrestling between DoH and Local DNS records. When both are enabled, which is used?
Update: I tested with a NextDNS url and that was not enough. As shown here, the router wants an IP address too. Why? The server/host name/URL is all that NextDNS needs in any other environment.
We have started to roll this out to our test QA servers and would like to know where we can get access to the new DWB interface and its settings?
We have looked through the client web UI (MAX Transit Duo, MAX HD4 MBX, UBR LTE and 310 5G) and also on our FusionHub servers and cannot see where these settings are hiding.
We use DWB extensively and would really like to get these tested and provide feedback.
On the DoH settings, if you select the predefined DoH server, the router will refer to the associated provider DNS server IP addresses (as per the description above) embedded in the firmware. While using the [Custom URL:], the router needs you to manually enter the provider secured DNS server IP addresses.
I see from this article, NextDNS server IP is 45.90.28.19 & 45.90.30.19.
DoH takes precedence over what? The description you highlighted is about DNS requests leaving a WAN port going out to the Internet. The second sentence says it will not send UDP port 53 out the WAN port. Fine. But, Local DNS requests do not leave the WAN port. Thus the question of whether Local DNS records are honored or ignored when using DoH.
Update: Testing whether Local DNS records are being processed or not is simple. I tested it and even when DoH is active, Local DNS records are processed and used.
NextDNS differs from other Secure DNS providers in that they do not have just two IPv4 addresses. They have a pool of them. You can see this yourself in this screen shot which shows the article you referred to overlayed on a brand new NextDNS account that I just created. The IPv4 addresses differ.
