The fiber router provided by my ISP reports a WAN IP address of 100.65.6.xxx which I take it is not a public IP address since WhatIsMyIP, canyouseemenow, etc. all report the IP as 135.84.223.xxx. One potential solution I’ve seen in these forums is to set up Port Forwarding to point to the router’s WAN IP address instead of my server’s internal IP but unfortunately the router will only let me configure rules for local IP addresses. So is the solution to ask the ISP to help me set up a double port forward where on my router I set the remote IP as the WAN IP (100.65.6.xxx) and on the gateway they open the same port (32400) to that IP also? If not, what are the other possible solutions? I was on the phone w/the ISP for a couple hours yesterday before I’d read enough to suggest this approach and everything else we tried didn’t work, including putting the server IP address in the DMZ and bridging the server’s ethernet port on the router directly to the internet (which sounded promising but I don’t really know what he was doing with that exactly and I don’t think he did either).
I’ve got another call w/the ISP in a couple of hours and by then one of their more senior network techs should be weighing in also. I was just hoping to brainstorm it here first before I call them back. Thanks in advance for any feedback or suggestions.
What you need the ISP to provide you is a WAN IP which matches what is reported by whatsmyip or ipchicken.com. The reason for this is because when you connect your server to plex, the IP plex.tv gets has to have a valid reverse path using that port. When in the ISP NAT environment, your public IP could change with each browse of the internet.
To state it clearly to them, you need a “Public facing IP, which is the same address as reported on the WAN IP address on your router”. If it is also “static” (non-changing) so much the better as that IP will always be yours.
My ISP provides “DHCP issued, public facing, IP addresses” and this is fine. The modem’s WAN IP matches what the IP sites report.
My ISP is Windstream. If they can do it, so can yours
In these days if IPv4 depletion we will see more users behind CGN, which in short straws are away for lazy ISP to put of IPv6, one way for people who are effected by CGN is to get a VPN which gives them a public IPv4. Just be sure to get an VPN which provides proper port forwarding.
When you do call your isp ask them to put your modem in bridge mode, and push them on ipv6. Bridge mode is basically what @ChuckPa said only in terms network engineer also can relate to.
Sadly IPv6 would be the best option is not yet widely supported around the world and all kinds of devices is not yet ready for prime time although many including my self argue that it should have been 10 years ago and we never should have gone down the path of natting.
@Night said:
In these days if IPv4 depletion we will see more users behind CGN, which in short straws are away for lazy ISP to put of IPv6, one way for people who are effected by CGN is to get a VPN which gives them a public IPv4. Just be sure to get an VPN which provides proper port forwarding.
When you do call your isp ask them to put your modem in bridge mode, and push them on ipv6. Bridge mode is basically what @ChuckPa said only in terms network engineer also can relate to.
Sadly IPv6 would be the best option is not yet widely supported around the world and all kinds of devices is not yet ready for prime time although many including my self argue that it should have been 10 years ago and we never should have gone down the path of natting.
Most VPN providers do not provide port-forwarding through the tunnel and exit-node IP addresses are often just as, if not more dynamic then that of an ISP. If you have a VPN provider who will give you an address, guaranteed static for the session duration, and port port forward inbound Plex traffic… GET IT
@Night said:
In these days if IPv4 depletion we will see more users behind CGN, which in short straws are away for lazy ISP to put of IPv6, one way for people who are effected by CGN is to get a VPN which gives them a public IPv4. Just be sure to get an VPN which provides proper port forwarding.
When you do call your isp ask them to put your modem in bridge mode, and push them on ipv6. Bridge mode is basically what @ChuckPa said only in terms network engineer also can relate to.
Sadly IPv6 would be the best option is not yet widely supported around the world and all kinds of devices is not yet ready for prime time although many including my self argue that it should have been 10 years ago and we never should have gone down the path of natting.
Most VPN providers do not provide port-forwarding through the tunnel and exit-node IP addresses are often just as, if not more dynamic then that of an ISP. If you have a VPN provider who will give you an address, guaranteed static for the session duration, and port port forward inbound Plex traffic… GET IT
I already have an VPN like that, well i have two, one which is a normal VPN provider an another that is running on my VPS :). The normal VPN provider gives me more or less a static ip with port forwarding on all ports I have made plex accessible on that s a test, works great even with 4x1080p streams.
My personal feeling about IPV4… If the entire 1.0.0.0 - 127.0.0.0 block weren’t restricted to class A and unusable, we’d really be fine with IPV4 for quite a while longer. IPV6 isn’t the answer most think it is. Amazon, which has a huge cloud hosting service, doesn’t support IPV6 and there are others as well. Before you even think of speaking about individual ISPs, you have to look at the state of the internet backbone itself. It’s predominantly IPV4 with IPV6 ‘tunneled’ in it. It’s a layer on top of IPV4, not a sibling. That should speak volumes about “IPV6 acceptance” as a whole.
@ChuckPa said:
My personal feeling about IPV4… If the entire 1.0.0.0 - 127.0.0.0 block weren’t restricted to class A and unusable, we’d really be fine with IPV4 for quite a while longer. IPV6 isn’t the answer most think it is. Amazon, which has a huge cloud hosting service, doesn’t support IPV6 and there are others as well. Before you even think of speaking about individual ISPs, you have to look at the state of the internet backbone itself. It’s predominantly IPV4 with IPV6 ‘tunneled’ in it. It’s a layer on top of IPV4, not a sibling. That should speak volumes about “IPV6 acceptance” as a whole.
Not to take this too far off topic, but the entire facebook, google and many other large backbones are 100% IPv6, there are much tunnling going on and sangtalent at best ipv6 implementations I’ve seen some ISP proclaim that they have native v6 but in reality it is a tunnel to the end user CPE inside their /28 v4(sorry for techno talk people),
Granted end user might not have the same urgency for IPv6 as large internet companies, and that large companies use IPv6 instead of v4 for their back bone is does reduce the pressure for end user.
On a personal note that amazon does not provide native v6 support will come back and bit them.
I my self have had native ipv6 for close to a decade now and where ever possible I host things dual stacked from my /24 v4 and /48 v6. If one looks at google and their v6 tracking one alse sees that adoption is on the raise.
and yes i agree that some of the allocated /8 are ridicules as are the reserved blocks you mentioned.
There are very very few single companies that need a /8 block (2^24 addresses).
but enough off topic.
on topic doubling natting and cgn is hard to end user to manage thus, only way around it is to get their modem in bridge, switch isp or a vpn hosted or provider.
Thanks Chuck, and apologies for the delay in responding. The ISP was able to assign a WAN IP that matched the public IP reported by whatsmyip which took care of the problem. Appreciate your help on this.
