From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Mitar <mitar@tnode.com>
Subject: Re: [B.A.T.M.A.N.] Migration to Batman
Date: Fri, 13 Apr 2012 11:24:47 +0200 [thread overview]
Message-ID: <20120413092447.GL7664@lunn.ch> (raw)
In-Reply-To: <CAKLmikNt0M4+MEQRsDH-fdnLD664+0G1pCcGKyCNWKim-6ro7Q@mail.gmail.com>
> If I understand correctly, this would allow us also easier peering
> with other networks as quagga supports also redistribution of routes
> and so on. So if we decide for OSPF, it will be easy also to setup BGP
> on border nodes within the single daemon, no?
Yes, quagga has BGP, but depending on your organizational structure,
it might be easier to use OSPF on your peering links. It depends on
your peers. If its The Internet, then you probably have little choice,
you need BGP. However, if your peer is another mesh network, you can
decide for your self what routing protocol to use.
> How CPU and memory heavy it is to run it on consumer routers like
> TP-links and so on? Probably depends on number of routes and not on
> itself? But is there a big penalty of running it on all nodes?
I've used quagga on Gateworks Cambria devices, with a Xscale CPU,
667MHz, 128Mbytes RAM. These tend to have more RAM than typical
consumer devices, but i've no idea how much is actually consumed.
Andrew
next prev parent reply other threads:[~2012-04-13 9:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 10:26 [B.A.T.M.A.N.] Migration to Batman Mitar
2012-04-12 10:36 ` Gioacchino Mazzurco
2012-04-12 12:00 ` Antonio Quartulli
2012-04-12 15:13 ` Mitar
2012-04-12 15:36 ` Andrew Lunn
2012-04-12 17:12 ` Mitar
2012-04-12 18:12 ` Andrew Lunn
2012-04-12 19:49 ` 3zl Trizonelabs
[not found] ` <CAOaDhSRTgejL5tzAnAx6wBso1sjWn_7bVuT6P1_C1qcVu25McQ@mail.gmail.com>
2012-04-12 15:37 ` Jernej Kos
2012-04-12 17:19 ` Mitar
2012-04-12 21:08 ` Mitar
2012-04-12 21:15 ` Gioacchino Mazzurco
2012-04-13 5:59 ` Andrew Lunn
2012-04-13 7:58 ` Mitar
2012-04-13 8:15 ` Andrew Lunn
2012-04-13 8:41 ` Mitar
2012-04-13 9:24 ` Andrew Lunn [this message]
2012-04-13 13:24 ` Mitar
2012-04-14 2:26 ` Nicolás Echániz
2012-04-14 9:06 ` Mitar
2012-04-16 10:25 ` Mitar
2012-04-16 10:37 ` Marek Lindner
2012-04-16 10:46 ` Mitar
2012-04-16 10:58 ` Marek Lindner
2012-04-16 12:32 ` Mitar
2012-04-16 12:40 ` Antonio Quartulli
2012-04-16 13:59 ` Mitar
2012-04-16 18:28 ` Marek Lindner
2012-04-16 18:30 ` Marek Lindner
2012-04-16 11:03 ` Antonio Quartulli
2012-04-16 12:37 ` Mitar
2012-04-12 17:10 ` Mitar
2012-04-12 22:13 ` Marek Lindner
2012-04-12 17:05 ` Mitar
2012-04-12 22:17 ` Marek Lindner
2012-04-13 6:22 ` Antonio Quartulli
2012-04-13 7:29 ` Mitar
2012-04-13 7:43 ` Andrew Lunn
2012-04-13 7:51 ` Mitar
2012-04-13 8:26 ` Andrew Lunn
2012-04-13 8:35 ` Mitar
2012-04-13 8:52 ` Christian Huldt
2012-04-13 13:32 ` Mitar
2012-04-13 13:50 ` Andrew Lunn
2012-04-13 13:53 ` Mitar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120413092447.GL7664@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mitar@tnode.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox