Please read the manual. You need to assign some chains to your BGP peers (in-filter and out-filter), then use them in Filters
-- Подпись: (добавляется в конце всех исходящих писем) 2013/9/4 Tayeb Meftah <tayeb.mef...@gmail.com> > ok, now i have added static route to my edge, and marked it as fullbogon > 217.0.0.0/8 > and assigned it to bgp community 65000:888 > but i dont see the bgp chain in the routing filter? > :) > > Tayeb Meftah > Voice of the blind T Broadcast Freedom > http://www.vobradio.org > Phone:447559762242 > ----- Original Message ----- From: "Chupaka" <chup...@gmail.com> > To: "Mikrotik discussions" <mikrotik@mail.butchevans.com> > Sent: Wednesday, September 04, 2013 2:07 PM > > Subject: Re: [Mikrotik] BGP Community > > > /routing filter add chain=announce-out >> prefix=224.0.0.0/24set-bgp-**communities=65332:888<http://224.0.0.0/24set-bgp-communities=65332:888> >> >> >> -- >> Подпись: >> (добавляется в конце всех исходящих писем) >> >> >> 2013/9/4 Tayeb Meftah <tayeb.mef...@gmail.com> >> >> thank but how to add the bgp community? >>> >>> thank >>> Tayeb Meftah >>> Voice of the blind T Broadcast Freedom >>> http://www.vobradio.org >>> Phone:447559762242 >>> ----- Original Message ----- From: "Chupaka" <chup...@gmail.com> >>> To: "Mikrotik discussions" <mikrotik@mail.butchevans.com> >>> Sent: Wednesday, September 04, 2013 2:01 PM >>> Subject: Re: [Mikrotik] BGP Community >>> >>> >>> Then you add some community to that announce, and on other routers you >>> >>>> create routing filter that will change that route to >>>> blackhole/unreachable, >>>> like "/routing filters add chain=announce-in bgp-communities=65332:888 >>>> action=accept set-type=unreachable", or "set-routing-mark=fullbogon", or >>>> whatever you want. >>>> >>>> >>>> -- >>>> Подпись: >>>> (добавляется в конце всех исходящих писем) >>>> >>>> >>>> 2013/9/4 Tayeb Meftah <tayeb.mef...@gmail.com> >>>> >>>> Hello, >>>> >>>>> what's the use of a BGP community? >>>>> i for example, want to anounce a specific network from one of my >>>>> edge's >>>>> and all other edges receive it, but put it in a special routing mark >>>>> let's say, 202.0.0.0/8 want to mark it "DROP" >>>>> but all the traffic that's received but not marked as drop dont want to >>>>> mark it >>>>> is that pocible? >>>>> thank >>>>> Tayeb Meftah >>>>> Voice of the blind T Broadcast Freedom >>>>> http://www.vobradio.org >>>>> Phone:447559762242 >>>>> -------------- next part -------------- >>>>> An HTML attachment was scrubbed... >>>>> URL: < >>>>> http://mail.butchevans.com/****pipermail/mikrotik/**<http://mail.butchevans.com/**pipermail/mikrotik/**> >>>>> attachments/20130904/70ebe2f4/****attachment.html<http://mail.** >>>>> butchevans.com/pipermail/**mikrotik/attachments/20130904/** >>>>> 70ebe2f4/attachment.html<http://mail.butchevans.com/pipermail/mikrotik/attachments/20130904/70ebe2f4/attachment.html> >>>>> > >>>>> > >>>>> ______________________________****_________________ >>>>> Mikrotik mailing list >>>>> Mikrotik@mail.butchevans.com >>>>> http://mail.butchevans.com/****mailman/listinfo/mikrotik<http://mail.butchevans.com/**mailman/listinfo/mikrotik> >>>>> <http**://mail.butchevans.com/**mailman/listinfo/mikrotik<http://mail.butchevans.com/mailman/listinfo/mikrotik> >>>>> > >>>>> >>>>> >>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>>> RouterOS >>>>> >>>>> -------------- next part -------------- >>>>> >>>> An HTML attachment was scrubbed... >>>> URL: >>>> <http://mail.butchevans.com/****pipermail/mikrotik/**<http://mail.butchevans.com/**pipermail/mikrotik/**> >>>> attachments/20130904/c6a2258c/****attachment.html<http://mail.** >>>> butchevans.com/pipermail/**mikrotik/attachments/20130904/** >>>> c6a2258c/attachment.html<http://mail.butchevans.com/pipermail/mikrotik/attachments/20130904/c6a2258c/attachment.html> >>>> > >>>> > >>>> >>>> ______________________________****_________________ >>>> Mikrotik mailing list >>>> Mikrotik@mail.butchevans.com >>>> http://mail.butchevans.com/****mailman/listinfo/mikrotik<http://mail.butchevans.com/**mailman/listinfo/mikrotik> >>>> <http**://mail.butchevans.com/**mailman/listinfo/mikrotik<http://mail.butchevans.com/mailman/listinfo/mikrotik> >>>> > >>>> >>>> >>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>> RouterOS >>>> >>>> >>> ______________________________****_________________ >>> Mikrotik mailing list >>> Mikrotik@mail.butchevans.com >>> http://mail.butchevans.com/****mailman/listinfo/mikrotik<http://mail.butchevans.com/**mailman/listinfo/mikrotik> >>> <http**://mail.butchevans.com/**mailman/listinfo/mikrotik<http://mail.butchevans.com/mailman/listinfo/mikrotik> >>> > >>> >>> >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>> RouterOS >>> >>> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: <http://mail.butchevans.com/**pipermail/mikrotik/** >> attachments/20130904/55ccacc8/**attachment.html<http://mail.butchevans.com/pipermail/mikrotik/attachments/20130904/55ccacc8/attachment.html> >> > >> >> ______________________________**_________________ >> Mikrotik mailing list >> Mikrotik@mail.butchevans.com >> http://mail.butchevans.com/**mailman/listinfo/mikrotik<http://mail.butchevans.com/mailman/listinfo/mikrotik> >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> > > ______________________________**_________________ > Mikrotik mailing list > Mikrotik@mail.butchevans.com > http://mail.butchevans.com/**mailman/listinfo/mikrotik<http://mail.butchevans.com/mailman/listinfo/mikrotik> > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik > RouterOS > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.butchevans.com/pipermail/mikrotik/attachments/20130904/54681ef4/attachment.html> _______________________________________________ Mikrotik mailing list Mikrotik@mail.butchevans.com http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
