Print

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

[ftras]

Loaded 1.33b02NA_HNAP this morning.

Had issues with 1.32 and securespot, and had to disable Secure Spot temporarily until a new firmware came out, so I am glad to try the beta.  36 minutes with Secure Spot running and no loss of connection so far.    

Will repost in a day or so with an update but thought that others may want to post their results here as well.  

Hope I'm not too presumptuous by creating a topic.  

[Krusher]

I've noticed one annoyance now while moving from the 1.32beta09 to 1.33beta02...I am experiencing symptoms of what I think is the DNS relay bug returning.  I had the same issue with 1.33beta01 but wanted to see what happens first with the upgrade before I made a posting.  It's one of those things that is very subtle and you don't know if it's your PC at first or something else.

When I visit random web sites during the day; I will sometimes get pages that don't load and just sit there forever with a blank screen.  When I refresh, they instantly load.  This happens in IE and Firefox.

With 1.32beta09, this never happened after 2+ weeks.  What I am seeing now returns after a day or two.

When I ran the 1.32 commercial release it was much worse.  The web admin page was not accessible.  I would also sometimes get only parts of the web page; i.e. some pictures might not load (probably pictures from another server).  The only fix was a reboot.

I am running now with DNS relay turned off.  I'll report back in a few days either way.  Maybe my PCs here just DO NOT like the DNS relay feature.   

[mackworth]

that sounds like the issue that many of us had in 1.21, which led to the eventual problems in 1.22B05+ when they attempted to fix it.

Maybe they reverted the first they put in before?

[foxium]

I'm having the same problem that the OP has. Sometimes I have to hit the refresh button otherwise the page just won't show (regardless of browser). Tried firmware 1.32NA (the released version), 1.33NAb01 and 1.30EA_b05. Before coming across this thread I thought it's a problem upstream with my ISP  .

I'll give 1.32NAb09 a try.

[mackworth]

I'm having the same problem that the OP has. Sometimes I have to hit the refresh button otherwise the page just won't show (regardless of browser). Tried firmware 1.32NA (the released version), 1.33NAb01 and 1.30EA_b05. Before coming across this thread I thought it's a problem upstream with my ISP  .

I'll give 1.32NAb09 a try.

Is this with DNS relay on?  Try turning it off.

[Cobra]

Tried firmware 1.32NA (the released version), 1.33NAb01 and 1.30EA_b05.

Might be the problem right there...loading american and chinese firmwares.

[Krusher]

Chinese firmware?  If you load that, isn't the language in Chinese?   

So far, no more stalled web pages with 1.33b02 after turning off DNS Relay.  I'm crossing my fingers.

[mercurey]

