D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: icemankent on December 09, 2010, 01:13:59 PM
-
Ok, so I thought I found the problem - why I keep seeing "wireless restart" in my logs.
I thought it was due to WISH being enabled.
It turns out that is not the case - as it still happens, even when WISH is turned off.
I have firmware 1.23NA - which is the latest (and greatest ?).
In any event - there is absolutely no rhyme or reason for these restarts - they are random and can (and do) occur when there is even only just "1" wireless client connected.
To be honest, I have not even noticed anything when these "wireless restarts" happened - meaning I did not perceive a loss of internet connectivity.
I am therefore not sure how big of an issue this really is - except for the fact that one would expect them not to happen at all.
Any clues as to why these happen, and if it is an indication of a hardware problem ?
-
What wireless mode are you using? Mixed?
There was a resent issue just like this that was being caused by an iPhone connection.
What wireless devices do you have? And what highest modes do they support?
I would do this: Set up WiFi for single G mode only @ 2.4GHz with out any security for a quick test. Clear the routers logs. Make sure all WiFi devices are turned off or the devices radio's disabled. Once you have the router set up, bring up one device and check the connection on the device and router. Go to some place on the device and check for internet or data thruput. If you have more than one WiFi device, turn off the 1st one and go to the next one and check the connection and operation. Do this for all devices one at a time to make sure they connect with out any issues and check the routers logs for any thing while your doing this. If you find anything then you'll know.
After this, turn on Security and set a pass word. Again try the devices to make sure they connect with the security. Check the logs again.
If you don't have any devices that use modes A, B or N at this time, then using Single mode G will be beneficial as the router wont have to do any broadcasting if no supported devices are going to be using those modes. Some people are using Mixed G and N @ 2.4Ghz. I only have one device that supports N so I run mixed sometimes.
I would also check the channels too, change them from auto to manual and check using chl 1, 6 the 11. If there are other WiFi radios in the near by vicinity, they could cause interference and thus making the WiFi reset and try to regain a stable broadcast on a different channel and why your seeing resets.
A lot of the issues seen in WiFi are just inherently to the beast and not a FW issue. Dealing with radio signals and various channels and frequencies can't be very complicated. Trust me. I've been in the Communications world for a long time.
Give these suggestions a try and let us know what happens. I hope we can help resolve this issue.
-
Thanks.
I am using G-only @ 20Mhz, autochannel scan (currently on ch6), with WISH enabled.
Interesting that you should mention an iPhone issue, though - as there is an iPhone4 in the house - and it is wirelessly connected.
What is the issue with iPhones and this router and what is the fix ?
I think what I'll do first is disable the wifi on the iPhone4 to see if any of this improves - and then I'll try your other suggestions and report back on my findings.
-
Ok, I tried everything.
Still get the wireless restarts happening.
I sure wish the Dlink log would give more of a "reason" for the wireless restart - so I could troubleshoot it better.
Something like (too much interference - need to switch channels - wireless restart), etc.
I have no idea - maybe I'll just stop looking at the logs and be done with it.
-
What windows versions are you running on your connected PCs? Any of them Vista or 7? There has been some reports that IPv6 has caused some issues on this router as it is enabled by default on Vista. Not fully sure about 7. Let us know what you have running on ur PCs.
What kind of Anti Virus and Firewall programs are you using if any. There has been reports and certain AV and firewall programs can impact routers. Let us know what you have running if anything.
http://forums.dlink.com/index.php?topic=8272.0 (http://forums.dlink.com/index.php?topic=8272.0)
Also do you have any wireless home land line phones around the house? If so, what are there operating frequencies. Might be from 1Ghz to 5Ghz. These can interfere and cause the router to exhibit these restarts. I've experienced this as well.
I'd like you to try switching the Wireless mode from G only 2.4Ghz to Mixed A and N at 5Ghz and see if you get the same issue. If you don't have any devices that support N however I think you should be able to connect to A mode. Don't worry if you can't get any thing connected. Let it run for awhile then go back in and look at the logs while at 5Ghz. I'd like to see if this happens on the 5Ghz band as well.
Please let us know.
-
Ok, so far I have:
- disabled ipv6 on the only laptop that ran vista and had it enabled
no difference.
My router is hardware revision A2 - if that matters.
I am continuing to try different things as per your suggestions and will report back.
One last thing - is it at all possible that this brand new router is actually at fault (instead of me going on a witch hunt to find another culprit) ?
I had a dlink dir-625 (which I had for the last 3 years) and only 2 weeks ago replaced it with this dgl4500.
The 625 was rock-solid stable - and did not exhibit any wireless restarts or anything else buggy - (same exact devices and config here at home).
That's what makes me feel that the router is at fault - although I will keep trying to troubleshoot this.
PS - just checked the logs now and saw the following - which seems to be a big deal - never happened before:
[INFO] Fri Dec 10 20:44:48 2010 Wireless link is up
[INFO] Fri Dec 10 20:44:36 2010 Wireless link is down
[INFO] Fri Dec 10 20:44:36 2010 Wireless restart
[INFO] Fri Dec 10 20:44:36 2010 Disconnect all stations
[INFO] Fri Dec 10 20:44:36 2010 All Wireless shut down
[INFO] Fri Dec 10 20:44:34 2010 Wireless restart
What would cause the whole "all wireless shutdown and disconnect all stations ?!
-
Ya, there is a possible HW issue with the router. There is another poster on here with the same HW version, A2. Over the years I have seen a good amount of posters with problems with A2 routers. I don't have a A2 to compare too. I have 2 A1s and both of them work great. Makes me wonder more that A2s could have more issues then A1s. Like i told the other poster, I might be worth going out and buying a different router and see if you have any issues there. If you don't see the same issues. I would get a hold of DLink and tell them what you have done.
It seems that you had a different router what worked well on your same ISP network and bring the 4500 online as introduced issues and leads me to believe there is a probable issue with this router, if you haven't changed anything upstream on the line.
Are there any other wireless routers in the area? Also please let us know if you have house hold wireless land line phones. As these can also cause interference with the router.
Do you have anyone near by that has Internet that you could take the 4500 router to and put on there network? This would also help to determine if the problem travels or not.
-
Yes, there are quite a few wireless routers in the area - but with my previous dir-625, this was not a problem (boy I wish I still had that router !).
Anyway, I also did another test - using only 802.11a - since I have one laptop that can use it.
There were NO wireless restarts when using only a.
When I switched back to g, they restarts happened again.
TWO things:
-1-
I really don't notice any degredation in connectivity when these wireless restarts happen - in fact, if I did not look at the logs, I probably would never know there was a problem. Obviously, my previous dir-625 never had any wireless resets, so I am bummed that this brand new dgl-4500 has this issue - being brand new ! If it was YOUR router, would you live with it, or return it for exchange/refund ?
-2-
The dgl-4500 came with firmware 1.21 on it. Before even configuring anything I went to the tools page and clicked on "check for new firmware". The router said there was no new firmware. Since I (knew) that 1.23 was out there - I downloaded it separately. (I wonder why the router reported that there was not any new firmware ?)
In any case, I upgraded the firmware to 1.23na, and then started configuring it. (I did not do a factory reset as you suggested to others - since there really was no config on it to begin with).
SO, my question would be - do you think there is any remote chance that my wireless restarts issue is firmware related - or did I get a box with a bum wireless radio in it ? Should I try DOWNgrading my firmware back to the 1.21 - or try reloading 1.23 ?
I now NEED a router at home, and I don't want to be (without) one if I have to ship this thing to either D-link or the retailer I bought it from. I am hoping they would send me a replacement and then I could send them this one back when the replacement arrives .... damn.
-
Yes, there are quite a few wireless routers in the area - but with my previous dir-625, this was not a problem (boy I wish I still had that router !).
Anyway, I also did another test - using only 802.11a - since I have one laptop that can use it.
There were NO wireless restarts when using only a.
When I switched back to g, they restarts happened again.
Seems like if A works with out a restart and G does, and you have other wireless in the area. I'm wondering if interference is a factor for this router. Have you tried changing the channels?
TWO things:
-1-
I really don't notice any degredation in connectivity when these wireless restarts happen - in fact, if I did not look at the logs, I probably would never know there was a problem. Obviously, my previous dir-625 never had any wireless resets, so I am bummed that this brand new dgl-4500 has this issue - being brand new ! If it was YOUR router, would you live with it, or return it for exchange/refund ?
All avenues should be investigated before determining if it's a actual router hardware issue. Just because the router exhibits problems when put online doesn't mean the HW is defective. I won't rule that out however other factors can impact how the router fuctions. Especially in close proximity to other WiFi radios and wireless phone phones. Any Wireless home phones in the area that you know of? Returning the router is an option and your choice. I would recommend also calling Dlink for advise. Another option would be to buy a different router and test it and see what goes on.
-2-
The dgl-4500 came with firmware 1.21 on it. Before even configuring anything I went to the tools page and clicked on "check for new firmware". The router said there was no new firmware. Since I (knew) that 1.23 was out there - I downloaded it separately. (I wonder why the router reported that there was not any new firmware ?)
DLink might not have set up the new FW to be broadcast to the routers automatically.
In any case, I upgraded the firmware to 1.23na, and then started configuring it. (I did not do a factory reset as you suggested to others - since there really was no config on it to begin with).
SO, my question would be - do you think there is any remote chance that my wireless restarts issue is firmware related - or did I get a box with a bum wireless radio in it ? Should I try DOWNgrading my firmware back to the 1.21 - or try reloading 1.23 ?
Was there a reason why you upgraded to v1.23? Was the router functioning well before the upgrade? It's always not necessary to have the latest and greatest if units are working well out of the box. Yes that is an option to download and see if there is any change. You might try and go back to v1.21.
I now NEED a router at home, and I don't want to be (without) one if I have to ship this thing to either D-link or the retailer I bought it from. I am hoping they would send me a replacement and then I could send them this one back when the replacement arrives .... damn.
I understand the frustration. I would definitely try this router at a friends place or family member if you can. Would be interested if this issue travels. I'm wondering since A mode works with out issue and G goes, and there are other radios in the area that could be having an impact on this.
-
Wait...so these restarts aren't actually causing you any connection issues, in either throughput, latency, or packet loss? You said you wouldn't even notice them if you didn't look at the logs? Well not to be a jerk...but have you considered just not looking at your logs? I understand the tendency to want to fix something just because you can...but I think you may be investing too much time into a minor issue. Just my two cents.
-
I contacted dlink.
They agreed that wireless restarts should not be happening (at all) unless I had manually changed a setting in the wireless setup, etc.
D-link is slow to respond to me, however.
Since 2 days have gone by without a reply to my last email, I am going to return it to where I bought it.
Since I cannot be (without) a router in my home (they estimated at least 15 days for the shipping, replacement, etc....) - I will go out to FutureShop/Bestbuy and pick up a DIR-655 to get me by until the replacement dgl-4500 arrives.
Since there is a 30-day return policy, I can take the 655 back for a refund IF my replacement 4500 actually works properly.
Lastly, I should not have to accept flaws in operation from a brand new router that costs twice what other models out there do. I am happy the logs are there to assist me in troubleshooting a problem that could very well turn into a larger chronic issue that "does" cause a connectivity failure in the near future.
As far as loss of connectivity - whenever the wireless restarts happen, the wireless devices reconnect - so that is actually a problem.
As a consumer, I deserve to get the quality I paid for.
-
Ok then. Good luck. ::grin::
-
Let us know how both of those routers work. Hope one of them gets you up and running with out these restarts. Let us know.
-
Update:
I bought a dir-655 last night (as a temporary replacement until I get new 4500).
What a nightmare !!
I cannot wait to return it to the store (but have to wait for my replacement 4500 first).
The dir-655 is buggy and slooooow !!!
(No wireless restarts, though from what I can tell from their cryptic logs !).
The web interface on the 655 is at least 5 times slower (no joke) compared to the 4500.
Almost every change/update you save on the 655 requires a restart - typically 30 seconds or so (wasted).
At first, this 655 was not "seeing" any hard wired or wireless clients. I had no idea why - it almost seemed that it was not aggressive enough at giving out dhcp ip addresses.
EVENTUALLY, it populated itself with clients, so then I decided to reserve ips for these devices.
I almost ripped this router off the desk and threw it into the garbage it was soooo frustrating to set up.
The router got confused about ip addresses and what was dhcp vs reserved so many times that even after "saving" the changes, things did not set up correctly.
I actually had to reset to factory settings and reboot this thing about 3 times - just to try and get it configured properly.
Even now, with all clients connected, when I go to the status screen and click on wireless - it takes (forever) to populate the screen and is hit and miss whether it actually decides to display the wireless connected clients or not. Unbelievable !
Regarding QoS, I have set up different priorities for traffic and when I check the internet sessions, it does display the streams, however it does not display the priority - so i have NO way to verify if my QoS is working or not.
Regarding the logs - for some reason they LOOK very different than what I am used to on the 4500. For one, they are broken into MANY pages, rather than allowing them all to be viewed on one page, which makes navigating the info a pain. Plus, many of the messages it displays are strange:
For example, what is all this garbage ?
Priority Time Message
info Dec 14 21:05:12 [ 5641.620000] m_table count= 1 Del 01005e00 00fc000b
info Dec 14 21:04:14 [ 5583.620000] m_table count= 2 Del 01005e7f fffa000b
info Dec 14 20:54:28 UDHCPD Inform: add_lease 192.168.0.67
info Dec 14 20:54:24 UDHCPD Inform: add_lease 192.168.0.67
info Dec 14 20:48:56 [ 4665.780000] m_table count= 2 Add 01005e7f fffa000a
info Dec 14 20:48:45 UDHCPD sending OFFER of 192.168.0.55
info Dec 14 20:48:18 [ 4627.470000] m_table count= 1 Add 01005e00 00fc000a
info Dec 14 20:48:00 UDHCPD sending OFFER of 192.168.0.97
info Dec 14 20:47:57 [ 4606.000000] module arch cleanup nf_ubicom_streamengine_default_classifier: OCM instruction memory free of 0 @00000000
info Dec 14 20:47:55 [ 4604.940000] module arch cleanup sch_ubicom_streamengine: OCM instruction memory free of 0 @00000000
What a collossal nightmare. I cannot imagine how Dlink can get away with selling such a shoddy product.
Perhaps the processor on the 655 is junk, I don't know, but I have a theory.
The HARDWARE revision of the unit is B1.
It would almost seem that Dlink does a good job on their routers with the FIRST/original Hardware revision.
When they make a newer version, the problems seem to start.
Even Furry noted that his 4500's are on A1 (which work fine), and most problems are on devices with A2 (which mine is).
This dir-655 is on version B1 - so who knows "what" they've done to the hardware to make it this excrutiatingly frustrating to work with.
In the store, they only had 655s with h/w rev B1, so no luck there.
I only hope that I get my replacement 4500 soon, so I can take this white albatross back to the store for a refund - as its buggy behavior is making my blood boil !
-
Have you gone over to the dir-655 forum and reviewed there issues there? I might have done that before buying this unit. How about any FW updates for this unit? Might help speed up it's functionality. Hard to believe that unit is that bad. Wow.
I'm getting a 4500 A2 unit from a buddy of mine in the mail. I'm going to be doing some testing on his unit and see how the A2 works on my network and with a Arris Cable modem. He's been having issues with it on his system. He sent it back to DLink for RMA and just got it back and still has issues. I'm thinking there is something incompatible with the 4500 and the Arris modems. I'll be checking for wireless restarts as well.
I can't wait. I'll keep you posted.
-
Thanks man - this will be an interesting experiment.
The 655 does "work" technically, but is horrible to configure/use via its interface.
I am living with it only because it is a "temporary" solution while I wait for my 4500 to be shipped back to vancouver, have them do the RMA thing, then ship me back a new one.
I really am starting to think that there are a ton of "lemons" out there - not too sure why Dlink has such shoddy manufacturing QualityAssurance, but it is obvious from looking through all the posts that some lucky people have the "gems", whereas many of us - for no appreciable reason at all - get lemons.
One thing regarding my 4500.
When I got it, I immediately upgraded its firmware to 1.23na. It came loaded with 1.21.
I am wondering now, if I should have tested it first with the original firmware to see if all worked.
Perhaps I could have DOWNgraded the 4500 back to 1.21 and tested before going the route of returning it to the online store I bought it from.
Oh well, one way or another, this story is not over, and you can be sure that I'll post what ends up happening.
I just have to grit my teeth and put up with the 655 for a few weeks....somehow.....I will try to survive it.
-
Ok, Ya I was looking at the dir-655 emulator just a few minutes ago..seems like its not very user friendly. :-\
I see there are some issues with it in that forum but nothing related to UI operations.
Here's a good rule of thumb I try to uphold when working with any piece of HW, Electronic or non. "if it works, don't fix it!" Always try the units that are already loaded and make sure it works right out of the box. Always. If there seems to be a problem, upgrading to the latest and greatest may not always fix the issue and leaving the real issue still to be fixed. (These units work great on any FW version they released save one. V1.21 had been known to be buggy for some of us that tried it. That's not saying that not everyone saw the same issue for this version. Some people on here have it loaded are are having great experiences with it.)
Always troubleshoot the issue until all resources have been exhausted with FW that comes loaded in the box. If at that point the issue hasn't been resolved, then review the details of FW updates and apply them and then test the results again. If at that point the issue hasn't been resolve then there might be due cause for calling up CS and asking for and RMA.
There is always the possibility that there are lemons out there. However going through some troubleshooting to figure out if it is needs to be done is key first. Why I'm getting my friends returned RMA 4500 from him and see whats going on with it and to test on a different ISP network system. Were looking to see if his issue travels or not. This is apart of troubleshooting.
I've talked to some people about our issues and the majority of the time issues stem from user configurations and setup. The rest and seem to be a small part and agree with you to a point that there are some HW failures on this unit.
BTW, Vancouver B.C? Was curious, I'm headed to Victoria B.C. for the holidays. ;D
-
Yeah I bought it online from a company in Vancouver BC - I am in Ottawa ON, so shipping is an unfortunate reality.
There are NO local retailers in Ottawa that sell the 4500, unfortunately.
-
Well hope it gets figured out man. Let us know how it goes.
-
Update:
I bought a dir-655 last night (as a temporary replacement until I get new 4500).
What a nightmare !!
I cannot wait to return it to the store (but have to wait for my replacement 4500 first).
The dir-655 is buggy and slooooow !!!
(No wireless restarts, though from what I can tell from their cryptic logs !).
The web interface on the 655 is at least 5 times slower (no joke) compared to the 4500.
Almost every change/update you save on the 655 requires a restart - typically 30 seconds or so (wasted).
At first, this 655 was not "seeing" any hard wired or wireless clients. I had no idea why - it almost seemed that it was not aggressive enough at giving out dhcp ip addresses.
EVENTUALLY, it populated itself with clients, so then I decided to reserve ips for these devices.
I almost ripped this router off the desk and threw it into the garbage it was soooo frustrating to set up.
The router got confused about ip addresses and what was dhcp vs reserved so many times that even after "saving" the changes, things did not set up correctly.
I actually had to reset to factory settings and reboot this thing about 3 times - just to try and get it configured properly.
Even now, with all clients connected, when I go to the status screen and click on wireless - it takes (forever) to populate the screen and is hit and miss whether it actually decides to display the wireless connected clients or not. Unbelievable !
Regarding QoS, I have set up different priorities for traffic and when I check the internet sessions, it does display the streams, however it does not display the priority - so i have NO way to verify if my QoS is working or not.
Regarding the logs - for some reason they LOOK very different than what I am used to on the 4500. For one, they are broken into MANY pages, rather than allowing them all to be viewed on one page, which makes navigating the info a pain. Plus, many of the messages it displays are strange:
For example, what is all this garbage ?
Priority Time Message
info Dec 14 21:05:12 [ 5641.620000] m_table count= 1 Del 01005e00 00fc000b
info Dec 14 21:04:14 [ 5583.620000] m_table count= 2 Del 01005e7f fffa000b
info Dec 14 20:54:28 UDHCPD Inform: add_lease 192.168.0.67
info Dec 14 20:54:24 UDHCPD Inform: add_lease 192.168.0.67
info Dec 14 20:48:56 [ 4665.780000] m_table count= 2 Add 01005e7f fffa000a
info Dec 14 20:48:45 UDHCPD sending OFFER of 192.168.0.55
info Dec 14 20:48:18 [ 4627.470000] m_table count= 1 Add 01005e00 00fc000a
info Dec 14 20:48:00 UDHCPD sending OFFER of 192.168.0.97
info Dec 14 20:47:57 [ 4606.000000] module arch cleanup nf_ubicom_streamengine_default_classifier: OCM instruction memory free of 0 @00000000
info Dec 14 20:47:55 [ 4604.940000] module arch cleanup sch_ubicom_streamengine: OCM instruction memory free of 0 @00000000
What a collossal nightmare. I cannot imagine how Dlink can get away with selling such a shoddy product.
Perhaps the processor on the 655 is junk, I don't know, but I have a theory.
The HARDWARE revision of the unit is B1.
It would almost seem that Dlink does a good job on their routers with the FIRST/original Hardware revision.
When they make a newer version, the problems seem to start.
Even Furry noted that his 4500's are on A1 (which work fine), and most problems are on devices with A2 (which mine is).
This dir-655 is on version B1 - so who knows "what" they've done to the hardware to make it this excrutiatingly frustrating to work with.
In the store, they only had 655s with h/w rev B1, so no luck there.
I only hope that I get my replacement 4500 soon, so I can take this white albatross back to the store for a refund - as its buggy behavior is making my blood boil !
Yea, that does sound like one of the firmware bugs people were talking bout on the DIR-615 forums. (http://forums.dlink.com/index.php?topic=7825.0) I don't like some of attitudes on the forum though so fair warning. Anyone that uses racial stereotypes in their rants should be banned. ::shrug:: JMHO.
BTW, whats the hardware revision of your DIR-655, I suspect you have a import. From someone who has used a 655, I can tell you that log is not normal at all.
-
The 655 is hardware verion B1, running firmware 2.00na.
I checked (all 22) of the boxes they had on the shelves and they were all the same.
-
Well I dug around, and looks like the B1 was first release in Taiwan.
Picture of both (http://www.dlinktw.com.tw/support/download_version.asp)
Looks like the B1 was released there first, but with a firmware update 11/26/10 while the newest firmware here is 9/16/10. The main different looks cosmetic, a different case and lights to match the newer look. Who knows what is under the hood though. Also because the router came out in Augest in Taiwan, how can the first Taiwan firmware build have a build date of 11/26/10? Unless they shipped with the firmware of a different hardware revision. And I am wondering if thats what it is. If the B1 has the latest firmware of the A3 just with a different name. Its over 6MB so it appears to be a stock firmware, so its hard to say. All I really know is those logs look like firmware errors. Anytime you can see under a GUI's skirt like that, its not a good thing.
PS. Awsome Icon.
-
UPDATE:
They are (finally) sending me a new 4500 (the company I bought it from).
I got an email that they have just shipped it via Purolator (from Vancouver to Ottawa).
I estimate about 4 days max. Meanwhile I will continue to enjoy my Netgear WNDR3700.
WHEN it arrives, I will NOT upgrade the firmware right away.
I'll set it up like the last time and babysit it.
If this one gives me the same wireless restart BS, then I will send this back and swear off D-Link for good.
BTW, I know many on here feel that there must be some magical combination of (configuation settings) that will make these routers behave. I am starting to believe that if these routers were worth anything at all, they would not be so flaky as to be affected by simple configuration settings - which the router enables you to make in the first place.
It shouldn't be this difficult to make the router perform properly.
-
Well that maybe true however not all or everyone has issues. Sorry that you've had a bad experience. I hope this one will be fixed. I enjoy mine. I do understand that there are some lemons out there. Just bad luck I guess. Better luck is out there. Let us know.
-
I was helping a user through private message, he has the Dir 615 and Port forwarding was not working for him nor did my rules. I even tried DMZ but so far nothing worked out. I guess the router deserves a replacement. Anyways, he might purchase a 4500 the best routers available! :)
--
Chris
-
I received my (new-replacement) 4500 a couple of days ago.
I did not upgrade the firmware to 1.23 (it came with 1.21 loaded on it).
I manually configured the router (instead of loading the config file I had for the previous 4500).
I am HAPPY to report that in the 4 days it has been "up", I have not had ANY wireless restarts.
If things continue to work properly, then I will not upgrade the firmware to 1.22 or 1.23.
The only mystery that remains is if my whole wireless restart issue was due to a bad wireless radio in my first router, or if it was due to the 1.23 firmware.
I guess I'll find out when the day comes that I am either brave or stupid enough to upgrade the firmware.
Lastly, can someone please let me know about the "wan slowdown" issue that 1.22 fixed ?
How did this issue manifest itself - ie, how long did it take to happen, and what did it look like, what was the fix for it, etc - (if the symptoms were not intuitively obvious).
-
Good to hear man. Glad you got it back and it's running well. I would save off your Configuration to file and keep it safe for later use.
Some people saw the wireless hang and WAN slowdown and hang on v1.21. Some of us didn't. I did. Seem to crop off after being on for like a day or 2. Then I would come home from work and nothing would get connected to the Internet. Would have to power cycle the router to fix it. After I beta tested follow-ons for DLink, finally v1.22 fixed those issues and remains fixed in v1.23.
If your having good experiences with thats loaded now. KEEP IT! Don't upgrade until you really need to.
Gonna give up on the DIR-655? ::)
-
Yeah, I gave up on the 655 as it was garbage from day 1.
I returned it before my 30 day return expired - then replaced it with a temporary Netgear wndr3700).
Now that I have a working 4500, I have returned the the Netgear.
I am now liking my 4500 - again.
So far so good !
-
YAAAAAAAAY! ;D
-
O snap, can't be left out. YAAAAAAAY!
--
Chris
-
Hmm, thats too bad.Because when our DGL's start dying (is going to start happening sooner or later) what do you think will be our replacements? The 855? I am personally thinking about trying one of those Asus routers with dd-wrt. They offer some pretty nifty features.
-
Will find me a used 4500 till I can't find anymore. ;D
I wish they made the DD-WRT FW a little less advanced. Soooo many options and seems a bit less intuitive. :P
-
Seems I have spoken to soon.
Only starting today - I saw "Wireless Restart" in the logs.
Once at 7:42am and another (so far) at 1:33pm.
I am going monitor this and if it happens again I will try locking it on a specific channel (instead of auto) - although it did (not) change channels when it did its restart.
Now why after 6 days of being a good little router, has it decided to act up ?!
At least there is ONE difference from the last router - in that this time, the Wireless Restarts were not accompanied by DE-Auth and RE-Auth of the wireless clients - these restarts are all alone by themselves.
Hmmmmm.....
-
You have any Iphones?
Try locking in Chl 11.
-
Yes - one iphone4.
What is the relevance to channel 11 ?
-
Been told it give the best connection and performace. Does the wireless restart happen if you put the I4 on a static IP address?
-
All my wireless clients have a reserved IP address.
This makes troubleshooting easier as well.
I can try changing to ch 11 and see what happens (it is on ch 9 auto right now).
-
I might also try shutting down all wireless devices for a test accept for one and see what you find out. I presume you are using the default Wireless mode of mixed? If you don't have any A or B devices, you could try Mixed G and N. No need to broadcast what modes your not using. I would save off your configuration to file at some point so you can go back should something really go wrong while your tweeking. ::)
-
Nothing fancy on my router.
Using "g" only.
It was working fine for 6 days, then - well, you know.
No changes in environment or configs between when it was behaving, to when it decided to throw in those two wireless restarts to make my day more interesting.
-
did it give an ip address if the restart and whats connected to that IP address?
-
Hmm, I did some digging around and its a pretty complex issue. Theres a couples issues going around and a TON of misinformation so its hard to dig through the BS. Most of the issues you have already resolved with the DHCP reseverations, channel 11, and WPA instead of WEP. There was another more subtle problem I saw a trend of, and thats with most Iphone 4, and the later patched Iphone 3G. Seems there is a firmware bug with the phone handing off encription confirmation using WPA with AES. Iphone forgets the key, so requests a new one, so the router restarts the wireless to regenerate a new one. When I say key, I don't mean your pass phrase. This someone ties into the use of 3G though. Maybe it something about 3G requires it to send keep alive signals to network, so has to switch from Wifi to 3G? Maybe its interference from the antenna itself? I cant find info on it other then user experiences, and most of those are less then accurate. And you know how Apple is, if its not in their support site, your imagining the problem. LOL. So things to try:
1. Try turning off 3G on your Iphone and see if they helps. If so, they call Apple and report, and likly its a firmware issue.
2. Try changing from AES with TKIP, that will hand over the encription to the OSi software, and avoid the chip(and firmware bug) causing the issue. There are other problems associated with TKIP though and the Iphone.
3. Make sure your Iphone is set to G only, since the Iphone 4 is the first to be capable of N.
4. If all else fails, try to keep your Iphone off(100% powered down) while in the house. If nothing else, if it happens even once with the phone off, it confirms its not the phone. In retrospect, probably be a good idea to try this first.
-
Just a quick update.
I have made no changes (yet) , but checked the logs frequently.
There have been no further instances of "wireless restart" since 20-jan-2011 @ 742am and 1:33pm.
I will continue to monitor this before I try any changes to config or otherwise.
-
Ok, I think it has something to do with your Iphone, 3G and the security process of WPA with AES. And if I had to guess, something simular to how my G1 would randomly broadcast some kind of signal that would actually create ripples on my kitchen TV if it was too close to it. Never if I was in power conserve mode which would turn off 3G.
-
Ok, so this morning my 4500 decided to HANG.
(UP time approximately >4 days)
I was trying to browse the internet on wireless AND wired pc's.
I could not even connect to the router's own web interface on either pc.
I WAS able to sometimes get sloooooooow (eventual) connectivity to "some internet sites".
As far as wireless - still had good connectivity (strength and speed) - so the wireless part of the router seemed to be ok.
It is just the router, itself that wasn't doing any routing.
As a result - I just updated to 1.23na - so we'll see what happens now.
-
OK sounds like v1.21 strikes again. >:(
Should see any with v1.23.
Keep us posted.
-
If 1.23 does not produce results you can always try downgrading to 1.15 firmware, which I think allows you to downgrade even further if needed. I think it is very stable and many other users, I remember, also had good results with it. Here is the link to it if you want want too try it. just throwing it out there as a last option sort of thing...
http://www.ispgeeks.com/wild/modules.php?name=Forums&file=viewtopic&p=15926 (http://www.ispgeeks.com/wild/modules.php?name=Forums&file=viewtopic&p=15926)
-
Ok - so far, so good with 1.23na.
(Mind you, it has only beeen a day and a bit, now).
So far, no wireless restarts or any other abnormal behavior.
I'll post any updates.
-
Kewl, keep us posted.
-
After an UPtime of about 2.5 days, today I received 1 Wireless Restart (at 6:53am Tue Jan 25).
The router did not change its channel - and no other "events" or environmental issues were apparent.
So this seems to be happening out of the blue - relatively INfrequently.
Since it did not cause any disconnections of any clients, I may just learn to live with this behavior - until it becomes service-affecting.
Related to this, I emailed D-Link tech support 2 days ago.
Specifically, I asked them about how they programmed the firmware of the router.
I asked what needs to happen for the router to report "wireless restart" in the logs.
No reply (yet).
-
OK. well something is going on. I wish we could figure it out for ya. ???
Keep us posted.
-
Consider downgrading to 1.15 fw
-
Well - today - after 7 days and 12 hours of uptime, I got one wireless restart.
The channel did not change.
The time of day was 11:25 am.
There were no apparent environmental anomalies.
There were no other issues (deauthentications/reauthentications, etc).
So, if this happens so infrequently - with no perceivable impact - I think I can live with it.
I asked D-link to give me mroe info on just what a wireless restart "is" - what causes it, what happens when it "does" a wireless restart.
When that answer comes - (it has been almost 2 weeks now of waiting) - I will post here.
Lastly, I do not feel this is firmware related, as my previous 4500 had this problem in a chronic way, whereas this router exhibits maybe 1% of the issue - same firmware, etc - so leads me to beleive it was the hardware itself - both A2 version.
I will update when I get more info.
-
Ok.
I started testing my A1 last night. I am seeing a ton of deauthentications/reauthentications and not sure why.
I have forward this info to DLink.
I'm currently on v1.12 and will be updating to v1.23 tonight and testing again and see what happens. I didn't see any restarts from the logs that were sent to me this am. Will look again tonight before updating.
I have 2 1st gen iPhones, a blackberry on 3 month loan and a Mac Book Pro.
I'm hoping to help narrow this down.
-
After about 10 days of UPtime, my 4500 rebooted itself.
(I am not sure what causes this)
As for wireless restarts, I have received two more - both were about 2 days apart from each other, and both happened in the early morning hours (one at 530am, and the other at around 6am) - with no obvious issues or behavior noted (environmental or in the logs).
BTW, my email to D-link - now 2 weeks old - still has not yet been responded to.
I am just glad that my wireless restarts (on "this" router) have not yet become service-affecting.
-
Hey Ice,
Was curious, were your Iphones idle at these time frames or active?
Been doing some testing on my 4500 and my 1st gen iPhone. I haven't been seeing any restarts on my A1 HW however I'm seeing a ton of De-authentication log entries for some reason. Even during times that the iPhone is Idle and I'm asleep. Have you seen anything like this in your logs?
I'm curious, would it affect your services at your place if you used just the iPhones data network and shut off the WiFi on the iPhones for a few days and see if you see anything on the router? Log entries and re-starts?
-
There's only one iphone4 in the house, and it was idle (5am) when the wireless restart was reported.
I have received a wireless restart before when the phone was not in the house, or when its wifi was disabled - so I have eliminated it as a possibility.
-
Ok, would be interesting to get a wireless sniffer in your area and see what other environmental conditions could be effecting this router.