Unable to route outbound since DSM4 Upgrade

[JohnnieE]

Hi,

Since upgrading my DS211j to v4.0 It is unable to resolve DNS it seems :S

I usually have it set to my router IP which is also the default gateway, I have also tried setting it to the ISP's DNS server too.

I am unable to update the time automatically, it won't detect my external IP, or do any other outbound network actions such as update system packages.

I can however access the NAS over the WAN and LAN.

Any pointers appreciated

[dotslasher]

I have the same issue on my DS411

things I've tested:

disable firewall, set DHCP, back to Static IP address. Reboot NAS.

nothing works.

[Tyranny]

After updating from DSM3.2 to DSM4 (DSM_DS211_2197) my DS211 has no outbound internet access. Nothing else in my network has changed. The DSM4 network settings are identical to those I set in DSM3.2. I've tried changing the settings from that of my router to those of my ISP with no improvement.

My DS211 currently has no access to any of the NTP servers (including the one I use on my PC without any issues), no access to Package Center downloads (on the available tab). DSM Update checking fails too.

LAN access seems to be working fine.

[Helena]

I have a serious problem after upgrading to 4.0. Internet connection is no longer possible; this has been confirmed by other users. While the LAN services remain available this of course is not acceptable. I would like to file a bug report if I knew how.

[HarryPotter]

I have no problem with internet connections on my DS712+. May be you should check the firewall settings in DSM.

Only the package center seems not to be able to connect anymore at the moment, but it was working this morning, I got all updates from there.

[dotslasher]

I have no problem with internet connections on my DS712+. May be you should check the firewall settings in DSM.

Only the package center seems not to be able to connect anymore at the moment, but it was working this morning, I got all updates from there.

the firewall seems to be the issue. If I completely disable it I am able to go outside my LAN again.

[diamore]

I can confirm this exact same bug. DS is unable to determine external IP. If I go into ezCloud it attempts to find the external IP and the CPU usage shoots to 100% while it does so. Only after it fails to find one does CPU usage drop. I've tried setting my DS to DHCP and back to manual IP to no avail. I hope this is fixed soon, pretty huge bug.

[HarryPotter]

I am 100% sure IT IS NOT a bug. Also the external IP detection workes, even if sometimes it takes longer or may be fails. It must be the Synology server in Taiwan or wherever it is located that has problems , probably too many users are trying to get all this new stuff at this moment.

[diamore]

I am 100% sure IT IS NOT a bug. Also the external IP detection workes, even if sometimes it takes longer or may be fails. It must be the Synology server in Taiwan or wherever it is located that has problems , probably too many users are trying to get all this new stuff at this moment.

Okay, if it's not a bug is there a way to use a DDNS service to grab my external IP?

[iket]

I concur with HarryPotter. I get a listing sometimes of available packages and then it fails. I believe it may be a server overload problem.

[JohnnieE]

I have no problem with internet connections on my DS712+. May be you should check the firewall settings in DSM.

Only the package center seems not to be able to connect anymore at the moment, but it was working this morning, I got all updates from there.

the firewall seems to be the issue. If I completely disable it I am able to go outside my LAN again.

You are right, its definitely firewall. If I set the 'if no rules are matched' radio button to allow the network graph on the system monitor jumps up.

I have tried recreating my rules and got the same problem, the only way I've found I can get it working so far is to set my LAN subnet to allow all applications.

Perhaps something has changed since DSM4 in the way it processes the firewall rules, or maybe my rules were set incorrectly in the first place?

Code: Select all

For Wan traffic:

Applications: Management UI etc 5000
Source IP: All
Action: Allow

For LAN:

Applications: Management UI 5000, iSCSI 3260, Windows file server 137-139 145, netbackup
Source IP: Subnet 192.168.0.0 255.255.255.0
Action: Allow

If no rules are matched: Deny


[diamore]

Yep, confirmed. Disabling the firewall or adding LAN subnet to "allow all" allows DS to grab external IP. I'm thinking I shouldn't have to do this though?

EDIT: actually enabling 'all' for applications for my lan subnet doesn't work. I spoke prematurely, though entirely disabling the firewall still works immediately after doing so.

[jlshakeme]

I can also confirm that the issue is with the firewall rules. I am emailing back and forth with one of the techs to see if there are any port rules we can change so we don't have to have our firewall set to allow all requests.

I did have some problems earlier today with going into the Package Manager even after disabling the firewall. If anyone has that same problem, I did a Soft Reset on the DS and that helped.


DS411+ with DSM 4.0

[kumpa]

I can confirm the same behaviour. If I allow all hosts in my subnet behind NAS, then I can ping or nslookup a server, but wget, for example, does not connect to a remote HTTP server. If I disable the firewall, everything works as expected. There must have changed something in the firewall in DSM 4.0.

[thunderbird]

I am 100% sure it's a bug, since I did a complete reinstall of the DSM (reset device and install DSM via tool).
When a firewall rule scheme is used that lists a few allow rules and then denies all the rest outbound traffic is somehow dropped. The only workaround is to have a rule at the end that denies unused services and services used only in the LAN (create a rule, check all services and then select deny. However do not set ports to ALL, really select all services listed).