I have been the issue 2nd or 3rd month ago (firmware 1.32NA).
First time, the wireless disconnects and reconnects as soon. On these days, it disconnect all the time. So, I connect by wire.
Please see the below the log. That is the wireless auto restarting with badly. There was no speed down and go to the disconnection. So, I could not connect the internet through the DIR-655.
Sometime, the device itself reboot without the rebooting log. All LED are off and on (Maybe, it happen twice per day).
So, I have upgraded the firmware with 1.33b02NA.
It is not useful action.
The wireless restarting is continuing.
What can I do?
===========
[INFO]   Thu Jan 28 06:58:53 2010   Wireless link is up
[INFO]   Thu Jan 28 06:58:30 2010   Wireless link is down
[INFO]   Thu Jan 28 06:58:30 2010   Wireless restart
[INFO]   Thu Jan 28 06:58:30 2010   Disconnect all stations
[INFO]   Thu Jan 28 06:58:30 2010   All Wireless shut down
[INFO]   Thu Jan 28 06:58:28 2010   Wireless restart
[INFO]   Thu Jan 28 06:58:16 2010   Wireless link is up
[INFO]   Thu Jan 28 06:57:52 2010   Wireless link is down
[INFO]   Thu Jan 28 06:57:52 2010   Wireless restart
[INFO]   Thu Jan 28 06:57:52 2010   Disconnect all stations
[INFO]   Thu Jan 28 06:57:52 2010   All Wireless shut down
[INFO]   Thu Jan 28 06:57:50 2010   Wireless restart
[INFO]   Thu Jan 28 06:57:22 2010   Wireless link is up
[INFO]   Thu Jan 28 06:56:59 2010   Wireless link is down
[INFO]   Thu Jan 28 06:56:59 2010   Wireless restart
[INFO]   Thu Jan 28 06:56:59 2010   Disconnect all stations
[INFO]   Thu Jan 28 06:56:59 2010   All Wireless shut down
[INFO]   Thu Jan 28 06:56:57 2010   Wireless restart
[INFO]   Thu Jan 28 06:51:00 2010   Wireless link is up
[INFO]   Thu Jan 28 06:50:37 2010   Wireless link is down
[INFO]   Thu Jan 28 06:50:37 2010   Wireless restart
[INFO]   Thu Jan 28 06:50:37 2010   Disconnect all stations
[INFO]   Thu Jan 28 06:50:37 2010   All Wireless shut down
[INFO]   Thu Jan 28 06:50:35 2010   Wireless restart
[INFO]   Thu Jan 28 06:49:43 2010   Wireless link is up
[INFO]   Thu Jan 28 06:49:20 2010   Wireless link is down
[INFO]   Thu Jan 28 06:49:20 2010   Wireless restart
[INFO]   Thu Jan 28 06:49:20 2010   Disconnect all stations
[INFO]   Thu Jan 28 06:49:20 2010   All Wireless shut down
[INFO]   Thu Jan 28 06:49:18 2010   Wireless restart
[INFO]   Thu Jan 28 06:48:47 2010   Wireless link is up
[INFO]   Thu Jan 28 06:48:23 2010   Wireless link is down
[INFO]   Thu Jan 28 06:48:23 2010   Wireless restart
[INFO]   Thu Jan 28 06:48:23 2010   Disconnect all stations
[INFO]   Thu Jan 28 06:48:23 2010   All Wireless shut down
[INFO]   Thu Jan 28 06:48:21 2010   Wireless restart
===cut hear because too many same log===

[foxium]

Might be the problem right there...loading american and chinese firmwares.

The EA (Chinese) firmware can display English. I flashed it to see if it will fix my router's duplicate LAN MAC address problem which D-link can't help me with, other than telling me the hardware is fake (does fake DIR-655 really exist?).

[foxium]

Is this with DNS relay on?  Try turning it off.

Thank you! The page not showing problem is indeed caused by DNS relay -- turned it off and all is fine again.

I thought the 1.32 beta/1.33 versions are supposed to have it fixed  Anyway, I don't need it, "it's not a function deemed necessary for a router" lol

[Cobra]

Did you reboot your PC or disable then enable your NIC after changing DNS relay?

You have to or you will not have a connection or connection will be flakey as your DNS requests are not routed correctly.

[foxium]

ipconfig /renew would do the trick too.

[Krusher]

that sounds like the issue that many of us had in 1.21, which led to the eventual problems in 1.22B05+ when they attempted to fix it.

Maybe they reverted the first they put in before?

I am still experimenting with DNS Relay but I think my particular situation on 1.33 may be related to Zone Alarm.

When the hesitation started up again, I disabled (and eventually deleted) Zone Alarm and the hesitation did not return.  I just re-enabled DNS Relay again without Zone Alarm installed to see what happens.

1.32 was definitely hosed for me; I had tried removing Zone Alarm earlier and that did not help.  If you have Zone Alarm and 1.33; try disabling it if you have hung web sites and respond if that fixes it.

[kthaddock]

Just have to answere, is ZA cracked ? well you don't need ta answere.
I have used cracked ZA and then it becom strange behavior.
I think they update some stange code and then ZA is strange.

kthaddock

[Krusher]

Nope, it's the same free ZA that I've been using for the last few years.  You don't really need a firewall on your internal network because the router is a firewall, but it's nice to know what programs are sending data and that's why I used ZA in the past.  I keep the Windows firewall up now just because it will help slow viruses in case a guest shows up here with an unknown virus.