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
Hi,
I am struggling to setup proper routing policies on my local test mesh.
I have mentionned my setup previously so I won't repeat it here, but I
can expand by saying that most mesh routers export their default
routes. Not all of them have such a thing, but some do, in particular
carton
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
I forgot, here's my whole babeld.conf on roadkiller:
redistribute metric 128
in ip 0.0.0.0/0 le 0 deny
in ip 0.0.0.0/32 le 0 deny
The other nodes have just the first line:
redistribute metric 128
... but I do not want to assume I control the other nodes.
A.
--
The problem is not a lack of
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
On 2012-08-02, Juliusz Chroboczek wrote:
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
On 2012-08-02, Juliusz Chroboczek wrote:
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/)?
I am not sure. It is in /etc.
And that the spurious route is not being
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 to
On 2012-08-02, Juliusz Chroboczek wrote:
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
On Thu, Aug 2, 2012 at 10:02 PM, Juliusz Chroboczek j...@pps.jussieu.fr wrote:
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
sample configuration file available as patch here:
git://src.anarcat.ath.cx/babeld
it's a merge of the OpenWRT sample config file and the mailing list
post.
I removed the -X notes because I didn't understood what they were
refering to. I also toyed with the idea of removing the name of the
I noticed that the default route problem started to happen when I
reverted the RTF_PROTO2 patch. Running without the patch: no such
problem. Of course, reverting the patch brings me back to the point
where the FreeBSD node announces the mesh's routes as itself's again and
basically breaks the
Hi,
I have also found a significant problem with the mesh implementation in
FreeBSD. It seems that after a few announcements, the FreeBSD babeld
will start announcing routes it added to its routing from the mesh back
to the mesh as native routes.
What happens if you try to revert
On 2012-08-02, Gregoire Henry wrote:
Then, on a late night, I probably forgot to implement another filtering
mechanism. I don't know yet what to do:
- revert the patch and don't use atomic route change on OS X (and probably
old BSD)
- implement another filtering mechanism (by comparing
14 matches
Mail list logo
