Bug causing virtual interface to drop every 24hours... had setup a 5ghz only virtual interface for myself, dropped twice in 48hrs. Main interface remains connectable. Guess I'm asking for too much making a virtual interface on both 2.4 and 5ghz, don't really care about the 2.4 as its a guest network, was a fool to just /assume/ it would be stable... back to letting it switch me back and forth from HT40/HT20 even though I want HT40 fulltime..... sigh
Nothing about dma tx, nothing at all in the logs actually... i have ssh running fulltime with tail -f /var/log/messages because i'm just waiting for it to drop
Posted: Mon Jul 27, 2015 10:38 Post subject: installed but skeptical
i just installed this on my dir 825 rev b1 i have three questions will this still be developed and is the performance good and also are there any bugs with the lastet build
Posted: Mon Jul 27, 2015 14:46 Post subject: Re: installed but skeptical
hug1r wrote:
i just installed this on my dir 825 rev b1 i have three questions will this still be developed and is the performance good and also are there any bugs with the lastet build
1. DD-WRT is actively being developed, and will continue to be. For this router? No idea. This is really an end of life product now.
2. Yes, when it works well it kicks ass. If you are a gamer you WILL notice a real difference. You might not see a big difference in numbers like ping in games, but you will notice less latency (latency is more than just ping) and DD-WRT is far more stable than your typical retail firmware.
3. I'm sure there are some bugs, there always are, but I haven't noticed any so far. This may sound like a contradiction to 2. but it isn't. Firmware is complex software and with any complex software there are always bugs. _________________ Netgear XR500
Rogers Ignite Cable
150mbps down/15mbps up
Normal to have no 5ghz blinking light? Have 2 workstations connected but no activity light at all.. Still getting booted off 5ghz randomly.. have to go in router settings and change/apply any random wireless setting and I can connect to 5ghz again, until the next time it happens... sometimes 24hrs, sometimes less
Went back to r26653 for now, 5ghz light is working again, have split the ssid's will see if it stays stable, just had it die within less than an hour with r27456
Last edited by bondpard on Tue Jul 28, 2015 16:02; edited 1 time in total
Normal to have no 5ghz blinking light? Have 2 workstations connected but no activity light at all.. Still getting booted off 5ghz randomly.. have to go in router settings and change/apply any random wireless setting and I can connect to 5ghz again, until the next time it happens... sometimes 24hrs, sometimes less
Went back to r27086 for now, 5ghz light is working again, have split the ssid's will see if it stays stable, just had it die within less than an hour with r27456
You realize the latest version is 27506? As far as I know all the previous versions going back at least a year had 5ghz dropping issues... _________________ Netgear XR500
Rogers Ignite Cable
150mbps down/15mbps up
You realize the latest version is 27506? As far as I know all the previous versions going back at least a year had 5ghz dropping issues...
Yes I realize that, I only get stability with 2.4ghz, even though the router is right above me, very good signals, very low noise. The 5ghz can't stay operational for 24hrs, and I only noticed the light is not working either recently... If I don't split the SSID's (on the latest build), initially it connects as HT40, then after maybe 4-18 hours it randomly drops to HT20, I can still turn on my phone Wi-Fi and connect to HT40, but the PC won't go back up to HT40 unless I restart it, or apply some setting in the router, no amount of heavy traffic ever pushes it back to HT40.
First I made a virtual interface for the 5ghz, and noticed the drops, then I split the SSID entirely, still noticing drops, so now I'm just going back versions trying to find something.
In the last hour I just flashed 26653, 26839, 26854, 26866, 26947, 27086, 27096, 27119, 27147, 27240, the only version I get a working 5ghz light is 26653, so I guess I'm testing stability of strictly 5ghz, something is clearly wrong here with the 5ghz with rev C
Only thing I see "wrong" in 26653 is even though the operating system confirms DFS, 5ghz, 40mhz, wireless stats page reports HT20, but speed tests confirm HT40 speeds.. cosmetic issues don't really bug me as long as there's stability. Since 2.4ghz is so slow and I have a 100mb connection, if I can't resolve the 5ghz issues, I will have no choice but to go back to stock :\ Never realized the 5ghz was such an issue til very recently when I tried to isolate it... not cool maxing out 20-25mbps over 2.4 when I can do over 75-80 over 5ghz, very important for 5ghz stability to exist
After restarting the PC the router also shows HT40... but I know it won't stay that way, after looking a bit more into it when I'm ath1 and HT20, even though OS reports 5ghz/40mhz, the Txrate is locked @ 144, when the router is reporting it correctly, the OS also jumps between values higher than 144 upto 300, which is how it should be working 100% of the time
I keep noticing how the Android, and iPhone are able to jump back and forth between HT20/HT40, and the iPhone even has a double connection, one to ath0 and another with ath1. Some of my issues appear to be cosmetic but I am not certain, I do get HT40 speeds when testing but I don't get why it doesn't change on the router page to HT40.... Does it have anything to do with the fact I have a G device with max 54mbps on the network?
Still at HT40 & 300 after almost 12 hours... tried turning everything on the network on and off to see if speeds dropped but no, everything still looks normal
It seems as if splitting the SSID was more unstable, I have both merged again
If I manually connect to my 2.4 ghz guest network though, or any 2.4ghz network, I will no longer be able to connect to my 5ghz until I reboot. Kinda sounds like some error on both ends, why they're not able to negotiate highest link speed
Ok so its pushed me back to HT20, this is all I see in logs
Code:
Jul 29 20:37:19 DD-WRT daemon.info hostapd: ath0: STA xx:xx:xx:xx:03:fc IEEE 802.11: Station tried to associate before authentication (aid=-1 flags=0x0)
Jul 29 20:37:19 DD-WRT daemon.info hostapd: ath0: STA xx:xx:xx:xx:03:fc IEEE 802.11: Station tried to associate before authentication (aid=-1 flags=0x0)
Jul 29 20:37:22 DD-WRT daemon.info hostapd: ath0: STA xx:xx:xx:xx:03:fc IEEE 802.11: authenticated
Jul 29 20:37:22 DD-WRT daemon.info hostapd: ath0: STA xx:xx:xx:xx:03:fc IEEE 802.11: associated (aid 3)
Jul 29 20:37:22 DD-WRT daemon.info hostapd: ath0: STA xx:xx:xx:xx:03:fc RADIUS: starting accounting session 55B92D81-00000002
Jul 29 20:37:22 DD-WRT daemon.info hostapd: ath0: STA xx:xx:xx:xx:03:fc WPA: pairwise key handshake completed (RSN)
Jul 29 20:41:37 DD-WRT daemon.info hostapd: ath1: STA xx:xx:xx:xx:03:fc IEEE 802.11: disassociated due to inactivity
Jul 29 20:41:38 DD-WRT daemon.info hostapd: ath1: STA xx:xx:xx:xx:03:fc IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Jul 29 20:46:09 DD-WRT daemon.info hostapd: ath0: STA xx:xx:xx:xx:03:fc WPA: group key handshake completed (RSN)
From this point it will remain on ath0 forever, until I reboot (or change wireless channel, or some other random wireless setting, hit Apply and then it also connects back in HT40), phones and macbook can still go back and forth HT20/HT40, but not me..
Could my cards locale have something to do with it? It doesn't have a country code or locale...
Going to "Wireless" and just clicking "Apply" fixes it, I guess I can live with doing that when I notice I've been booted from ath1
Hope for stable 5ghz fix soon
Posted: Wed Dec 09, 2015 3:23 Post subject: weird issues with 5GHz channel :(
was using the 3.0 beta build, since that seemed to be the default dd-wrt build for dir-825 (as of 07 dec 2015) and the router would interrupt the connection while I was tab casting from Chrome to my Chromecast. And this happened to me about a dozen times today. And a few times, the router would not accept a connection on the 5GHz channel at all, for a little while.
What's weird is that my router and my Chromecast unit are about 4-5 feet apart from each other with a direct line of sight so there really shouldn't be any major interference/issues. In terms of ideal wireless conditions, this is probably as ideal as it can possibly get. Also, it seems like 5GHz signals don't pass through walls very well, so it's unlikely to be due to a neighbor's signal.
I don't remember this happening with the factory d-link firmware in any significant sense. If this is due to the 3.0 beta, I would consider it to be a showstopper type bug.
Anyways, ended up switching to firmware DD-WRT v24-sp2 (03/25/13) and keeping my fingers crossed.
Posted: Sat Jan 09, 2016 17:29 Post subject: Re: weird issues with 5GHz channel :(
The 5GHz signal will always have less range than the 2.4GHz signal, it is just how much output power is used. Both signals are limited to a max of 1000mW, 1 watt of power, the 2.4 GHz signal will go farther with that power than the 5 GHz signal.
As for walls, 2.4 GHz is much better at penetrating walls. On the 2.4 band, I get about 50% signal strength to my main router, while with 5GHz, I only get about 22% signal strength, with the DIR-825 B1. The distance is about 30 feet or so, through at least four 6-8 inch thick walls. The other issue is what angle is the signal passing through the wall? the lower the angle (closer to parallel), the thicker the wall will seem. Line of sight is best but not always possible. Also, upgrading the external antennas on the router may help, as well as playing around with the TX power. Highest transmit power is not always best.
but then upgraded to 29440 but now I can't get the GUI to come up for some reason, the router works but I can't access the GUI, I may have to TFTP the next firmware version over, stick with 29396, do not use anything older than this year at all. No 14XXX, 18XXX, or anything like that. Newer builds are more refined but you still get the odd bug.
These will show what other users are reporting. I don't usually report all of my errors because more often than not they are caused by me, not the firmware.