set bgp prepend path in v7

RouterOS Forwarding Protocols
1

how can I have something similar to v6 “set bgp pepand path” in v7?
for exemple:
chain=out-to-sky prefix=1XX.1AA.CCC.DDD/24 invert-match=no action=accept set-bgp-prepend-path=65002

I dodn’t see any writable parameter similat to this in v7 routing filter.

any help?
thanks

2

I haven’t tried it yet but I think it’s something like this

ROS v7 accepts this syntax


add chain=test rule="if (dst in 200:co1d:c01a::/48) { set bgp-path-peer-prepend 5;accept}"
3

Nop,
the bgp-path-peer-prepend is used to check (in input chain) how many prepred has a prefix in its as-path.

my requestis about set-bgp-prepend-path that is about manipulation of as-path in output filter.

thanks
Ros

4

Create a filter like the one above. In BGP attach it to the output filter.

5

no the wiretable parameter above is not able to add as into the aspath

6

logically the conversion from v6 to v7 is not working.

7

use: set bgp-path-prepend 5;

edit: you are right, it does not work. another thing to fix in v7 BGP.

8

Inserting fake ASes in AS path will no longer be possible. You can prepend only your own AS or peer AS, nothing else.

9

Ok so what is the way to insert a few duplicates of the peer AS in a received path?
(to make it appear to have more hops and thus less preferred than another path)

10

set bgp-path-peer-prepend
or
set bgp-path-prepend

depending on which AS you want to prepend

11

Ok so in the input filter you need to use set bgp-path-peer-prepend or else it does nothing…
(in v6 set-bgp-prepend=3 worked both in input and output filter)
It looks like the conversion from v6 to v7 handles this incorrectly. Problem is of course that a filter cannot know if it is input or output filter, and in v6 it could be both.
Well, the filter conversion has more problems than that. E.g. it forgets to append an “accept” entry at the end of each chain, which is there implicitly in v6.
Maybe you could issue some warning to upgraders that they need to manually review their filter rules after upgrade, and what to look for.
(in fact I would appreciate it when you displayed a warning pointing to some page on help.mikrotik.com when users try to do a v6 to v7 upgrade and where you explain any known issues at that time, and that e.g. BGP is a work in progress so users that use BGP should be extra careful and/or ask their peers first)

12

There now is a dedicated help page for users upgrading to v7: https://help.mikrotik.com/docs/display/ROS/Upgrading+to+v7
It would be helpful when the issues with upgrading the Route Filters are mentioned there, aside of “you need to check them”.