Print

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

[vipervin]

Old topic, but I figure I bump it because mpb, you saved me from throwing my DIR 655 out the window.

I knew Symantec's products were garbage, but I decided to install it anyways.  Soon after, I started to get constant drops on my wireless connections.  Had no clue what was going on and I never connected the two together.  I did everything imaginable, firmware upgrades, change in settings, and even went out an bought a new DIR 655!

Nothing worked until I stumbled onto this thread.

Turned off SEP, and instantly everything worked like normal.    Symantec!

Anyways, I was so happy, I had to register on this forum just to tell my story. 

[smlunatick]

Just to add my experience with a Norton product also.  Norton "retail" grade security packages (360 and Internet Security 2009) firewall module need to be told to "trust" the network LAN gateway IP address and the wireless network name (SSID.) If not, the software will "deauthenticate" from the router.

[whitey019]

I haven't check this forum much since I solve my restart issue, but I can see that others have benefited from  my experiences .........that's great.  Maybe this thread should be a STICKY as suggested.

[mpb]

I'm glad disabling SEP is working for everyone else.  Honestly, I don't know what made me try it in the first place, except I noticed my wireless always seemed to drop shortly after my wired machine booted up.

SEP firewall on a wireless machine seems fine... it's only that wired connection that causes the issue.

I saw the other post about it being related to the IPV6 default rule... very interesting.  I'm not sure why the D-Link would react to whatever SEP is doing by deciding to restart the wireless, that's very strange, and maybe it's something D-Link could patch around, or it represents some unknown flaw in D-Link's code.

By the way, I'm running the latest version of SEP, 11.0.4202.75, and Symantec hasn't addressed or patched the issue.

I sometimes logon to the Symantec EP forums so maybe rather than wait for Symantec to stumble across this, I should actually start a thread and see if the Symantec engineers have any input.

[thecreator]

Hi All,

Let me jump it here. I do not know Symantec Norton Products, because I use McAfee Internet Security and while I do not use SecureSpot, D-Link might wish to check SecureSpot's Logs.

Why?

I am running the McAfee Personal Firewall on my Personal Desktop Computers. I always check its logs. Anyway, even though the Network is completely trusted, McAfee is blocking the Router and a number of other devices that are on the Network. And the Network, again is completely Trusted.

I would look at the logs of your Firewall products that all you use and see if anything is being blocked, that is part of your Network.

[TheWitness]

What this all tells me is that the DIR655 experiences a buffer overflow when certain classes of network traffic are blocked by internal devices.  In other words, it run's out of memory in some internal buffer and restarts the service (wireless in this case).

So, even though these personal firewalls are blocking things, it still points back to the DIR655.  However, the information here does let them (DLINK) know the specific traffic type that is causing the lockups on this new 1.3.x class of firmware.  This fact alone is worth the price of the post.

TheWitness

[Jmonster]

I have been having this as a issue for quite a while and I have un-installed SEP 11.0.4202.75 and my wireless has not restarted since(going on 2 days now). I only removed SEP from the one PC I have directly wired to the router.  The wireless restarts do not seem to be a issue with a PC that has SEP that is connected wirelessly to the router. 

Is this a firmware buffer overflow issue??

THANKS FOR THE FIX!

[whitey019]

Just to clarify things, you can still use SEP as long as you don't enable/install the firewall.

[perost]

I have had the same problems with wireless restarts. Then I read somewhere that it could be related to DHCP - maybe Windows 7 or IPv6 - that caused some kind of buffer overflow in the DIR-655. Well, I have reserved all my addresses and it had been solid for 48 hours. 

Per

[Arvald]

My findings on this... the issue is with SEP... the issue is not the IPv6 setting.

I'm trying to get my network guy at work to tell me what it was, we did try the IPv6 and it was not different.

The side note is that Dlink was not the only vendor that this hit... seems that only Linksys (my companies standdard provided router if you do not have one) did not get it.

[SandyS]

I have a DIR-655 A3, working over a DWA-142 rangebooster N from my desktop PC. I was not getting frequent restarts, but I was getting frequent de-authentication  requests being sent to the router, which disconnected my internet sessions. I'm not sure, but this may be related to the restart problem mentioned here. I upgraded my router firmware to 1.21, and the firmware for the rangebooster adapter N.
I also made all the changes to upgrade the speed to 300 mbps, which worked fine.
Per this thread, I set up my kaspersky antivirus to allow traffic from the addresses the router uses for my desktops and laptops, and to allow traffic from the router itself.
So far, so good. I booted up this morning and my internet hasn't gone  down all day.
 
