DIR-882 2.4 wireless keeps dropping

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink SoC based Hardware
Goto page 1, 2  Next
Author Message
shadowjig
DD-WRT Novice


Joined: 23 Sep 2017
Posts: 3

PostPosted: Wed Oct 04, 2017 15:38    Post subject: DIR-882 2.4 wireless keeps dropping Reply with quote
I bought a DIR-882 recently and I'm running DD-WRT v3.0-r33413 std (09/27/17) firmware right now. I noticed wifi was dropping out. I looked at messages log and didn't see anything regarding this issue. I checked ba0 and ra0 after the problem and after a reboot and both show an up status. 2.4 and 5 had the same SSID so I changed the 5ghz one. Now 2.4 drops out and I can still access 5g and via a lan port. Everything seems to be working fine except 2.4. Phones, laptop and Chromecasts will not connect when the 2.4.drops. I had the same problem with a build from July or August which prompted me to upgrade to 33413. The 2.4 SSID is exactly the same as the one from my old router (which is turned off). Might clients be caching something?


Anyone else have the same issue? Any thoughts on how to troubleshoot further or fix this issue?
Sponsor
sup2k
DD-WRT Novice


Joined: 26 Oct 2017
Posts: 6

PostPosted: Thu Oct 26, 2017 13:59    Post subject: Reply with quote
same here. the device seems to totally reboot every few hours.
shadowjig
DD-WRT Novice


Joined: 23 Sep 2017
Posts: 3

PostPosted: Thu Oct 26, 2017 16:40    Post subject: Reply with quote
sup2k wrote:
same here. the device seems to totally reboot every few hours.


Are you running DD-WRT or stock firmware? Did you do a 30-30-30 reset?

I didn't do the 30-30-30. I'm running the September or October build and I was ok for a while. Now it seems to reboot twice a day for the last 4 days. I have a reboot scheduled for 4am so that didn't help.

I can troubleshoot, I just don't know what I should look at. I don't see anything in the logs that would indicate an issue.

Anyone have any tips?
casualtester
DD-WRT User


Joined: 13 Dec 2015
Posts: 258

PostPosted: Thu Oct 26, 2017 23:08    Post subject: Reply with quote
Firmware 10-25-2017-r33607 released yesterday did not fix?

NB: New TEST firmware after 31571 may BRICK router
sup2k
DD-WRT Novice


Joined: 26 Oct 2017
Posts: 6

PostPosted: Thu Dec 14, 2017 20:38    Post subject: Reply with quote
Still hapenning with latest firmware (12/04). even more frequently...
casualtester
DD-WRT User


Joined: 13 Dec 2015
Posts: 258

PostPosted: Fri Dec 15, 2017 9:47    Post subject: Reply with quote
New firmware, 12-14-2017-r34080 available.

Did you try erase nvram?

What settings are you using for the 2.4GHz?
dblanche54
DD-WRT Novice


Joined: 17 Dec 2017
Posts: 1

PostPosted: Sun Dec 17, 2017 22:30    Post subject: Reply with quote
sup2k wrote:
same here. the device seems to totally reboot every few hours.

I'm finding myself with the same issue, I'm running DD-WRT v3.0-r34080 std (12/14/17).
Any help would be appreciated?
sup2k
DD-WRT Novice


Joined: 26 Oct 2017
Posts: 6

PostPosted: Mon Jan 22, 2018 20:00    Post subject: Reply with quote
I haven't tried nvram erase.
I've attached my 2.4 configuration
casualtester
DD-WRT User


Joined: 13 Dec 2015
Posts: 258

PostPosted: Tue Jan 23, 2018 5:07    Post subject: Reply with quote
No reboot problems encountered as of yet, with firmware: 12-29-2017-r34311

Minor note, as my usual practice, erased the nvram after the firmware update.
FurryNutz
DD-WRT User


Joined: 31 Oct 2010
Posts: 231

PostPosted: Tue Jan 23, 2018 14:58    Post subject: Reply with quote
Try Single mode G or N, and manual channel 1 then 11 if it's open. Set channel width to 20/40Mhz.

WPA2 and TPIK only, then try WPA2 and AES only.

sup2k wrote:
I haven't tried nvram erase.
I've attached my 2.4 configuration
casualtester
DD-WRT User


Joined: 13 Dec 2015
Posts: 258

PostPosted: Wed Jan 24, 2018 4:28    Post subject: Reply with quote
Update: Encountered an unscheduled reboot this evening. Will try other builds if problem is ongoing with 12-29-2017-r34311

Since there are no current "user-friendly" official changelogs, NOT bothering with recent builds unless required.
Last changelog dated: 2016/10/27 courtesy of KrypteX

