Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Mon Nov 12, 2018 20:55 Post subject:
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
Hmmm, can't see the BS build, Pulled already? _________________ 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: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Mon Nov 12, 2018 22:00 Post subject:
I don't have EA8500, Lol. Please feel free to delete it. _________________ 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
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.
Maybe your settings are not working anymore, several wireless modes did not work as designed in older builds, e.g. ng-mixed also allowed b devices to connect, this and other modes are fixed as well and will behave differently. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
1: If you have a timed base restriction set to deny at a time that already past...or within 1.5 hours...and reboot...it/they will not deny untill the next day
2: Although clicking "apply" on the Access Restrictiond page makes all rules current..DO NOT DO IT WITHOUT A REBOOT...clicking apply only does some funk to the firewall rules somehow!!
I have recently noticed that when I click "apply" only. My logs showed a crapload of internet based ip addresses attempting (at least I hope only) to access my router..plus a few ssl errors, over the following 2 days!!...That are never there normally
As far as QOS.....keep playing with it....It works for most once properly tweeked _________________ Location 1
R7800- DD-WRT v3.0-r53562 (10/03/23) Gateway
WNDR3400v1 DD-WRT v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R7800- DD-WRT v3.0-r51855 (02/25/23) Gateway
R6300v2- DD-WRT v3.0-r50671 (10-26-22) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
RBWAPG-5HACT2HND-BE RouterOS-v6.46.4 (2/21/20) Outdoor Access Point
2x RBSXTG-5HPACD RouterOS-v6.46.4 (2/21/20) PTP Bridge 866.6Mbps-1GbpsLAN
Location 3
2x R7000- DD-WRT v3.0-r50671 (10/26/22) Access Points
2x RBWAPG-60AD RouterOS-v6.45.9 (04/30/20) PTP Bridge 2.3Gbps-1GbpsLAN
2x RBSXTsqG-5acD RouterOS-v6.49.7 (10/14/22) PTP Bridge 866.6Mbps-1GbpsLAN Thank You BrainSlayer for ALL that you do & have done, also to "most" everyone here that shares their knowledge
Posted: Sat Jan 05, 2019 16:51 Post subject: VAP issue
I noticed an issue with this build yesterday when creating a virtual AP under the 5GHz antennae. The 5GHz would cease to broadcast or allow devices to connect to it until I deleted the VAP.
Posted: Sat Jan 05, 2019 17:34 Post subject: Re: VAP issue
the00guy wrote:
I noticed an issue with this build yesterday when creating a virtual AP under the 5GHz antennae. The 5GHz would cease to broadcast or allow devices to connect to it until I deleted the VAP.
Posted: Mon Jan 07, 2019 2:30 Post subject: Re: VAP issue
bushant wrote:
the00guy wrote:
I noticed an issue with this build yesterday when creating a virtual AP under the 5GHz antennae. The 5GHz would cease to broadcast or allow devices to connect to it until I deleted the VAP.
I had the same problem on that router.
Which router do you mean? I haven't even mentioned what router I was using, which is the R7800. Apologies for leaving that vital piece of information out.
Could any one by chance help me get dd wrt going on my r7800. I cannot get any versions running. Ends up in a boot loop. Method is the usual download kong build, use netgear ui to load, and then nothing. Just boot loop.
Likewise tried to do it over tftp but again no go.
Tried both latest stable kong and test build. Original fw is 1.0.2.60 but also tried the same right out of the box when it had a 1.0.2.4x (can't remember).
Could any one by chance help me get dd wrt going on my r7800. I cannot get any versions running. Ends up in a boot loop. Method is the usual download kong build, use netgear ui to load, and then nothing. Just boot loop.
Likewise tried to do it over tftp but again no go.
Tried both latest stable kong and test build. Original fw is 1.0.2.60 but also tried the same right out of the box when it had a 1.0.2.4x (can't remember).
Thanks.
Hope you used the factory to ddwrt build. Did you power cycle (turn off on) the router after it reboots? If that still didn’t work power off hold reset button while turning on (~15 seconds) until slow flashing light then tftp the Kong factory to ddwrt img file
Hope you used the factory to ddwrt build. Did you power cycle (turn off on) the router after it reboots? If that still didn’t work power off hold reset button while turning on (~15 seconds) until slow flashing light then tftp the Kong factory to ddwrt img file
Yes i used factory to ddwrt. And tried both the UI and tftp methods. I did powercycle at some point when i see nothing is happening. Didn't want to do it immediately after the flash as i don't want to do it a wrong time or such.
I have successfully and easily gotten OpenWRT and a Voxel cfw running on the same machine. DD WRT seems to be a pain tho.
Hope you used the factory to ddwrt build. Did you power cycle (turn off on) the router after it reboots? If that still didn’t work power off hold reset button while turning on (~15 seconds) until slow flashing light then tftp the Kong factory to ddwrt img file
Yes i used factory to ddwrt. And tried both the UI and tftp methods. I did powercycle at some point when i see nothing is happening. Didn't want to do it immediately after the flash as i don't want to do it a wrong time or such.
I have successfully and easily gotten OpenWRT and a Voxel cfw running on the same machine. DD WRT seems to be a pain tho.
that's because partition layout is different between stock lede/openwrt ddwrt. and it's not that openwrt is easy, it's because once you flashed openwrt it screw up the layout for others -> harder to switch. i'm a fan of them all just the pros and cons you have to live with