Print

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

[D-Linkuent]

What is happenning with the new firewall behaviour in 1.20 ?

My DIR-655 is now blocking my VoIP box (a Linksys PAP2T), not letting it get on the Internet.  The PAP's logs show both STUN and SIP messages being sent, but no responses received.  The router's logs don't mention anything that would help explain this.  I have the SIP ALG (application-layer gateway) turned off, but the firewall is behaving as if the SIP ALG were running!  Why else could it be blocking STUN?

Firmware 1.11 was always solid in my configuration: SIP ALG off, UDP ports manually forwarded for SIP and RTP.  But with 1.20, I can only register with the external SIP proxy if I disable that port mapping!  What sense does that make, unless a SIP ALG is running?

Can D-Link engineers kindly look into whether the SIP ALG really gets disabled when I untick its box in 1.20 !  If it is not, then file that as a defect.  This is of critical importance to users like me, who have only VoIP and no landline phone.  The firewall has no business blocking valid outgoing requests, especially in a critical application like telephony, and especially without even logging such actions.  D-Link, please don't take away my control over the firewall; I can never accept something like this.

By the way, many others are reporting this issue, including one person on this forum.

[Matteo]

  why would you get rid of your land line???    hahahaha....  wow

[D-Linkuent]

why would you get rid of your land line???

Because that's $300/year for a service I essentially am already getting (at $100/year).

The hard part of VoIP today is learning to deploy and configure it yourself.  The quality and reliability can be very good, while features and price are unbeatable.

[Matteo]

  I concede it is an expense, do you have a cable modem?  ours has the phone jack (and battery backup)right on it that connects to the demarcation point in our house and gives us phone service (even use the same phones !! ( i think i heard that in a comercial somewhere))...

  so you are using a vonage type thing ?? i am not really savy on the VOIP stuff....  its like IP Telephony?....   

[D-Linkuent]

No, Matteo; I have dry-loop DSL, not cable.  And yes, you can connect the VoIP phone port to your internal phone wiring (but must first disconnect internal from external at the demarc).

Providers like Vonage give you a locked VoIP box.  They configure it remotely, but you are stuck with that provider, and you pay a premium for it.  But then there are bring-your-own-device providers, for people willing to spend $45 on an unlocked box, and learn to configure it.  There is more competition in this category of providers, and, as a result, better offerings.

Of course, there are other benefits to putting your telephone on the Internet.  Like free calls to any other telephone on the Internet (unlike Skype, this works even without a computer).

[Matteo]

hrmmm...  seems a little confusing....  so you pay that ontop of the dsl charge? sorta like a software PBX?  wow... i really need to get more up to speed on this, i didnt think they had BYOH providers out there...

[D-Linkuent]

so you pay that ontop of the dsl charge?

Yes, though not to the same company.

sorta like a software PBX?

You could say that.  The provider basically bridges you from internet into public telephone network.

Wow, this thread has sure drifted off topic...  I wonder if the moderators will ever care to comment on the original post.

[Matteo]

probably not, sorry...        who is your provider?  (i am in Canada and i have not seen anything advertised like that here)

[Leolo]

Hi,

Your problem seems related to mine.

I cannot connect to the Kademlia network, used by eMule, with versions 1.20 and later. However, versions 1.11 and earlier worked very well.

I've noticed that eMule shows a lot of UDP packets sent, but none received. Seems that UDP Port Forwarding is seriously broken in 1.20 and later firmwares.

Let's hope D-Link fixes this soon!

[Lycan]

LOGS LOGS LOGS, please?

[Leolo]

In my case, the router doesn't show anything interesting in the logs. Even though I have all the log options checked to get the maximum possible info.

I clear the logs just before I open eMule. Then I open eMule, click to connect, and leave it a few minutes trying to connect.

I click Refresh, but nothing interesting comes up:

Priority   Time   Message
[INFO]   Wed Sep 24 21:35:06 2008   Log viewed by IP address 192.168.0.5
[INFO]   Wed Sep 24 21:33:08 2008   Above message repeated 29 times
[INFO]   Wed Sep 24 21:32:58 2008   Log viewed by IP address 192.168.0.5
[INFO]   Wed Sep 24 21:32:56 2008   Above message repeated 2 times
[INFO]   Wed Sep 24 21:32:55 2008   Log cleared by IP address 192.168.0.5

The router is silently discarding incoming UDP packets.

This is the log I obtain when I enable UPnP in eMule (I'm forced to use UPnP against my will, because it's the only configuration that works right now with 1.21 firmware)

Priority   Time   Message
[INFO]   Wed Sep 24 21:40:30 2008   Log viewed by IP address 192.168.0.5
[INFO]   Wed Sep 24 21:40:10 2008   Above message repeated 6 times
[INFO]   Wed Sep 24 21:39:54 2008   UPnP added entry 255.255.255.255 <-> 87.218.127.200:47551 <-> 192.168.0.5:47551 UDP timeout:-1 'eMule_UDP'
[INFO]   Wed Sep 24 21:39:54 2008   UPnP added entry 255.255.255.255 <-> 87.218.127.200:47550 <-> 192.168.0.5:47550 TCP timeout:-1 'eMule_TCP'
[INFO]   Wed Sep 24 21:39:13 2008   Log viewed by IP address 192.168.0.5
[INFO]   Wed Sep 24 21:39:12 2008   Log cleared by IP address 192.168.0.5

I've downgraded to 1.11 just to be totally sure, and I can confirm that 1.11 forwarded UDP ports perfectly with UPnP disabled.

The bug has been introduced in version 1.20.

Regards.

[Leolo]

D-Linkuent,

Could you please retest your configuration by opening the ports with the "Virtual Servers" menu instead of "Port Forwarding" ?

I've just discovered that "Virtual Server" does open the UDP ports correctly!!

Regards.

[egcarter]

The 1.20 firmware on my A2 version DIR-655 breaks my AT&T Callvantage VOIP using my D-Link DVG-1120M telephone adapter.   Even after performing a reset on the TA, it just sits there with the red light blinking.    Rolling back to 1.11 fixed it right away.

 

[optionstr8dr]

My ATT Callvantage D-Link DVG-1120M stop connecting when i upgraded the FW to 1.20 also. Setting the 'UDP Endpoint Filtering' and 'TCP Endpoint Filtering' to 'Endpoint Independent' solved this. Go to 'Advanced' tab, 'Firewall Settings' to configure. I'm running 1.21 FW without issues.

[Kittyburgers]

My ATT Callvantage D-Link DVG-1120M stop connecting when i upgraded the FW to 1.20 also. Setting the 'UDP Endpoint Filtering' and 'TCP Endpoint Filtering' to 'Endpoint Independent' solved this. Go to 'Advanced' tab, 'Firewall Settings' to configure. I'm running 1.21 FW without issues.

I have a DVG-1120 with Primus Canada - I think that's the same unit - in any case, the MGCP one.
Thanks for the tip.  I'm still using 1.11, but if anything goes wrong, at least I'll know where to look first.