Do filters support accessing properties of some interfaces?
-- Is it possible to get link status (up/down? anything else?) of an interface (specified by interface name or other reference way if there're any) for further use in routes' preferences/metrics calculations? Hi :) -- End of message. Next message?
No and it is not a trivial thing as the interface status may change independently on the routes so the routes may need reimport on interface status change. Anyway, in near future, the roa checks should be fixed in exactly this way, reimporting routes as roa changes. Then it should be an easy change to do. Please revive this thread after we announce the fixed ROA handling. I suppose it will happen in several months. Maria On January 16, 2019 5:34:36 PM GMT+01:00, Igor Podlesny <bird.user@poige.ru> wrote:
-- Is it possible to get link status (up/down? anything else?) of an interface (specified by interface name or other reference way if there're any) for further use in routes' preferences/metrics calculations?
Hi :)
-- End of message. Next message?
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Thu, 17 Jan 2019 at 01:35, Maria Jan Matějka <jan.matejka@nic.cz> wrote:
On January 16, 2019 5:34:36 PM GMT+01:00, Igor Podlesny <bird.user@poige.ru> wrote:
-- Is it possible to get link status (up/down? anything else?) of an interface (specified by interface name or other reference way if there're any) for further use in routes' preferences/metrics calculations?
No and it is not a trivial thing as the interface status may change independently on the routes so the routes may need reimport on interface status change.
oh yep -- as they say "The only trivial is how flies do coupling" :) But nevertheless, would be really great feature indeed. BTW, are there any properties available to filters outside the ones of route's they're processing? Are there any some "global variables"? Can users introduce some?
Anyway, in near future, the roa checks should be fixed in exactly this way, reimporting routes as roa changes. Then it should be an easy change to do. Please revive this thread after we announce the fixed ROA handling. I suppose it will happen in several months.
I also have a suggestion in regards of "check link": if it would be not only a switch, but, say, reference to an arbitrary interface would be supported, it would also extend Bird's flexibility significantly. Might be a good candidate to couple with that "interface properties" feature. ;) -- End of message. Next message?
BTW, are there any properties available to filters outside the ones of route's they're processing?
There are global constants. There will be some more properties of the protocols involved. Global variables won't be supported as it would break parallel execution of filters. If you need something really special, write your own protocol. (This should be also simpler, we should clean and better document the protocol API.)
Are there any some "global variables"?
Can users introduce some?
From 2.0.3 on, it is possible to have custom route attributes, anyway, I suppose this is something you aren't looking for.
I also have a suggestion in regards of "check link": if it would be not only a switch, but, say, reference to an arbitrary interface would be supported, it would also extend Bird's flexibility significantly.
Might be a good candidate to couple with that "interface properties" feature. ;)
Let's see what is feasible after the roa checks are fixed. Feel free to remind this topic then. Maria
participants (2)
-
Igor Podlesny -
Maria Jan Matějka