Run on EA8500.
Only last about one day and then wifi started dropping, both on 2.4G and 5G. Rolled back to 33772.
r33772 is a good build on that unit but just wondering if you done a reset & reconfig after installing a recent build??? ... that would probably be a good ideal ---
--- much has changed since 2017.
On the EA8500 I'm still using:
DD-WRT v3.0-r37495M kongat 10/25/18
Linux 4.9.135 #253 SMP PREEMPT Thu Oct 25 02:05:21 CEST 2018 armv7l
uptime 13 days, 11:42
VAPs on both radio
ovpn server
SAMBA share
VLAN on port 4
QOS HFSC FQ_CODEL
some stuff in 'Port Range Forwarding'
30 static leases
turned unbound off couple days ago just because without using 'Recursive DNS Resolving'
I can now also use local DNS while connected to its ovpn server.
Using QUAD9 public DNS and they do DNSSEC anyways.
tis all been good
My previous runing was Kong_37495M-102818_K3.18. Before Kong_37495M-102818_K3.18, I was in linksys FW_EA8500_1.1.4.169978_prod.img. After 30-30-30 reset on 169978, I Loaded Kong_37495M-102818_K3.18. And then had a "Restore Factory Defaults" in the web UI.
After basic setup, EA8500 worked very well. Most settings were default. The lan subnet setting to 192.168.2.1 and wan ip as 192.168.1.2(My modem is on 192.168.1.254). 2.4G was wpa2,N-only,40M and 5G was wpa2,AC-only,80M. But at the evening of the day after, wifi went mad. After power-off-on, the wifi was still not stable. I had to switch to the 33772.
Anything I can try on the new firmware?
I have a USB-SSD attached on EA8500 and conneted my laptop to EA8500 by wire. The R/W speed was about 90MB on linksys firmware on NTFS system. But on 33772 I only got 35MB on ext4 file system. Is it a normal speed on dd-wrt? Only about 1/3 of original. And on Kong_37495M-102818_K3.18, I only got 26MB even worse than 33772
Browser update from r36375M, no reset. Solid LAN, good Access Restrictions, no wifi access all bands [ath0/0.1, ath1/1.1]. Logs show no key handshake attempts made. Radios broadcasting status all show up good. Minor misplaced decimal with CPU temp.
Production system with no time to investigate so reverted successfully.
Joined: 17 Jan 2018 Posts: 64 Location: Georgia, USA
Posted: Fri Nov 09, 2018 10:36 Post subject:
r7800
DD-WRT v3.0-r37495M kongat (10/28/1
3.18.124 #361 SMP PREEMPT Sun Oct 28 16:18:27 CET 2018
Updated by GUI with no reset.
Up 8 days with no problems for me.
Single router setup with vlans, guest networks, openVPN client, no QOS. _________________ R7800 r53339 std (08/01/23)
Private network on bridge br0 = eth1 (vlan 1) + wlan0 + wlan1.
Guest network on bridge br1 = eth1.4 (vlan 4) + VAPs (wlan0.1 + wlan1.1) for IOT devices
(Roku's, Amazon Echos, smart switches, etc.) and guest.
Noob still finding my way.
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "1 2 6"
swconfig dev switch0 vlan 4 set ports "3 4 6t"
swconfig dev switch0 set apply
vconfig add eth1 4
brctl addif br1 eth1.4
ifconfig eth1.4 up
Last edited by sweatbee on Fri Nov 09, 2018 17:42; edited 1 time in total
oh well what the heck -- since the k4.9.x killed over after 16 days I decided to install this one:
The k4.9x worked perfect after a power cycle --- anyways we'll see it this last longer than 16 days.
EA8500
DD-WRT v3.0-r37495M kongat 10/28/18
Linux 3.18.124 #362 SMP PREEMPT Sun Oct 28 16:25:17 CET 2018 armv7l
WAN MAC clone
WAN DHCP
30 static leases
OVPN server
Local DNS
SAMBA share FAT32 USB stick
VAPs on both radio + VLAN port4 via br1
QOS HFSC FQ_Codel
same config I had before ...I just done an 'erase nvram' and reconfig from scratch for the hell of it
Option: right after input, you can add -i interfacename (find the real name with ifconfig) and apply it just to wifi, which is handy if the abusive clients are only on wifi. Usually, 5000 connections and a router crash is from wifi appliances on a retry spree.
After you try these usual steps, if your router still crashes, then you may have found a bug (connectivity fault) that blocks clients from something they really want, causing them to retry way too much.
I mention it here, because we sure do need modern timeouts and Connlimit in the gui.
oh well what the heck -- since the k4.9.x killed over after 16 days I decided to install this one:
The k4.9x worked perfect after a power cycle --- anyways we'll see it this last longer than 16 days.
EA8500
DD-WRT v3.0-r37495M kongat 10/28/18
Linux 3.18.124 #362 SMP PREEMPT Sun Oct 28 16:25:17 CET 2018 armv7l
WAN MAC clone
WAN DHCP
30 static leases
OVPN server
Local DNS
SAMBA share FAT32 USB stick
VAPs on both radio + VLAN port4 via br1
QOS HFSC FQ_Codel
same config I had before ...I just done an 'erase nvram' and reconfig from scratch for the hell of it
Well just had same issue with my k3.18 r7500v2. Had to power cycle to bring things back. This time I disabled both beamformings and noise immunity (with better results in previous builds). Will see how this goes
Well just had same issue with my k3.18 r7500v2. Had to power cycle to bring things back. This time I disabled both beamformings and noise immunity (with better results in previous builds). Will see how this goes
hmmm...... I was hoping maybe the K3.18.x would not kill-over. That's bad news
I disabled all beamformings and noise immunity on the EA8500 a while back since I really
have no use for it and they are few other WiFi devices around here close anyways.
May have to put it on a weekly reboot or stick with an older build..... have to look up what build I was running around first part of March. I know it worked fine cause I was unable to even check on it for couple months.
May have to put it on a weekly reboot or stick with an older build..... have to look up what build I was running around first part of March. I know it worked fine cause I was unable to even check on it for couple months.
Quick question: I'd like to schedule reboot it too but currently I have to run this command at startup manually to fix dnssec (need to be after everything comes up, the Save startup option doesn't work because it starts before dns entries insert, which overwrites it). Any ideas on how to get it autorun at the end of the bootup sequence?
head -n 2 /tmp/resolv.dnsmasq > /tmp/resolv.dnsmasq.tmp && mv /tmp/resolv.dnsmasq.tmp /tmp/resolv.dnsmasq
Quick question: I'd like to schedule reboot it too but currently I have to run this command at startup manually to fix dnssec..
I don't have anything in startup other than VLAN config.
Guess you could have something like ' sleep 10 ' at its first if you really must have that startup.
Quick question: I'd like to schedule reboot it too but currently I have to run this command at startup manually to fix dnssec..
I don't have anything in startup other than VLAN config.
Guess you could have something like ' sleep 10 ' at its first if you really must have that startup.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Nov 10, 2018 23:31 Post subject:
jerrytouille wrote:
mrjcd wrote:
oh well what the heck -- since the k4.9.x killed over after 16 days I decided to install this one:
The k4.9x worked perfect after a power cycle --- anyways we'll see it this last longer than 16 days.
EA8500
DD-WRT v3.0-r37495M kongat 10/28/18
Linux 3.18.124 #362 SMP PREEMPT Sun Oct 28 16:25:17 CET 2018 armv7l
WAN MAC clone
WAN DHCP
30 static leases
OVPN server
Local DNS
SAMBA share FAT32 USB stick
VAPs on both radio + VLAN port4 via br1
QOS HFSC FQ_Codel
same config I had before ...I just done an 'erase nvram' and reconfig from scratch for the hell of it
Well just had same issue with my k3.18 r7500v2. Had to power cycle to bring things back. This time I disabled both beamformings and noise immunity (with better results in previous builds). Will see how this goes
if ur certain its wifi related enable logs and post them if it happens again _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I'm currently running my EA8500 on r37420M-K3.18.
As per previous post:
"My Internet radio doesn't work on either r37495M builds, but is fine on r37420M
So something has broken between r37420M and r37495M that affects the 2.4 wifi.
The digital/internet radio is an older unit, running 2.4/54Mbps G wifi and uses the Jupiter 6.2 chipset by Frontier Silicon."
I have the router reboot once a week automatically, so can't speak to the >15 day lockups.
Looks like r37495M may have more issues than the r37420M builds. _________________ ------------------------------------
Linksys WRT3200ACM DD-WRT r55819 (Gateway)
Linksys EA8500 OpenWrt-23.05.3 (Wired AP)
Netgear WNDR3700v4 DD-WRT r55819 (spare Gateway)
Photos: https://www.flickr.com/photos/nickant44/albums
Absolutely great build, one of the best. Thanks Kong! No wonder it was promoted stable. The k4.9 one has good QoS, too, k3.18 gets lags lower by some 10-15ms. But if ISP is giving already a good pipe, like the one in the above post, in real usage with same QoS settings for build r37495M, k4.9 and k3.18 don't make any perceptible difference on VoIP, gaming, streaming. Choice is here!
No wonder it was promoted stable. The