Trentbg77, I'm using channel 149 upper/upper and not seeing problems with speeds all over the place. At least not more than the usual variations with wireless. And definitely stable with wired connections. I'd suggest trying different channels, like 149, and see how that looks.
Really liking the wireless here, after about 3 days.
I don't have anything that connects at 1300Mbps, but 867Mbps is fine.
Trentbg77, I'm using channel 149 upper/upper and not seeing problems with speeds all over the place. At least not more than the usual variations with wireless. And definitely stable with wired connections. I'd suggest trying different channels, like 149, and see how that looks.
Really liking the wireless here, after about 3 days.
I don't have anything that connects at 1300Mbps, but 867Mbps is fine.
What is your router, I dont have an option for channel 149, all I have from the drop down is - 48, 64, 112, 144, 161.
Trentbg77, I'm using channel 149 upper/upper and not seeing problems with speeds all over the place. At least not more than the usual variations with wireless. And definitely stable with wired connections. I'd suggest trying different channels, like 149, and see how that looks.
Really liking the wireless here, after about 3 days.
I don't have anything that connects at 1300Mbps, but 867Mbps is fine.
What is your router, I dont have an option for channel 149, all I have from the drop down is - 48, 64, 112, 144, 161.
Sorry, when I said upper/upper, I meant lower/lower. I usually use upper/upper, but this time chose lower/lower. Choose lower/lower and then "Save", and you'll see channel 149 as a choice. Sorry for the trouble I caused.
I have a Netgear R7000, but I don't think that the channel choice depends on your router (unless you don't have 5GHz., or your router doesn't support the upper 5GHz. channels for some reason). It depends more on your region, and apparently your choice of channel width, and upper/upper, lower/lower, etc. *smile*.
Anyways, channel 149 is working really well for me *smile*.
I've had the latest build of this running on my R8500 since it came out on 1/3. Worked solid for 6 days, now today it's been rebooting every few hours. Any thoughts as to what to check? It feels like an NVRAM overflow, but this one doubled the max and I'm at 58.57 KB / 128 KB. Anything else to check?
If you cn reproduce the reboots it would be good to see a serial log.
I haven't opened up the R8500 yet, but I'm assuming it's got a JTAG connector like any other?
In the meantime, following my NVRAM hunch, I disabled the wan traffic daemon. Up 12 hours straight now, but much of that was overnight with no usage. I'll see how it goes all day today.
Router: Netgear R67000
Firmware: DD-WRT v3.0-r28600M kongac (12/31/15)
Kernel: Linux 3.10.94 #59 SMP Thu Dec 31 09:20:23 CET 2015 armv7l
Status: Working
Reset: No
Errors: No
Have a great new year!
I woke up this morning and my unit reset itself to defaults and uptime says 15 minutes, it must be rebooting itself. And I don't know how all settings got wiped. The web gui changed and said I had an R7000. I reflashed and reset to defaults now. Will see if it sticks and does not reboot.
And after reset it said 6700 again?
The way detection is done for the R6700 vs 7000 it means it would be corrupted nvram (e.g. power outage), but if the detection stillclaims it is a R7000, then there is a problem with the partitioning.
Note the driver in my builds hasn't changed in a few month, thus if it ran fine before it should still run fine.
I'm sure the R8500 won't be running stable with the older driver, I have to upgrade the driver for the R8500, Netgear and Asus both have stability problems with their 1.4Ghz broadcom drivers.
A power outage is possible. On a reset today it correctly said R6700. The re-flash is working fine right now. I will keep monitoring. Thank you for your great work, happy new year
stable since the re-flash and reset to defaults. Router has not rebooted once. I don't run any special options not even wireless and but no issues with this build. Could have been a problem caused because I flashed originally but did not reset to defaults. Still confused about when and what command to erase nvram so I'll stay away from that
I'm still experiencing 2nd VAP instability on 2.4g even after reset ... Seems like configuration changes are causing some sort of nvram corruption (deleting the VAP, recreating and reboot allows client to connect once again) ... Happy to help troubleshoot (logs, nvram dump, ect)
Still experiencing VAP instability on 2.4ghz ... Clients cannot connect ... Only way to fix is delete and recreate the VAP followed by reboot
In <28600 build I noticed a problem where my physical AP did not broadcast, VAP was fine for both radios.
Right now I have a guest setup for both 2.4/5G and it is working fine, not tested without a radio schedule though. I setup radio schedules for both radios on my router.
Do you have more than one VAP per radio?
No VAP on 5G, two VAPs on 2.4G (a guest (isolated subnet) and another hidden one) ... also VLAN tagging between two r7000 ... both r7000s experience instability with 2.4g VAP (during config changes, upgrades, etc)
Did you reset? If you had more then one VAP, then your vap macs were incorrect and they will be only corrected if you reset your config.
just did a reset on one of the routers, VAP seems to be more stable, but did need two reboots for all the clients to connect successfully ... Will I need a reset after every upgrade? kind of a pain since I have a lot of settings ... thx!
sorry, my previous post in wrong spot
I'm still experiencing 2nd VAP instability on 2.4g even after reset ... Seems like configuration changes are causing some sort of nvram corruption (deleting the VAP, recreating and reboot allows client to connect once again) ... Happy to help troubleshoot (logs, nvram dump, etc)
If you cn reproduce the reboots it would be good to see a serial log.
I haven't opened up the R8500 yet, but I'm assuming it's got a JTAG connector like any other?
In the meantime, following my NVRAM hunch, I disabled the wan traffic daemon. Up 12 hours straight now, but much of that was overnight with no usage. I'll see how it goes all day today.
Disabling the ttraff daemon didn't make a difference. I did turn on syslog, which obviously doesn't show the same detail as serial logs, but I am seeing this recurring in there if it helps:
Code:
Jan 11 15:33:13 router kern.warn kernel: JFFS2 compression type 0x06 not available.
Jan 11 15:33:13 router kern.warn kernel: jffs2: Error: jffs2_decompress returned -5
Jan 11 15:33:13 router kern.warn kernel: jffs2: read_cache_page() returned error: -5
Jan 11 15:33:13 router kern.err kernel: jffs2: Error garbage collecting node at 0384f890!
I am using JFFS for the DHCP leases, nothing else. I'm going to try disabling JFFS to see if *that* helps.
If you cn reproduce the reboots it would be good to see a serial log.
I haven't opened up the R8500 yet, but I'm assuming it's got a JTAG connector like any other?
In the meantime, following my NVRAM hunch, I disabled the wan traffic daemon. Up 12 hours straight now, but much of that was overnight with no usage. I'll see how it goes all day today.
Disabling the ttraff daemon didn't make a difference. I did turn on syslog, which obviously doesn't show the same detail as serial logs, but I am seeing this recurring in there if it helps:
Code:
Jan 11 15:33:13 router kern.warn kernel: JFFS2 compression type 0x06 not available.
Jan 11 15:33:13 router kern.warn kernel: jffs2: Error: jffs2_decompress returned -5
Jan 11 15:33:13 router kern.warn kernel: jffs2: read_cache_page() returned error: -5
Jan 11 15:33:13 router kern.err kernel: jffs2: Error garbage collecting node at 0384f890!
I am using JFFS for the DHCP leases, nothing else. I'm going to try disabling JFFS to see if *that* helps.
Stayed up about 10 hours after disabling JFFS... and then rebooted again. This time it rebooted right as I was doing a download over WiFi. Not sure it's related but... certainly correlated.
Joined: 24 Mar 2015 Posts: 175 Location: Tacoma, Wa
Posted: Tue Jan 12, 2016 19:54 Post subject:
Kong et al
Is anyone else seeing the Wireless radios all drop connections and slowly anything connected able to connected again after 30 seconds? It's like the radio stacks are crashing and restarted. I've seen this happen a few times.. One incident happened badly enough that I had to power down and restart the router.
Is there any logging I can turn on to trace this for a bit? _________________ Routers:
Netgear R8000 - DD-WRT v3.0-r43420 std (06/15/20)
Netgear R9000 - DD-WRT v3.0-r43420 std (06/15/20)
Is anyone else seeing the Wireless radios all drop connections and slowly anything connected able to connected again after 30 seconds? It's like the radio stacks are crashing and restarted. I've seen this happen a few times.. One incident happened badly enough that I had to power down and restart the router.
Is there any logging I can turn on to trace this for a bit?
I've noticed this, but thought it was more with the specific client or internet connection. _________________ R7000 Nighthawk - DD-WRT v3.0-r50308
R7000 Nighthawk - DD-WRT v3.0-r50308
~~~~~~~~~~Dismantled for learning opportunities~~~~~~~~~~
WRT54Gv2
WRT54Gv8.2
~~~~~~~~~~Other Settings~~~~~~~~~
https://nextdns.io/?from=2d3sq39x https://pi-hole.net/ https://github.com/DNSCrypt/dnscrypt-proxy
With the previous build 28575M, I was having wireless drop out unit I disabled Airtime Fairness. _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54517 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r54517 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
Joined: 24 Mar 2015 Posts: 175 Location: Tacoma, Wa
Posted: Wed Jan 13, 2016 4:48 Post subject:
mac913 wrote:
With the previous build 28575M, I was having wireless drop out unit I disabled Airtime Fairness.
Airtime fairness doesn't want to disable via the UI.. I'll see if I can figure out the command to do it.
EDIT : using nvram set wl0_atf="1" etc followed by nvram commit worked.. however I've had airtime fairness set for a while. I don't think ATF is the culprit.. I'll keep it running for a while tho. _________________ Routers:
Netgear R8000 - DD-WRT v3.0-r43420 std (06/15/20)
Netgear R9000 - DD-WRT v3.0-r43420 std (06/15/20)
With the previous build 28575M, I was having wireless drop out unit I disabled Airtime Fairness.
Airtime fairness doesn't want to disable via the UI.. I'll see if I can figure out the command to do it.
EDIT : using nvram set wl0_atf="1" etc followed by nvram commit worked.. however I've had airtime fairness set for a while. I don't think ATF is the culprit.. I'll keep it running for a while tho.
Yes, I've had airtime fairness enabled since I started to use this firmware release on the R7000, and the router has been doing great for 4 days now (plus some other days before I went off to try new firmware for the WRT1900AC *smile*). Also tried to turn it off when I initially configured the router with this firmware, and that didn't work, so I just left it. Didn't want to turn it off badly enough to find the nvram settings for it.
I'm really happy with this firmware, but I only use the R7000 for routing and wireless, so not very demanding. IPv6 has also been working well, and I like to see that, too.