Hopefully this helps someone else who may also have these problems.
I do suspect that it was the rangemaster N firmware upgrade that did the trick, but I didn't have time to do the incremental testing to confirm this.

[khein2]

ALL, thanks to everyone for their relentless pursuit to fix this problem. Like vipervin, you saved an perfectly good router from taking a flying leap.

That said, to add a note. I was running a much older Motorola Router and upgraded to a Trendnet 655 N router. No big issues until I added a second and then third computer. I didn't attribute the SAV to the problem and figured it was from a cheap router, did my research on-line and found the DIR-655 fit my needs. Still had the same issue so figured it was my Cable Modem which was pretty old (2004) so I got the cable company to replace it. New router, new modem, new computers, old PC (with SAV) same problem until now. I changed the firewall settings and so far so good. 

I will max my system as much as I possibly can, adding 2 more laptops and another PC on the LAN. I will update based on good or bad results.

Thanks again!

[partach1]

Have scanned the articles in this thread.
I have the 655 connected to a dlink green Gb switch, which connects it to all clients. At the time of the wireless restarts there was no laptop or any PC like client active. Only active party each night is my linux based DS207+ NAS. No SEP to be seen anywhere in the house.... So are there other reasons to let it restart? BTW i have syslog running for more than a week and this is the first with these restarts....

