<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Maria!<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 22 Mar 2019, at 14:24, Maria Matejka <<a href="mailto:jan.matejka@nic.cz" class="">jan.matejka@nic.cz</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello!<br class=""><br class="">On 3/22/19 1:29 PM, remco van mook wrote:<br class=""><br class=""><blockquote type="cite" class="">Ideally I’d like to replace a statement like<br class="">print "REJECTING: ",net.ip,"/",net.len," received from ",from," AS ",bgp_path.first,": Prefix is a martian";<br class="">with<br class="">syslog LOG_WARNING, "REJECTING: ",net.ip,"/",net.len," received from ",from," AS ",bgp_path.first,": Prefix is a martian”;<br class="">Right now I’m just commenting out the print statements that get hit too often to prevent spamming log files with ten thousands of rows, and ideally I’d like to use the log command that Bird uses for it’s own messages to set where these messages should go based on relevance.<br class=""></blockquote><br class="">This seems feasible, based on the user point of view. What is worse, the print command itself is hacked into the filter language in quite a crude and insane way.<br class=""><br class="">If it is enough for you, there is currently a fundamental filter rewrite undergoing code review and testing before being merged into v2 branch. After this is merged, it is possible to simplify the print command quite a lot and also to implement syslog. Is that enough for you?<br class=""><br class="">I don't like implementing this in v1.6.x – the legacy branch will never get the new interpreter.<br class=""><br class=""></div></div></blockquote>That would be great - it’s not super urgent. I can see how it’s not feasible to back port the new filtering to the 1.6 tree. Looking forward to try the new fast filtering.</div><div><br class=""></div><div>Would it however, for compatibility’s sake, be possible for the 1.6 code to get an alias from syslog *, “foo”; to print “foo”; ?</div><div><br class=""></div><div>Background: I’ve been building Papageno ( <a href="https://github.com/asteroidhq/papageno" class="">https://github.com/asteroidhq/papageno</a> ) to create BGP configs that are ‘default free zone safe’, and currently it produces equivalent configs for Bird 1.6 and 2.0. While I can work around not having a syslog statement for the 1.6 code this difference would create a massive headache on my side.</div><div><br class=""></div><div>Thanks</div><div><br class=""></div><div>Remco</div><br class=""></body></html>