I’m trying to do something pretty simple to start off here.
To start Broadband into ether1
I simple want to pass this through to ether2 for a wired desktop. No DCHP server.
I set the MikroTik up as a DCHP Client on ether1 where it gets ip 172.16.0.3/24 from the ISP.
I can get this to run via Bridges fine, however this leads me to my major problem. In this setup I also have a SR2 setup to be used as a AP.
I would like to run a DCHP server on the AP 192.168.0.1/24. I seem to be able to do this okay, however since I have already bridged ether1 and ether2 the Mikrotik OS won’t let bridge wlan1 to ether1 as it’s already being bridged to ether2. In essence not allowing my to send the data from ether1 to wlan1 AND ether2 at the same time. I’m under the impression that maybe simply routing the data rather then bridging the ports is the way to go, I’m just not having any luck doing it
I was hoping some of the MikroTik guru’s out there could get me set in the right direction. Any help in the matter would be appreciated.
You don’t say how you are connecting to your ISP, I assume Cable Modem or ADSL?
The most common mistake when routing through an MT Router is to forget to add a static route to the Cable/ADSL Modem to tell it where to find the network on Ether2. You also need to ensure that systems on Ether2 are given the correct default gateway, either via DHCP or statically.
Assuming Ether2 network is 192.168.0.0/24 and you’ve allocated 192.168.0.1/24 to Ether2.
On the Cable/ADSL modem add a static route for 192.168.0.0 netmask 255.255.255.0 gateway 172.16.0.3
In the MT Router DHCP or configure statically on each system connected to Ether2, add a default route 0.0.0.0 netmask 0.0.0.0 gateway 192.168.0.1
In the MT router, /ip route add dst-address=0.0.0.0/0 gateway=<ip address of Cable/ADSL Modem>
RJ -
Chris forgot to tell you that you will have to nat or masquerade the internal LAN to your cable/dsl modem IP. This is also done in the firewall under the NAT tab (winbox). Simply add a rule to masq (as in Chris’s example) 192.168.0.0/24 out interface WAN (the interface your ISP is on) that way no matter what the IP changes to you’ll get your internal IP masqueraded to the correct one(s).
