<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: Babel - bug ?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Right now, I have some other things to do. But I will make much more tests in few weeks, and I will let you know.<BR>
<BR>
I agree with you on security, at this moment I am using babel only for educational/research purposes so need to have any security at all.<BR>
<BR>
For now, thank you very much for support.<BR>
<BR>
Robert Lukan <BR>
<BR>
-----Original Message-----<BR>
From: Juliusz Chroboczek [<A HREF="mailto:Juliusz.Chroboczek@pps.jussieu.fr">mailto:Juliusz.Chroboczek@pps.jussieu.fr</A>]<BR>
Sent: Sat 6/7/2008 3:49 PM<BR>
To: Robert Lukan<BR>
Cc: babel-users@lists.alioth.debian.org<BR>
Subject: Re: Babel - bug ?<BR>
<BR>
> I am using default configuration of babel, just -l and -C are added<BR>
> on both sides. I really dont know if is this a bug, or I am doing<BR>
> something wrong. But is strange because, everything is working<BR>
> good. But in third maybe fourth iteration I came to that problem. As<BR>
> I can see in debug output, metric is 65535. If I restart babel<BR>
> everything is OK than.<BR>
<BR>
The link cost estimation hasn't converged yet. By default, Babel uses<BR>
a very large hello interval on wired links (see the -H option in the<BR>
manual page), you may want to reduce it if you want faster convergence.<BR>
<BR>
As a rough guide, link state convergence will happen after 3 hello<BR>
intervals. (Once link state has converged, route convergence will<BR>
happen faster -- 100 ms per hop is typical.)<BR>
<BR>
> Do you have any suggestions for using your protocol over limited<BR>
> bandwidth connection, or any other suggestion for my case ?<BR>
<BR>
Babel should work fine at 38 kbps, even if you reduce the hello interval.<BR>
<BR>
One thing you may want to experiment with is the -l flag, which will<BR>
cause Babel to react immediately to notifications from the link layer<BR>
(LCP in your case). Since I don't really understand cross-layer<BR>
notifications, it's marked as experimental in the manual page; let me<BR>
know how it works for you.<BR>
<BR>
> The only thing I am really missing its security, do you have any<BR>
> plan to implement security in babel. Or is there any easy way I can<BR>
> do it my self(begginer in C), if you dont plan. Lets say symmetrical<BR>
> key would be enough, as it is in olsr protocol.<BR>
<BR>
What is your attack model? I.e. what are you trying to protect against?<BR>
<BR>
If your link is insecure, an attacker may use simpler techniques to<BR>
poison your network than participating in the routing protocol. It<BR>
doesn't make much sense to secure Babel if you haven't secured ARP.<BR>
<BR>
Juliusz<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>