Hi i have setup NAT on my secondary mikrotik(Home). I am able to nat from eth1(192.168.0.0/24) to wlan1(192.168.8.0/24) and vise versa. The parent mikrotik(work) is not allowing natting to go throught. I have setup bridge and eoip on both mikrotiks sp that the eth1 on the secondary mikrotik can use 192.168.0.0/24. But i cannot nat from eth1(work) to wlan1(home). But i am able to ping the ip(192.168.0.20) i have created for natting. I think it may be something to do with the routing. I have setup routing on HOME to route packets to 10.44.101.1.
10.44.101.1 is wlan1(work), The wlan2 ip on HOME is 10.44.101.1. The route set on WORK is routing packets to 192.168.0.2.
192.168.0.2 is the main proxy on the network. The proxy shows that all traffic from HOME is directed to WORK and then forwarded to 192.168.0.2
That means that all data from 192.168.0.0/24(Home) and 192.168.8.0/24(Home) is directed to Work and then forwared to 192.168.0.2
My dns and gateway settings on computer from eth1 on HOME is set to 192.168.0.2(dns and gateway) but still packets is forwared to 10.44.101.1 and not directly to 192.168.0.2. But if i set my dns to 10.44.101.1 then i cannot use the internet.
All computers on 192.168.8.0/24 is using dns 10.44.101.1 and it is working.
If I understood everything correctly you need to route those networks together not NAT them.
I have block users from ip range 192.168.8.0/24 to see users on ip range 192.168.0.0/24. But i have nat one 192.168.0.17 —> 192.168.8.3
I canot underdtand why i am able to ping 192.168.0.20 but not access it when from the eth1 side on WORK. But i can access it from eth1 on HOME.
strange…
I resolved the problem. What i did was i reset the router(work) to factory default and set it up with the same ip’s and dns and routes as before and now it seems to work and i am able to access the natted ip 192.168.0.20.
I wonder why the router did that. Maybe it got confused with all the changes i made recently.
Hi i did not actully resolve the problem. but i found ou what was cuasing it. well what happens is if i try to access the natted ip 192.168.0.20 from main rb side then the packets is send throught the main rb and then the rb uses it’s ip to connect to the second ap.
I i want to allow natting then i must allow the main rb’s ip to access the nat. BUt when i do that then everyone on 192.168.0.0/24 can see the natted computers and i dont want that. I only want ip address 192.168.0.17 and 192.168.0.101 to see that natted ip’s
The packet is send from 192.168.0.101(pc on eth1) then goes to 192.168.0.10(bridge1), then goed through (wlan1)10.44.101.1 to wlan2(10.44.101.2). Then to ip 192.168.0.20 natted to 192.168.8.4
I was wondering if i may be possible to skip ip 192.168.0.10(ap1) and go directly to 192.168.14(ap2)