Hi!
> This release addresses a crash found when using redistribute statements.
> It is recommended that all users upgrade to this release.
>
>
> This release is up on Savannah or download at:
>
>
> http://download.savannah.gnu.org/releases/quagga
>
> http://download.savannah.gnu.org/releases/
Hi!
> We felt that there was enough functionality in this new release that it was
> time to roll the release #. In the discussion about this several parties
> wanted the ability to know the date of release, so it we started using the
> date as the bugfix #.
Ah, thanks. As I'm preparing a patch f
Hi!
> Second, BFD has always been underwhelming on server platforms,
> like those that Quagga typically runs on. [...]
> I'm not aware of anyone that can do BFD in the control
> plane, and support BFD rates less than 100ms.
ICMP round-trip can be far below 100ms (below 1ms is easy), so at least
Hi!
> >> Second, BFD has always been underwhelming on server platforms,
> >> like those that Quagga typically runs on. [...]
> >> I'm not aware of anyone that can do BFD in the control
> >> plane, and support BFD rates less than 100ms.
> >
> > ICMP round-trip can be far below 100ms (below 1ms is
Hi!
> When I type "vtysh" now it's appears the following messages:
>
> Multiple command installs to node 4 of command:
> list
[...]
I see the same on FreeBSD from the ports (1.1.0_1).
--
p...@opsec.eu+49 171 3101372 4 years to go !
_
Hi!
> ???I've got exactly the same problem (Quagga 1.2.1 on FreeBSD 11.1-BETA2):
>
> R2# sh bgp neighbors 2001:db8:23::3 received-routes
> BGP table version is 0, local router ID is 192.168.56.12
> Status codes: s suppressed, d damped, h history, * valid, > best, =
> multipath,
> i
Hi!
> I am trying to set up Quagga router as a BGP router for Looking Glass.
> I am facing the following issue right now: when I log in to port 2601 in
> order to run
> ping or traceroute command I am getting the error message:
Log into the unix shell on the box that runs quagga, not to the quagg
Hi!
> I was trying to make a small app using the quagga API available in
> /usr/local/include/quagga/
> But when I #include some file, I get way too many errors. Here is one such
> example.
>
>
> my test.c code is
> #include
> int main(){return 0;}
>
>
> If I compile it using gcc e.g. gcc -o
Hi!
> is there a limitation of quagga to being a Router ?
>
> i mean , what if a have a requirement to forward 20Gbps using BGP , can
> quagga handle this ?
Quagga only maintains the routing info. The forwarding is normally
being done by the kernel of the unix box you run it on.
So the forward
Hi!
> i actually use GRE to establishs BGP connections , that means all
> forwarding data will going in the GRE tunnel , what do you think of
> this GRE perfermence limitation ?
Depends on the kernel and cpu GHz rate used to process GRE.
What CPU is in use ? What kernel ? I assume that forward
Hi!
> well , my quagga bgp stack , ospf stack will exit automatically in a
> low rate . do you know what is going on ?
Come on, look around your bug report! That is not a valid bug report,
that is a joke! At least provide details about your setup!
--
p...@opsec.eu+49 171 3101372
Hi!
> For new users would it be better to start off with FRR or Quagga?
On FreeBSD (and maybe somewhere else) there's this bug in 1.2.1
of quagga:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214481
https://bugzilla.quagga.net/show_bug.cgi?id=870
So maybe use 1.1.1 to stay away from that
Hi!
> On Mon, 28 Aug 2017, Kurt Jaeger wrote:
>
> > At least on FreeBSD, net/frr is a port and therefore, switching
> > between quagga and free looks pretty straigtforward.
>
> The Quagga project had informal legal advice years ago on something.
Interesting. Where can
Hi!
> > Interesting. Where can we find more about that advice ?
>
> > Can you point to some URL where we can read more about that ?
>
> I think anyone who's followed this list the last couple of years will
> know what it's about.
I subscribed around February 2013, and I'm at loss right now.
>
HI!
> after 3 years of operating quagga bgpd, i did have suddenly hit error
> between two Quagga BGPD routers:
>
> 2017/09/30 20:05:47 BGP: 185.120.68.25: BGP type 2 length 3300 is too
> large, attribute total length is 2309. attr_endp is 0x55b24ff1f323.
> endp is 0x55b24ff1ef3c
Yes, we had the
Hi!
> > Yes, we had the same problem this morning.
> >
> > See the discussion around this mailthread
> >
> > https://lists.quagga.net/pipermail/quagga-users/2017-September/014836.html
>
> please take a look at the following patch by Andreas Jaggi:
>
> https://lists.quagga.net/pipermail/q
Hi!
> So, FreeBSD users that have installed Quagga from ports don't need to
> apply this patch?
Only if you build from a ports tree after the commit r451045.
And currently, I'd suggest to use the just-committed net/quagga-esr,
which is based on 0.99.24.1, which does not seem to have the issue
d
Hi!
> The fix for this problem is available in master and would obviously be in
> the next release which would happen in a day or two
Will that new release also fix
https://bugzilla.quagga.net/show_bug.cgi?id=870
?
--
p...@opsec.eu+49 171 3101372 3 years to
Hi!
> I can ping 2001:690:810:5::1 in the router configured to be the active
> one (LP=302) but the route isn't placed in the routing table reporting
> "inaccessible" (see show command).
I have no idea if that fits your problem, but
https://bugzilla.quagga.net/show_bug.cgi?id=870
has somethin
19 matches
Mail list logo
