[quagga-users 7491] quagga on freebsd6.1?

Hello,

Has anyone successfully compiled quagga on freebsd 6.1-STABLE? I get the
following :

make: don't know how to make pkginfo.daemons.full. Stop
*** Error code 1

Stop in /usr/home/rob/quagga/unstable/quagga-0.99.5.
*** Error code 1

Stop in /usr/home/rob/quagga/unstable/quagga-0.99.5.

Any ideas?

Thanks.

--
Rob Rypka
703-886-4875
rob.rypka@...

[quagga-users 7492] Re: quagga on freebsd6.1?

At 11:43 AM 9/1/2006, Rypka, Robert A (Rob) wrote:
>Hello,
>
>Has anyone successfully compiled quagga on freebsd 6.1-STABLE? I get the
>following :

What configure options were you using ? I used

./configure --includedir=/usr/local/include 
--enable-exampledir=/usr/local/share/examples/quagga 
--enable-user=quagga --enable-group=quagga 
--sysconfdir=/usr/local/etc/quagga --localstatedir=/var/run/quagga 
--enable-vtysh --prefix=/usr/local

and then just gmake to build

and it works fine from the snapshot this morning 
(http://www.quagga.net/download/cvs/quagga-latest.tar.gz)

If you mean from the ports (0.99.4), yes it works too.

         ---Mike

>make: don't know how to make pkginfo.daemons.full. Stop
>*** Error code 1
>
>Stop in /usr/home/rob/quagga/unstable/quagga-0.99.5.
>*** Error code 1
>
>Stop in /usr/home/rob/quagga/unstable/quagga-0.99.5.

[quagga-users 7493] Fail-over configuration for quagga routers?

Hi

I'm new to the list so let me introduce myself:
My name is Sebastian and I am running a yet small but growing ISP
company in germany.
Until now I never had need to think about routing, but this is coming now.

The only possibility seemed to be spending thousands of Euro for
'original' big hardware routers when a friend of mine pointed me to the
quagga website.

I am quite thrilled about the possibilities quagga offers, but there is
(at the moment) one question I can't find an answer for:

I'd like to set up (at least) two routers for my network to gain
redundancy at this point. Cisco provides the HRSP (Hot Router Standby
Protocol), is there anything similar possible with Quagga?
How, if I may ask that way, did you solve this single point of
failure-problem?

Greetings from germany

Sebastian (Kueppers)

[quagga-users 7494] Re: Fail-over configuration for quagga routers?

On Sun, Sep 03, 2006 at 10:51:00PM +0200, wk-serv.de | Sebastian Kueppers wrote:
> I'd like to set up (at least) two routers for my network to gain
> redundancy at this point. Cisco provides the HRSP (Hot Router Standby
> Protocol), is there anything similar possible with Quagga?
> How, if I may ask that way, did you solve this single point of
> failure-problem?

I don't believe Quagga itself offers this feature, but there are related
projects which provide similar functionality.  OpenBSD's CARP is one
that seems to be popular:

http://www.openbsd.org/faq/pf/carp.html

There is a Linux port, too:

http://www.ucarp.org/project/ucarp

Also, there seems to be a VRRPv2 implementation for Linux:

http://off.net/~jme/vrrpd/

Hope this helps.

- Mark

--

-- 
Mark Kamichoff
prox@...
http://prolixium.com/
Rensselaer Polytechnic Institute, Class of 2004

[quagga-users 7495] Re: Fail-over configuration for quagga routers?

wk-serv.de | Sebastian Kueppers wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi
> 
> I'm new to the list so let me introduce myself:
> My name is Sebastian and I am running a yet small but growing ISP
> company in germany.
> Until now I never had need to think about routing, but this is coming now.
> 
> The only possibility seemed to be spending thousands of Euro for
> 'original' big hardware routers when a friend of mine pointed me to the
> quagga website.
> 
> I am quite thrilled about the possibilities quagga offers, but there is
> (at the moment) one question I can't find an answer for:
> 
> I'd like to set up (at least) two routers for my network to gain
> redundancy at this point. Cisco provides the HRSP (Hot Router Standby
> Protocol), is there anything similar possible with Quagga?
> How, if I may ask that way, did you solve this single point of
> failure-problem?

What sort of 'router' are you talking about here? Are you talking about 
doing internal routing or external routing or both? On linux there are 
several high-availability projects that you can take advantage of:
http://www.linux-ha.org/
http://www.ultramonkey.org/

[quagga-users 7496] Re: Problem with Quagga's bgpd - accepted prefixes keeps increasing erroneously

Hi Joni,

Could you try out tomorrow morning's CVS snapshot? I've added a 
command:

   show ... bgp .... neighbour <peer> prefix-counts

which walks the RIB and gives detailed counts for routes in various 
states. If you enable 'terminal monitor' you'll see log messages for 
discrepencies in specific routes. E.g. See below for an example of a 
slight drift due to dampening.

I still can't see why there would be problems without dampening 
though (unless it's the graceful-restart/NSF stuff, but even 
there..). Also there are some discrepencies when dampening is 
enabled, but even there it's almost self-correcting and differences 
should stay minor.

E.g. an example of dampening drift (with 'terminal monitor' set):

# sh ip bgp nei ..... prefix-counts
2006/09/03 23:03:13 BGP: ........ [pcount] 87.126.110.0/24 is counted but flags 0x412
2006/09/03 23:03:13 BGP: ........ [pcount] 89.37.19.0/24 is counted but flags 0x412

Prefix counts for ......., IPv4 Unicast
PfxCt: 193698

Counts from RIB table walk:

               Adj-in: 193703

[quagga-users 7497] Re: Problem with Quagga's bgpd - accepted prefixes keeps increasing erroneously

On Sun, 3 Sep 2006, Paul Jakma wrote:

> The dampening problems are trivial to fix and add the missing PfxCt 
> adjustments (might also be in CVS before snapshot time ;), maybe), 
> I need to see the output of the above for the case you had (without 
> dampening).

