Changing the Remote (WAN) Access IP

[DarrenClimie-Newman 6]

Hi All,

I have a really frustrating issue that I hope can be resolved.

I have just changed ISP in the UK to Sky. Previously I was on BT and they provided a 1:1 ratio of IPv4 mapping on the WAN IP, so my external IP was only for me. However, with the new ISP Sky, I have encountered an issue accessing Emby remotely and I have found the reason why. Sky have recently started to deploy what is called MAP-T, which you can read about here - ISP Sky Broadband UK Deploying IP Address Sharing via MAP-T UPDATE - ISPreview UK.  Its basically sharing an IPv4 WAN IP address between multiple subscribers!

Firstly I have set up port forwarding as normal, like I did with my previous ISP no issue on the Sky Router

When trying to connect to Emby remotely via Android on my mobile device, it fails to connect. 

When I look at the WAN address picked up by the Emby Server it shows: 109.146.112.XXX:PORTNUMBER.

When I then go and look at the WAN IP Address on my new Sky Router is shows : 151.227.44.XXX

When I try and connect manually via a browser session on my mobile device to the Emby address 109.146.112.XXX:PORTNUMBER, it fails. (Same as Android client)

I then tried to connect manually via a browser session on my mobile device to the WAN address on my router 151.227.44.XXX:PORTNUMBER... It succeeds!!!

So the Emby Server is picking up the incorrect WAN IP Address from my Router/ISP.

My question is, can I manually change the Remote (WAN) Access IP on the Emby Server?

Thanks

Edited September 4, 2024 by DarrenClimie-Newman

[GrimReaper 4739]

It appears MAP-T basically serves same purpose as CG-NAT. Correlating to that, you might try using some tunelling software (like Tailscale) or VPN (with port forwarding). Look a bit around the forum for various solutions of users going around CG-NAT restrictions. 

[Q-Droid 989]

34 minutes ago, DarrenClimie-Newman said:

I then tried to connect manually via a browser session on my mobile device to the WAN address on my router 151.227.44.XXX:PORTNUMBER... It succeeds!!!

Were you on mobile network or WiFi for this test? If on WiFi then this was basically a loopback connection. Though, and other forum members on Sky BB could chime in, it looks like the ISP implemented MAP-T in a way to accommodate port forwarding and reduce the IP sharing ratio for those who do.

Quote

NOTE: Switching between IP sharing profiles/ratios, once triggered, isn’t instantaneous and it may take a few minutes, as well as a brief disconnection, before it’s fully activated (i.e. because they’re terminating the old DHCPv6 lease so they can get a new one from a different DHCPv6 pool).

You could try restarting your router after configuring the port forwarding rules so that it can acquire a new DHCPv6 lease.

[DarrenClimie-Newman 6]

7 hours ago, Q-Droid said:

Were you on mobile network or WiFi for this test? If on WiFi then this was basically a loopback connection. Though, and other forum members on Sky BB could chime in, it looks like the ISP implemented MAP-T in a way to accommodate port forwarding and reduce the IP sharing ratio for those who do.

You could try restarting your router after configuring the port forwarding rules so that it can acquire a new DHCPv6 lease.

Always on a mobile network when manually connecting to the 151.227 address on the router.

Just been to a neighbours house who accesses my server, successfully connects using the manual IP, not Emby Connect account.

So I have port forwarding set up OK, because I'm using it to manually connect via a browser or neighbours network using the client app on a Firestick

Am rebooting the router now to see what I get, and will reboot the server after.

[DarrenClimie-Newman 6]

OK so have rebooted the router and got the same WAN IP (151.227.44.XXX)

Rebooted the emby server and still retrieves the same WAN as before 109.146.102.XXX:PORTNUMBER.

I'm no expert on networks and routing or NAT, so some help would be greatly appreciated.

Why would Emby be finding a different IP to what is on my router?

[Q-Droid 989]

Emby uses external services to detect the public IP. It sounds like the IP detection still works as if behind CGNAT. But while it's similar, MAP-T is doing things differently. Your inbound is working so it could be a matter of using a different method for detection. 

Do sites like canyouseeme or whatismyip also show the 109 network? 

If your router has a DDNS feature that might work if you have or get a domain. Another option perhaps from the ISP itself. MAP-T is new to me and maybe the ISP has prepared for this very thing by offering an IP checker?

 

 

[Happy2Play 9780]

It will create issues if your IP address changes but put your WAN address in Network-Domain Name field and the dashboard will show that address.

[Luke 42077]

So maybe a DDNS is your best bet?

[DarrenClimie-Newman 6]

Hi.

Emby has now picked up the correct WAN IP, it took over 24hrs for it to register, I wonder if the server was holding on to my previous WAN IP from the previous ISP.

Thanks

[Luke 42077]

5 hours ago, DarrenClimie-Newman said:

Hi.

Emby has now picked up the correct WAN IP, it took over 24hrs for it to register, I wonder if the server was holding on to my previous WAN IP from the previous ISP.

Thanks

Usually it should only need a few hours. Restarting the server would also have helped it pick up the change quicker.