Redirect traffic from a Source IP

RouterOS Forwarding Protocols
1

Hi

I have a MikroTik router (RouterOS v7.9) with the goal of creating a specific route to only direct traffic from source address 10.10.2.0/24 to destination 192.168.100.253.
(In 192.168.100.253 I have an openMTCProuter which aggregates several links)


By performing the configuration in the “Routing” section then “Route”:
Routing_Route.PNG
I don’t ping 1.1.1.1



On the other hand in “IP” then “route”, I can redirect the default route (which I don’t want) to 192.168.100.253
IP_Route.PNG
I ping 1.1.1.1



Do you have any ideas to redirect 10.10.2.0/24 to 192.168.100.253 ?

2

hello wetdarrfr,

is this your setups?

10.10.2.0/24 ---> MT ---> 100.253

https://wiki.mikrotik.com/wiki/Policy_Routing_in_RouterOS_3.x

3

Hi wiseroute,

That’s it,

My Router1 (Mikrotik):
R1.PNG
My Router2 (OpenMTCProuter):
R2.PNG
I ping fine one way or the other.
What I would like to do is a default route but taking into account only a source address (10.10.2.0/24).
In order to output 10.10.2.0/24 to the internet by OpenMTCProuter (fiber + 5G) and another network (for example 192.168.0.0/24) to output to the internet by the standard box.

4

hello

What I would like to do is a default route but taking into account only a source address (10.10.2.0/24).

I’m sorry, but your setup and your requirements just doesn’t make sense because your MT only have 100.253 as gateway? or do you have any other gateway on MT?

let us say you make a PBR classifier for 10.10.2.0/24 to go 100.253 as gateway - the other !10.10.2.0/24 too will heading the same gateway? or you just want to Block those !10.10.2.0/24 for accessing the internet?

or do you have any other gateway on MT besides that 100.253? —> this will make sense.

5

192.168.100.253 is my OpenMTCProuter router

I made you a diagram to better understand the configuration I have :slight_smile:
config.PNG
I want for example 192.168.2.254 to go out to 192.168.0.254
And that 10.10.2.254 goes out to 192.168.100.253


The addresses of Router1 (Mikrotik):
route.PNG
And the routes I have:
address.PNG
I’m missing the Source Route 10.10.2.0/24 to 192.168.100.253

I tried to add in “Routing” then “Route” that (by deleting before the default route 0.0.0.0/0) but the ping 8.8.8.8 does not work :
Routing_Route.PNG

6

@ werdarrfr,

aaa… you have multiple gateways there.

in that case - this will help

https://wiki.mikrotik.com/wiki/Manual:PCC#Application_Example_-_Load_Balancing

don’t overlook at the load balancing part - but focus on the classifiers to drive 10.10.2.0/24 out to your mtcp router.

7

I tried to follow https://wiki.mikrotik.com/wiki/Manual:PCC#Application_Example_-_Load_Balancing
to solve my problem

  • Create a route for the destination 192.168.100.253 with an appropriate gateway:
    already OK

  • Configure a firewall rule to mark traffic coming from the source address 10.10.2.0/24:
    /ip firewall mangle add chain=prerouting src-address=10.10.2.0/24 action=mark-routing new-routing-mark=to_OpenMTCProuter

Error message: input does not match any value of new-routing-mark
He only wants “main”

  • Add a routing rule to route tagged traffic to destination 192.168.100.253:
    add dst-address=0.0.0.0/0 gateway=192.168.100.253 routing-mark=to_OpenMTCProuter


    Don’t accept / don’t know the “routing-mark” parameter
    (I’m on routerOS 7.9)


    So I tried to do something in firewall without any success:
    Mangle :
    nat.PNG
    NAT :
    mangle.PNG
    Filter rules :
    filter-rules.PNG
8

Hi forum,


For those who are looking to do the same:

  1. in Routing > Tables:
    Create your different WANs:
    2.PNG
  2. In Routing > Rules:
    Create your routing rules:
    Src Address: Its LAN
    Action: lookup only in table
    Table: Select your wan wish to create at 1.
    1.PNG
  3. In IP > Routes:
    Create your different WANs:
    Dst. Address: 0.0.0.0/0
    Gateway: Address of a WAN
    Routing Table: Select your wan wish to create at 1.
    4.png
    Result if in Routing > Rules I modify my rule and I change my “Table” by putting my other WAN.
    He will take my other route :
    3.PNG
    My answer I was able to get it thanks to @anav in the topic http://forum.mikrotik.com/t/routing-based-on-source-ip-or-source-interface/111479/1
