Ondrej Zajicek wrote:
> >
> > Is there a way to export (extract) routes from BIRD as a list of
> > prefixes in text format, to a text file or pipe?
>
>
> IMHO the simplest way is just:
>
> birdc show route > file
Indeed. Thank you, Ondrej.
I have outwitted myself with all that "nc -w1 -U /var
On Wed, Feb 17, 2016 at 09:29:14AM +0600, Victor Sudakov wrote:
> Dear Colleagues,
>
> Is there a way to export (extract) routes from BIRD as a list of
> prefixes in text format, to a text file or pipe?
Hi
IMHO the simplest way is just:
birdc show route > file
You just have to cut out the firs
Will Dowling wrote:
> > Thanks for the link. So do you advise against sending commands
> > directly to the BIRD control socket?
>
> Not at all, that???s all those scripts are doing :)
>
> The only thing you???ll need to watch out for is the output separators in
> BIRDC output (numbers).
> I can
> Thanks for the link. So do you advise against sending commands
> directly to the BIRD control socket?
Not at all, that’s all those scripts are doing :)
The only thing you’ll need to watch out for is the output separators in BIRDC
output (numbers).
I can confirm that we’re using this for monito
> Is there a way to export (extract) routes from BIRD as a list of
> prefixes in text format, to a text file or pipe?
Hi Victor,
You can run bird tool with the -x option to list accepted routes, one per line.
This can be combined with other options such as -a to limit to a specific peer.
Downlo
Dear Colleagues,
Is there a way to export (extract) routes from BIRD as a list of
prefixes in text format, to a text file or pipe?
I can perhaps write an expect script to communicate with birdc, but
such kind of screenscraping is always the last resort.
Or should I communicate through the /var/r
