Hi Malcolm, It may be worth running an ongoing traceroute to somewhere to see if the route changes at any particular interval - but if you have connection tracking enabled, that may make the routes persist per session regardless of the routes changing. If you don't need it, it's generally a good idea to turn off connection tracking to improve performance, but depending on your firewall/mangle/NAT rules you may not have that option. Adding the route filter rule you suggested will work, and will apply to all existing routes too - you won't need to drop the peer or anything like that. However, once you add the rule, it will add it at the end of the list by default. If you want to move it, you will need to disable it, then move it, then enable it - if you just move it, it may not function as expected. Also be mindful that you have "accept" as the action - if you have other rules you want to have apply too, you could put this new rule at the top of the list with an action of "passthrough" so that you don't lose your existing functionality. Regards, Philip Loenneker | Senior Network Engineer | TasmaNet -----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Malcolm Faed Sent: Monday, 9 September 2019 10:41 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] BGP with ISP and IXP traffic variation Thanks Philip, The route numbers are not changing significantly +-10, and the peer uptime has not reset. I think then the solution for me then would be to configure the Megaport In filter as follows: *add action=accept chain="In_Filter_Megaport IX" comment="Set LOCAL PREF to 200 to favour the IXP routes over ISP" set-bgp-local-pref=200* Would you happen to know if this would take immediate affect, or only on new routes learned? Thanks and regards, *Malcolm Faed*Network Broadcast Engineer malcolm@avcomm.com.au Av-Comm Office: +61 2 9939 4377 Mobile+61 424 957 053 Unit 24 / 9 Powells Road, Brookvale, NSW 2100, Australia. avcomm.com.au [image: Twitter] <https://twitter.com/AvCommSatellite>[image: Google Plus] <https://plus.google.com/+AvcommAustralia/>[image: Youtube] <https://www.youtube.com/channel/UCO8ZtcnwoTH7e54LAndE-yw>[image: Linkedin] <https://www.linkedin.com/company-beta/6583589/> This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorised disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Av-Comm is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company. On Mon, 9 Sep 2019 at 09:19, Philip Loenneker < Philip.Loenneker@tasmanet.com.au> wrote:
Hi Malcolm,
Since this is outbound, it is the routes on your device that define where the traffic goes. Have you checked the uptime of the BGP peers to ensure they aren't dropping for any reason? If you view your route list for a few minutes, do you see lots of fluctuations of which routes are active?
If, like most organisations, you have higher capacity on an IX than you have on your IP transit, and you want to ensure that your traffic prefers that path where possible, the easiest way to prefer that path is to set the LOCAL PREF of the routes learned via Megaport to anything above 100 (the default). This value propagates via iBGP peers so if you have multiple POPs, they are preferred across your whole network. If you don't want that, then other settings such as prepending routes learned via IP transit may be more practical.
Regards, Philip Loenneker | Senior Network Engineer | TasmaNet
-----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Malcolm Faed Sent: Friday, 6 September 2019 6:39 PM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] BGP with ISP and IXP traffic variation
Hi All,
I have just completed implementing BGP with Megaport and our ISP.
I am seeing an usual pattern only with my outbound traffic. See https://malfunction.faed.name/ for a graph.
I can't easily see what 1000's of users are doing but it seems like some routes are changing between ISP and IXP, then changing back causing this pattern.
Can anyone suggest how to investigate this further? Or perhaps this is normal if anyone has experience in this.
Thanks in advance, Mal
*Malcolm Faed*Network Broadcast Engineer malcolm@avcomm.com.au
Av-Comm
Office: +61 2 9939 4377 Mobile+61 424 957 053
Unit 24 / 9 Powells Road, Brookvale, NSW 2100, Australia. avcomm.com.au
[image: Twitter] <https://twitter.com/AvCommSatellite>[image: Google Plus] <https://plus.google.com/+AvcommAustralia/>[image: Youtube] <https://www.youtube.com/channel/UCO8ZtcnwoTH7e54LAndE-yw>[image: Linkedin] <https://www.linkedin.com/company-beta/6583589/>
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorised disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Av-Comm is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company. _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au