Dec  4 00:03:16 192.168.1.250 Fri Dec 04 00:03:19 2009 paco System Log: Wireless restart
Dec  4 00:04:23 192.168.1.250 Fri Dec 04 00:04:27 2009 paco System Log: Wireless restart
Dec  4 00:06:51 192.168.1.250 Fri Dec 04 00:06:54 2009 paco System Log: Wireless restart
Dec  4 00:16:42 192.168.1.250 Fri Dec 04 00:16:46 2009 paco System Log: Wireless restart
Dec  4 00:18:01 192.168.1.250 Fri Dec 04 00:18:04 2009 paco System Log: Wireless restart
Dec  4 00:21:33 192.168.1.250 Fri Dec 04 00:21:37 2009 paco System Log: Wireless restart
Dec  4 00:21:47 192.168.1.250 Fri Dec 04 00:21:50 2009 paco System Log: Wireless restart
Dec  4 00:22:12 192.168.1.250 Fri Dec 04 00:22:16 2009 paco System Log: Wireless restart
Dec  4 00:25:39 192.168.1.250 Fri Dec 04 00:25:43 2009 paco System Log: Wireless restart
Dec  4 00:27:29 192.168.1.250 Fri Dec 04 00:27:33 2009 paco System Log: Wireless restart
Dec  4 00:29:54 192.168.1.250 Fri Dec 04 00:29:58 2009 paco System Log: Wireless restart
Dec  4 00:34:05 192.168.1.250 Fri Dec 04 00:34:09 2009 paco System Log: Wireless restart
Dec  4 00:35:51 192.168.1.250 Fri Dec 04 00:35:55 2009 paco System Log: Wireless restart
Dec  4 00:38:41 192.168.1.250 Fri Dec 04 00:38:45 2009 paco System Log: Wireless restart
Dec  4 00:38:48 192.168.1.250 Fri Dec 04 00:38:52 2009 paco System Log: Wireless restart
Dec  4 00:39:15 192.168.1.250 Fri Dec 04 00:39:19 2009 paco System Log: Wireless restart
Dec  4 00:39:47 192.168.1.250 Fri Dec 04 00:39:51 2009 paco System Log: Wireless restart
Dec  4 00:41:23 192.168.1.250 Fri Dec 04 00:41:27 2009 paco System Log: Wireless restart
Dec  4 00:41:32 192.168.1.250 Fri Dec 04 00:41:35 2009 paco System Log: Wireless restart
Dec  4 00:41:35 192.168.1.250 Fri Dec 04 00:41:39 2009 paco System Log: Wireless restart
Dec  4 00:42:10 192.168.1.250 Fri Dec 04 00:42:13 2009 paco System Log: Wireless restart
Dec  4 00:46:09 192.168.1.250 Fri Dec 04 00:46:13 2009 paco System Log: Wireless restart
Dec  4 00:46:27 192.168.1.250 Fri Dec 04 00:46:31 2009 paco System Log: Wireless restart
Dec  4 00:48:44 192.168.1.250 Fri Dec 04 00:48:48 2009 paco System Log: Wireless restart
Dec  4 00:49:18 192.168.1.250 Fri Dec 04 00:49:22 2009 paco System Log: Wireless restart
Dec  4 00:50:14 192.168.1.250 Fri Dec 04 00:50:18 2009 paco System Log: Wireless restart
Dec  4 00:50:40 192.168.1.250 Fri Dec 04 00:50:44 2009 paco System Log: Wireless restart
Dec  4 00:50:43 192.168.1.250 Fri Dec 04 00:50:47 2009 paco System Log: Wireless restart
Dec  4 00:57:47 192.168.1.250 Fri Dec 04 00:57:51 2009 paco System Log: Wireless restart
Dec  4 00:58:35 192.168.1.250 Fri Dec 04 00:58:39 2009 paco System Log: Wireless restart
Dec  4 00:58:51 192.168.1.250 Fri Dec 04 00:58:55 2009 paco System Log: Wireless restart
Dec  4 01:00:46 192.168.1.250 Fri Dec 04 01:00:50 2009 paco System Log: Wireless restart
Dec  4 01:09:33 192.168.1.250 Fri Dec 04 01:09:38 2009 paco System Log: Wireless restart
Dec  4 01:11:13 192.168.1.250 Fri Dec 04 01:11:18 2009 paco System Log: Wireless restart
Dec  4 01:13:09 192.168.1.250 Fri Dec 04 01:13:14 2009 paco System Log: Wireless restart
Dec  4 01:19:47 192.168.1.250 Fri Dec 04 01:19:52 2009 paco System Log: Wireless restart
Dec  4 01:34:53 192.168.1.250 Fri Dec 04 01:34:58 2009 paco System Log: Wireless restart
Dec  4 01:35:02 192.168.1.250 Fri Dec 04 01:35:07 2009 paco System Log: Wireless restart
Dec  4 01:38:02 192.168.1.250 Fri Dec 04 01:38:07 2009 paco System Log: Wireless restart
Dec  4 01:38:23 192.168.1.250 Fri Dec 04 01:38:28 2009 paco System Log: Wireless restart
Dec  4 01:39:12 192.168.1.250 Fri Dec 04 01:39:17 2009 paco System Log: Wireless restart
Dec  4 01:40:34 192.168.1.250 Fri Dec 04 01:40:39 2009 paco System Log: Wireless restart
Dec  4 01:40:50 192.168.1.250 Fri Dec 04 01:40:55 2009 paco System Log: Wireless restart
Dec  4 01:42:07 192.168.1.250 Fri Dec 04 01:42:12 2009 paco System Log: Wireless restart
Dec  4 01:42:36 192.168.1.250 Fri Dec 04 01:42:41 2009 paco System Log: Wireless restart
Dec  4 01:43:58 192.168.1.250 Fri Dec 04 01:44:03 2009 paco System Log: Wireless restart
Dec  4 01:44:02 192.168.1.250 Fri Dec 04 01:44:07 2009 paco System Log: Wireless restart
Dec  4 01:46:21 192.168.1.250 Fri Dec 04 01:46:26 2009 paco System Log: Wireless restart
Dec  4 01:46:47 192.168.1.250 Fri Dec 04 01:46:52 2009 paco System Log: Wireless restart
Dec  4 01:47:12 192.168.1.250 Fri Dec 04 01:47:17 2009 paco System Log: Wireless restart
Dec  4 01:48:49 192.168.1.250 Fri Dec 04 01:48:54 2009 paco System Log: Wireless restart
Dec  4 01:55:27 192.168.1.250 Fri Dec 04 01:55:32 2009 paco System Log: Wireless restart
Dec  4 01:55:31 192.168.1.250 Fri Dec 04 01:55:36 2009 paco System Log: Wireless restart
Dec  4 01:58:05 192.168.1.250 Fri Dec 04 01:58:10 2009 paco System Log: Wireless restart
Dec  4 01:59:05 192.168.1.250 Fri Dec 04 01:59:10 2009 paco System Log: Wireless restart
Dec  4 02:00:33 192.168.1.250 Fri Dec 04 02:00:38 2009 paco System Log: Wireless restart
Dec  4 02:02:55 192.168.1.250 Fri Dec 04 02:03:00 2009 paco System Log: Wireless restart
Dec  4 02:03:01 192.168.1.250 Fri Dec 04 02:03:05 2009 paco System Log: Wireless restart
Dec  4 02:03:49 192.168.1.250 Fri Dec 04 02:03:54 2009 paco System Log: Wireless restart
Dec  4 02:04:33 192.168.1.250 Fri Dec 04 02:04:38 2009 paco System Log: Wireless restart
Dec  4 02:04:39 192.168.1.250 Fri Dec 04 02:04:43 2009 paco System Log: Wireless restart
Dec  4 02:06:59 192.168.1.250 Fri Dec 04 02:07:04 2009 paco System Log: Wireless restart
Dec  4 02:15:52 192.168.1.250 Fri Dec 04 02:15:57 2009 paco System Log: Wireless restart
Dec  4 02:19:28 192.168.1.250 Fri Dec 04 02:19:33 2009 paco System Log: Wireless restart
Dec  4 02:22:26 192.168.1.250 Fri Dec 04 02:22:31 2009 paco System Log: Wireless restart
Dec  4 02:22:37 192.168.1.250 Fri Dec 04 02:22:42 2009 paco System Log: Wireless restart
Dec  4 02:24:20 192.168.1.250 Fri Dec 04 02:24:25 2009 paco System Log: Wireless restart
Dec  4 02:27:42 192.168.1.250 Fri Dec 04 02:27:47 2009 paco System Log: Wireless restart
Dec  4 02:34:40 192.168.1.250 Fri Dec 04 02:34:45 2009 paco System Log: Wireless restart
Dec  4 02:34:59 192.168.1.250 Fri Dec 04 02:35:04 2009 paco System Log: Wireless restart
Dec  4 02:35:05 192.168.1.250 Fri Dec 04 02:35:10 2009 paco System Log: Wireless restart
Dec  4 02:36:18 192.168.1.250 Fri Dec 04 02:36:22 2009 paco System Log: Wireless restart
Dec  4 02:37:19 192.168.1.250 Fri Dec 04 02:37:24 2009 paco System Log: Wireless restart
Dec  4 02:39:13 192.168.1.250 Fri Dec 04 02:39:18 2009 paco System Log: Wireless restart
---after this the device decided to reboot itself---

