Good days
I dont how this is called i dont’know even if this is possible
lets say i have more than 254 devices between cellphones and computers in mi network soo theoretically need two nets
lets say i set up one dhcp1 server on
eth3 it assign from 192.168.0.1-192.168.0.200 gateway 192.168.0.1
now i set up other dhcp2 server on
eth4 it assign from 192.168.1.1-192.168.1.200 well i dont know how to make the second go out
now i want that all the devices could be seen from each other network so the reception PC on 192.168.0.23 could enter to the share folders on 192.168.1.52 and so on
and all could navigate Internet
##############
now the question
- is possible to merge networks this way ??
- ¿if its possible to merge transparently different networks, how do you call it ??
- ¿and at least how do you do it ?
thanks for reading
Guess with “transparent” you mean a bridged scenario: just use a bigger subnet. You will have a bridged (switched) network.
To achieve this, instead of using 192.168.0.0/24, use 192.168.0.0/23:
Network: 192.168.0.0/23
HostMin: 192.168.0.1
HostMax: 192.168.1.254
Broadcast: 192.168.1.255
Hosts/Net: 510
Mask: /23 (255.255.254.0)
Just make sure all masks use the new one on IP > Addresses, and DHCP server network settings.
Don’t forget to modify the pool.
To follow the approach you described, i.e. using different subnets, you’d be routing between the networks instead of switching/bridging, which for a network of that size, is in fact better practice.
However you will need to isolate both networks at Layer 2 level for this, either:
- Use a different switch/stack for 192.168.1.0/24, isolated from the one(s) running 192.168.0.0/24. It should be wired to an standalone interface (ether4 in your example), which shouldn’t be part of any bridge or switch group).
or
2. Keep switches/wiring as is and deploy VLANs (would require manageable switches, and its reconfiguration).
Then the second DHCP server will be set either on the interface connected to that second, isolated switch/stack, or on the appropiate VLAN interface.
Nothing special required for routing, as its name implies RouterOS routes by default.