Linksys EA8500
DD-WRT v3.0-r34900M kongat [02/14/18]
Linux 3.18.94 #274 SMP PREEMPT Wed Feb 14 22:40:44 CET 2018 armv7l
DAMN KONG!!!
I see some EA8500 people have had good luck with this but I'll tell ya my opinion.
It's a bloody fkng scary nightmare if you are running servers and using
'Port Range Forwarding' which I have for years for multiple http servers & ftp plus some other junk.
This build --- IT DON"T WORK -- any DNS resolved to my IP goes straight to the router asking for router UN & PW.
Prolly something broken with loopback --- cause I was inside local doing this.
Yea I did a reboot and also clicked apply settings in port range forwarding.
No I didn't try from an external source --- 50/50 chance it might have worked but
I just needed to get back in order so I booted back into part 1 that has r34800M and
all is good ... ok thankyouthankyougottago
Linksys EA8500
DD-WRT v3.0-r34900M kongat [02/14/18]
Linux 3.18.94 #274 SMP PREEMPT Wed Feb 14 22:40:44 CET 2018 armv7l
DAMN KONG!!!
I see some EA8500 people have had good luck with this but I'll tell ya my opinion.
It's a bloody fkng scary nightmare if you are running servers and using
'Port Range Forwarding' which I have for years for multiple http servers & ftp plus some other junk.
This build --- IT DON"T WORK -- any DNS resolved to my IP goes straight to the router asking for router UN & PW.
Prolly something broken with loopback --- cause I was inside local doing this.
Yea I did a reboot and also clicked apply settings in port range forwarding.
No I didn't try from an external source --- 50/50 chance it might have worked but
I just needed to get back in order so I booted back into part 1 that has r34800M and
all is good ... ok thankyouthankyougottago
There's the new Kong test build 35030M with 3.18 kernel that might fix this.
Linksys EA8500
DD-WRT v3.0-r34900M kongat [02/14/18]
Linux 3.18.94 #274 SMP PREEMPT Wed Feb 14 22:40:44 CET 2018 armv7l
DAMN KONG!!!
I see some EA8500 people have had good luck with this but I'll tell ya my opinion.
It's a bloody fkng scary nightmare if you are running servers and using
'Port Range Forwarding' which I have for years for multiple http servers & ftp plus some other junk.
This build --- IT DON"T WORK -- any DNS resolved to my IP goes straight to the router asking for router UN & PW.
Prolly something broken with loopback --- cause I was inside local doing this.
Yea I did a reboot and also clicked apply settings in port range forwarding.
No I didn't try from an external source --- 50/50 chance it might have worked but
I just needed to get back in order so I booted back into part 1 that has r34800M and
all is good ... ok thankyouthankyougottago
I also see occasional logins to dropbear from the router itself, really strange, do you use ad block with privoxy?
Somethings goes in the wrong pipe. Have to check what major commits might have broken it. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
I also see occasional logins to dropbear from the router itself, really strange, do you use ad block with privoxy?
Somethings goes in the wrong pipe. Have to check what major commits might have broken it.
Yeah must have been something between 34800-900 as 34800 worked great for mrjcd
Linksys EA8500
DD-WRT v3.0-r34900M kongat [02/14/18]
Linux 3.18.94 #274 SMP PREEMPT Wed Feb 14 22:40:44 CET 2018 armv7l
DAMN KONG!!!
I see some EA8500 people have had good luck with this but I'll tell ya my opinion.
It's a bloody fkng scary nightmare if you are running servers and using
'Port Range Forwarding' which I have for years for multiple http servers & ftp plus some other junk.
This build --- IT DON"T WORK -- any DNS resolved to my IP goes straight to the router asking for router UN & PW.
Prolly something broken with loopback --- cause I was inside local doing this.
Yea I did a reboot and also clicked apply settings in port range forwarding.
No I didn't try from an external source --- 50/50 chance it might have worked but
I just needed to get back in order so I booted back into part 1 that has r34800M and
all is good ... ok thankyouthankyougottago
I also see occasional logins to dropbear from the router itself, really strange, do you use ad block with privoxy?
Somethings goes in the wrong pipe. Have to check what major commits might have broken it.
Have never used adblock.
Router also has NOT ever had remote access on....although this build and BS latest public release all traffic on port 80 to my IP goes directly to router login.
Yea, something going down the wrong pipe
You other people may want to load your WAN IP into a browser and see what happens.
Could be cause in forwarding I have port 80 forwarded to other IP but might be 80 is open to router anyways???? You should check if running this build or BS r35034.
Linksys EA8500
DD-WRT v3.0-r34900M kongat [02/14/18]
Linux 3.18.94 #274 SMP PREEMPT Wed Feb 14 22:40:44 CET 2018 armv7l
DAMN KONG!!!
I see some EA8500 people have had good luck with this but I'll tell ya my opinion.
It's a bloody fkng scary nightmare if you are running servers and using
'Port Range Forwarding' which I have for years for multiple http servers & ftp plus some other junk.
This build --- IT DON"T WORK -- any DNS resolved to my IP goes straight to the router asking for router UN & PW.
Prolly something broken with loopback --- cause I was inside local doing this.
Yea I did a reboot and also clicked apply settings in port range forwarding.
No I didn't try from an external source --- 50/50 chance it might have worked but
I just needed to get back in order so I booted back into part 1 that has r34800M and
all is good ... ok thankyouthankyougottago
I also see occasional logins to dropbear from the router itself, really strange, do you use ad block with privoxy?
Somethings goes in the wrong pipe. Have to check what major commits might have broken it.
Have never used adblock.
Router also has NOT ever had remote access on....although this build and BS latest public release all traffic on port 80 to my IP goes directly to router login.
Yea, something going down the wrong pipe
You other people may want to load your WAN IP into a browser and see what happens.
Could be cause in forwarding I have port 80 forwarded to other IP but might be 80 is open to router anyways???? You should check if running this build or BS r35034.
that build NTP is screwed so it completely useless to EA8500
I get login attempts to dropbear that originate from the router itself, but as far as I can tell they only occur if I PCs surf the web via privoxy. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Linksys EA8500
DD-WRT v3.0-r34900M kongat [02/14/18]
Linux 3.18.94 #274 SMP PREEMPT Wed Feb 14 22:40:44 CET 2018 armv7l
DAMN KONG!!!
I see some EA8500 people have had good luck with this but I'll tell ya my opinion.
It's a bloody fkng scary nightmare if you are running servers and using
'Port Range Forwarding' which I have for years for multiple http servers & ftp plus some other junk.
This build --- IT DON"T WORK -- any DNS resolved to my IP goes straight to the router asking for router UN & PW.
Prolly something broken with loopback --- cause I was inside local doing this.
Yea I did a reboot and also clicked apply settings in port range forwarding.
No I didn't try from an external source --- 50/50 chance it might have worked but
I just needed to get back in order so I booted back into part 1 that has r34800M and
all is good ... ok thankyouthankyougottago
I also see occasional logins to dropbear from the router itself, really strange, do you use ad block with privoxy?
Somethings goes in the wrong pipe. Have to check what major commits might have broken it.
Have never used adblock.
Router also has NOT ever had remote access on....although this build and BS latest public release all traffic on port 80 to my IP goes directly to router login.
Yea, something going down the wrong pipe
You other people may want to load your WAN IP into a browser and see what happens.
Could be cause in forwarding I have port 80 forwarded to other IP but might be 80 is open to router anyways???? You should check if running this build or BS r35034.
that build NTP is screwed so it completely useless to EA8500
I get login attempts to dropbear that originate from the router itself, but as far as I can tell they only occur if I PCs surf the web via privoxy.
The problem is timing --- EA8500 eth0 don't come up till --
[ 17.271678] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
ALL previous builds was --
[ 9.003827] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 9.031959] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
and then we have NTP is slow as forever
all this screws up dnscrypt-proxy and DNSMasq and just about everything --
I installed 35030M this morning with same results --- any hit to my IP would result in router login page.
Booted back into 35030M a while ago --- waited minute or so (after booted & loaded webif) NTP finally set itself but dnscrypt never picked up and .... trying from cell phone (cell network) mrjcd.com would pull up router login page.
killed dnscrypt-proxy --- yay everything went to working with fail back DNS set on main page.
Turned DNSCrypt + DNSSEC back on as I normallly run and all is good.
All DNS test show using my dnscrypt.ca server 3 buddy.
So yea, it's all working.
Short story - had to turn off dnscrypt-proxy then turn him back on after everything else was set
good grief .... now that I know what's going on I'll let r35030M kongat run few days.
this is a bit scary --- just tested simple reboot and it gets into the same tangeled mess
Linksys EA8500
DD-WRT v3.0-r34900M kongat [02/14/18]
Linux 3.18.94 #274 SMP PREEMPT Wed Feb 14 22:40:44 CET 2018 armv7l
DAMN KONG!!!
I see some EA8500 people have had good luck with this but I'll tell ya my opinion.
It's a bloody fkng scary nightmare if you are running servers and using
'Port Range Forwarding' which I have for years for multiple http servers & ftp plus some other junk.
This build --- IT DON"T WORK -- any DNS resolved to my IP goes straight to the router asking for router UN & PW.
Prolly something broken with loopback --- cause I was inside local doing this.
Yea I did a reboot and also clicked apply settings in port range forwarding.
No I didn't try from an external source --- 50/50 chance it might have worked but
I just needed to get back in order so I booted back into part 1 that has r34800M and
all is good ... ok thankyouthankyougottago
I also see occasional logins to dropbear from the router itself, really strange, do you use ad block with privoxy?
Somethings goes in the wrong pipe. Have to check what major commits might have broken it.
Have never used adblock.
Router also has NOT ever had remote access on....although this build and BS latest public release all traffic on port 80 to my IP goes directly to router login.
Yea, something going down the wrong pipe
You other people may want to load your WAN IP into a browser and see what happens.
Could be cause in forwarding I have port 80 forwarded to other IP but might be 80 is open to router anyways???? You should check if running this build or BS r35034.
that build NTP is screwed so it completely useless to EA8500
I get login attempts to dropbear that originate from the router itself, but as far as I can tell they only occur if I PCs surf the web via privoxy.
The problem is timing --- EA8500 eth0 don't come up till --
[ 17.271678] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
ALL previous builds was --
[ 9.003827] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 9.031959] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
and then we have NTP is slow as forever
all this screws up dnscrypt-proxy and DNSMasq and just about everything --
I installed 35030M this morning with same results --- any hit to my IP would result in router login page.
Booted back into 35030M a while ago --- waited minute or so (after booted & loaded webif) NTP finally set itself but dnscrypt never picked up and .... trying from cell phone (cell network) mrjcd.com would pull up router login page.
killed dnscrypt-proxy --- yay everything went to working with fail back DNS set on main page.
Turned DNSCrypt + DNSSEC back on as I normallly run and all is good.
All DNS test show using my dnscrypt.ca server 3 buddy.
So yea, it's all working.
Short story - had to turn off dnscrypt-proxy then turn him back on after everything else was set
good grief .... now that I know what's going on I'll let r35030M kongat run few days.
this is a bit scary --- just tested simple reboot and it gets into the same tangeled mess
Problem is, no permanent clock in these home routers and dnscrypt won't work if clock is off too much, it needs the correct time in order to work. One idea I have in order to improve this, we save the time every hour to nvram and at startup, before ntp is called, set the last saved time from nvram. If the router hasn't been offline for a long time this might work around the issue. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Problem is, no permanent clock in these home routers and dnscrypt won't work if clock is off too much, it needs the correct time in order to work. One idea I have in order to improve this, we save the time every hour to nvram and at startup, before ntp is called, set the last saved time from nvram. If the router hasn't been offline for a long time this might work around the issue.
Yea I understand the time issue --- but why when dnscrypt-proxy broke down did it cause port forward issues.
It should never make any difference if I have internal DNS .... sites resolved to my IP(WAN) should still always be forwarded to the correct internal IP -- not the router.
I've had many issues with unbound or dnscrypt servers broken but it never affected outside clients from reaching the correct internal server.
Something in the code has a link with dnscrypt-proxiy and port forwarding and it shouldn't.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Feb 21, 2018 20:36 Post subject:
this fw has no "stable" builds. every single router on every build has something wrong with it, not counting issues affecting all routers all the time. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
this fw has no "stable" builds. every single router on every build has something wrong with it, not counting issues affecting all routers all the time.
Show me any firmware that does not have issues. LOL
I don't know any hw,sw that does not have any bugs.
If there would have been a firmware that worked 100% I would have never started developing my own. Before I created my first build I bought 4 different routers within a year and each one of them had issues.
Some oems are more stable, just because they never add any features or update any of their base software e.g. kernel and therefore come with 10y old kernels, where no one knows how many security issues they have. They simply stay on the same software for the whole life cycle and just fix bugs or just simply never fix the bugs and just release a new product. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
i guess "stable"was the wrong phrase.what kong do you guys think would work the best on the WZR1750DHP in your opinion?i've tried 6 different bs builds with alot of opendns instability,and other broken/non working features.the one i tried that was rock solid was almost 4 years old.
.... now that I know what's going on I'll let r35030M kongat run few days.
