NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dbrewood
Sep 05, 2021Guide
Orbi RBK53S having blocking outgoing connections from Synology NAS
Guys I need some help, I've recently been suffering with a problem whereby my Synology NAS (DS918+) is unable to access the internet (to update DDNS data, etc)
This has worked fine for 9 months but since the last Orbi firmware update (I think) this has been problematical. To debug the issue all network cables have been replaced and the NAS connected to various ports. If I switch back to using the British Telecom Home Hub 5 as a modem / router everything works.
Tests that synology have asked me to run give results as follows:
root@mynas:~# ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. 64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.357 ms 64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.327 ms 64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.423 ms 64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=0.323 ms 64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=0.233 ms ^C --- 192.168.1.254 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 0.233/0.332/0.423/0.064 ms root@mynas:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.1.254 icmp_seq=1 Destination Port Unreachable From 192.168.1.254 icmp_seq=2 Destination Port Unreachable From 192.168.1.254 icmp_seq=3 Destination Port Unreachable From 192.168.1.254 icmp_seq=4 Destination Port Unreachable From 192.168.1.254 icmp_seq=5 Destination Port Unreachable From 192.168.1.254 icmp_seq=6 Destination Port Unreachable From 192.168.1.254 icmp_seq=7 Destination Port Unreachable ^C --- 8.8.8.8 ping statistics --- 7 packets transmitted, 0 received, +7 errors, 100% packet loss, time 8ms root@mynas:~# ping www.google.com PING www.google.com (142.250.187.196) 56(84) bytes of data. From 192.168.1.254 (192.168.1.254) icmp_seq=1 Destination Port Unreachable From 192.168.1.254 (192.168.1.254) icmp_seq=2 Destination Port Unreachable From 192.168.1.254 (192.168.1.254) icmp_seq=3 Destination Port Unreachable From 192.168.1.254 (192.168.1.254) icmp_seq=4 Destination Port Unreachable From 192.168.1.254 (192.168.1.254) icmp_seq=5 Destination Port Unreachable ^C --- www.google.com ping statistics --- 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 7ms root@mynas:~# nslookup www.google.com Server: 81.139.57.100 Address: 81.139.57.100#53 Non-authoritative answer: Name: www.google.com Address: 142.250.200.36 Name: www.google.com Address: 2a00:1450:4009:81f::2004 root@mynas:~# nslookup www.google.com 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: www.google.com Address: 142.250.200.36 Name: www.google.com Address: 2a00:1450:4009:820::2004 root@mynas:~# traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 0.352 ms 0.392 ms 0.403 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * root@mynas:~#
As you can see outgoing connections to Google (used as a test) fail at the Orbi (192.168.1.254)
This is causing major concerns as I host a forum on the NAS and the issue takes it offline.
Any ideas how to fix it folks? Any assistance would be greatly appreciated. If any more information is needed please advise.
Thanks in advance.
13 Replies
Sort By
- Hansdampf74Aspirant
Did you find a solution for this problem? This bothers me for more than two months now.
- dbrewoodGuide
I just posted this on Synoforum:
I had a call from them yesterday, they asked how things were for me with the issue. I advised that I've not had the problem for over 3 weeks now and as far as I myself was concerned the issue looked to be fixed. I did state that it was still an issue for other DSM7 users.
They advised they we're still waiting for the higher tier developers to report back (IMHO after liaising with the Bitdefender Armor team - my own opinion there). I did say I wanted the ticket to remain open until they had the information I could feedback to Synology so that the problem could properly be closed out from both sides.
At least we know now it is a Bitdefender Armor issue and I guess we need them to apply whatever fix they have made out globally?
For me it's now 23 days, 23 hours, 54 minutes since I last had to toggle Armor off / on to resolve the issue.
Netgear has set up a community forum specifically for the Orbi AC products. Most of the people who watch that forum are more likely to have experience with Orbi and know how to work it better than those of us who follow this router forum. Might be more likely to find someone who has a solution if the question is posted there:
https://community.netgear.com/t5/Orbi/bd-p/Orbi
Please use this link to the main forum product list to review and choose where to make your posts.
https://community.netgear.com/t5/NETGEAR-Forum/ct-p/en-netgear
Thank you.- dbrewoodGuide
Today Netgear has replied to me with:
As per the engineers the issue was caused by BD agent incorrectly handling some of the packets. Let us know if you have any other concerns or clarifications.
I have replied to them saying:
So does that mean the issue should be fixed for all Synology DSM7 users now? If so do you want me to check with the other users who were affected and also tell Synology? Should I be okay to go back to using LAN1 on the NAS?
I am waiting on their reply.- Hard to imagine a less useful response. What is a BD agent? Did they fix the software?