Router: Buffalo WZR-1750DHP
Firmware: buffalo-wzr-1750dhp-webflash.bin (v3.0-r38159 std)
Kernel: Linux 4.4.169 #4419 SMP Mon Dec 31 09:50:12 CET 2018 armv7l
Status: Working
Reset: No
Notes on configuration:
Posted: Fri Jan 04, 2019 22:02 Post subject: Re: EA6350 V2
technoside2 wrote:
I'd like to see a fix for the 2.4Ghz Wireless security. Every time the Router reboots the 2.4Ghz goes unprotected. I have to re-apply in Web GUI to re-protect my 2.4Ghz wireless.
anyone have a workaround for this?
It sounds like your settings aren't being saved for some reason, and therefore can't survive a reboot.
When was your last full reset (erase nvram)? Then reconfigure from scratch, don't apply old settings from a saved config.
(regarding my comment earlier in the thread; your question was constructive, other people's responses to KP69/Kong's answer were not)
Posted: Sat Jan 05, 2019 0:49 Post subject: Re: EA6350 V2
flyzipper wrote:
When was your last full reset (erase nvram)?
Im quoting you for reference..not calling you out
This is old information...that command performs differently now.....actually since 04/18
Though some will say that it now performs better..if you pull the power right after running it.....leaving out the fancy && reboot...or separate reboot command.
Im sure <Kong> ....and others.. are sick of me quoting his posts over and over on this......so I won't.....
Eahhh.....what the heck..I'll do it once more...but more politely
Disclaimer:
As long as it is safe to run on your router without semi/bricking.......though I believe it changed.....partly to help elevate that risk ¯\_(ツ)_/¯ _________________ 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 2:14 Post subject: Re: EA6350 V2
Dr_K wrote:
flyzipper wrote:
When was your last full reset (erase nvram)?
Proper command since 04/18 is "nvram erase"
Disclaimer:
As long as it is safe to run on your router without semi/bricking.......though I believe it changed.....partly to help elevate that risk ¯\_(ツ)_/¯
Joined: 08 May 2018 Posts: 14222 Location: Texas, USA
Posted: Sat Jan 05, 2019 3:26 Post subject: Re: EA6350 V2
You can try the CLI command or soft reset through the WebUI, but I doubt it will work . I have been testing being connected / connecting to both AP bands and 2.4 band has issues. Usually takes a few tries to authenticate, but no issue of losing the saved settings for the 2.4 band on E4200v1. What you may have to do is figure out what parameters need to be 'nvram set' and 'nvram commit' and reboot. and see if that fixes the issue. I can't remember the specific parameters off the top of my head, and it's time to get ready for the 'day job'...
Posted: Sat Jan 05, 2019 4:18 Post subject: Re: EA6350 V2
kernel-panic69 wrote:
I should've been specific. CLI = command line interface (via telnet or ssh)....
Sorry then...
I was just typing fast to be sure HE didn't do what I thought you were suggesting ¯\_(ツ)_/¯ _________________ 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 4:37 Post subject: Re: EA6350 V2
flyzipper wrote:
Dr_K wrote:
flyzipper wrote:
When was your last full reset (erase nvram)?
Proper command since 04/18 is "nvram erase"
Disclaimer:
As long as it is safe to run on your router without semi/bricking.......though I believe it changed.....partly to help elevate that risk ¯\_(ツ)_/¯
Thanks for the clarification!
Thank you for the info, I’ll give it a try. _________________ WRT54GL v1.1 - Flashed
Linksys WRT54G2 v1 - Flashed
EA6350 v2 - Flashed
root@DD-WRT:/# ifconfig usb0 up
root@DD-WRT:/# udhcpc -i usb0
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: sending select for 192.168.42.90
udhcpc: lease of 192.168.42.90 obtained, lease time 3600
usb0: No such process
cat: can't open '/proc/sys/net/netfilter/nf_conntrack_flush': No such file or directory
Code:
root@DD-WRT:/# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.42.129 0.0.0.0 UG 0 0 0 usb0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
192.168.42.0 * 255.255.255.0 U 0 0 0 usb0
I can ping to the Internet from TP-Link shell, but not on my computers @ 192.168.0.0/24.
I had to go back to older FW, perform HARD factory reset, UPGRADE to last version, and performed another HARD reset.
However there is still errors (in red) as you can see below:
root@DD-WRT:/# cd /lib/modules/4.4.169
root@DD-WRT:/lib/modules/4.4.169# insmod usbnet.ko
root@DD-WRT:/lib/modules/4.4.169# insmod cdc_ether.ko
root@DD-WRT:/lib/modules/4.4.169# insmod rndis_host.ko
root@DD-WRT:/lib/modules/4.4.169# ifconfig usb0 up
root@DD-WRT:/lib/modules/4.4.169# udhcpc -i usb0
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: sending select for 192.168.42.90
udhcpc: lease of 192.168.42.90 obtained, lease time 3600
usb0: No such process
cat: can't open '/proc/sys/net/netfilter/nf_conntrack_flush': No such file or directory
cannot open /proc/sys/net/ipv4/conf/br0/loop
Overclocking doesn't work or needs a different command:
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r38159 std (01/02/19)
Kernel: Linux 4.4.169
Mode/Status: Gateway / working
Reset: Yes ( I ran nvram erase && reboot and reconfigured)
Issues/Errors: Yes:
I did: nvram get clkfreq (I got 1000,800)
Then: nvram set clkfreq=1200,800
And: nvram commit && reboot
After reboot, I ran nvram get clkfreq ( I got 1000) Just plain 1000
I had to run "nvram erase && reboot" and start all over
I actually replaced an Atheros based router (D-Link DIR-825) with a Broadcom router (Archer C9) partly because of its vlan support (useful for ftth in our case). I always assumed that Broadcom hardware allows for more advanced network setups than Atheros but I might've been wrong.
Anyway I hope the devs keep supporting Broadcom or at least that they fix several major bugs in more recent builds. I went back to old build 35244 to regain actual VHT80 AC speeds (with 866 Mbps link speeds) and the possibility to set a fixed channel number instead of auto channel as the only option available with that channel width.
I have gigabit fiber (Google Fiber), and I've used both the TEW-673GRU (identical in hardware to your DIR-825) and a WZR-1750DHP (Broadcom ARM) as the router (I ditched Google's crap hardware entirely--my DD-WRT box connects directly to the Google Fiber Jack). First, the Atheros can do VLAN tagging. The interface for that setting is very different from the Broadcom interface, but it works just fine. Second, to my surprise, the Atheros actually performs better at routing, even though its CPU is single-core and has a slower clock speed. With SFE, I get about 940 Mbps up and down on the Atheros, whereas I got about 850 Mbps using the newer and more expensive Broadcom unit as the router. So what I do now is have the 673GRU as a routing-only unit (WiFi disabled), and the 1750DHP as an access point (routing disabled). _________________ Buffalo WZR-1750DHP: 34311
TRENDnet TEW-673GRU: 34311
TRENDnet TEW-811DRU: 33986
