EA8500...main router
DD-WRT v3.0-r39855M kongat (05/25/19)
Linux 4.9.177 #413 SMP Sat May 25 15:14:58 CEST 2019 armv7l
No reset --install over r39830M
all is working well for me --- seems about same as previous
Something has changed in dnsmasq or firewall as dns no longer works with this build.
I get "dnsmasq log overflow" with this build, this is strange because I set the log to be quiet in the conf file.
I will check the commit logs if I can find them and see whats changed. I had to switch back to r39830 for now to get everything working again.
the connection problems of esp8266 based devices relies on SNR. with build r39830M (21-05-2019) it gets a signal strength of -75. in r39855 it doesn't get a connection without relocating.
Something has changed in dnsmasq or firewall as dns no longer works with this build.
I get "dnsmasq log overflow" with this build, this is strange because I set the log to be quiet in the conf file.
I will check the commit logs if I can find them and see whats changed. I had to switch back to r39830 for now to get everything working again.
dnsmasq works just fine same as it always has here
No problems at all with EA8500
up 23:53
Something has changed in dnsmasq or firewall as dns no longer works with this build.
I get "dnsmasq log overflow" with this build, this is strange because I set the log to be quiet in the conf file.
I will check the commit logs if I can find them and see whats changed. I had to switch back to r39830 for now to get everything working again.
It took a bit of playing with it and I have no idea which one did it but I changed a few things.
I noticed that my hostname had changed to the first entry as 0.0.0.0 instead of localhost.
So I added an entry for my router for 0.0.0.0 and :: and used the my local domain.
Clarification -
My 0.0.0.0 host kill file for spam domains was now assigning my router domain to the first domain listed in the kill file instead of nvram setting and the web interface, so I just adjusted the first entries to be my router and it seemed to have solved it.
I also added
no-resolv
to dnsmasq.conf
I then changed all three entries on the
"Network Address Server Settings (DHCP)" page to the router IP.
Then rebooted and DNS seems to be fine now.
I have no idea which one did it, lol.
found that turning on Filter TOS/DSCP in Security helps improve qos throughput especially upload fq_codel. TOS/DSCP is used by modern cake qos which is not in ddwrt so filtering it reduces overhead
Joined: 03 Jan 2010 Posts: 7248 Location: YWG, Canada
Posted: Tue May 28, 2019 5:10 Post subject:
fq_codel upload finally much closer to my entered limit, Filter TOS/DSCP isnt checked never was. im guessing the problem was https://svn.dd-wrt.com/changeset/39849
edit: nevermind.. its actually having my subnet in qos netmask (10.150.10.0/24) and set to express, even if no other subnets are entered, that will fix this and give me more proper upload.. accidentally discovered this when i was testing something unrelated. tried filter tos, and it completely broke download qos (disabled it) till i turned it off, which took 2x apply settings for some reason, and had no effect on upload. _________________ LATEST FIRMWARE(S) || Qualcomm Atheros Wi-Fi Settings Guide || Qualcomm Atheros Repeating
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
tried filter tos, and it completely broke download qos (disabled it) till i turned it off, which took 2x apply settings for some reason, and had no effect on upload.
Joined: 30 Jan 2015 Posts: 673 Location: Texas, USA
Posted: Tue May 28, 2019 15:02 Post subject:
Yes, its working fine on my R7800 with this build. _________________ 1 X R7800: Main gateway( r39855M kongat (05/25/19)
1 X RAX120 WAP Bridge
1 X RAX75 WAP Bridge
1 X R7800 Mesh
2 X R9000 Mesh
1 X R8000: Repeater bridge
1 X R8500: Client bridge (RB doesn't work on R8500)
Yes, its working fine on my R7800 with this build.
can you share your setup? can't get it working here which is weird since it was before
I have bad news...you need to erase NVRAM...
I had a similar issue with it not wanting to work when I switched from an older build to a newer build. Doing a factory reset seems to have killed the gremlins...
