Print

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

[StephanFr]

I purchased by DIR 655 in the first month it was available and have had no problems with it whatsoever, until recently.  I run an Asterisk PBX in my house and after upgrading from Firmware 1.11 to 1.21 I started getting messages from my SIP service provider that my Asterisk server was returning Channel Unavilable messages when it tried to complete a call.  This appears to be the result of a long delay occuring between the initial INVITE from my service provider to my server and the OK response from my server to my service provider.  This started literally the day after the upgrade and I had never seen the issue before (in 3 years).

Additionally, I noticed that even on my internal network if I used Putty to connect to one of my Linux boxes, the login name prompt appeared quickly, but the prompt for the password was delayed by 15 to 20 seconds.  Again, the only thing that changed was the DIR 655 Firmware upgrade.

Overall, everything on my network seemed a bit sluggish with the 1.21 Firmware.  I know that is a diffuse statement, but I am a software engineer and I rely heavily on my home network.  My wife has also noticed a sluggishness problem browsing the internet with her laptop as well.

It took me a while to really settle on the Firmware upgrade being the issue and I confirmed it tonight.  I downgraded to 1.11 and with the base settings, the password prompt from my Linux box appears immediately.  With both 1.20 and 1.21 the password prompt is delayed.  I checked twice, again using the out-of-the-box settings that are applied with the firmware.

I've downgraded to 1.11 and the PBX seems to be 1000% happier as well.

Does this sound familiar to anyone?  I'd like to upgrade to a version of the Firmware that has the Guest Account, it is a wonderful feature, but I'm not moving from 1.11 until I have some confidence that the problem I've been seeing has been solved.

BTW - I tried all the normal configuration changes against the out-of-the-box settings:

SPI On and Off
ALG all On and Off
etc.

None made a difference.

Thanks,

Stephan

[funchords]

Disable DNS Relay, restart the router.

If the Asterisk machine doesn't change DHCP servers from the router to your ISP's server, then have the Asterisk release/renew DHCP (or reboot it).

If this helps, it's a DNS Relay bug that freezes for 15 seconds on each failed DNS lookup request (these usually take less an a second). 

[StephanFr]

I gave that a shot and it resolved the delay between the username and password prompts when creating a SSH session to my Linux box.  Frankly, I'm not terribly reassured by having that problem go away, as I don't understand why a DNS resolution issue would cause a delay between the username and password prompts to establish a telnet session when I am addressing the server directly with an IP address.  Ought there not be any name resolution at that point in the process?

In looking over a number of other posts on this board, clearly there is a problem with Port Forwarding, Virtual Servers and/or the DMZ in V1.20 forward.  SIP depends on opening both signalling and media channels and the media channels are typically chosen dynamically from a port range.  I need reliable port forwarding and I just don't trust 1.20 forward for this critical function.

Given that my phone service passes through this router, I'm disinclined to spend another couple days with missed or dropped calls to determine something else is wrong.  I've downgraded to V1.11.

What would be valuable is some indication from DLink as to when they intend to fix these issues.

[funchords]

I gave that a shot and it resolved the delay between the username and password prompts when creating a SSH session to my Linux box.  Frankly, I'm not terribly reassured by having that problem go away, as I don't understand why a DNS resolution issue would cause a delay between the username and password prompts to establish a telnet session when I am addressing the server directly with an IP address.  Ought there not be any name resolution at that point in the process?

My guess is that it's doing a reverse DNS lookup, maybe part of the /etc/hosts.allow or /etc/hosts.deny policy ... or some kind of auth process where users are associated with hosts (or ssh's "known hosts" thing) -- I'm definitely not sure and you could scope it out with Wireshark. 

What would be valuable is some indication from DLink as to when they intend to fix these issues.

Me too.

[bjrosen]

I'm seeing the same problem, ssh is virtually unusable with the 1.20 and 1.21 versions of the firmware, it takes about a minute to connect to an ssh port. I've tried both port forwarding and virtual servers, I get the same result. I've also tried various different firewall settings, it doesn't make a difference. Downgrading to 1.11 fixes the problem. I'll give the DNS relay thing a try.

[bjrosen]

Disabling DNS Relay fixes the problem so the bug is in the DNS relay code.

[funchords]

Great!  Thanks!  We're building quite a case to get DNS Relay fixed.