I think there is something wrong with the site survey in this build. I had a second router in use, a wrt3200acm setup as a VPN. I know there are issues with the 5ghz band on the wrt3200acm but I think the 2.4 is performing OK.
when I do a site survey from the EA8500 it is reporting the wrt3200acm as b/g so I dug out and old DLink and did a site survey and it reports the wrt3200acm correctly. I also checked with WifiInfoView and it reports the wrt3200’s 2.4 band correctly. Am I missing something?
I think there is something wrong with the site survey in this build. I had a second router in use, a wrt3200acm setup as a VPN. I know there are issues with the 5ghz band on the wrt3200acm but I think the 2.4 is performing OK.
when I do a site survey from the EA8500 it is reporting the wrt3200acm as b/g so I dug out and old DLink and did a site survey and it reports the wrt3200acm correctly. I also checked with WifiInfoView and it reports the wrt3200’s 2.4 band correctly. Am I missing something?
I don't know about the 3200 ... I guess it don't know what to think of the Marvell chips.
Maybe the EA8500 just don't like it. Tis something Kong would prolly have to answer.
AFAICT site survey looks ok to me.
Survey from EA8500 WAP running r31870M kongat (04/16/17)
@ mrjcd, as usual you're correct. I connected a wrt1900acs and did the site survey from the EA8500 once again with the latest Kong build and it don't like that one either. It could have been doing on previous builds but never noticed it until now. Here the 3200 and 1900 reporting as b/g
@ mrjcd, as usual you're correct. I connected a wrt1900acs and did the site survey from the EA8500 once again with the latest Kong build and it don't like that one either. It could have been doing on previous builds but never noticed it until now. Here the 3200 and 1900 reporting as b/g
That is interesting... Have you bridged them with 2.4 to see how they will do??
Client or Client Bridge is not something I use on regular basis but I like to play with it sometimes.
Just wondering if it would stay connected to the 3200
@ mrjcd, I’m using the EA8500 as my primary router. I have the wrt3200 configured as a VPN client. I connected the wrt3200’s WAN port to the EA8500’s LAN port. At the moment the wrt3200 is getting really fast speeds on the VPN over the 2.4ghz band. I posted the speed results here
@ mrjcd, I’m using the EA8500 as my primary router. I have the wrt3200 configured as a VPN client. I connected the wrt3200’s WAN port to the EA8500’s LAN port. At the moment the wrt3200 is getting really fast speeds on the VPN over the 2.4ghz band. I posted the speed results here
That looks good. The EA8500 should hold close to those rates as VPN client
When I win the lottery I'll get fast internet. The ISP has fiber run into the place years ago... they use us a guinea pigs in all their adventures. Good thing is all fiber connections with them are same up/down .. bad news is a 100/100 connection is currently priced at $199.95 per mo
We are lucky in that aspect because we are in a somewhat congested area so the trade off with the congestion is there are competing ISP’s which usually benefits the consumer. My sister on the other hand is in a less congested area with only one ISP so she’s kind of held hostage.. I think that’s the reason why you see all this “cord cutting” going on. Just for laughs I added an HD antenna a few years ago and the antenna channels that come in are just as crisp as the ISP delivered local channels. Hopefully your ISP will do something for you or another will jump-in and compete
Any reason to update to the latest Kong over this? I am at 23 days uptime on this 31500M so far, no problems.
Ath 0
Wireless Packet Info
Received (RX)26939926 OK, no error
Transmitted (TX)67831671 OK, no error
Ath 1
Received (RX)15106084 OK, 169 errors
Transmitted (TX)25189653 OK, no error
If it's working well for you might as well leave as is....or not
Don't remember all but think there was an update to unbound if you use that or newest builds BS & Kong
have DNSCrypt you can enable thru the webif if you want to use that. May have been some slight updates/changes
to openVPN... probably many other slight changes. Wireless is good on the Kong latest build although I'm not
running it at the moment. Seemed like errors on my VAPs (ath0.1 & ath1.1) have been reduced considerably last build or so.
It's good to update from time to time I reckon and the good thing is you can always boot the EA8500 back into
the other partition and be right back where you were if needed.
Of course it is good to keep a backup handy also --
I'm just waiting on them to move us up to the K4x and see what evil lurks there ... it should be fun when they do ... bugs and all
EA8500
DD-WRT v3.0-r31900M kongat (04/26/17)
Linux 3.18.50 #97 SMP PREEMPT Wed Apr 26 22:16:46 CEST 2017 armv7l
Thanks for fixing openVPN server logging.
Log in local time is also very nice.
Everything seems good but the DNSCrypt OpenNIC buffoons run-a-muck 'bout 16:00 my time yesterday.
Could no longer retrieve server certificates.
Switched to 'CS Dallas TX US DNSCrypt server'. Run for about 10 hrs but got hundreds logged
daemon.warn dnsmasq[xxxxx]: possible DNS-rebind attack detected: from multiple domains
DNS-rebind attack detected was always from address formatted like, e.g. -- site.domain.com or site.site.domain.com
I dunno for sure but leads me to think the 'CS Dallas TX US DNSCrypt server' does not block private IPs.
Very likely my subnet may be in some type conflict there?????
Using DNSCrypt Cisco OpenDNS now without any problem.
My preference is to use unbound all time but it screws up local access from the openVPN server tun.
Guess could work on its confg file but I really don't like to do that. I'll get tired of
playing with this DNSCrypt stuff before long and go back to unbound and use openVPN server from
one of the WAPs -- no problem with that
root@--:~# date
Thu Apr 27 10:30:18 CDT 2017
root@--:~# uptime
10:30:22 up 15:39, load average: 0.09, 0.09, 0.02
Well OpenNIC Anycast DNSCrypt is back so I'm using them again. Someone must have done them a dirty yesterday.
I'm still hitting their 45.32.202.172 in Dallas... works dang good -- when its alive. Their certs still
say valid from [2016-05-28] to [2017-05-28] so I expect that to go to shit in near future unless someone pulls
their head out. Just a FYI - the Cisco bunch have a 10 year span on theirs certs.
Absolutely no more possible DNS-rebind attack detected using OpenDNS or OpenNIC.
r31900M kongat (04/26/17)
Seems a good solid build.
WDS w/TurboQAM still just 600 but I ain't complaining.
root@--:~# uptime
10:34:21 up 1 day, 15:43, load average: 0.08, 0.05, 0.00
root@--:~# date
Fri Apr 28 10:34:22 CDT 2017
I'm slow compared to a lot of you but I still get around
EDIT: some people just should not own some devices...
From ioactive.com, "We found that 11% of the ~7000 exposed devices were using default
credentials and therefore could be rooted by attackers."
This kind of stuff about people just blows my mind. That's about the equivalent of posting
on social media that you are leaving on vacation and the house will be unlocked.
~ likely to get much worse before it gets better ~
Firmware version: 1.1.7.182977
Release date: Aug 9, 2017
- Update for compliance of the latest CE requirements (European models)
- Addressed IOActive security issues
- Additional security fixes and enhancements
- Resolved issue of DHCP reservation feature not working properly if user changes local
network configuration
- Resolved issue of toggling Wi-Fi disable/enable button may disable guest network
- Resolved issue of DMZ feature not working properly
- Resolved issue of PPPoE detection overriding DHCP detection in a dual server environment
on WAN even though DHCP is first detected
- Resolved issue of IPv6 incompatibility when prefix is not 64-bit
- Resolved issue of not being able to display IPv6 prefix address in status report if the
prefix is not 64-bit
- Resolved issue of Linksys Smart Wi-Fi and NTP not working with Universal Telecom in Sweden
- Resolved issue of IPv6 firewall blocking inbound, unsolicited IPsec traffic (IKE and ESP)
- Addressed an issue of notification function of the product
- Various minor bug fixes and enhancements
Have I ever used it? No, I probably won't.
Do I know anything else about it? No, I probably don't.
This is just a friendly reminder that you should use lastest version if you want to run stock firmware.
Last edited by mrjcd on Fri Aug 18, 2017 8:31; edited 1 time in total
FYI -for the folks still on stock FW or ones that may want to go back....
Thanks for the warning. On my EA8500 both partitions are dd-wrt but over in wrt3200 land I’m only using the stock firmware (as with other users) to toggle between LEDE and dd-wrt. Hopefully they could resolve the wrt3200acm dd-wrt issue so I could just flash both partitions and put the 3200 in back of the EA8500 to run our vpn service and be done with it.
So as the 3200 continues to struggle with wireless problems I have to give kudos to the EA8500. It has remained a solid performer and my primary router and will continue to do so. Just up over 13 days with the last Kong build so that’s where is going to stay. Besides for me it’s time to see one of my dd-wrt routers crack the 50 day & 100 day uptime barrier, yes its nice to have he latest and greatest FW but I want to see what it could do in the long haul since I haven’t done a 50 or 100 day run in while so its time.
