Hello! I have problem and can’t find a solution … probably asking wrong questions;(
I need to add new isolated networks for external servers communicating by different WAN but provide communication witch selected hosts from existing internal network.
I can’t replace existing Linksys router, but I added route to my new network behind mikrotik.
I got filter rules and NAT sorted, but I have more basic problem with routing.
My workstations have default route pointing to Linksys 192.168.2.110
In Linksys I added Route to 10.64.128.0 MASK 255.255.248.0 thru 192.168.2.111
but it does not work unless I ping 192.168.2.110 form my mikrotik 192.168.2.111
or add route to my 10.64.128.x network on specific workstation.
If I ping 10.64.128.2 from 192.168.2.4 most of the time I can see with Torch ping packets coming to bridge port eth2 but not to the bridge.
I tested /ip settings RP filter set to loose but no effects.
What I’m do wrong?
Other than that: if Linksys works like a decent router, it reacts to packets originating from 192.168.2.0/24 and targeting 10.64.128.0/22 with ICMP redirect sent to original sender. If original sender is using over-configured firewall, it can drop this ICMP packet and keep bothering Linksys. IMHO linksys is supposed to forward all packets to RB, but then Linksys could implement that differently.
It is weird that Linksys only forwards packets to RB if RB pings it … as if RB was pushing itself into Linksys’ ARP table while Linksys were not able to find RB’s MAC address on its own (perhaps there’s a bug where Linksys won’t do ARP request if it had to forward packet to better router or something?).
it doesn’t work - devices on 192.168.2.0/24 can’t reach devices in 10.64.128.0/22.
3a) you ping 192.168.2.110 from 192.168.2.111: the route starts working and devices on 192.168.2.0/24 can reach devices in 10.64.128.0/22 - everything works as it should?
3b) you add a route to 10.64.128.0/22 on one device from 192.168.2.0/24, try to ping 10.64.128.0/22 and then all devices gain access to 10.64.128.0/22? or just that one device with the route?
how you return to step 2, when everything is not working again?
yes
3a) yes when ping is performed everything works as it should
Ping takes about 5 timeouts before receiving replays, and when it is running (and few seconds after) devices from 192.168.2.0/24 can communicate with 10.64.128/22
3b) only device with route configured
I don’t understand question.
If you asking how to return to state where 192.168.2.0/24 can not communicate with 10.64.128/22, then I just stop pinging.
How does 192.168.2.111 get it’s address: from DHCP on 192.168.2.110 or you assign it manually?
It is assigned manually, as most devices in that network.
One more interesting observation:
if I ping 192.168.2.111 from 129.168.2.110 it is receiving replays, but 192.168.2.0/24 still can’t communicate with 10.64.128/22.
P.s. sorry for delay, I had to get out form building before alarm armed itself.
In your Linksys config for the route I see, that you choose “3 (DMZ)”.
Is it possible, that Linksys applies some different firewall behaviour to this route because of that?
For example opening/closing ports automatically?
Are DMZ settings configured anywhere else?
“DMZ” is a name I have given to the route.
1 rule is for 192.168.0.0/24
2 rule is for 192.168.20.0/24
3 is for 10.64.128.0/16
On Linksys there is only one forwarded port (9xxx) configured.
Just NAT for 192.168.2/24 and 3 routes.
DMZ function is disabled
I can ping any machine in 192.168.2.0/24 network from others routes - 192.168.0.0 and 192.168.20.0
I have many specific rules in /ip firewall
in nat there is few dst-nat for trusted networks, and few others for anybody
in filter I have rules blocking almost anything from WAN and my DMZ except 10.64.128.0/24
but for tests I’m placing before them Allow filters for INPUT, FORWARD and OUTPUT.
In other cases I had problems with FastTrack so I disabled it for tests in /IP settings.
I didn’t spot any potential problems.
Especially if you allow everything in firewall during the tests.
I can suggest you to take any other mikrotik router and try to simulate the situation.
First placing in instead of LinkSys, with your first mikrotik in place, and configured as it is now.
And second - in place of your current mikrotik, with simplified configuration.