Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mocher]

Hello,


Recently I bought dir-655 ( version A4 running on 1.21 fw) and I have problem with wireless. Every time I change something in wireless settings ( apart from authentication ) my router keeps restarting wireless. My logs:
[INFO]   Sun Feb 01 01:07:18 2004   Wireless link is down
[INFO]   Sun Feb 01 01:07:18 2004   Wireless restart
[INFO]   Sun Feb 01 01:07:18 2004   Disconnect all stations
[INFO]   Sun Feb 01 01:07:18 2004   All Wireless shut down
[INFO]   Sun Feb 01 01:07:16 2004   Wireless restart
[INFO]   Sun Feb 01 01:07:14 2004   Wireless link is up
[INFO]   Sun Feb 01 01:06:49 2004   Wireless link is down
[INFO]   Sun Feb 01 01:06:49 2004   Wireless restart
[INFO]   Sun Feb 01 01:06:49 2004   Disconnect all stations
[INFO]   Sun Feb 01 01:06:49 2004   All Wireless shut down
[INFO]   Sun Feb 01 01:06:47 2004   Wireless restart
[INFO]   Sun Feb 01 01:06:45 2004   Wireless link is up
[INFO]   Sun Feb 01 01:06:20 2004   Wireless link is down
[INFO]   Sun Feb 01 01:06:20 2004   Wireless restart
[INFO]   Sun Feb 01 01:06:20 2004   Disconnect all stations
[INFO]   Sun Feb 01 01:06:20 2004   All Wireless shut down
[INFO]   Sun Feb 01 01:06:18 2004   Wireless restart
[INFO]   Sun Feb 01 01:06:16 2004   Wireless link is up
[INFO]   Sun Feb 01 01:05:51 2004   Wireless link is down
[INFO]   Sun Feb 01 01:05:51 2004   Wireless restart

on factory settings the wireless is up but I would like to change chanel. There are no wireless phones or other devices near router. Also it's my second model of dir-655 ( the previous had the same problem so I switched to a new one ). Router is connected only to an ADSL modem.

[lotacus]

Some setting require only the wireless module to reload others require that the whole kernel. This is so those settings can take effect without much down time of the router.

[mocher]

I understand but the wireless keeps restarting even after rebooting the device. Only after resetting to factory default the link is stable.

[lotacus]

I didn't see the log you posted for some reason I experienced this last night but of yet not found the cause.

[arod]

Try the beta firmware.

http://forums.dlink.com/index.php?topic=4464.0

[lotacus]

I have the 1.22 installed and noticed it last night but was the only time I noticed it being so aggressive . This seemed to happen after several changes without rebooting between.

An explanation that I can come up with would be that those changes are being queued up then when hit reboot it brings wireless down applies the first change brings up wireless, and repeats this process before it sends the kill signal to the kernal.  That's not verified but the only logical thing I can Think of.

[EddieZ]

You could try resetting to defaults, reboot and set the device up again from scratch

[Lycan]

If you disable the wireless, does the behavior continue?

[mocher]

First I would like to thank all of you for the feedback

You could try resetting to defaults, reboot and set the device up again from scratch

The thing is that every time i reset the router and change wireless settings it starts the loop that resets wifi on and on.

If you disable the wireless, does the behavior continue?

Honestly I don't know but all I care about is wireless, why disabling it? I will try that when I will be at home

[EddieZ]

set to defaults, reboot and reflash with the 1.22beta firmware (through wired connection). Might be a bad firmware load.

[Lycan]

wireless might be picking up interference and the router is rebooting in order to clear the errors.

[mocher]

If you disable the wireless, does the behavior continue?

No nothing happens and I know it might be interfrering that's why I'm trying to change the chanel but every chanel I set keeps reseting the router ( apart from factory defaults). Right now I'm trying to get rid of the problem with beta fw I hope it works


Update 1:
After installing 1.22 beta the logs are:


[INFO]   Sat Jan 31 10:37:58 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56877 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:51 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56970 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:48 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56976 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:46 2004   Wireless link is down
[INFO]   Sat Jan 31 10:37:46 2004   Wireless restart
[INFO]   Sat Jan 31 10:37:46 2004   Disconnect all stations
[INFO]   Sat Jan 31 10:37:46 2004   All Wireless shut down
[INFO]   Sat Jan 31 10:37:44 2004   Wireless restart
[INFO]   Sat Jan 31 10:37:43 2004   Blocked incoming TCP packet from 199.7.50.72:80 to 192.168.1.122:56898 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:42 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56976 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:42 2004   Wireless restart

Update 2:
In the new fw the router acts the same ( I can't change anything in wireless exept authentication)

[drfun]

I really hope I dont have this issue with the 655 that I just bought.
I just returned the dir-825 for the same reason and bought the 655 thinking it would be more stable.

I was running the radios separate.
N was on 5ghz
G only was on 2.4ghz

One day I saw both card restarting with out any changes to the system.
I had reset default firmware and reloaded firmware 3 times with no luck on clearing the issue.
I didnt think anything of it until I tried streaming a TV show or a movie to the PS3. During the show it would restart.. Cutting off the wifi connection to the ps3. Then I would have to start the movie over, fast forward to the part I was at just to have it restart 25 minuets later.

Well I guess I will have to watch the logs on the 655 closer for the next few weeks.
But if it happens again I am going back to the Apple access point that I sold to buy the dlink.

Note: I only bought the dlink for the jumbo packet support. It makes a BIG difference when jumbo packet is enabled on the desktop and the Netgear ReadyNas.

Later

[thecreator]

No nothing happens and I know it might be interfrering that's why I'm trying to change the chanel but every chanel I set keeps reseting the router ( apart from factory defaults). Right now I'm trying to get rid of the problem with beta fw I hope it works


Update 1:
After installing 1.22 beta the logs are:


[INFO]   Sat Jan 31 10:37:58 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56877 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:51 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56970 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:48 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56976 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:46 2004   Wireless link is down
[INFO]   Sat Jan 31 10:37:46 2004   Wireless restart
[INFO]   Sat Jan 31 10:37:46 2004   Disconnect all stations
[INFO]   Sat Jan 31 10:37:46 2004   All Wireless shut down
[INFO]   Sat Jan 31 10:37:44 2004   Wireless restart
[INFO]   Sat Jan 31 10:37:43 2004   Blocked incoming TCP packet from 199.7.50.72:80 to 192.168.1.122:56898 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:42 2004   Blocked incoming TCP packet from 64.78.164.232:80 to 192.168.1.122:56976 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 10:37:42 2004   Wireless restart

Update 2:
In the new fw the router acts the same ( I can't change anything in wireless exept authentication)

Hi mocher,

No one asked, so I will. Where are you living? Meaning House, Apartment, High-rise Building, Row-House.
If you are not living in a seperate House, but in an Apartment Building, one of your Neighbors could be jamming your Wireless Router, for the reason you are seeing what you are seeing.

Or simply having something that operates on the same frequency as your Router.

Try changing the Wireless Channel. Don't use Auto. Experiment around until it works.

[lotacus]

try turning the pwer down to medium too. see what happnes (though you shouldn't) maybe the router is just over heating. try puting it in the freezer for 10 minutes.