hey,
the problem semms to be found and very much trivial. the recent openWRT-release
(or especially the ixp4xx-port ?!) as well as the rather old slackware10.2
comes _without_ policy-routing compiled into the kernel. figure this out ... an
OS for embedded routers comes without advanced routing
ciao Elektra
need some hunters ? :)
we are strongly testing batmand 0.3-beta since its alpha revisions:
actually rv674 seems the best working one. Today rv719 is now in
testing...
We appreciate very much your work
-- Antonio
> I'm sorry to say that 0.3beta is not usable at the moment. We are in
Hi
coming from rv674 and approaching to rv719 the very first remarkable
difference I see is the "second" number (among parenthesis) in title
column
Router (#/255 #/64) issuing the command:
batmand -c -d 1 -b (or -d 2 looking for gateways)
There is a second sliding window (size) ?
thanks
-- Ant
Hello Marek,
we used rev718 ... from yesterday evening ... and all facts you mentioned are
right ... we disabled anything that enables batman to set or announce default
routes ... thats why we completely don't understand whats happening there. and
because the same things happens on a slackware/
Hi,
> r...@openwrt:/etc/init.d# route -n
> Destination Gateway Genmask Flags Metric RefUse Iface
> [...]
> 0.0.0.0 0.0.0.0 0.0.0.0 !0 0 0 *
> [...]
>
> batmand has been started with the following parameters: /usr/sbin/batmand
> -g 0 -r 0 eth2
as
I'm sorry to say that 0.3beta is not usable at the moment. We are in the
status of bug-hunting.
cu elektra
Hi Freifunk
I don't know if you have a typo in your mail but starting batmand as
/usr/sbin/batmand -g 0 -r 0 eth2
means you do not want set any default route (-r equal 0). Moreover, using
-g equal 0 means disabling gateway functionality for the node (normally -g
0 is used on a recpeater/client n
hello batmen, ;)
here in berlin NE we are about to update the batmands on our backbone to 0.3.0
. atm our net is mainly running on olsr and batman in parallel for testing
purpose.
after some changes in the net we got heavy HNA-hopping with olsr which is
related to the improper metric in our cas
Hi,
On Montag 15 Oktober 2007, Jan Hetges wrote:
> Hello everyone
> first: nice work, i'm impressed!
> i'm migrating 15 node olsr network to batman.
> right now all nodes run olsrd and batman-0.2 parallel,
> but there are some issues with "hidden nodes" (thanks to Axel for
> the bmx-reference-manu
Hello everyone
first: nice work, i'm impressed!
i'm migrating 15 node olsr network to batman.
right now all nodes run olsrd and batman-0.2 parallel,
but there are some issues with "hidden nodes" (thanks to Axel for
the bmx-reference-manual)
so my question, which of the switches from bmx (if any) a
10 matches
Mail list logo
