@whiteswan wrote:
had cause to ring up Support yesterday and was told you no longer have to open any ports for the doorbells.
I am having problems with my RVD 2 and a new tp link mesh system - so I asked about opening ports and was told that’s a thing of the past.
Maybe that’s why they took it down ?
I have a call booked with a level 2 tech on Tuesday so I will ask him.
Dave
NAT has generally made port forwarding/triggering unnecessary and a thing of the past. Most consumer routers will have zero problems with ports.
However, if you have a dedicated hardware firewall, that can be a different story, but usually there’s a way to whitelist entire devices (by MAC or IP) so that they are exempt from the firewall, again making port opening irrelevant. But there are some limited cases where you may need to open specific ports in the firewall for each Ring (or most any other IoT device) device. However, your consumer TP-Link mesh router/wifi is not going to be one of them.
If you want to discuss your particular issue further, I’d suggest creating a new post with the problems you’re having, the devices and networks you’re using when having the problems, etc. so as not to clog up this port-related thread with a separate issue. I don’t work for Ring nor are a moderator so I can’t just move this myself. But if you post a new topic I’ll see it, even if it takes me a couple hours. If you’re using a PC to post here, you can tag me specifically which will email me. Tag me by typing @abqnm and as you type it should give you a drop down to choose my username. This won’t work on mobile though, so if on mobile, I’ll just see your post when it shows up in the rss feed.
