Hello, i have a problem using batman-adv. At the moment i use v0.1, but i had the same problem when trying the svn version 1241.
All the nodes send their ogm, but none does recieve any of these. What i did on all nodes is:
iwconfig $wlaninterface essid batman mode ad-hoc and then echo "$wlaninterface" > /proc/net/batman-adv/interfaces echo 15 > /proc/net/batman-adv/log_level
cat /proc/net/batman-adv/log after that shows somethink like this:
Adding interface: ath0 Can't activate module: the primary interface is not active Sending own packet (originator 00:18:84:14:48:e5, seqno 1, TTL 50) on interface ath0 [00:18:84:14:48:e5] Sending own packet (originator 00:18:84:14:48:e5, seqno 2, TTL 50) on interface ath0 [00:18:84:14:48:e5] Sending own packet (originator 00:18:84:14:48:e5, seqno 3, TTL 50) on interface ath0 [00:18:84:14:48:e5]
I also tried to set the channel on all nodes, but with no effect.
Maybe someone can tell me what i do wrong.
Thank you,
Hi,
the same problem when trying the svn version 1241.
please don't use the trunk for batman-adv as it has a serious bug that requires fixing.
Adding interface: ath0 Can't activate module: the primary interface is not active
I think this message gives you a pretty good idea of what the problem might be. I guess your interface ath0 is not up & running. Try an "ifconfig ath0 up". :-)
Regards, Marek
2009/3/31 Marek Lindner lindner_marek@yahoo.de:
Hi,
the same problem when trying the svn version 1241.
please don't use the trunk for batman-adv as it has a serious bug that requires fixing.
Ok :)
Adding interface: ath0 Can't activate module: the primary interface is not active
I think this message gives you a pretty good idea of what the problem might be. I guess your interface ath0 is not up & running. Try an "ifconfig ath0 up". :-)
Actually i already tried that and it didn't change anything. And when that is really the problem, why is the module than even starting to send messages?
Greets,
On Wednesday 01 April 2009 03:13:01 Kai Timmer wrote:
Actually i already tried that and it didn't change anything. And when that is really the problem, why is the module than even starting to send messages?
Athough the interface is down batman still runs internally to trigger events, timeouts, link quality updates, etc. That does not mean the packets go out although the logs might indicate packets were sent. You can easily verify whether the packets leave the system or not by using the battools or tcpdump.
I agree with Simon: If you experience connection problems first make sure that ping & friends run smoothly.
Regards, Marek
Hello Kai,
Quoting Kai Timmer email@kait.de:
Hello, i have a problem using batman-adv. At the moment i use v0.1, but i had the same problem when trying the svn version 1241.
All the nodes send their ogm, but none does recieve any of these. What i did on all nodes is:
iwconfig $wlaninterface essid batman mode ad-hoc and then echo "$wlaninterface" > /proc/net/batman-adv/interfaces echo 15 > /proc/net/batman-adv/log_level
cat /proc/net/batman-adv/log after that shows somethink like this:
Adding interface: ath0 Can't activate module: the primary interface is not active
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
are you sure you set ath0 up?
ifconfig ath0 up
should do the trick.
If you start experimenting, a good idea is to first check the connectivity without batman. Just set some IP addresses on the wifi devices and ping the other nodes to make sure your adhoc network works. If it does, you can activate batman-adv. :)
good luck, Simon
b.a.t.m.a.n@lists.open-mesh.org
-
Kai Timmer -
Marek Lindner -
Simon Wunderlich