I’ve been working on getting this achieved for a collective of 6 hours at least and am all googled out. I’m replacing my old cisco running ddwrt with a 951g and am trying to achieve the following config:
[Internet–Ubiquiti Network on 192.168.0.0/24| {Wireless} [Mikrotik on 192.168.88.0/24]
Goal will be to have both networks be able to see each other, but I want the option to disconnect the 88 network during network backups.
I’ve got the Mikrotik connected to my network via wifi, nat is off since I don’t need it, firewall rules are disabled, the MT router has internet directly, but I haven’t been able to share the internet connection with the lan ports even though all ports are bridged.
The only thing that’s been done from default is to bridge all ports, set wlan1 as dhcp client and connect to my network.
I did something like this for my house. It’s not WDS.
FTTH 30mbps ------ RB2011UAS-2HnD (my router) ------ hAP Lite —{wifi}— Asus RT-N2D1(Neighbour) ------ FTTH 30mbps
The hAP Lite is acting as a wireless repeater (station pseudobridge). My network is 10.0.1.0/24 and neighbour’s is 192.168.1.0/24. Both networks can see each other. I did it for load balancing.
RB2011 is 10.0.1.1.
RB2011’s Ether10 is 192.168.251 and connected to the hAP Lite and of course, a dynamic route is created: dst-address=192.168.1.0/24 gateway=ether10-wan2
hAP Lite is 192.168.1.250 with this route dst-address=10.0.1.0/24 gateway=192.168.1.251
Asus has this route dst-address=10.0.1.0/24 gateway=192.168.1.250
I’m still very much a beginner so not sure if that’s the correct way to do it but it works.
Sounds like all you need is a static route on the Ubiquiti side of the network, pointing 192.168.88.0/24 to the 192.168.0.x-IP assigned to the dhcp client on mikrotik. This should ofcourse be made static.
Thanks for the input. I’ll play with it more tonight and this weekend. Coming from using a Cisco DDWRT setup with DHCP forwarding, wanted to take some of the load off my main router during backups.
So seems after playing around with routing on the ubnt, nat and user modes on the MT, it seems like I’ve covered all the options and still unable to get access to the Ethernet ports. What else could I possibly be missing?
I wanted to chime back in on this if anyone has any thoughts. I decided to try to change my MTK to pass dhcp requests, since accessing the wired network became difficult and the double firewalled connection was stupid slow. After looking and looking, it occurred to me that according to the wiki, the mtk can’t pass DHCP requests and the MAC over wifi (which my old DD-WRT router DID do, still don’t get why this isn’t possible with mtk?).
Does anyone have any thoughts or potential solutions before I get rid of the MTK for something less time-consuming?
Goal:
[Internet–Ubiquiti Network on 192.168.0.0/24| {Wireless} [Mikrotik on same lan with 2-3 devices WIRED]
I’m a little confused here cap’n. You want to bridge (layer 2) your Ubiquiti network (192.168.0.0/24) to the LAN ports of your MikroTik?
This is a different objective than your original post. I just want to be crystal clear on your expectation.
If your goal is bridge (layer 2) your 192.168.0.0/24 network via wireless and have all services function that is not possible. The method that would work the cleanest is station-bridge. That requires like hardware. The MikroTik wiki clearly calls this out as only MikroTik to MikroTik hardware for their particular implementation. Like one of the earlier replies hinted at. You can blame the WDS standard for this incompatibility. They called out the need for this behavior but left it up to each vendor to implement it independently. Meaning it is a standard that only works when each vendor implements it in a like fashion. Typically this boils down to chip-set constraints of the actual wireless brand. You can try the station-wds mode but no promises there on whether it will work or not. That’s supposed to be MikroTik proprietary as well but can provide the 4 address frame like some other WDS implementations might be expecting.
If you’re serious about your original statement, having 192.168.0.0/24 separate from 192.168.88.0/24 then it is possible to connect via wireless to 192.168.0.0/24 and route packets to your 192.168.88.0/24 network. You can even have a single layer of NAT if you add a route to the Ubiquiti router.
For this setup, you’d use the regular station mode and connect the MikroTik to your 192.168.0.0/24 wireless network. It’d be best to assign a static IP to the WLAN interface. Then create a static route on the Ubiquiti device to point to the MikroTik device IP for the destination of 192.168.88.0/24. Then you’ll need to provide a DHCP server for the LAN ports on the network of 192.168.88.0/24 locally on the MikroTik. If you wish to have the MikroTik also broadcast an SSID you’ll need a device with 2 radio’s I believe (wlan1 and wlan2). I’m not sure if you can set virtual-ap’s in different modes and how well that would work sharing a single radio (it would for sure cut bandwidth in half).
