Print

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

[Lycan]

I'm able to use it no problem, however I him our PM team about the possiblity that there is still an issue with the feature, they said they've been following the thread and are following a few possibilities.


I'm not really sure what that means, but I'll ask for clarification today.

[arod]

Try this
http://forums.dlink.com/index.php?topic=5841.0

[jason1722x]

Any comments on 1.32beta working or not on DNS and freezing issuse?

[EddieZ]

Try this
http://forums.dlink.com/index.php?topic=5841.0

It's BETA code ! 

[jason1722x]

LOL..I was trying to responed but router locked up as I was using bit torrent earlier. 1.31na

45 Log Entries:   Priority Time Message
[INFO] Thu Jun 04 08:57:58 2009 Blocked incoming UDP packet from 89.134.21.233:49000 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:57 2009 Blocked incoming UDP packet from 88.171.94.154:42952 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 115.64.141.79:10574 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 70.181.148.160:53266 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 76.106.46.77:39112 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:54 2009 Blocked incoming UDP packet from 121.6.206.140:10016 to xx.xx.xx.xx:65003

I've been watching the response on the 1.32beta topic and I do understand it's beta.

It's seems most responding was directed towards shareport issuse.

[lotacus]

LOL..I was trying to responed but router locked up as I was using bit torrent earlier. 1.31na

45 Log Entries:   Priority Time Message
[INFO] Thu Jun 04 08:57:58 2009 Blocked incoming UDP packet from 89.134.21.233:49000 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:57 2009 Blocked incoming UDP packet from 88.171.94.154:42952 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 115.64.141.79:10574 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 70.181.148.160:53266 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 76.106.46.77:39112 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:54 2009 Blocked incoming UDP packet from 121.6.206.140:10016 to xx.xx.xx.xx:65003

I've been watching the response on the 1.32beta topic and I do understand it's beta.

It's seems most responding was directed towards shareport issuse.

[/size]

When I'm torrenting, the router will show similar logs, however utorrent connections work fine. The router in my case is doing it's job because it detects something funny with the tcp headers so it blocks the connection.

As well for lycans suggestion a few days ago about killing short-gi, I'll be able to tell late tonight or tomorrow since it will be the four day mark, after a couple resets from changing some settings.

[jason1722x]

When I'm torrenting, the router will show similar logs, however utorrent connections work fine. The router in my case is doing it's job because it detects something funny with the tcp headers so it blocks the connection.

As well for lycans suggestion a few days ago about killing short-gi, I'll be able to tell late tonight or tomorrow since it will be the four day mark, after a couple resets from changing some settings.

I'm @ a loss as to how short-gi would affect a hard wired  connection as my understand it's a wireless setting.

[EddieZ]

It doesn't, but probably some of these issues may very well be non-router related 

[lotacus]

Jason, this is where everything got confusing.  Your post that I replied to, was posted in the wrong thread.

However, my reply had a reply to two different posts, to kill 2 birds with one stone. So i replied to your post my experience, as well, to lycans asking me to turn off short-gi. Again, its a work-around but not a fix and if work-arounds work, then dlink doesn't have to fix it.

[jason1722x]

Jason, this is where everything got confusing.  Your post that I replied to, was posted in the wrong thread.

However, my reply had a reply to two different posts, to kill 2 birds with one stone. So i replied to your post my experience, as well, to lycans asking me to turn off short-gi. Again, its a work-around but not a fix and if work-arounds work, then dlink doesn't have to fix it.

LOL..no problem. I tried it anyway, no affect that I could tell.

[lotacus]

@ Lycan. Disabling the short-gi had no effect. When I came home from work today/night, wireless was frozen solid. Still havn't figured out what it could be. Strange thing is, that on the wired computer, msn messenger was still logged in and able to be used but browsing the web, or trying to get to the web gui, failed. The router just seems to be blocking all web access. I dont know if it's blocking ports or not.