9

@ werdarrfr

congratulations!

hmm, in case you interested in - what i thought - more simple way…

let us say - MT with 4 ethers :

  • mtcp router, LAN : 192.168.100.253/24, WAN : 172.16.1.2/24 (masqueraded)
  • lte router, LAN : 192.168.2.2/24, WAN : 172.16.1.3/24 (masqueraded)
  • MT,
    to-mtcp : 192.168.100.1/24
    to-lte : 192.168.2.1/24
    to-lan192 : 192.168.1.1/24
    to-lan10 : 10.10.2.1/24

requirements :

  • lan192 needs to go out to the internet via lte router.
  • lan10 needs to go out to the internet via mtcp router.
  • both lan192 and lan10 can contact each other.
source-based routing using pbr/dst-nat

# show interfaces

[admin@MT] > interface/print
Flags: R - RUNNING
Columns: NAME, TYPE, ACTUAL-MTU, L2MTU, MAC-ADDRESS
#   NAME           TYPE    ACTUAL-MTU  L2MTU  MAC-ADDRESS
0 R ether1-lan192  ether         1500         50:00:00:01:00:00
1 R ether2-lan10   ether         1500         50:00:00:01:00:01
2 R ether3-mtcp    ether         1500         50:00:00:01:00:02
3 R ether4-lte     ether         1500         50:00:00:01:00:03

# ip addresses

[admin@MT] > /ip address/print
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS           NETWORK        INTERFACE
0 192.168.1.1/24    192.168.1.0    ether1-lan192
1 10.10.2.1/24      10.10.2.0      ether2-lan10
2 192.168.100.1/24  192.168.100.0  ether3-mtcp
3 192.168.2.1/24    192.168.2.0    ether4-lte

# default route via mtcp and lte.
# note those ECMP path on mtcp and lte gateway

[admin@MT] > ip route/print
Flags: D - DYNAMIC; A - ACTIVE; c, s, y - BGP-MPLS-VPN; + - ECMP
Columns: DST-ADDRESS, GATEWAY, DISTANCE
#      DST-ADDRESS       GATEWAY          DISTANCE
0  As+ 0.0.0.0/0         192.168.2.2             1
1  As+ 0.0.0.0/0         192.168.100.253         1
  DAc  10.10.2.0/24      ether2-lan10            0
  DAc  192.168.1.0/24    ether1-lan192           0
  DAc  192.168.2.0/24    ether4-lte              0
  DAc  192.168.100.0/24  ether3-mtcp             0

# masquerade on both wan interface (mtcp and lte) - for simplicity.

[admin@MT] > ip firewall/nat/add chain=srcnat out-interface=ether3-mtcp action=masquerade
[admin@MT] > ip firewall/nat/add chain=srcnat out-interface=ether4-lte action=masquerade

# pre-pbr ping and traceroute test 
# from lan 192.168.1.0/24 to lan 10.10.2.0/24 and to inet (172.16.1.1/32)

lan192> ping 10.10.2.2

84 bytes from 10.10.2.2 icmp_seq=1 ttl=63 time=62.541 ms
84 bytes from 10.10.2.2 icmp_seq=2 ttl=63 time=6.323 ms
84 bytes from 10.10.2.2 icmp_seq=3 ttl=63 time=1.965 ms
84 bytes from 10.10.2.2 icmp_seq=4 ttl=63 time=2.068 ms
84 bytes from 10.10.2.2 icmp_seq=5 ttl=63 time=3.341 ms

lan192> ping 172.16.1.1

84 bytes from 172.16.1.1 icmp_seq=1 ttl=62 time=10.958 ms
84 bytes from 172.16.1.1 icmp_seq=2 ttl=62 time=7.210 ms
84 bytes from 172.16.1.1 icmp_seq=3 ttl=62 time=10.256 ms
84 bytes from 172.16.1.1 icmp_seq=4 ttl=62 time=5.275 ms
84 bytes from 172.16.1.1 icmp_seq=5 ttl=62 time=4.448 ms

lan192> trace 172.16.1.1
trace to 172.16.1.1, 8 hops max, press Ctrl+C to stop
 1   192.168.1.1   2.161 ms  1.249 ms  1.716 ms
 2   192.168.100.253   14.839 ms  4.361 ms  3.569 ms
 3   *172.16.1.1   4.335 ms (ICMP type:3, code:3, Destination port unreachable)

