NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 ...
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?
It was looking like the issue was with Bitdefender Armor as toggling that off / on (On the Orbi) immediately fixed the problem for me.
I assume BD agent is 'Bitdefender Agent' part of the RBK53S Armor system.
Interesting reply from Netgear:
As per the team it will be fixed in the next release no ETA was provided yet. Let us know if you have any other concerns or clarifications.
So I've gone back with:
So is this then an issue with each and every Orbi and the fix will be in place when the firmware is updated?
This sounds strange as the problem has not hit me four 2 weeks now with no firmware uplift. Or have support put a temporary fix in place (tied to my MAC address etc?) so it is fixed for me?
Can you please get some clarity from the higher tier as I've got at least 3 other users to advise as well as Synology.
It'll be very interesting to see what they come back with.
A final update from Netgear:
I have checked this with the team and they confirmed that engineering did no change on your router. They just identified the cause and confirmed that they will address it in later firmware release that we do not have an ETA yet.
It seems there is no response as to why I'm no longer suffering from the issue. I have asked....