Print

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

[netdevil]

HI everybody,
I am having major difficulties with my DIR-655 router. I am using a VoIP hardware device (Fritz!Box FON) which for some strange reason will only work with firmware 1.11 (I tried both 1.20 and 1.21, both failed to work). With the 1.11 firmware, however, wireless networking only works occasionally - either the WLAN card (with a Ralink chipset) cannot establish any network connection, or do so only after at least 5 attempts, sometimes even more than 10. I have tried multiple operating systems, all have the same problem. With the newer firmwares the WLAN works flawlessly - but I cannot get the VoIP to work. I have enabled port forwarding (3478,3479,5060-5070,10000-30000,21,53,69,123) and have set UDP endpoint filtering to "Endpoint Independent" - this setting works under fw 1.11 but not under anything newer.
I have googled for this to no avail. Do you have any suggestion what I can do? I already contacted my VoIP provider and it is certainly a local router problem.
 
Thanks!

Edit: Also tried DMZ, turned SIP ALG off ... nothing.

Edit 2: OK - this is too weird: went back to 1.11 and WLAN seems to work for now... any suggestions as to what could be the problem with 1.21 though?

[D-Linkuent]

I believe starting with version 1.20, Port Forwarding basically does not work.  Actually, it's worse than that.  It prevents the creation of port mappings that would normally be created on-demand, when LAN nodes initiate communication with the internet, if these mappings are listed under Port Forwarding.

Use 1.11 or use Virtual Server to pass through NAT.

[KevTech]

I would have to agree that firmware past 1.11 has issues.

[netdevil]

I tried it again, this time used the 1.21B08 firmware and following the suggestion for a workaround in another thread disabled DNS Relay. This made one of my two voip providers work - though my VoIP device reported a connection to both servers, the calls were not routed through both inbound and outbound... so back to 1.11 it is once more...

The WLAN issue is not completely resolved either - I occasionally get disconnects.  I do not think it is a problem of the operating system (Ubuntu), but I think it's router related. I'll post a log next time it happens.

This is really a shame... I am getting closer to buying a new router... Is there any new firmware coming that might solve some of these issues? There seem to be sooooo many users with problems.

[netdevil]

Status update:
I tried again after our line constantly appeared to be busy to callers... I tried the NEWEST 1.21 firmware (Nov. 13 from the DLINK ftp server), I changed port forwarding to Virtual Server... nothing. I tried with restoring the factory defaults and then setting up the rules again, then turning off the power to make sure it really rebooted, nothing. The calls are not going through. I also had to turn off the DNS relay as I was experiencing like 5-10sec wait until the connection was established... switched over to OpenDNS and to my providers DNS site and it worked.

PLEASE, does anybody have any idea what else I could do or try? I am about to try to return this damn router... 

My setup is very simple: I have one WLAN device, one networked computer, and one VoIP Device (FritzBox)... it should not be such a difficult thing to get the port forwarding to function?? The only firmware it seems to work with (not perfectly, but at least mostly functional) is 1.11

@Moderators: Can't you find out what has changed since regarding DNS relay, port forwarding and ask them to fix it??

[funchords]

Netdevil, is anything NOT working if DNS Relay is turned off?

[netdevil]

Hi funchords,

if DNS Relay is turned off the port forwarding is still not working... so I am not sure whether that is really the cause for all the trouble as you're suggesting... though I am pretty sure it has something to do with it.

One scenario of what happens is this: there seems to be a delay up to 30 sec until the packets actually get to the VoIP device, so the caller gets no answer or a busy signal, while my phone starts to ring 30sec later and nobody's on the line.

Another is that there is no reaction whatsoever...

I am basically still stuck with 1.11 but would call the performance sub-optimal at best. At least its useable.

I can try to post a log from 1.21, but that means having no telephone for at least 1 h - and from what I can tell it is not really all that informative...

[funchords]

I think I know why you're getting the 30 second delay.  If 1.11 is working, then don't mess with it. 

But if you're already messing with 1.21 someday, turn off DNS relay and ALSO restart your VOIP device and other computers (make sure clients get good DNS settings that point to actual DNS servers and not the router). 

