Posted: Tue Mar 20, 2018 0:58 Post subject: Kong test r35400M
Linksys EA8500
DD-WRT v3.0-r35400M kongat [03/19/18]
Linux 3.18.99 #283 SMP PREEMPT Mon Mar 19 22:41:50 CET 2018
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Test/
ddwrt-Linksys-EA8500.bin 2018-03-19 23:25 26M
DNSCrypt has same problems I mentioned here
https://www.dd-wrt.com/phpBB2/viewtopic.php?p=1121938#1121938
Takes approx 1 full minute after router is fully booted before time will set and DNSCrypt will eventually start working but ---
my port 80 is still completely screwed where everything coming in on 80 goes to router login.
I have rebooted multiple times using different DNSCrypt servers also turning off Cache DNSSEC data and Validate DNS Replies (DNSSEC).
Don't know what's wrong w/DNSCrypt --- works after you turn it off and back on --- hell the ovpn server even starts & works just fine once time is synced.
Done tired of messing with it. Never liked DNSCrypt anyways --- wish you woud fix unbound on your builds.
Anyways, I picked out 3 fast-ass OpenNic no-logging DNS servers that work great.
fastest here in Texas, 2nd in North Carolina, 3rd in New Jersey and all seem good so don't think there is any way I'll lose all three.
I can do a reboot and time is synced before you can even get to the webif.
So heck with all that fancy incognito DNS bullshit.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Mar 20, 2018 1:10 Post subject:
is lzo compression still there in wifi settings? if i flash i cant get back to r35384 since it was pulled & theres ONE, thing it has improved, wifi throughput is absurdly high _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
is lzo compression still there in wifi settings? if i flash i cant get back to r35384 since it was pulled & theres ONE, thing it has improved, wifi throughput is absurdly high
yeahuh in 2.4 & 5 ... I have it disabled on both my radio.
somethesesdays imma get some fast wireless stuff but for now I just saturate the EA8500 with old-ass devices
EDIT:
This does have the double nvram so I'm using 44/128 where I was using 44/64 in r34800 but didn't have any problem there --- have NO ideal what might happen if tried to boot back into r34800.....most likely won't have to worry about it.
You should be fine since you already had 128 with that build buit I would certainly have backup handy ---
The EA8500 has been on 10.4-3.5.3-00050 for long while now 3.18 & k4.x
I gotta tell you how fucked up this nvram thing is on a dual boot router.... well until you understand it anyways
The 2nd EA8500 has been live running as a switch / ovpn ser / vlan running r35384 before I put Kong new r35400M.
All went well same settings all good.
Ok I just installed r34800M onto it and it booted (after I found it at (192.168.1.1) with zero config to the set username password page.
Didn't touch the webif but telnet in and boot other part back into r35400M and it boots up with its old normal IP 10.72.29.52 and config ... ovpn ser still good , VLAN good.
You think this won't be some confusing crap for most people????
So I assume if I have to boot the main router back into r34800 it will have a dd-wrt default config....this is almost laughable.
I'm also sure this is not just a dual boot router thing ---- I bet if your r7800 installed earlier build w/64K nvram you would have default config but if you then without changing anything installed a 128K nvram build you would have you same old config back.
I can see this getting really interesting in the coming weeks...All this talk about lost nvram settings is bullshit --- they aint lost they just moved
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Mar 20, 2018 5:16 Post subject:
mrjcd wrote:
The EA8500 has been on 10.4-3.5.3-00050 for long while now 3.18 & k4.x
I gotta tell you how fucked up this nvram thing is on a dual boot router.... well until you understand it anyways
The 2nd EA8500 has been live running as a switch / ovpn ser / vlan running r35384 before I put Kong new r35400M.
All went well same settings all good.
Ok I just installed r34800M onto it and it booted (after I found it at (192.168.1.1) with zero config to the set username password page.
Didn't touch the webif but telnet in and boot other part back into r35400M and it boots up with its old normal IP 10.72.29.52 and config ... ovpn ser still good , VLAN good.
You think this won't be some confusing crap for most people????
So I assume if I have to boot the main router back into r34800 it will have a dd-wrt default config....this is almost laughable.
I'm also sure this is not just a dual boot router thing ---- I bet if your r7800 installed earlier build w/64K nvram you would have default config but if you then without changing anything installed a 128K nvram build you would have you same old config back.
I can see this getting really interesting in the coming weeks...All this talk about lost nvram settings is bullshit --- they aint lost they just moved
thats what i hated most about ea8500, and every so often the partition magic gets reversed (when the one u dont want flashed/switched to does so).
noticed the radio temps are fixed now not synced to cpu temp.
so is this actual 128kb nvram or is bad things going to happen when we get over 64kb, like those linksys broadcom ea series over 32kb?
edit: so which lzo detection is right here? https://imgur.com/a/1kLQn im thinking the wifi status page is wrong cause i disabled it on the wndr4300 wds sta (ath0.sta2) and it still says lzo on the r7800, its tx'ing some compressed packets to it but not rx'ing any compressed back
kong's site readme needs an update for wifi leds statement _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
edit: so which lzo detection is right here? https://imgur.com/a/1kLQn im thinking the wifi status page is wrong cause i disabled it on the wndr4300 wds sta (ath0.sta2) and it still says lzo on the r7800, its tx'ing some compressed packets to it but not rx'ing any compressed back
Haven't played with it but will hook the two EA8500 up later see what happens.
I'm thinking the lzo showing in GUI is meaning it is on on that router for that client regardless if the client has it off/on or actually using it or whatever (the router has it available for use) .... but I could be wrong
EDIT: As I said mine is turned off but still show
so I guess I told you completley backwards or the GUI is NOT right
BTW, I put your pic in same directory as this one if you want to link back to it --- I'll use for later ref......
http://mrjcd.com/junk/dd-wrt/EA8500/r35400M/
..much easier to see than imgur BS . All I got time for ATM
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Thu Mar 22, 2018 8:06 Post subject:
For me, the lzo compression works in simplex mode:
WDS AP ------------------------------------------- WDS STA
Tx:compressed ------------------------------->>> Rx:compressed
Rx: No compress <<<------------------------------Tx:No compress
I have enabled lzo everywhere I saw _________________ ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Tue Apr 17, 2018 18:15 Post subject:
tatsuya46 wrote:
mrjcd wrote:
The EA8500 has been on 10.4-3.5.3-00050 for long while now 3.18 & k4.x
I gotta tell you how fucked up this nvram thing is on a dual boot router.... well until you understand it anyways
The 2nd EA8500 has been live running as a switch / ovpn ser / vlan running r35384 before I put Kong new r35400M.
All went well same settings all good.
Ok I just installed r34800M onto it and it booted (after I found it at (192.168.1.1) with zero config to the set username password page.
Didn't touch the webif but telnet in and boot other part back into r35400M and it boots up with its old normal IP 10.72.29.52 and config ... ovpn ser still good , VLAN good.
You think this won't be some confusing crap for most people????
So I assume if I have to boot the main router back into r34800 it will have a dd-wrt default config....this is almost laughable.
I'm also sure this is not just a dual boot router thing ---- I bet if your r7800 installed earlier build w/64K nvram you would have default config but if you then without changing anything installed a 128K nvram build you would have you same old config back.
I can see this getting really interesting in the coming weeks...All this talk about lost nvram settings is bullshit --- they aint lost they just moved
thats what i hated most about ea8500, and every so often the partition magic gets reversed (when the one u dont want flashed/switched to does so).
noticed the radio temps are fixed now not synced to cpu temp.
so is this actual 128kb nvram or is bad things going to happen when we get over 64kb, like those linksys broadcom ea series over 32kb?
I haven't seen MRJCD post in almost 4 weeks, hope he's doing ok and on a NICE vacation somewhere Awesome...
Tatsuya- Can you clarify this NVRAM thing for me; were older builds from Kong & BS at 64kB and now they are at 128kB? Any Idea at what SVN this happened?
Also, what does this mean in lay-mans terms?
I assume it means that if you try to revert to older builds your settings are all lost and you have to re-set up everything?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Apr 17, 2018 21:00 Post subject:
msoengineer wrote:
tatsuya46 wrote:
mrjcd wrote:
The EA8500 has been on 10.4-3.5.3-00050 for long while now 3.18 & k4.x
I gotta tell you how fucked up this nvram thing is on a dual boot router.... well until you understand it anyways
The 2nd EA8500 has been live running as a switch / ovpn ser / vlan running r35384 before I put Kong new r35400M.
All went well same settings all good.
Ok I just installed r34800M onto it and it booted (after I found it at (192.168.1.1) with zero config to the set username password page.
Didn't touch the webif but telnet in and boot other part back into r35400M and it boots up with its old normal IP 10.72.29.52 and config ... ovpn ser still good , VLAN good.
You think this won't be some confusing crap for most people????
So I assume if I have to boot the main router back into r34800 it will have a dd-wrt default config....this is almost laughable.
I'm also sure this is not just a dual boot router thing ---- I bet if your r7800 installed earlier build w/64K nvram you would have default config but if you then without changing anything installed a 128K nvram build you would have you same old config back.
I can see this getting really interesting in the coming weeks...All this talk about lost nvram settings is bullshit --- they aint lost they just moved
thats what i hated most about ea8500, and every so often the partition magic gets reversed (when the one u dont want flashed/switched to does so).
noticed the radio temps are fixed now not synced to cpu temp.
so is this actual 128kb nvram or is bad things going to happen when we get over 64kb, like those linksys broadcom ea series over 32kb?
I haven't seen MRJCD post in almost 4 weeks, hope he's doing ok and on a NICE vacation somewhere Awesome...
Tatsuya- Can you clarify this NVRAM thing for me; were older builds from Kong & BS at 64kB and now they are at 128kB? Any Idea at what SVN this happened?
Also, what does this mean in lay-mans terms?
I assume it means that if you try to revert to older builds your settings are all lost and you have to re-set up everything?
it means theres more nvram. if ur going to revert to something old that has 64kb just try it first and see what happens, if things go weird then u reset.