Oh, this also begs the question:

- What do people expect the PfxCt to count?

There's a dichotomy of conflicting uses for PfxCt:

a) Quickly see how many /useable/ prefixes you have from a peer

b) Guard against (via maximum-prefix) a wacky peer causing
    resource usage problems.

The latter case wants the /full/ count, regardless of useability of 
the paths. A path from a peer in the RIB takes up space whether it's 
useable or not.

Opinions? :)

regards,
--

-- 
Paul
Jakma	paul@...	paul@...	Key
ID: 64A2FF6A
Fortune:

[quagga-users 7498] Re: Syntax check

Paul Jakma wrote:
> On Thu, 31 Aug 2006, Oliver Hookins wrote:
> 
>> I had a look at the patch, and it seems to be fairly simple. If all 
>> the daemons operate in the same way by calling the threads then it 
>> seems it would be easy to modify all the daemons in the same way 
>> without any knowledge of their operation. If Stergiakis Alexandros 
>> isn't interested in making a patch for all daemons then I might have a 
>> go.
> 
> Please do. Provide a changelog reflecting both your contributions and 
> i'll apply it.

Not sure if you saw it, I posted a patch including the changelog to the 
devel list over the weekend. Hope it is up to scratch.

--

-- 
Regards,
Oliver Hookins
Anchor Systems

[quagga-users 7499] Re: Fail-over configuration for quagga routers?

> Hi
Hi,
>
> I'm new to the list so let me introduce myself:
> My name is Sebastian and I am running a yet small but growing ISP
> company in germany.
> Until now I never had need to think about routing, but this is coming now.
Welcome ;>
>
> The only possibility seemed to be spending thousands of Euro for
> 'original' big hardware routers when a friend of mine pointed me to the
> quagga website.
>
> I am quite thrilled about the possibilities quagga offers, but there is
> (at the moment) one question I can't find an answer for:
>
> I'd like to set up (at least) two routers for my network to gain
> redundancy at this point. Cisco provides the HRSP (Hot Router Standby
> Protocol), is there anything similar possible with Quagga?
> How, if I may ask that way, did you solve this single point of
> failure-problem?
You might join me in poking Paul to implement vrrp in the quagga suite ;)

Other options might indeed be carp/ucarp/vrrpd/keepalived;
or you might consider using L3 switches and combine those with your quagga 
boxes.
That way you could use quagga for bgp, and build an ospf mesh with your 
quagga boxes and the layer3 switches.
Next, use the layer3 switches' HRSP functionality, and go for layer3 
redundancy (which ospf gives you) at anything in your core.

[quagga-users 7500] Re: Fail-over configuration for quagga routers?

Sebastian,

On Sun, Sep 03, 2006 at 10:51:00PM +0200, wk-serv.de | Sebastian Kueppers wrote:

> I'd like to set up (at least) two routers for my network to gain
> redundancy at this point. Cisco provides the HRSP (Hot Router Standby
> Protocol), is there anything similar possible with Quagga?
> How, if I may ask that way, did you solve this single point of
> failure-problem?

Well, when your are talking about dynamic routing this is not what HSRP
or VRRP are supposed to do. The goal of HSRP/VRRP is to provide a 
"redundant default-gateway" for the hosts in a LAN segment while the
dynamic routing protocols are used beetween the routers in a network in
order to announce path and reachability information. [There may be other
definitions - but this is my short summary  ]

Of course, the are VRRP-like tools available as OpenSource, eg. the
keepalived for Linux / Linux Virtual Server or the Common Address
Resolution Protocol (CARP), which is well known at *BSD systems.

Best regards,

   Klaus

_______________________________________________
Quagga-users mailing list
Quagga-users@...