* John Arnold:
> Casual searching shows support for RFC 3021 in linux, in several of
> the tools, and in quagga.
Technically, RFC 3021 is not relevant here because Ethernet is not a
point-to-point link.
For this reason, some vendors claim they support RFC 3021, although
you cannot configure /31
* John Arnold:
> Is configuring Ethernet interfaces with /31 via zebra bugged?
> Broadcast address gets configured as 0.0.0.0 and pings to the far
> side don't work. I've reviewed RFC3021 and I think the broadcast
> address is supposed to be set to link local broadcast,
> 255.255.255.255.
Is the
Is there a less resource-intense way to get data similar to "show ip
bgp" from bgpd?
I'm mainly interested in the network prefixes themselves. Origin AS
information would be useful. Right now, I don't need the next-hop
router address or the full AS path.
* Daniel Seidenstücker:
> Maybe this hint/approach helps you:
>
> You can call vtysh commands the following way and pipe the results in normal
> unix commands (examples from ubuntu):
>
> sudo vtysh -c "show ip bgp summary" | grep 00: | wc -l#number of
> established peers, with connection u
* Paul Thornton:
>> The problem is that in my case, the command itself needs a lot of
>> resources. bgpd needs a couple of hundred MiB RAM extra while it
>> runs, and the CPU utilization is quite significant as well.
>
> Is it an option for you to have another machine / VM / whatever
> running Qu
* Donald Sharp:
> Just out of curiousity how long is it taking to do your queries? Can you
> show us some timed commands?
Roughtly 1.5 seconds for a full table dump. It's currently not a
problem because the machine is mostly idle. But I need to run the
command every couple of seconds.
___
* Martin Winter:
> Document Revision History:
> 1.0 22 September 2016 - Initial (internal) draft
> 1.1 18 October 2016 - CVE release version
Why didn't you coordinate the disclosure with distributions?
Debian assigned a CVE ID to you in good faith, but the promised
coordination never happene