If this helps its because the DNS Relay in the DIR-655 is failing with certain lookups (NXDOMAIN at least).  DNS lookups are a blocking action for some software and network devices, either programmatically (the program waits for a response before executing the next instruction) or naturally (you can't go to www.google.com until it is translated into an IP address by DNS) -- as a result, while an outstanding DNS query exists, these programs have to wait for the response.  This might also be a blocking action in the DIR-655 itself, if it is programmed to complete all queries in serial order then it would have to wait for a delayed response before it could process the next one.  As a result, many interactive uses (such as web surfing, game playing, file transferring) that is waiting on a DNS query to continue will tend to stall. 

[netdevil]

Hi funchords, hello everybody else,

I did try the DNS relay and restart thing, for some reason it did not work. I also checked the log again today (back at 1.11, HW A3) and found that the SIP ALG rejects a whole bunch of packages - could that be a reason why the phone line appears to be busy if somebody is trying to call us?

here is some part of the log (I took out the parts concerning the other network devices) - what I find strange is that sometimes these rejections appear to be repeated 10 times or more:

Code: [Select]

[INFO] Tue Dec 02 10:55:37 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:55:05 2008 Above message repeated 10 times
[INFO] Tue Dec 02 10:55:05 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:54:57 2008 Above message repeated 2 times
[INFO] Tue Dec 02 10:54:53 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:54:49 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:54:45 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:54:41 2008 Above message repeated 1 times
[INFO] Tue Dec 02 10:54:37 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:54:33 2008 Above message repeated 3 times
[INFO] Tue Dec 02 10:45:48 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:45:16 2008 Above message repeated 10 times
[INFO] Tue Dec 02 10:27:32 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:27:00 2008 Above message repeated 10 times
[INFO] Tue Dec 02 10:27:00 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:26:35 2008 Above message repeated 6 times
[INFO] Tue Dec 02 10:26:31 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:26:28 2008 Above message repeated 3 times
[INFO] Tue Dec 02 10:18:15 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:17:51 2008 Above message repeated 6 times
[INFO] Tue Dec 02 10:17:47 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:17:44 2008 Above message repeated 2 times
[INFO] Tue Dec 02 10:17:43 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 10:00:17 2008 Above message repeated 2 times
[INFO] Tue Dec 02 09:59:26 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:58:55 2008 Above message repeated 10 times
[INFO] Tue Dec 02 09:58:54 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:58:23 2008 Above message repeated 10 times
[INFO] Tue Dec 02 09:50:42 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:50:11 2008 Above message repeated 10 times
[INFO] Tue Dec 02 09:31:21 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:31:17 2008 Above message repeated 1 times
[INFO] Tue Dec 02 09:31:13 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:30:49 2008 Above message repeated 8 times
[INFO] Tue Dec 02 09:30:49 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:30:17 2008 Above message repeated 10 times
[INFO] Tue Dec 02 09:23:10 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:22:38 2008 Above message repeated 10 times
[INFO] Tue Dec 02 09:04:10 2008 Above message repeated 2 times
[INFO] Tue Dec 02 09:03:15 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:03:07 2008 Above message repeated 2 times
[INFO] Tue Dec 02 09:03:03 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:02:59 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:02:55 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:02:44 2008 Above message repeated 5 times
[INFO] Tue Dec 02 09:02:43 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 09:02:12 2008 Above message repeated 10 times
[INFO] Tue Dec 02 08:55:37 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:55:09 2008 Above message repeated 7 times
[INFO] Tue Dec 02 08:55:07 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:35:09 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:34:39 2008 Above message repeated 8 times
[INFO] Tue Dec 02 08:34:38 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:34:38 2008 Above message repeated 1 times
[INFO] Tue Dec 02 08:34:37 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:34:06 2008 Above message repeated 10 times
[INFO] Tue Dec 02 08:28:04 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:27:32 2008 Above message repeated 10 times
[INFO] Tue Dec 02 08:07:02 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:06:30 2008 Above message repeated 10 times
[INFO] Tue Dec 02 08:06:30 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 08:05:58 2008 Above message repeated 10 times
[INFO] Tue Dec 02 08:00:30 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:59:58 2008 Above message repeated 10 times
[INFO] Tue Dec 02 07:38:56 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:38:24 2008 Above message repeated 10 times
[INFO] Tue Dec 02 07:38:24 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:38:11 2008 Above message repeated 3 times
[INFO] Tue Dec 02 07:38:07 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:38:03 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:37:52 2008 Above message repeated 5 times
[INFO] Tue Dec 02 07:32:56 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:32:25 2008 Above message repeated 10 times
[INFO] Tue Dec 02 07:10:49 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:10:45 2008 Above message repeated 1 times
[INFO] Tue Dec 02 07:10:41 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:10:37 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:10:18 2008 Above message repeated 7 times
[INFO] Tue Dec 02 07:10:17 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:09:46 2008 Above message repeated 10 times
[INFO] Tue Dec 02 07:09:05 2008 Above message repeated 1 times
[INFO] Tue Dec 02 07:05:22 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 07:04:51 2008 Above message repeated 10 times
[INFO] Tue Dec 02 06:42:43 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 06:42:11 2008 Above message repeated 10 times
[INFO] Tue Dec 02 06:42:11 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 06:42:07 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 06:41:39 2008 Above message repeated 9 times
[INFO] Tue Dec 02 06:37:49 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 06:37:17 2008 Above message repeated 10 times
[INFO] Tue Dec 02 06:14:36 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 06:14:05 2008 Above message repeated 10 times
[INFO] Tue Dec 02 06:14:04 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 06:13:33 2008 Above message repeated 10 times
[INFO] Tue Dec 02 06:10:15 2008 SIP ALG rejected packet from 192.168.0.102:5060 to XXX.XXX.XXX.XXX:5060
[INFO] Tue Dec 02 06:09:43 2008 Above message repeated 10 times

The rejections concern both my VoIP providers. Any idea what causes them? It seems to be an awful lot...

I sure would appreciate any help!

[EddieZ]

Do you have some PC or device active in DMZ?

[netdevil]

No...

[StephanFr]

I just posted a new message on this topic - I should have checked deeper into the messages before adding a new one...

For what it is worth netdevil, I see the exact same problem.  I run an Asterisk server for my house and use a SIP trunk for connection to the PSTN.  Using anything past 1.11 appears to be hopeless.  I tried all the same configuration tricks, even putting the server into the DMZ (which I did only for testing purposes) to no avail.  It appears as if the SIP INVITE hits my server quickly, but my server has problems getting the OK back.

I'm not real happy with 'finding a version of the firmware that works for you and stick with it', Versions 1.20 and 1.21 seem just plain broken.  I'd like the Guest Account and the SharePort capabilities.....

[funchords]

I did try the DNS relay and restart thing, for some reason it did not work. I also checked the log again today (back at 1.11, HW A3) and found that the SIP ALG rejects a whole bunch of packages - could that be a reason why the phone line appears to be busy if somebody is trying to call us?

My memory is getting foggy on this issue, but memory is that something works inversely here --

It's either disabling the SIP ALG that solves it, or if that doesn't help, then re-enable the SIP ALG but disable the SPI function of the firewall. 

[netdevil]

@StephanFr - I am inclined to say "FINALLY SOMEBODY WHO TELLS ME I AM NOT CRAZY" - while at the same time it is pretty sad that these issues are out in the open and nobody seems to be doing anything about them.

@funchords - If I remember correctly I tried to turn of the SIP ALG, which did not do anything. I"ll give the other one a shot.

@ALL: I second StephanFr's "I'm not real happy with 'finding a version of the firmware that works for you and stick with it', Versions 1.20 and 1.21 seem just plain broken.  I'd like the Guest Account and the SharePort capabilities....."!!!

[EddieZ]

@ALL: I second StephanFr's "I'm not real happy with 'finding a version of the firmware that works for you and stick with it', Versions 1.20 and 1.21 seem just plain broken.  I'd like the Guest Account and the SharePort capabilities....."!!!

If they are broken, the issue should be a generic one. And VOIP (sip) and WLAN work fine on version 1.21 with my Acer laptop and desktop....how could that be?