For those who have the time to actually sort through everything,
They can read through the dd-wrt Timeline: LINK
FurryNutz
DD-WRT User


Joined: 31 Oct 2010
Posts: 231

PostPosted: Wed Jan 24, 2018 17:22    Post subject: Reply with quote
You might try a recent build to see if anything is encountered.

Might check your logs to see if there is any thing listed around the time frame this reboot happened.


casualtester wrote:
Update: Encountered an unscheduled reboot this evening. Will try other builds if problem is ongoing with 12-29-2017-r34311

Since there are no current "user-friendly" official changelogs, NOT bothering with recent builds unless required.
Last changelog dated: 2016/10/27 courtesy of KrypteX

For those who have the time to actually sort through everything,
They can read through the dd-wrt Timeline: LINK
sup2k
DD-WRT Novice


Joined: 26 Oct 2017
Posts: 6

PostPosted: Sun Apr 22, 2018 9:06    Post subject: Reply with quote
Any updates on stable versions? casualtester, which version are you currently using and for how long?
I'm getting too many crashes, thinking of reverting to D-Link firmware.
casualtester
DD-WRT User


Joined: 13 Dec 2015
Posts: 258

PostPosted: Sun Apr 22, 2018 21:53    Post subject: Reply with quote
sup2k wrote:
Any updates on stable versions? casualtester, which version are you currently using and for how long? ...


Currently running 04-06-2018-r35681
No problems encountered since it's release.
As my usual practice, erased nvram just before and just after the firmware update.
Note: The testing environment of the D-Link is in a condo complex, so the 2.4 GHz Channel Width is set to only 20 MHz due to ridiculously large amount of wireless traffic from neighbour routers and use of Apple (iPhones & iPads) products from some users. The Beacon Interval was also changed to 50, again due to the Apple products.

I intentionally avoided the last two releases, 04-19-2018-r35770 which was removed from the ftp server and 04-20-2018-r35770, due to feedbacks of "bricked" routers among some of the other brands.
sup2k
DD-WRT Novice


Joined: 26 Oct 2017
Posts: 6

PostPosted: Mon Apr 30, 2018 19:02    Post subject: Reply with quote
tried it.. still dropping.
This was in my logs sent to papertrail:
Code:


Apr 30 21:56:02 <IP> logger:  : httpd : http daemon successfully stopped
Apr 30 21:56:02 <IP> httpd:  httpd server shutdown
Apr 30 21:56:02 <IP> logger:  : vpn modules : nf_conntrack_proto_gre successfully loaded
Apr 30 21:56:02 <IP> logger:  : vpn modules : nf_nat_proto_gre successfully loaded
Apr 30 21:56:02 <IP> httpd:  httpd server started at port 80
Apr 30 21:56:02 <IP> logger:  : resetbutton : resetbutton daemon successfully stopped
Apr 30 21:56:02 <IP> logger:  : vpn modules : nf_conntrack_pptp successfully loaded
Apr 30 21:56:02 <IP> logger:  : vpn modules : nf_nat_pptp successfully loaded
Apr 30 21:56:02 <IP> logger:  : resetbutton : resetbutton daemon successfully started
Apr 30 21:56:02 <IP> logger:  : process_monitor successfully started
Apr 30 21:56:02 <IP> logger:  : upnp : upnp daemon successfully stopped
Apr 30 21:56:02 <IP> ntpclient:  Connecting to 2.pool.ntp.org [109.226.40.40] ...
Apr 30 21:56:02 <IP> ntpclient:  Time set from 2.pool.ntp.org [109.226.40.40].
Apr 30 21:56:02 <IP> process_monitor:  cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Apr 30 21:56:02 <IP> process_monitor:  Restarting cron (time sync change)
Apr 30 21:56:02 <IP> logger:  : upnp : upnp daemon successfully started
Apr 30 21:56:02 <IP> logger:  : cron : cron daemon successfully stopped
Apr 30 21:56:02 <IP> logger:  : wland : WLAN daemon successfully started
Apr 30 21:56:02 <IP> logger:  : process_monitor : Process Monitor successfully stopped
Apr 30 21:56:02 <IP> logger:  : WAN is up. IP: <IP>
Apr 30 21:56:02 <IP> logger:  : cron : cron daemon successfully started
Apr 30 21:56:02 <IP> cron:  (CRON) STARTUP (fork ok)
Apr 30 21:56:02 <IP> logger:  : process_monitor successfully started
Apr 30 21:56:02 <IP> process_monitor:  We need to re-update after 3600 seconds
Apr 30 21:56:02 <IP> process_monitor:  set timer: 3600 seconds, callback: ntp_main()
Apr 30 21:56:13 <IP> logger:  : ttraff: data collection started


Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum