We downgraded from 6.45 to 6.44 when we read this post 2 weeks ago, and seems now is stable. Not any freezy / reboot.
Seems the 6.45 is something wrong.
Ok, it seems the correct way is:AS Path filters are regular expressions. You don't have a regular expression in your filter.
No option for prefix-list filters/routing filter ?Cisco, Juniper, Huawei, Alcatel, etc... all have the option to create a "prefix-list" for filters. I'm surprised Mikrotik doesn't offer this option...
what's your problem?
close port 80 from outside use.
Yes, note that the route destination of the image of the firt post in not the same as the second. Are different prefixesReeeeeally stupid question, but worth asking: is the nexthop reachable on both routes? (target scope within scope?)
routing bgp advertisements print
/routing filter add action=accept chain=Peer-OUT prefix=0.0.0.0/0 prefix-length=0 add action=discard chain=Peer-OUT
One peer is IX point, with a lot of members.That is a lot of route filters for such a small number of peers !
/ip firewall address-list remove [find]
/routing bgp advertisements Read only information about outgoing routing information currently advertised.
/ip firewall mangle add action=route chain=prerouting passthrough=yes src-address=x.x.x.0/24 route-dst=y.y.y.y