I have a eero pro acting as my router behind my AT&T Arris modem in IP passthrough mode. I cannot access my Channels DVR remotely, I ran troubleshooting from my server, all is well EXCEPT Remote Access, which reads:
Outgoing connections are coming from 172.0.137.241 but the external IP of the router is 192.168.1.161
I have port 8089 opened to my Synology NAS within the eero settings.
Thanks in advance for any assistance. Be well!
Is it one of those modem/router combos? Is it in Bridge mode or are you using the DMZ option? I know even with my DMZ option on my Cox supplied modem/router I still had to open up 8089 to my router and on the router 8089 to Channels. In bridge mode this was not necessary. Plus there was an advanced security option available on the Cox unit that could be turned off and on that I noticed I had to sign in and approve the specific outside connection regardless of my port openings. Maybe the AT&T modem has a similar option or your Eero pro? I don't know or have experience with Eero products but I thought the pro had some special security stuff that may block access to that port until you give it approval? I know and understand you open the ports but maybe like my Cox unit there is a "2 step approval" if an "advanced security" option is on?
It is a modem/router combo. I’ve reviewed the eero instructions to put the AT&T device into IP passthrough and disable the WiFi, essentially making it a modem only. I want to take advantage of the functionality of the eero system, working toward enabling Apple HomeKit compatibility for our IOT devices. Bridge mode seems to be preferred but AT&T makes it very difficult with their hardware to opt for something other than IP passthrough. AT&T provides limited support assistance with IP passthrough since their connection terminates at the next down line device while I understand no support is available for bridge mode. There was another thread about Double NAT traversal, but I’m not knowledgeable to know if that is the situation I find myself in.
This is most likely the case, as the external IP you posted earlier is a private IP address not used for external-facing networks.
If that's the case, you need to have 2 port-forward rules: one on your modem to route port 8089 from outside to inside, and another on your Eero router to get the traffic to your server.
Just beware that mesh-network routers are known to be problematic with this type of situation. If, after exhausting all other troubleshooting options, your only option to get remote access would be a change in your networking hardware.
Well, then, with direction and a modicum of confidence, I’ll give that a try as it only looks as if I’d need to open the port on the modem which should be simple enough. I’ll give it a go and report back. As an aside, this may be the push needed to abandon AT&T altogether but I’ll just be trading one master for another as I’m likely to go Comcast...but at least I’ll own the hardware!