Hello, I have a basic understanding of RouterOS. I managed to setup a PPToE WAN (VDSL bridge mode) on ether1, two WiFi networks (2 and 5ghz) and some basic NAT for portforwarding. In the near future I’ll get another internet provider (Starlink, first version dish) which I would like to connect to ether2 and create another set of WiFi networks (both 2 and 5 ghz) that should be virtual? But I would also like these WiFi networks to use the second DHCP client WAN through Starlink instead of the already existing one on ether1. I would also like that the new set ot WiFis can also access the already existing local network and see the devices connected there.
Is there a way to setup this? I know how to setup the DHCP client for Starlink on ether2 but not sure how to proceed from there to create more (virtual?) WiFis with separat WAN access but same LAN access.
Can you guys help me out?
P.S
Not an IT noob, long time professional developer experience, but never fiddled with networking much.
. You might learn that networking is a complete different discipline in IT, different from application development and even systems operation.
Be ready to learn and explore new things.
But what you ask for can certainly be done. Having 2 separate networks (in WAN and wifi) can be the first step. But along the implementation you will have new requirements.
Like: VDSL failover for Starlink clients, and Starlink failover for VDSL users.
Ok to give you a start…
VDSL router WAN and wifi’s are what is called a gateway connection : DHCP on the router for the LAN devices, NAT or masquerade of the clients towards WAN
Starlink normally comes with it’s own router, that you can use or not. Starlink router does already NAT, has DHCP , has LAN IP address 192.168.100.1
You can decide that one NAT in the Starlink track is enough. If so, then you will bridge the (Starlink served) wifi’s to the Starlink router.
Extra wifi on the AP is done with “virtual” interfaces. (Radio and frequency, bandwidth, etc are the same (can not be set different), but SSID and security are separate).
Virtual wifi interfaces are extra interfaces independent from the first 2, that also can be connected to a bridge
Separation of networks is normally done with VLAN. VLAN are managed by the bridge. This is to avoid to have one bridge per network, what still would work
( There are other options in the wifi interfaces to handle the VLAN tag there. But bridge handling of VLAN is the way to go for most cases)
Inter VLAN routing (or inter bridge routing) can also be done, limited by firewall rules as needed.
