I have an SSR with Starlink configured as the WAN connection. The WAN IP on the SSR is assigned via DHCP from the Starlink network, which typically provides a public IP (e.g., 100.x.x.x).
I also have a Linux box connected to another interface on the SSR, which acts as a management LAN (on a different tenant).
Starlink provides a management IP (192.168.100.1) accessible locally when connected directly to its modem. I need to be able to reach this IP from the Linux box via the SSR.
I can achieve this connectivity by manually configuring the SSR's WAN interface with a static IP in the same subnet as the Starlink M&C IP-for example, 192.168.100.50. With proper service routes and policies, the Linux box can then reach 192.168.100.1.
However, the problem is that when I use a static IP on the WAN interface, Starlink's actual internet traffic stops working. Starlink requires the WAN interface to use DHCP to assign its public IP address for normal operation
How can I reach the Starlink management IP (192.168.100.1) from my Linux box via the SSR, while still allowing Starlink's internet traffic to function via DHCP on the WAN interface? Since the SSR doesn't allow a secondary static IP on the physical interface directly (only via VLAN), what would be the recommended approach to enable both functionalities?
Any suggestions or best practices would be greatly appreciated
------------------------------
Danish Vallanchira
------------------------------