Getting around Internet Box static route limitations

Jossatze19

Hoi Zäme,

I have a home server connected to my Internet Box 4 that I access both locally and remotely from a range of devices (phone, tablet, laptop). For remote access I use Tailscale VPN, which assigns a long-term 100.x.y.z address to the server.

I had a solution in my previous setup for accessing the server on my LAN with the same configuration in all apps, but without the need for the VPN: I have set a static route in the router [Tailscale IP with 255.255.255.255 mask -> LAN IP], and it worked perfectly. In the Internet Box however, this cannot be configured because of the following limitations:

- The IP address must be within a private network address range (192.168.x.x, 10.x.x.x, 172.16.x.x - 172.31.x.x )- The subnet mask must be between 255.255.0.0 - 255.255.255.240.

Would it be possible to disable these checks with an "I know what I'm doing" setting or getting around them by injecting the entry in the configuration manually and restoring it to the device?

Black Mamba

@Jossatze19

this discussion [TUTO] on the Community FR may help

[TUTO] Accéder à distance à votre NAS Synology | Swisscom Community

see also this more recent one on the Community DE

Einrichten einer VPN-Verbindung eines Windows Rechners und IB3 | Swisscom Community

Jossatze19

Thanks, but I don't have a problem setting up the VPN, DHCP or port forwards, those are all done and working. I don't want to expose anything to the public internet either, as it's a huge security risk.

I just want traffic going to a specific, public looking, but not publicly routed IP to be routed to my server by the Internet Box. So basically a static route.

ChristianEb

Dear @Jossatze19, i think i got you point about the static route, I somewhen wished that I'm allowed to add a static route points to a public IP too,
but in a lookvise of https://datatracker.ietf.org/doc/html/rfc6598 I'm not sure if you should use this IP Range.

or if it's easier to change to a RFC1918 IP.

Regards

Chris