# pre-pbr ping and traceroute test from lan 10.10.2.0/24 to lan 192.168.1.0/24 and to inet (172.16.1.1/32)

lan10> ping 192.168.2.2

84 bytes from 192.168.2.2 icmp_seq=1 ttl=63 time=3.009 ms
84 bytes from 192.168.2.2 icmp_seq=2 ttl=63 time=5.473 ms
84 bytes from 192.168.2.2 icmp_seq=3 ttl=63 time=5.074 ms
84 bytes from 192.168.2.2 icmp_seq=4 ttl=63 time=5.349 ms
84 bytes from 192.168.2.2 icmp_seq=5 ttl=63 time=4.085 ms

lan10> ping 172.16.1.1

84 bytes from 172.16.1.1 icmp_seq=1 ttl=62 time=6.169 ms
84 bytes from 172.16.1.1 icmp_seq=2 ttl=62 time=10.623 ms
84 bytes from 172.16.1.1 icmp_seq=3 ttl=62 time=4.208 ms
84 bytes from 172.16.1.1 icmp_seq=4 ttl=62 time=7.421 ms
84 bytes from 172.16.1.1 icmp_seq=5 ttl=62 time=9.439 ms

lan10> trace 172.16.1.1
trace to 172.16.1.1, 8 hops max, press Ctrl+C to stop
 1   10.10.2.1   2.170 ms  0.985 ms  1.074 ms
 2   192.168.2.2   3.946 ms  11.984 ms  2.309 ms
 3   *172.16.1.1   5.542 ms (ICMP type:3, code:3, Destination port unreachable)

# pbr classifiers on MT : 10.10.2.0/24 via mtcp, 192.168.1.0/24 via lte

# creating address-list for local LAN :

[admin@MT] > ip firewall/address-list/print
Columns: LIST, ADDRESS, CREATION-TIME
# LIST   ADDRESS         CREATION-TIME
0 local  192.168.1.0/24  jul/14/2023 16:28:43
1 local  10.10.2.0/24    jul/14/2023 16:28:50

# dst-nat based pbr
# lan10 to-mtcp
# lan192 to-lte

[admin@MT] > ip firewall/nat/print
Flags: X - disabled, I - invalid; D - dynamic
 0    chain=srcnat action=masquerade out-interface=ether3-mtcp
 1    chain=srcnat action=masquerade out-interface=ether4-lte
 2    chain=dstnat action=dst-nat to-addresses=192.168.100.253 dst-address-list=!local in-interface=ether2-lan10
 3    chain=dstnat action=dst-nat to-addresses=192.168.2.2 dst-address-list=!local in-interface=ether1-lan192
 
# post-pbr traceroute test.

# from lan 192.168.1.0/24 to internet

lan192> trace 172.16.1.1
trace to 172.16.1.1, 8 hops max, press Ctrl+C to stop
 1   172.16.1.1   1.683 ms  1.401 ms  1.993 ms
 2   *172.16.1.1   5.192 ms (ICMP type:3, code:3, Destination port unreachable)

# from lan 192.168.1.0/24 to lan 10.10.2.0/24
 
lan192> trace 10.10.2.2
trace to 10.10.2.2, 8 hops max, press Ctrl+C to stop
 1   192.168.1.1   2.530 ms  1.710 ms  1.277 ms
 2   *10.10.2.2   3.322 ms (ICMP type:3, code:3, Destination port unreachable)
 
# from lan 10.10.2.0/24 to internet
 
lan10> trace 172.16.1.1
trace to 172.16.1.1, 8 hops max, press Ctrl+C to stop
 1   172.16.1.1   1.475 ms  0.960 ms  0.973 ms
 2   *172.16.1.1   6.249 ms (ICMP type:3, code:3, Destination port unreachable)
 
# from lan 10.10.2.0/24 to lan 192.168.1.0/24
 
lan10> trace 192.168.1.2
trace to 192.168.1.2, 8 hops max, press Ctrl+C to stop
 1   10.10.2.1   1.306 ms  1.413 ms  1.755 ms
 2   *192.168.1.2   7.687 ms (ICMP type:3, code:3, Destination port unreachable)
 
# notes :
# - the actual masquerade to the internet handled by those mtcp (192.168.100.253) and lte (192.168.2.2/24) routers.
# - those mtcp and lte uses fixed internal IP address.

hope this helps.