INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Port forwarding with Starlink and TP-Link Deco X90  (Read 114 times)

maliceme

  • Junior Woodchuck
  • **
  • Posts: 98
Port forwarding with Starlink and TP-Link Deco X90
« on: December 19, 2024, 02:29:07 pm »

Current setup is a SL gen 2 router in bypass mode, gen 3 dish (rectangle), ethernet connected to a TP-Link X90 in router mode. (Other X90 in mesh mode, but irrelevant to the post.) I cannot get port forwarding to work on the X90. I am also not a networking expert.

I'm trying to port forward JRemote media player (iOS app) to my music server. This will allow me to access my music server from outside my wifi network. Before moving to the sticks in Vermont I had Comcast - so a single IPv4 address - and the port forwarding worked seamlessly.

Now I have the SL/X90 setup and cannot get the port forwarding to work. I'm confused, as I'm seeing multiple IPv4 addresses:


If I go to What is My IP Address, I see 98.xx.xx.xx, with SpaceX NYC as the ISP.
In the Deco (X90) app, the IP is listed as 100.xx.xx.xx. This address cannot be located on WIMIPA.
In the JRemote app, it thinks my Global IP address is 84.xx.xx.xx (even though it cannot connect to it). The ISP for this address is Invite Systems SRL in Delaware. I have no idea where the app is finding this address from.

If I enter the 100.xx address and music server port # into a browser on my network PC, it finds the server. Entering this same address into a phone browser (not on the wifi) gives me "This site cannot be reached." Neither of the other two addresses (98 or 84) go anywhere in either the PC browser or the phone.
Any assistance is appreciated.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7879
  • Long cold Winter...
Re: Port forwarding with Starlink and TP-Link Deco X90
« Reply #1 on: December 19, 2024, 02:32:15 pm »

Are you sure your ISP doesn't block all port forwarding? If you setup the port forwarding rules on the router, and you still can't access it nor https://canyouseeme.org/ can see the port being open on any of your public IP addresses there's a chance your ISP blocks port forwarding.

My ISP unfortunately blocks port forwarding due to them using CGNAT and I can't access my library outside of my network directly. I have to use a VPN (ProtonVPN) that supports port forwarding within the VPN to access my library outside of my network and bind it to Media Center. This also requires remote access for the computer the MC server is running on to make adjustments, as the forwarded port changes if the VPN is disconnected, for example.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7879
  • Long cold Winter...
Re: Port forwarding with Starlink and TP-Link Deco X90
« Reply #2 on: December 19, 2024, 02:38:41 pm »

Just looked it up, Starlink is known to block all port forwarding due them using CGNAT. So it's probably not going to work without using a VPN that supports port forwarding.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

maliceme

  • Junior Woodchuck
  • **
  • Posts: 98
Re: Port forwarding with Starlink and TP-Link Deco X90
« Reply #3 on: December 19, 2024, 03:06:51 pm »

Ok, so it looks like it is a CGNAT issue. There may be a workaround via using my VPN provider to assign a static IPv4 address. Still investigating.
Logged
Pages: [1]   Go Up