I'm still stumped as what could be causing it. Now, I can tell you that I've previously created access rules allowing only ports 80, 443, 53 and blocking all other access, but for the longest time I had evertything disabled. Trying to think out of the box here, when this freezing router happens, it's almost as if it's doing the reverse, it's enabling the access control, but reversing the allowed ports to blocked ports. I only say that because Windows Live Messenger was the only thing allowed to remain connected on the wired pc, but again, for some reason, the router would deny any wireless associations.

[lizzi555]

Did you already try what happens if you disable all access rules / schedules - just with all needed settings as encryption.
If it doesn't lock then, enable one rule after the other and try again.

[anonposter]

Aside from wpa2 encryption and mac address filters, I have every single function disabled.  I get the same "freezing" issue that others get along with some spontaneous reboots from time to time.  As stated earlier in the thread through logs, the freezes always seem to be preceeded by various errors but the most common include IP Protcol 17, IP Protocol 6, and DNS Relay error.  I'm not sure what those errors actually mean.

However I should also state that I have not tried out 132 beta.  I need this router to work and prefer only to use final versions of firmware with the Dlink seal of approval.

[mirceani]

My router freezes too, every couple of days.

Nothing changed from the days when it used to work fine, except the firmware - I made the mistake to update to the latest available.

I am puzzled by the inefficiency of Dlink support, considering that so many people have this problem after changing the firmware.

How could you possible release bad products without testing?

[GullyFoyle]

Some Linksys routers had a similar issue. The NAT table would hold dead links for something like five hours. DDWRT allowed you to change the release time. Setting it for 90 seconds fixed the freeze problem.
http://en.wikipedia.org/wiki/Linksys_WRT54G_series

Some performance issues have been encountered with the Linksys firmware which may cause sluggish or total network failure. This is usually caused by a large number of connections clogging the router, in other words NAT table overflow. Symptoms of NAT table overflow include inability to initiate new network connections while existing connections remain active. This is due to the small size of the NAT lookup table in default Linksys firmware coupled with a long table entry timeout. Installing a third-party firmware such as DD-WRT allows the user to change these values to prevent or delay NAT table overflow occurring. Installing a third party firmware and increasing the maximum ports setting to allow more connections is the usual solution (in DD-WRT found under Administration->Management->Maximum Ports).

http://www.ben.geek.nz/linksys-wrt54gl-router/

The first thing I changed was the NAT table settings, increasing the table size from the default 512 to 4096, and dropping the NAT timeout from 3600 seconds to 90. In English this basically tells the router “store heaps of connection details, but discard them pretty sharpish if you don’t need them anymore”, which is exactly the behaviour we want with Bittorrent and other P2P apps.

A quick GOOGLE for DDWRT and NAT tables brings up things like this
http://www.overclock.net/networking-security/370371-router-nat-table.html

All the gigabit routers I have have very small NAT tables - even with under 100 connections the table fills up (so no more connections can be made)

http://www.dslreports.com/forum/r20073419-Small-NAT-table-a-thing-of-the-past

A NAT table is tiny in comparison to the amount of memory used for IP buffers, especially when jumbo frames are supported.
The AT has 29MB of memory, less than 1/2 of which is used. That is far more memory than is available in typical consumer routers such as LINKSYS.
Each NAT table entry requires about 16 bytes for IPV4 addresses. The NAT table in VZ's firmware allows 128 entries. That is 2KB of memory.
If 3rd party firmware where to increase the NAT table from 128 to 2000 entries, that would only be 32KB of memory.

http://www.broadbandreports.com/forum/r22361134-Will-Tomato-DDWRT-really-increase-speed-for-15-Mbps-line

Number of open connections are whether the router's CPU gets bogged down or a full NAT table. Both will affect the router's performance but neither will make data transfers any faster.

The last quote suggests a slow CPU may be causing the freeze.
Disabling DHT may help.
The problem is files with large seeds/peers. Those seem to cause a freeze for me.