I was fiddling with filtering out cero's /27s with the method
described in the previous thread, using the blackhole route to the
covering /24 and
redistribute ip 0.0.0.0/0 le 24 allow
in the conf file
and a command line of babeld -D -z3 -c /etc/babeld.conf ge00 se00 gw00
gw01 gw11 sw00 sw10
I was kind of hoping to be rid of most of P2P announcements also...
What do you mean by P2P? Everything's P2P in Babel. (We don't do
centralised protocols here at Babel Towers.)
If you mean the host routes (/32 and /128), you can say
redistribute local deny
to get rid of them. (You could
On Wed, Jul 02, 2014 at 06:58:59PM +0200, Juliusz Chroboczek wrote:
including the files generated by UCI, if any.
UCI does not generate any file, it builds a huge command-line (and yes,
this is a bug: https://github.com/openwrt-routing/packages/issues/33).
--
Gabriel
On Wed, Jul 2, 2014 at 9:58 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
I was kind of hoping to be rid of most of P2P announcements also...
What do you mean by P2P? Everything's P2P in Babel. (We don't do
centralised protocols here at Babel Towers.)
If you mean the host
Could you please send the full configuration? I.e. babeld's command line
in full, together with any files mentioned on the command line, including
the files generated by UCI, if any.
The simplest thing from my perspective...
Please send me the command-line that caused Babel to run amock.
The simplest thing from my perspective...
Please send me the command-line that caused Babel to run amock.
Sorry if that sounded dry, Dave. I do appreciate your help with that.
-- Juliusz
___
Babel-users mailing list
On Wed, Jul 2, 2014 at 11:05 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Could you please send the full configuration? I.e. babeld's command line
in full, together with any files mentioned on the command line, including
the files generated by UCI, if any.
The simplest thing
On Wed, Jul 2, 2014 at 11:09 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
The simplest thing from my perspective...
Please send me the command-line that caused Babel to run amock.
Sorry if that sounded dry, Dave. I do appreciate your help with that.
np! I have implemented
Nothing wrong with your config, Dave. I'd need a -d3 log of when Babel
gets into the feedback loop.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
My assumption is that I will blow up a goodly portion of my network,
but that the damage will be constrained to immediate hops only. ?
And: I should also get a tcpdump of what happens.
I am running a test series at the moment; I can do it after lunch
(T+1.5 hours). I'll need some popcorn for the
On Wed, Jul 02, 2014 at 11:14:51AM -0700, Dave Taht wrote:
attached is the command line generated and the babeld.conf
/usr/sbin/babeld -D -I /var/run/babeld.pid -z 0,128 -c /etc/babeld.conf -L
/tmp/babeld.log -C 'interface ge00' -C 'interface se00' -C 'interface sw00'
-C 'interface sw10'
11 matches
Mail list logo
