I'm not familiar with firefox upcoming DOH feature. What's the difference of automatically and manually enabling DOH in firefox? Aren't they both ends with DOH?DNSFilter will block client DoT (port 853) if the DNSFilter mode does not support DoT. The new DoH setting will prevent Firefox from automatically enabling DoH (port 443) in upcoming Firefox releases. There are not yet any plans to block DoH in the firmware since it looks the same as normal https traffic. So a Firefox client that manually enables DoH will pass through the router just fine, which is part of the Firefox controversy.
There were rumors that Firefox and Chrome would enable DoH in upcoming releases. DoH is in Firefox now but has to be manually enabled.I'm not familiar with firefox upcoming DOH feature. What's the difference of automatically and manually enabling DOH in firefox? Aren't they both ends with DOH?
There were rumors that Firefox and Chrome would enable DoH in upcoming releases. DoH is in Firefox now but has to be manually enabled.
DoH and DoT have gotten some bad press lately from uninformed persons. Seems that we are trying to keep law enforcement from seeing what we do...
Firefox checks for a special canary domain before automatically enabling DoH. If that domain fails their test, they will not automatically enable DoH, assuming you are currently using a special DNS server (for parental control or ad blocking, for instance). However if you manually decide to enable DoH, then that canary domain will not be checked.
All the router can do is handle requests sent for this canary domain. It has no way of blocking the DoH traffic itself, because that's the idea behind DoH: to avoid detection/filtering by hiding as regular HTTPS traffic.
Firefox will automatically enable DoH if you are in the US, and a certain canary domain lookup succeeds.
Chrome is going for a slightly different route: they detect what DNS server you use, and if that server is known to also support DOH (for instance if you are currently using 1.1.1.1) then they will upgrade to the DoH protocol. Not as brain-damaged as Firefox, but still problematic if you intend to handle DNS traffic differently on your network through QoS rules. The decision will be made based on a built-in database of known DoH capable servers.
If you have your HTTPS traffic handled with a lower priority (to avoid large downloads from slowing down your network), then DoH requests will also end up throttled at this lower priority. You can imagine the results.
if it’s possible to eliminate any overruling by a special setting, when we not paying attention with future updates from them.
Does this mean Firefox will bypass my Pi's Unbound implementation?
RT-AC66U_B1 upgraded to the Alpha 2. Seems to run well but am not seeing the DHCP reserved list in Edge and Chrome.
Yesterday I transferred some large files from a wired PC to my NAS. Noticed in the Traffic Monitor on Daily that the internal transfer was recorded which blew away the graph display. Don't think the internal, wired and WIFI should be displayed in the traffic monitor.View attachment 19533
it's Thanksgiving Weekend here in Canada, Motor City Superman. Merlin is in a turkey coma, or travelling, or tied up with family, or taking a well-deserved long weekend.I don't see why Merlin wont just update the build to include these fixes. Most people have no clue how to add commands or SSH in there routers. Maybe he is busy.
Isn't this the day we commemorate Columbus discovering Canada?it's Thanksgiving Weekend here in Canada, Motor City Superman. Merlin is in a turkey coma, or travelling, or tied up with family, or taking a well-deserved long weekend.
Problem Activating SSH in GUI
After upgrading my AC86 from 13 to 14 beta, when using the GUI I was unable to activate SSH access to the router.
When I clicked apply a box kept popping up telling to select a number between 1-65535. Regardless of what port number I entered it would not work. Rebooting the router did not help.
I finally reverted to V 13 turned on SSH the upgraded again to V14. After turning on SSH in V13 SSH was working in V14.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!