@jaredmwright said:
See my post which solved my problem on AT&T Fiber:https://forums.plex.tv/discussion/255113/using-plex-server-with-google-wifi-double-nat
So your’e relying on UpNp? I’m likely going to pay for a public ipv4. From what I’ve read, UpNp is very unreliable and will almost certainly fall down at some stage, hence the reason for it being advised to reserve a static IP for Plex.
I haven’t done it, but it seems to me like you could get a VPS somewhere in the cloud (DigitalOcean?) with a static IP and have it tunnel all Plex requests to your server. Maybe over a permanently-established VPN connection between them?
I’ve also heard of lots of people using Tunnel Broker to get ipv6 working at their homes when their ISPs don’t natively support IPv6. Maybe whatever protocols they employ would be helpful to you?
I wish I knew a little more about this so I could help further. Just throwing ideas out there.
Cheers. I’ve done loads and loads of reading on this. I’m no expert by any means but the problem here is that Carrier-grade NAT usually prevents the ISP customers from using port forwarding, because the network address translation (NAT) is usually implemented by mapping ports of the NAT devices in the network to other ports in the external interface. This is done so the router will be able to map the responses to the correct device; in carrier-grade NAT networks, even though the router at the consumer end might be configured for port forwarding, the “master router” of the ISP, which runs the CGN, will block this port forwarding because the actual port would not be the port configured by the consumer. One way round this, the ONLY way in my case, is to pay for a public ipV4 address.
