> 1) When testing against an older babel (circa september)
>
> The zebra version would not install "via" routes for
> subnets.
Okay, I'm starting to understand. IPv6 works fine, it's only IPv4
that's broken. (Why don't we all switch to IPv6 and be done with it?)
Babel sets both the gateway and
> IPv4 didn't work for me either, this was briefly noted before. I am
> not sure, if any IPv4 information was ever exchanged in PDUs.
Yes, the on-the-wire packets are fine (tcpdump), babeld has the right
information (show babel database), but it doesn't get communicated
correctly to zebra (show ip
>> Okay, I'm starting to understand. IPv6 works fine, it's only IPv4
>> that's broken. (Why don't we all switch to IPv6 and be done with it?)
>> Apparently, either quagga doesn't like an IPv4 route to have both
>> a next-hop address and an ifindex, or we're doing something wrong.
> but nexthop+
Hi,
I've spent much of the last two days reading the Babel/Quagga code.
Many, many thanks to Matthieu Boutier and Denis Ovsienko for getting
this to work.
Unless I'm confused, here's the current status.
Basic functionality
***
For IPv6, Babel/Quagga should be just as functional
> Redistributing Kernel->Babel, RIP->Babel and RIPng->Babel work fine. (I
> cannot easily test OSPF->Babel and BGP->Babel.) Babel->RIP and
> Babel->RIPng don't work, I'll look into it.
Meanwhile, Matthieu has fixed Babel->RIP and Babel->RIPng (commits
cd603d and 5af239). So all forms of redistr
> Do you have a gitweb to view those commits?
Upstream tree:
http://code.quagga.net/?p=quagga-RE.git
Matthieu's tree (obsolete?):
https://github.com/boutier/babeld-for-quagga
My tree:
https://github.com/jech/babeld-for-quagga
I recommend tracking the upstream tree, which is where the t
> (I can’t reach code.quagga.net right now but it might be my ISP’s
> fault).
There's a routing problem with Renater (Denis has filed a ticket). It
works fine from Proxad.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
htt
Hi,
Matthieu has noticed that the implementation of "idle" interfaces
(babeld -i) is incompatible with per-interface timer values. I'm
therefore planning to remove this little-used feature.
Please let me know if you're using this feature, and if you'd be sorry
to see it go.
-- Juliusz
Version 1.3.1 of the babeld routing daemon is available from:
http://www.pps.jussieu.fr/~jch/software/files/babeld-1.3.1.tar.gz
http://www.pps.jussieu.fr/~jch/software/files/babeld-1.3.1.tar.gz.asc
For more information about the Babel routing protocol, please see
http://www.pps.jussieu.fr/
Hi to all,
We've merged 1.3.1 into Quagga, and the Quagga command-line interface
has been cleaned up and made more uniform. Quagga has also learnt to
save Babel's configuration (show running-config). For your greater
kibbitzing pleasure, I've put a copy of the docs on
http://www.pps.jussieu.f
> 1) when doing a 'save' from the vtysh interface some key information
> is lost.
Yep, that's a known limitation. I'm leaving it for later, I don't think
it's essential in a first release.
> Where A has a /64 ipv6 address and a /27 ipv4 address
> gets a correct looking 'via' line for the /128 an
Does anyone use -P? I'm half tempted to remove it in a future release,
since filtering is both more flexible and more intuitive.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/
> Is there a right way to not announce ipv4 routes through a natted
> interface, but announce ipv6?
In standalone Babel (untested):
out if eth42 ip 0.0.0.0/0 deny
(The part between "out" and "deny" is a list of keyword/value pairs, so
it should be read as "when if=eth42 and ip is in 0.0.0.0/0"
There's been some movement in the Babel-quagga trees:
1. The official Quagga-RE tree is now mirrored on github:
https://github.com/Quagga-RE/quagga-RE
or
git clone git://github.com/Quagga-RE/quagga-RE.git
The RE-testing-0.99 contains the most up-to-date version of
Babel-enabl
standalone Babel daemon [2] or the quagga-RE version.
-- Juliusz Chroboczek
[1] https://github.com/Quagga-RE/quagga-RE
[2] http://www.pps.jussieu.fr/~jch/software/babel/#download
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http
> The primary reason for using MIT/X11/BSD is precisely to allow others
> to *relicense* the code as they wish.
This is correct.
Please read my initial mail again. At no point have I argued the
legality of Paul's actions. I'm simply stating that I find his actions
rude.
And I don't enjoy worki
> I recently had a chance to catch up with the quagga-babel implementation,
> and set it up as a leaf node on my laptop and connected it to bloatlab #1,
Cool.
> 1) when connectivity to a destination is lost, babeld puts an 'unreachable'
> route in place, zebra puts a 'blackhole' route in place. I
Now that I've set the record straight, there's hardly any point to
continuing this thread.
> What would you have preferred Paul to do instead? Not merge the code at all?
The respectful thing to do would have been to give us the choice between
adding GPL headers or not getting merged. Adding the
> 1) This was mostly just a note as to the difference in behavior
>
> 2) Unreach, as it give instant feedback, and is the same as the original
> behavior, is preferable to me. It might not be to others.
Yes, but Babel's hold time is a transient situation -- it's just a loop
avoidance mechanism tha
> I went looking to see how ahcpd did it, only to discover that it only
> sort of did, in that there is some support for client side delegation
> but no server side support in the code at present.
That's right. I've been planning to implement it on the server side,
but other things have been comi
>> I've been planning to implement it on the server side, but other
>> things have been coming up.
> No worries.
Let me know if you have plans to do something with it, and I can reorder
my todo list.
> As one of many examples of tricky policy issues
As usual, Dave, you're overcomplicating thing
> Does Babel support client roaming?
Client-roaming is a BATMAN-specific concept, that doesn't make sense in
Babel. There's no such thing as "client roaming" in Babel, since Babel
doesn't have the notion of "client" -- it's a pure peer-to-peer protocol.
So rather than using non-standard terms th
> So if I have APs connected together with
> Babel, can Babel help in some way when one AP (A) client migrates to
> another AP (B)? I would like that client keeps the same IP and all
> connections stay open. What it would be the way to setup this in a
> mesh using Babel to mesh APs together.
[...]
> OK, so such daemon which would allow roaming in combination with Babel
> in the sense I am hoping for does not yet exist. Do you maybe know if
> there is already some project hoping to implement that?
Not to my knowledge. Certainly not difficult to write if you're
interested.
(The people who a
Antonio, are you trying to be constructive, or do you just feel
a compulsive need to object to everything I say?
>> BATMAN is a commercial project,
> I just want to point out that BATMAN is an open source project
There is absolutely no contradiction between open-source and commercial.
RedHat Lin
https://groups.google.com/a/hacdc.org/group/Byzantium/browse_thread/thread/360ab7142f7001e5
(You'll need to click on "- Show quoted text -" to see the content.
Don't we all love Google Groups?)
-- Juliusz
___
Babel-users mailing list
Babel-users@lists
Hi Denis,
> An implementor of an authenticated Babel network is left with the
> following options:
> * Authenticate all packetes in the network (e.g. WPA).
Yes.
> * Selectively authenticate Babel packets with IPSec policy.
I don't think that can be made to work, at least not without some
proto
We've just had a long discussion with Denis on IRC. Here's a summary.
Short summary: this is very impressive work, and I'm very grateful to be
able to accept that as an experimental extension to the Babel protocol
(which is itself experimental). TLV types 11 and 12 are hereby assigned
to this ex
> Will this be going int the babeld mainline branch
I see no reasons (technical or legal) why it couldn't. However, I'm
badly overloaded right now, and security is pretty far from my research
interests, so unless you're volunteering, don't hold your breath.
(I personally think that fixing the is
> an excellent, huge, advance on the state of the art of secure mesh
> routing,
Well, Dave has a tendency to overstate things, but in this particular
case it is true that this is the first case in history that we have
a production-level, documented and open-source secure routing protocol
for mesh
>> For IPv4, you need to have a prefix on your interfaces that covers all
>> your neighbours, and the prefixes on all of your interfaces must be
>> disjoint.
> There are commits in RE-testing-0.99 addressing onlink nexthop
> management in zebra and babeld. The problem should be gone on Linux,
> co
>> There are commits in RE-testing-0.99 addressing onlink nexthop
>> management in zebra and babeld. The problem should be gone on Linux,
>> could anyone confirm?
Denis, why is this not used also by the RIP code? This would make it
possible to use Linux-style unnumbered interfaces with RIP, and w
>> K>* 0.0.0.0/0 via 134.157.168.126, eth0
> Is this the only default route around?
Good catch. There's also a default route advertised over Babel, and
restarting Quagga just got it to appear. Sorry I don't have time to
debug it right now.
-- Juliusz
__
>> Denis, why is this not used also by the RIP code? This would make it
>> possible to use Linux-style unnumbered interfaces with RIP, and would
>> make RIP behave the same as RIPng.
> Well, there may be multiple places where RIP nexthops are matched
> against connected prefixes. Perhaps, it's be
> the very exciting authentication code is now in there,
Please note that the auth TLV format is changing right as we speak
(commit f0f71a), so if you enable auth by default, warn your users about
the incompatibilities.
> 1) I liked the original add route/delete old route update scheme
> better t
> babel rxcost auto
> no babel rxcost
> no babel rxcost 100
> ! custom value, visible in running-config
> babel rxcost 100
> ! implicitly change rxcost in "auto" mode
> babel wired
> babel wireless
No objection, but I really think that route-maps are the right solution
for what Dave is sug
Dear all,
Babeld-1.3.2 is available from
http://www.pps.univ-paris-diderot.fr/~jch/software/files/babeld-1.3.2.tar.gz
http://www.pps.univ-paris-diderot.fr/~jch/software/files/babeld-1.3.2.tar.gz.asc
For more information about the Babel routing protocol, please see
http://www.pps.univ-par
>>> babel rxcost 100
Implemented, committed, tested, pushed, and documented.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
Hi,
The author of the attached bug report wishes to remain anonymous. I'll
puzzle over it later, in the meantime I'm sharing it with the list (with
his permission).
-- Juliusz
I am a bit new to babel but I am having an odd problem that looks like
a race condition in babel. I am running babel-1
> wifi already has enough jitter and delay built into it already, IMHO,
> as well as means to arbitrate contention to the medium.
No. The natural jitter of wifi will not prevent synchronisation of
different routers.
Floyd, S. and V. Jacobson, "The synchronization of periodic routing
mess
> I would like to point you towards a nice feature that Henning is
> currently implementing: DLEP - a (mostly routing protocol independent)
> framework for communicating settings and metrics between a radio and
> a routing daemon.
I reviewed an early draft of that.
As I understand DLEP, it is a s
> It looks like the internal babel route status and the kernel routing
> table can get out of sync when Node B regains comms while NodeA is in
> the process of banning the route.
I've had an extended e-mail exchange with the original reporter, and
spent all evening trying to reproduce the issue.
Dear all,
I'm currently experimenting with a new algorithm to improve the
stability of route selection in Babel. The algorithm is fully generic
(it should apply to any routing protocol that has flexible route
selection), and, after quite a few rounds of refinement, turns out to be
trivially simpl
> There is a kernel patch attached, which should fix the issue with IPv6
> default route delivery in CeroWrt (it does fix it on my PC).
I'm a little bit confused.
RAs are supposed to be ignored by routers -- the RFCs are very clear on
that. Linux obeys the RFCs, it will disable accept_ra when fo
> I will be changing the hardware wifi VO queue in cerowrt 3.3.8-10 to
> be sane (2 packets rather than 128).
That's probably going to kill your throughput for high-RTT links, unless
you also fix the lack of backpressure in Linux. It might break Babel on
networks with more than 120 nodes (the max
>>> with *your permission* I'd like to be marking babel packets in cerowrt
>>> as CS6 + ECN capable.
>> You're applying AQM to locally-originated data in order to compensate
>> for the lack of backpressure, and then falsely asserting ECN in order
>> to bypass the AQM policy.
> Have a sys call tha
> I can think of several other more silent metrics (like leveraging
> information from deep within minstrel and mac80211's states regarding
> transmission rates - or from within codel as to it's drop states) that
> would probably be more useful to use a base for metrics.
Yes, you've mentioned that
Hi,
I've just finished porting the Babel-Z extensions (radio diversity
routing) to Quagga. It's in RE-testing-0.99.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bab
Dear all,
Babeld-1.3.3 is available on
http://www.pps.univ-paris-diderot.fr/~jch/software/files/babeld-1.3.3.tar.gz
http://www.pps.univ-paris-diderot.fr/~jch/software/files/babeld-1.3.3.tar.gz.asc
Some important BSD fixes (thanks to Grégoire Henry) -- pure meshes are
now supported on BSD sy
> Babeld-1.3.3 is available on
Sorry for the invalid GPG signature -- it's a bounce that I resent, and
the signature got corrupted somehow. The signatures of the .tar.gz and
of the Git tag are correct.
-- Juliusz
pgpTQ7NKAVChr.pgp
Description: PGP signature
Hi,
I've just merged the smoothed-metric branch into master, and made
smoothed metrics the default. The defautl time constant is 4s, which is
very conservative; you'll probably want to increase this value if you're
seeing route flapping (-M). You can use '-M 0' to disable smoothing --
recommende
> Here, the value of c is in fact -1, but optimisations hide it. The
> culprit is gnc_string which returns -1 in case of error, but every
> error checking in this file checks (c < -1) for some reason.
[...]
> -return -1;
> +return -2;
The convention in this file is that -1 signa
>> -return -1;
>> +return -2;
>
> The convention in this file is that -1 signals EOF, while -2 signals an
> error. So the return value is correct, it's the handling of EOF that's
> broken.
@@ -71,7 +78,7 @@ getword(int c, char **token_r, gnc_t gnc, void
*closure)
c = skip_w
> Thanks for the fix! Should we add the patch to the FreeBSD port or wait
> for the next release?
Difficult to say. I'm waiting for feedback on another bug report, and
I'll make a 1.3.* release with both fixes. Unfortunately, I cannot give
you an ETA -- it depends on the reporter for the other b
For those of you allergic to Github, there's now a Gitweb server on
http://git.wifi.pps.jussieu.fr/
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
> in ip 0.0.0.0/0 le 0 deny
This should work.
> Any ideas? I have tried to look for a sample babeld.conf in the source
> distribution, couldn't find any... that would be very useful.
http://mid.gmane.org/7ive3ry9r7@lanthane.pps.jussieu.fr
This is linked from
http://www.pps.univ-par
> in ip 0.0.0.0/0 le 0 deny
I've just checked again, and it works just fine -- it rejects the
default route.
Are you sure that the babeld.conf file is being read (it's in /etc/)?
And that the spurious route is not being installed by DHCP or something
else?
-- Juliusz
__
> I still think that a sample babeld.conf should be shipped with the babel
> source code.
Well, the message I'm trying to send is that babeld "just works" -- you
don't need a babeld.conf for normal usage, you're only supposed to use
one if you have special needs.
(As mentioned on IRC, you appear
> git://src.anarcat.ath.cx/babeld
>
> it's a merge of the OpenWRT sample config file and the mailing list
> post.
Hmm, as you justly note, that's a wee bit too confusing.
I suggest the following:
- make the link to the Gmane posting to the Message-ID, which is more
stable:
http://mid.
> - revert the patch and don't use atomic route change on OS X (and
> probably old BSD)
That's what I would prefer.
> - implement another filtering mechanism (by comparing each route to
> the babel internal routing table ?
That won't work -- think about what happens when there's a static and
B
-paris-diderot.fr/~jch/software/babel/
This is a bug-fix release, and doesn't include the smoothed-metric
changes. If you're tracking the master branch, there is no need to
upgrade to this version.
Enjoy,
-- Juliusz Chroboczek
8 August 2012: babeld-1.3.4
* Disable atomic route change
> roadkiller# babeld -c /dev/null -d1
> Couldn't parse configuration from file /dev/null.
> roadkiller# touch /tmp/empty
commit d5e52adac4326f8b4bbb711c2645b1765efe2948
Author: Juliusz Chroboczek
Date: Sat Aug 4 16:29:16 2012 +0200
Fix typo in configuration parser.
> I'm working on building a mesh between a number of Ubuntu 10.04 boxes.
> I've managed to get babeld, ahcpd, and iptables all working together
> nicely, so I've got routes between all of them, internet gateways, the
> whole bit.
Cool. Is there a website describing your project?
> The question c
> babeld -g 33123 ...
> telnet ::1 33123
Yep, although that's not really meant for human consumption -- it's the
interface BabelDraw[1] and BabelWeb[2] listen on. I suppose it could be
extended for the kind of applications you envision, but you'll want to
coordinate with Gabriel, so that you don'
> I figured out what was throwing me off. AHCPd doesn't allocate the
> first IP address in the netmask. So for 10.99.1.32/27, it skips
> 10.99.1.32. Unfortunately, for 10.99.1.1/24, it skips 10.99.1.0.
Yes. In IPv4, the first and last addresses of a subnet are reserved
(the first is the network a
> Well, for one thing it would be more reliable to have a unix socket
> instead of a network port.
A Unix socket cannot easily be tunnelled using ssh or socat.
> Also, the output is not easy to parse as it is right now. First off,
> there is no delimitation that allows us to see when a listing is
> I don't have full control to my Internet provider router, so, I can't
> put babeld on this router. and I don't know how to give route to
> reach non-babel router from any babel node.
You need to put a static route on your Babel gateway (the Babel router
that's directly connected to your provide
> Netlink message: [multi] (msg -> "" 0), [multi] (msg -> "found address on
> interface eth1(3):
That's the output of ``babeld -d3'', which dumps every single activity
that the daemon performs. ``babeld -d2'' should usually be more than
enough -- it doesn't dump kernel-side activities (the "Netli
> Any babel people at the International Summit for Community Wireless?
>
> http://wirelesssummit.org/
Not to my knowledge, unfortunately. (I'm extremely busy this semester,
and Gabriel is starting at a new job; we could have asked Matthieu to
go, but we've been too busy to think about it.)
Sorry
Julien,
What you're suggesting is a pretty horrible hack, I'm not sure how
I feel about it.
> - eth0: linked to the FAI box
> - 2001:db8:1:3::5/64 scope global temporary dynamic
> - with a default route via fe80::1
> - eth1:
> - 2001:db8:42:2::1/64 scope global
> - radvd/dhcpd6 to other m
Quagga mainline; this should not be taken to imply that the work was
done by anyone else than Matthieu Boutier.
-- Juliusz Chroboczek
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
The current master branch appears to be working as designed, so I'm
planning to make a release of babeld-1.4.0 in the near future, perhaps
this week-end. If you have any bad experiences with the current master,
please let me know now rather than later.
-- Juliusz
Hi,
I've just added the ``-r'' flag to the master branch of babeld, which
causes router-ids to be drawn randomly rather than derived from the MAC
address of the first interface.
By default, babeld uses a persistent router-id. Most of the time that
works fine, but people are running babeld on nod
> Babeld 1.3.4 doesn't like channel interfering in configuration
Thanks for the report.
diff --git a/configuration.c b/configuration.c
index 64802a8..3b9368f 100644
--- a/configuration.c
+++ b/configuration.c
@@ -475,7 +475,7 @@ parse_ifconf(gnc_t gnc, void *closure)
free(t);
-
> Babeld 1.3.4 is dirtying routing table on our servers we can see the
> same destination as reacheable and unreacheable too
I've seen that happen when two babeld processes are running at the same
time. Normally, /var/log/babeld.pid protects against that, but it could
happen if you manually remov
> after a while dirty routes disappeared, it didn't seems deterministic
> how the problem appear, but heavy packets loss seems improve probability
> of problem
That's very strange. What happens when you shut down babeld cleanly
(using a plain kill, not kill -1 or -9)?
-- Juliusz
___
> >> after a while dirty routes disappeared, it didn't seems deterministic
> >> how the problem appear, but heavy packets loss seems improve probability
> >> of problem
> > That's very strange. What happens when you shut down babeld cleanly
> > (using a plain kill, not kill -1 or -9)?
> As you c
> What change between 1.3.4 and 1.4 ?
The main new feature is an algorithm for improving route stability
(decreasing flapping). It's been reported to work quite well, and
will be enabled by default.
There are some other minor tweaks (automatic detection of BATMAN
interfaces, random router-ids).
> One of the things I was hoping ahcp would gain one day would be a way
> to suggest a name to the ahcp server, and the ahcp server assign one,
> much like how dhcp works today.
I happen to prefer the model where the client registers its preferred
name with a dynamic DNS service rather than having
> The following patch uses the hostname instead of "alamakota"
[...]
> babelweb, to display a meaningful name automatically.
Thanks, applied with minor modifications.
(I've added some paranoia, since strncpy does not necessarily
NUL-terminate the destination. It should not matter in this
particu
> I had put up several of my thoughts towards extending the ahcp
> protocol somewhat, here:
> https://github.com/dtaht/dnsmasq-ahcp/blob/master/src/ahcp-extensions.md
Heh.
> Routing Protocol Extension
> Default gateway
Something similar was present in very early versions of AHCP, and was
remove
>> What application do you have in mind?
> Assume no global connectivity, where do you register?
With the DNS server advertised by AHCP?
> Since dnsmasq is rather common on just about everything embedded, and
> doesn't support a dynupdate facility
Oh, that's just an implementation detail. (Fam
> > Since dnsmasq is rather common on just about everything embedded,
> > and doesn't support a dynupdate facility,
> "Machines which are configured by DHCP have their names automatically
> included in the DNS and ___the names can specified by each machine___
> or centrally by associating a name
> Nexedi, will start porting babel to Windows,
Excellent news!
> unless someone already did it.
Not to my knowledge.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> Last summer, we have implemented a wired mesh network system based
> on babel which can provide stable IPv6 to all nodes of
> a decentralized cloud operation system. It works great.
Cool.
> A report will be published.
I'm looking forward to it.
> a- How can we prevent one babel participant to
> Nexedi, will start porting babel to Windows,
Excellent news!
> unless someone already did it.
Not to my knowledge.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> Last summer, we have implemented a wired mesh network system based
> on babel which can provide stable IPv6 to all nodes of
> a decentralized cloud operation system. It works great.
Cool.
> A report will be published.
I'm looking forward to it.
> a- How can we prevent one babel participant to
> > I told you last summer, I've come up with a cool way to measure
> > latency without increasing the amount of traffic much, so now it's
> > a simple matter of programming.
> awesome. in time for IETF?
Could do. I'm invited?
> I note that my (side?) of the work has been on reducin
>> Unfortunately, the maths of the problem is beyond me, so don't expect
>> anything more than some rough intuitions for the time being.
> I'd like to take a look if you don't mind, though I not sure algebraic
> number theory is the best suited branch of mathematics.
I think it's a control theor
> Some early mega-patches to run babel on Windows.
Jean-Paul,
Why are you using Cygwin rather than doing a native Windows port? My
experience with Polipo indicates that doing a native port is not much
more difficult than dealing with Cygwin, and yields cleaner and more
portable software at the e
The git repositories are back online, they're now on
git://git.wifi.pps.univ-paris-diderot.fr/babeld
git://git.wifi.pps.univ-paris-diderot.fr/ahcpd
Gitweb is on
http://git.wifi.pps.univ-paris-diderot.fr
The github mirrors are still online, of course.
(I'm trying to get a CNAME for the ol
> distribute-list dont-redistribute-v4 out wlan0
> ipv6 distribute-list redistribute-v6 out eth0
That should be eth0 in both cases, right?
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cg
After an exciting week-end of debugging, we've found a bug in the
smoothing algorithm that could significantly slow down convergence in
some cases. If you're running head with smoothing enabled, I strongly
recommend upgrading.
http://git.wifi.pps.univ-paris-diderot.fr/?p=babeld.git;a=commit;h=e
> There is a budget available in a public institution to sponsor a PhD
> student who would work on babel.
Do you have a topic in mind? Who would be the supervisor? What's the
deadline?
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth
> Of course rp_filter should be reset to its old value, and not to the old
> accept_redirects value.
Thanks, applied to both branches.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/ma
> Scaling dv to a million is something of a challenge.
With or without aggregation?
With aggregation, there should be no problem scaling to 500 subnets of
2000 nodes each.
> I would dearly like someone to work with on attempting to implement
> new metrics in babel.
We are working on that. The
> You will have to change babeld to only consider a slice of the network.
Manual aggregation can be done without changing anything. On a border
router for the network 192.168.42.0/24, you say
ip route add unreachable 192.168.42.0/24 proto static
and in babeld.conf,
out ip 192.168.42.0/24 g
> > So we thinked that it would be very useful if Babeld would suppert
> > a "team id" similar to AS number so we can just puts a line like
> > in team_id roman_routers_team_id deny and then set the same
> > team_id for every babeld router in rome
I strongly sympathise with your desire to drop Rom
> A single domain might have more border routers, so to avoid loops in
> redistribution of routes from a protocol to another (olsrd into babeld
> and babeld into olsrd) we need to identify the autonomous system these
> routes are coming from.
I still don't understand. Are the Babel and OLSR prefi
Hi,
As requested by the reseaulibre.ca folks, I've added an "done" marker
to the local interface that is sent after the initial dump. This
shouldn't break anything, since you should already be ignoring lines
that your software doesn't understand.
It is therefore now possible to say something lik
401 - 500 of 1070 matches
Mail list logo
