I did the bypass mode on starlink and am using my mikrotik to run the network. I saw a video on another brand that he set a static route to 192.168.100.1 to still be able to view the starkink device web page to be able to monitor the dish. I am new to programming. I added an address 192.168.100.1 255.255.255.252 eth1-gateway. I can pin the address dishy.starlink.com and it resolves to 192.168.100.1 and I can also ping 192.168.1.100. I tried the web address or ip address in my browser and it did to work. I tried adding a static route destination address of 192.168.100.1 to the gateway of my router 192.168.0.1 and its subnet is 255.255.255.0
Don’t know how the adresses are with bypass mode.
But in normal mode 192.168.100.1 is for the Starlink dishy. 192.168.1.1 is for the Starlink router.
If you connect the MT to the Starlink router in normal mode , it’s connected to the 192.168.1.0/24 network. Then you get an address like 192.168.1.1xx from the Starlink router on the MT router.
A route for 192.168.100.1/24 with 192.168.1.1 as gateway is then needed.
Bypass might give your an address in the 192.168.100.0/24 range (so then that route is not needed)
Using NAT in the MT
For your LAN network adressing that is mostly different , “masquerade” or SRC-NAT can be used on the eth1 interface of the MT, to the Starlink router.
For the default config of a MT in Home gateway (Home AP etc) , adding eth1 to the “WAN interface list” will do the trick. Eth1 is then an internet WAN connection, and has a DHCP client.
The masquerade NAT rule for the WAN interface list members should be there already by default.
Eth1 is not added as port on the LAN bridge. LAN Bridge that usually caries it’s own LAN subnet and DHCP server (your 192.168.0.0/24)
The Starlink then only sees the Eth1 address of the MT as connected.
Not using NAT in the MT
If you don’t want the NAT used in masquerade on the MT, then all devices must be in the address range of the Starlink LAN. (192.168.100.0) or in a extra subnet set as LAN in the Starlink router . (If this can be done. I have no access to this setting in my Starlink router).
ETH1 can then be a port on the bridge, which carries the DHCP client. There is no routing or NAT in the MT in this bridged case.
So I don’t understand what you want with
I tried adding a static route destination address of 192.168.100.1 to the gateway of my router 192.168.0.1 and its subnet is 255.255.255.0
Client devices should use the MT router as default gateway (192.168.0.1?) , or 192.168.100.1/32 should be properly routed to this MT via other gateways.
You get a CGNAT private like 100.64.x.x. is what I’ve seen. But the terminal does seem to have a 192.168.100.1/24 address too in the various models (square, rectancutar, circle) I’ve seen.
For by-pass mode, you can generally just add a 192.168.100.100/24 as an /ip/address on the Mikrotik for the interface going to starlink. Since “dishy.starlink.com” is in public DNS as 192.168.100.1, the starlink app etc all should work fine.
If you NAT’ing to the 192.168.1.0/24 used by the starlink router as the Mikrotik WAN, then you just need to add /ip/route on the Mikrotik for 192.168.100.1/32 to 192.168.1.1, as bpwl suggests.
In either case, if you have a more restricted firewall (e.g. no inter-lan routing), you may need to adjust firewall accordingly to allow.
I am using my Starlink router as the Mikrotik WAN.
I’m not skilled with programming my router. I tried this static route [https://i.imgur.com/FYIZ5Ll.png]
and I can ping 192.168.100.1 from the Mikrotik router
but I cannot ping it from my mac connected to the router with IP address 192.168.1.xxx on the LAN.
Can anyone tell give me plain, detailed instructions to add a static route to 192.168.100.1 on my Mikrotik?
You do not need to add a route separately. Just set the port of the mikrotik to which the Starlink is connected to an additional IP address from the network 192.168.100.0.0/24 any other than .1, the route will be created automatically.
In non bypass mode, I can’t seem to ping either the 192.168.1.1 Starlink router gateway address nor the 192.168.100.1 dish from inside my MT network. All Internet traffic works. I have created a static route to both the 192.168.1.0/24 address range and the 192.168.100.0/24 address range using eth1 as the gateway per instructions but can’t seem to talk to either dishy or the Starlink router. I get a Destination Host Unreachable. HELP!
If you’re in bypass mode, the Starlink dish’s 192.168.100.1 management page is still reachable, but you need to make sure your Mikrotik knows how to route traffic there. Usually that means adding a specific static route for 192.168.100.1/32 pointing to the interface that faces Starlink (often eth1), not to your LAN gateway. Also make sure there’s no firewall rule blocking access from your LAN to that IP. I’ve found that testing with a direct connection to the dish first helps confirm it’s reachable before adding it into the Mikrotik routing table.
