Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Jan 08, 2019 0:24 Post subject:
rickmav3 wrote:
Bestk4.9 M build up to date! All clients connecting at their max. speed. Wider UI config text boxes. And complete rainbow unicorn poop latencies, triple A+ with QoS, 29/17 ms.
For best possible WiFi connection just Disable all "fancy" features as beamforming, multichannel, even Noise immunity if not really needed, before going back and forth between builds. Consumer wireless is simply garbage as RF spectrum: only 3 non overlapping 2.4GHz channels with lots of interference from myriad of other devices operating on this freq., microwave included, 5GHz sharing radar spectrum, only 8 channels out of DFS. In crowded areas like highrises, good luck trying to get better than 60-70% quality channels. Everybody is blasting their routers at max. power and with as many as possible channels bonding. Getting over 100Mbps on WiFi can be considered luck. Adding to this mess, many client's drivers are improper coded and implemented, many closed source and cannot be updated, bitten fruit devices being maybe the worst. They could not even keep their WiFi routers around and now fighting the Co with the best hardware and knowledge on wireless transmissions, cell and WiFi, fitting their devices with subpar modems from Intel struggling for years to figure it out in this field. The idevices are giving the most problems and transmissions errors on DD-WRT. Even DD-WRT is giving now priority to QCA as the best performance hardware and firmware. Also, DD-WRT is actively developed with current drivers, to update mobile client's drivers their OS needs to be updated, old devices, even 1, 2 years old, are given the least priority as new devices need to be sold.
the neuter all features of wifi myth again? doesnt work. the wifi problems this firmware has arent in simple user settings, they are in drivers or qca firmware. doing that just still results in u having the same issues + less range, throughput, slower roaming, lack of fairness between devices with different phy rates etc. swear by what u want u think it works fine, but saying "do this this is proper way it works period" isnt the best way. as pleanty have already seen in here when they tried this stuff.. many revert back to turning useful features back on cause in the end, there was no difference or a worst difference with them off.
cause the problems with shit wifi latency @ speed, throughput, drops arent our basic user settings. its stuff in ath10k. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 19 Nov 2008 Posts: 274 Location: Madison, CT, US
Posted: Tue Jan 08, 2019 14:49 Post subject:
tatsuya46 wrote:
the neuter all features of wifi myth again? doesnt work. the wifi problems this firmware has arent in simple user settings, they are in drivers or qca firmware. doing that just still results in u having the same issues + less range, throughput, slower roaming, lack of fairness between devices with different phy rates etc. swear by what u want u think it works fine, but saying "do this this is proper way it works period" isnt the best way. as pleanty have already seen in here when they tried this stuff.. many revert back to turning useful features back on cause in the end, there was no difference or a worst difference with them off.
cause the problems with shit wifi latency @ speed, throughput, drops arent our basic user settings. its stuff in ath10k.
What do you all have for wan_dns and dnsmasq_options? I am not really sure that I set it up properly as tracert doesn't show any real problems. Just thought of asking the gurus of their setup. TIA.
My setting:
wan_dns="192.168.1.1 1.1.1.1 8.8.8.8"
lan_domain="ln"
dnsmasq_options="local=/ln/
expand-hosts
no-resolv
no-poll
all-servers
server=1.1.1.1
server=1.0.0.1
server=8.8.8.8
server=8.8.4.4" _________________ Netgear R7800 [DD-WRT]; ASUS RT-87U [DD-WRT]; ASUS RT-AC68U [FreshTomato]
WAN dns cannot be 192.168.1.1 unless its not an IP of another router before this one...
you do not have to use/set LAN domain name unless you need it for its purpose...
expand-hosts - I do not use this
no-resolv - this deny's the use of static DNS servers or default ISP DNS servers
no-poll - don't have this as this does Don't poll /etc/resolv.conf for changes and i need it
all-servers - this contradicts no-resolv as it let's static or ISP DNS servers to be used
all-servers Setting this flag forces dnsmasq to send all queries to all available servers
yep you can add them like this
server=1.1.1.1
server=1.0.0.1
server=8.8.8.8
server=8.8.4.4
and DNSmasq will use them all specivied like that
you can use also query in strict order if so
notice- i would ve stay away of 8.8.8.8 or any google stuff you can fairly replace with 9.9.9.9
what i have in my options
cache-size=2048
domain-needed
bogus-priv
no-resolv
server=9.9.9.9
server=149.112.112.9
no-negcache
filterwin2k _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Remove "wan_dns" and "lan_domain" variables and set:
nvram set dnsmasq_options="cache-size=2048
domain-needed
bogus-priv
no-resolv
server=9.9.9.9
server=149.112.112.9
no-negcache
filterwin2k"
Thank you very much for providing lot more detail on this and much appreciate it. _________________ Netgear R7800 [DD-WRT]; ASUS RT-87U [DD-WRT]; ASUS RT-AC68U [FreshTomato]
Remove "wan_dns" and "lan_domain" variables and set:
nvram set dnsmasq_options="cache-size=2048
domain-needed
bogus-priv
no-resolv
server=9.9.9.9
server=149.112.112.9
no-negcache
filterwin2k"
Thank you very much for providing lot more detail on this and much appreciate it.
@Alozaros,
I replicated your settings and some hosts that I use are not resolving now. Reverted to the settings that I had before and it works fine. For example, ping strangled.net doesn't resolve with your settings. _________________ Netgear R7800 [DD-WRT]; ASUS RT-87U [DD-WRT]; ASUS RT-AC68U [FreshTomato]
Joined: 16 Nov 2015 Posts: 6446 Location: UK, London, just across the river..
Posted: Thu Jan 10, 2019 8:01 Post subject:
RainGater wrote:
I replicated your settings and some hosts that I use are not resolving now. Reverted to the settings that I had before and it works fine. For example, ping strangled.net doesn't resolve with your settings.
And...This shows how copy/paste works...especially if you don't know whats all about it..
and...if there is a blocked hosts yep 9.9.9.9 tends to block hosts that contain malicious code
but yep i just noticed too... generally ping is disabled and all sites i ping either fail or request time out...it must be something i missed or probably no-resolve does it ill try at home later... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
So Google DNS announced DNS over TLS support today.
I used to use Voxel's firmware on my Netgear R7800, and that had stubby built-in, so enabling it was just a command or two and it was up and running.
It's been a while since I messed around with DD-WRT, so if anyone could point me in the right direction. Would Stubby still be required or is there DNS-over-TLS support already built-in to DD-WRT? _________________ Active devices:
Netgear R7800 - Stock v1.0.2.68
Linksys EA8500 - OpenWRT 19.07.1
ASUS RP-AC68U - 3.0.0.4.382.40019
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Jan 10, 2019 11:19 Post subject:
murtaza12 wrote:
So Google DNS announced DNS over TLS support today.
I used to use Voxel's firmware on my Netgear R7800, and that had stubby built-in, so enabling it was just a command or two and it was up and running.
It's been a while since I messed around with DD-WRT, so if anyone could point me in the right direction. Would Stubby still be required or is there DNS-over-TLS support already built-in to DD-WRT?
and? u believe google? one of the most tracking intensive companies on this earth? if "security" matters to u.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
So Google DNS announced DNS over TLS support today.
I used to use Voxel's firmware on my Netgear R7800, and that had stubby built-in, so enabling it was just a command or two and it was up and running.
It's been a while since I messed around with DD-WRT, so if anyone could point me in the right direction. Would Stubby still be required or is there DNS-over-TLS support already built-in to DD-WRT?
and? u believe google? one of the most tracking intensive companies on this earth? if "security" matters to u..
Okay... not Google then. Could go back to using CloudFlare's (1.1.1.1) DNS which also supports DoT, but getting stubby installed and working on DD-WRT seems quite complicated. _________________ Active devices:
Netgear R7800 - Stock v1.0.2.68
Linksys EA8500 - OpenWRT 19.07.1
ASUS RP-AC68U - 3.0.0.4.382.40019
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Jan 10, 2019 11:48 Post subject:
murtaza12 wrote:
tatsuya46 wrote:
murtaza12 wrote:
So Google DNS announced DNS over TLS support today.
I used to use Voxel's firmware on my Netgear R7800, and that had stubby built-in, so enabling it was just a command or two and it was up and running.
It's been a while since I messed around with DD-WRT, so if anyone could point me in the right direction. Would Stubby still be required or is there DNS-over-TLS support already built-in to DD-WRT?
and? u believe google? one of the most tracking intensive companies on this earth? if "security" matters to u..
Okay... not Google then. Could go back to using CloudFlare's (1.1.1.1) DNS which also supports DoT, but getting stubby installed and working on DD-WRT seems quite complicated.
id take cloudflare any day, i use them too, quite fast indeed. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
So Google DNS announced DNS over TLS support today.
I used to use Voxel's firmware on my Netgear R7800, and that had stubby built-in, so enabling it was just a command or two and it was up and running.
It's been a while since I messed around with DD-WRT, so if anyone could point me in the right direction. Would Stubby still be required or is there DNS-over-TLS support already built-in to DD-WRT?
and? u believe google? one of the most tracking intensive companies on this earth? if "security" matters to u..
Okay... not Google then. Could go back to using CloudFlare's (1.1.1.1) DNS which also supports DoT, but getting stubby installed and working on DD-WRT seems quite complicated.
id take cloudflare any day, i use them too, quite fast indeed.
Do you use DNS over TLS with CloudFlare since it supports it, or do you just have your router set to use 1.1.1.1 in the GUI? _________________ Active devices:
Netgear R7800 - Stock v1.0.2.68
Linksys EA8500 - OpenWRT 19.07.1
ASUS RP-AC68U - 3.0.0.4.382.40019
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Jan 10, 2019 13:24 Post subject:
murtaza12 wrote:
tatsuya46 wrote:
murtaza12 wrote:
tatsuya46 wrote:
murtaza12 wrote:
So Google DNS announced DNS over TLS support today.
I used to use Voxel's firmware on my Netgear R7800, and that had stubby built-in, so enabling it was just a command or two and it was up and running.
It's been a while since I messed around with DD-WRT, so if anyone could point me in the right direction. Would Stubby still be required or is there DNS-over-TLS support already built-in to DD-WRT?
and? u believe google? one of the most tracking intensive companies on this earth? if "security" matters to u..
Okay... not Google then. Could go back to using CloudFlare's (1.1.1.1) DNS which also supports DoT, but getting stubby installed and working on DD-WRT seems quite complicated.
id take cloudflare any day, i use them too, quite fast indeed.
Do you use DNS over TLS with CloudFlare since it supports it, or do you just have your router set to use 1.1.1.1 in the GUI?
no dns over TLS, i dont care, i want speed. i use 1.0.0.1 (cloudflare, but cause some of my devices dislike 1.1.1.1 so i use their secondary), + 4.2.2.3 (level3 dns, very good, check them out), + 208.67.222.222 (opendns), + my isp, i do not enforce any of them, all are there for redundancy, cause randomly my isp dns has gone down more than twice.
i intentionally ensure all my routing to these dns servers are different, so if something happens, which has already, i have a backup. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I replicated your settings and some hosts that I use are not resolving now. Reverted to the settings that I had before and it works fine. For example, ping strangled.net doesn't resolve with your settings.
And...This shows how copy/paste works...especially if you don't know whats all about it..
The reason why I asked the *gurus* on this thread (where I see the master @Kong actively chimes in) so that I don't have to research a lot on something as basic as DNS. I am sure most of you must have nailed it. It looks like I have to take the hard route and read it now.
What is your setting on the Setup - Basic Setup - Static DNS 1/2/3? I had 192.168.1.1 (router IP) on Static DNS 1 and now I zeroed it out. _________________ Netgear R7800 [DD-WRT]; ASUS RT-87U [DD-WRT]; ASUS RT-AC68U [FreshTomato]
