Hello Gargi,
your setup looks correct from what you've pasted. Some questions to find
the reason:
1. Have you set "up" all the interfaces by doing "ifconfig up"?
2. If you set IPs on br0 of open-mesh1 and br0 of open-mesh2 manually,
can they ping each other?
3. If yes (and configured within
On Mon, Jan 26, 2009 at 1:41 PM, Marek Lindner wrote:
> On Tuesday 27 January 2009 01:34:16 Gargi Purohit wrote:
>> I hope other than setting the interface "ath0" in
>> /proc/net/batman-advanced/interfaces - i dont
>> need any other configuration changes.
>>
>> Since I can batping between the two
Hi,
today I submitted the first patches into the 0.3.2 branch. Some of these
patches change the behaviour of batman:
- Aggregation is now enabled per default. We tested since a while now and
believe it is ready for a broader test. If you experience problems with your
routing you can disable t
On Tuesday 27 January 2009 01:34:16 Gargi Purohit wrote:
> I hope other than setting the interface "ath0" in
> /proc/net/batman-advanced/interfaces - i dont
> need any other configuration changes.
>
> Since I can batping between the two routers i guess the layer 2
> connectivity is established betw
On Sat, Jan 24, 2009 at 2:42 AM, Marek Lindner wrote:
>
> Hi,
>
> > OPENMESH 2 - configuration
> > ==
> >
> > 1. I stop the routing daemons. It has ath0, ath1, ath2 interfaces.
> >I again bridge these interfaces (br0 - ath0, ath1, ath2
> >
> >I try getting an IP for
Hi,
When batmand is launch and show this :
r...@fonera:~# /usr/bin/batmand -g 1mbit/1024 -o 2000 -d 3 ath2
Interface activated: ath2
Using interface ath2 with address 5.0.0.1 and broadcast address
5.255.255.255
B.A.T.M.A.N. 0.3.1 rv1203 (compatibility version 5)
Warning - batgat kernel modul inter
Hi,
> Adding route to 169.254.0.0/16 via 0.0.0.0 (table 254 - gate0)
> ^CDeleting route to 169.254.0.0/16 via 0.0.0.0 (table 254 - gate0)
> Error - can't delete route to 169.254.0.0/16 via 0.0.0.0 (table 254): No
> such process
> Deleting all BATMAN routes
> Interface deactivated: ath2
>
> The ro
Hi,
I've make a new test with the right syntax :
r...@fonera:~# /usr/bin/batmand -g 1mbit/1024 -o 2000 -d 3 ath2
Interface activated: ath2
Using interface ath2 with address 5.0.0.1 and broadcast address
5.255.255.255
B.A.T.M.A.N. 0.3.1 rv1203 (compatibility version 5)
Warning - batgat kernel mo
Hi,
> I read some posts on the web about B.A.T.M.A.N being (or becoming)
> a layer 2.5 protocol, which would make it operate below IP. But, at
> the website and some papers I read this is not mentioned, and the
> impression is that it is a regular layer 3 protocol. Can anyone please
> clarify
Hi,
> How can i debug this problem.
> I've use "-d 4" but i don't have see problem in log.
please use log level 3 to get more information on gateway and routing issues.
Level 4 is for the routing protocol.
> r...@fonera:~# /tmp/batmand -o 2000 -g 5000 ath2 -d 4
> Interface activated:
there is a 3 different derivitives of batman itslef, batman,
batman-advanced, and batman-experimental
batman - layer 3
batman-experimental - layer 3
batman-advanced - layer 2
there is also a kernel module called mod-batgat
On Mon, Jan 26, 2009 at 10:08 AM, Breno Jacinto wrote:
> Hello,
>
>I
Hello,
I read some posts on the web about B.A.T.M.A.N being (or becoming)
a layer 2.5 protocol, which would make it operate below IP. But, at
the website and some papers I read this is not mentioned, and the
impression is that it is a regular layer 3 protocol. Can anyone please
clarify, and if
12 matches
Mail list logo
