how add multiple route tables, route rules in v7 beta

RouterOS RouterOS beta
1

i make some routes tabel and making routing mark rule in mangle…my question how i can use this route marking in /ip route …i want to pass this marking traffic through specific gateway..

mangle and routing-mark can not work for RouterOS v7
V7 Route List
2

See this:
http://forum.mikrotik.com/t/cannot-set-routing-mark-or-table-for-routing-rule/133363/4

3

sorry i didnot understad that rule…why 8.8.8.8 dst adress use in route and 1.1.1.1 in route rule…

4

It is just an example to show the syntax. Use addresses you want to route.

5

sir…for example in mangle i routing marked a traffic with the name “Line1”… and my gateway is 192.168.1.1 … nw tel me which rules will b add in /ip route sectiin and /ip route rule section…then i will totaly understand about it

6

Show what IP routes and route rules you had on v6 and I will show you how they should look like in v7.

7

/ip route
add check-gateway=ping distance=1 gateway=“EXTRA PPPOE” routing-mark=G-2
add check-gateway=ping distance=1 gateway=192.168.100.1 routing-mark=G-SQ
add check-gateway=ping distance=1 gateway=103.225.xx.xx routing-mark=CIR
add check-gateway=ping distance=1 gateway=103.225.xx.xx
add check-gateway=ping distance=2 gateway=192.168.100.1
add check-gateway=ping distance=3 gateway=“EXTRA PPPOE”

8

/routing table
add name=G-2 vrf=main
add name=G0SQ vrf=main
add name=CIR vrf=main

/ip/route
add gateway=“EXTRA PPPOE@main” dst-address=0.0.0.0/0^G-2
add gateway=192.168.100.1@main dst-address=0.0.0.0/0^G-SQ
add gateway=103.225.xx.xx@main dst-address=0.0.0.0/0^CIR
…

9

thanks alotttt…

10

I’m wondering if it’s definitive. It’s not major obstacle or anything, but IMHO separate paramers look better than these “magic suffixes”.

11

We are open to suggestions while v7 is in beta state.

12

Yep, +1 for separate parameters. When being separate, parameters are somewhat self-documenting. At the very least it is immediately obvious the thing actually exists in this case.

13

^^ Exactly this, I like how parameters in RouterOS have nice descriptive names, it makes it easy to understand and intuitive. So at least table= would be nice, instead of appending ^ to destination.

I’m not sure about VRFs, my knowledge has serious holes there. I see there’s already something with @ in current RouterOS, but it looks like the meaning is different (?).