[Holy]

I had the same problems with the wireless restarts. First I could not find out wat the reason was, and D-link as well. I've never linked it to SEP that I installed in the last month. So after 2 years of no problems at all, they offered to replace it. And so I did.
After I received the new one I could correlate some of the issues and fixes described above.

My first router was A2 hardware. FW: 1.21 EU. On this router I had problems with wireless restarts. Both with a wired connection as well as with the wireless laptops. On all three machines I ran SEP version 12.0.122.192. Unfortunately I did not try disabling the SEP firewall before I returned the device to D-link.

My new router is A4 hardware, also FW: 1.21 EU. On this router I do not have any problems with wireless restarts. On the wireless laptops I have disabled the IPv6 firewall rules. Permanently disabling the SEP firewall at all does not work, since after some time it automatically switches itself on again. However. NO problems with wireless restarts, even with the SEP firewall ON.
But......as soon as I connected the wired desktop with SEP running with the firewall ON,  wireless restarts every couple of minutes. Disabling the SEP firewall on the desktop fixes it.
So: it is not just an wired vs wireless issue or just a SEP issue. It also has to do with the hardwareversion of your router.

I'm happy again with my router 

[obkook]

You guys have given me hope! My wireless restarts were getting more frequent and my wireless clients were all but useless. http://forums.dlink.com/index.php?topic=10045.0

I do have SEP, but *not* SEP firewall. But I have definiteyl confirmed that it is the wired machine which is killing the wireless clients.

Can you help me by explaining exactly which settings I need to change and where they are? Or is it possible my problem is similar but different?

Thanks!!

Kook