Basic setup for Starlink

RouterOS General
1

Hello
I purchased a Hex s I have tried to set it up very basic. I want my internal address to start at 192.168.1.10 the dns server at 192.168.1.1. When I set this in the router no traffic comes through on from Starlink. Traffic flows to the client pc but I can’t reach any outside domains. I put Starlink in bypass mode and am at a loss. I don’t know what the issue is at this point

Thanks in advance for any advice
Robert

2

One of the problems may be that your LAN network’s addresses overlap with those handed out by the Starlink because, if I remember correctly, it is CGNAT. Nevertheless, an export of the config is advisable for us to be able to help you:

/export file=anynameyouwish (minus sensitive info)

3

Reset Hex S to default config and it will use 192.168.88.0/24 as base subnet.
Most likely your issue will be solved then.

192.168.1.0/24 is indeed too common for most brands. Most likely you have a conflict there.

4

For once, I will impersonate @anav: “what do you want to achieve?”

You have the following options:

  • use the hEX S as just a switch and let the Starlink router do the routing. The Starlink router indeed uses the 192.168.1.0/24 subnet on its LAN side, so it could not work when hEX S was in the default setting acting as a router with NAT and had its LAN side subnet reconfigured to 192.168.1.0 as well
  • use the hEX S as a router and keep the Starlink router in default settings. In this case, you have to use some other subnet than 192.168.1.0/24 on the LAN side of the hEX S because Starlink prefers simplicity to flexibility, so there is no way to change the LAN subnet at the Starlink router
  • use the hEX S as a router and switch Starlink to bypass mode. In this case, hEX S will be the only NAT on your end (so you’ll have just double NAT rather than a triple one in the previous case, there is always a NAT in Starlink’s data center unless you have a “golden” contract providing you with a public address) and it will get an address from the CGNAT range (100.64.0.0/10) from Starlink on its WAN. But unlike in the previous two cases, bypass mode also automatically provides you with a /56 global IPv6 prefix.
5

Imagine that, communicated requirements are the answer to a successful outcome!!!
@holvoe - First poster process strikes again, or lack thereof.

6

Go translate some Dutch, you … :laughing: