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 possible, point to some reference that may confirm
that batman is or is not operating at layer 2.5?
I'm writing a paper on mesh protocols and I need to know which
layer batman really operates in order to cite it correctly.
best regards,
--
--
:: Breno Jacinto ::
:: breno - at - gprt.ufpe.br ::
:: FingerPrint ::
2F15 8A61 F566 E442 8581
E3C0 EFF4 E202 74B7 7484
:: Persistir no difícil é a única maneira de torná-lo fácil algum dia. ::
Hi,
I've make a test today with Batman and La Fonera2.
I've a problem with the 169.254.0.0/16 routing. In fact, when i launch
batman, the 169.254.0.0/16 route with gate0 dev don't add correctly.
With this, i can't have reply on my request.
If i add manually the route with "ip route add table 254 to
169.254.0.0/16 dev gate0" this work.
How can i debug this problem.
I've use "-d 4" but i don't have see problem in log. I past you a quick
start without node connected :
root@Fonera:~# /tmp/batmand -o 2000 -g 5000 ath2 -d 4
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)
[ 30] Warning - batgat kernel modul interface (/dev/batgat)
not usable: No such file or directory
This may decrease the performance of batman!
[ 30] Warning - batgat kernel modul interface (/dev/batgat)
not usable: No such file or directory
This may decrease the performance of batman!
debug level: 4
originator interval: 2000
gateway class: 49 -> propagating: 4MBit/1024KBit
[ 70] schedule_own_packet(): ath2
[ 80]
[ 100] Adding route to 169.254.0.0/16 via 0.0.0.0 (table 254 -
gate0)
[ 2050]
[ 2060] Sending own packet (originator 5.0.0.1, seqno 1, TTL
50, IDF off) on interface ath2
[ 2060] schedule_own_packet(): ath2
[ 2060] ------------------ DEBUG ------------------
[ 2060] Forward list
[ 2060] 5.0.0.1 at 4151
[ 2060] Originator list
[ 2060] Originator (#/255) Nexthop [outgoingIF]:
Potential nexthops
[ 2060] No batman nodes in range ...
[ 2060] ---------------------------------------------- END DEBUG
[ 2060]
[ 2060] Received BATMAN packet via NB: 5.0.0.1, IF: ath2
5.0.0.1 (from OG: 5.0.0.1, via old OG: 5.0.0.1, seqno 1, tq 255, TTL
50, V 5, IDF 0)
[ 2060] Is an internet gateway (class 49)
[ 2070] Drop packet: received my own broadcast (sender: 5.0.0.1)
[ 2070]
[ 4160]
[ 4170] Sending own packet (originator 5.0.0.1, seqno 2, TTL
50, IDF off) on interface ath2
[ 4170] schedule_own_packet(): ath2
[ 4170] ------------------ DEBUG ------------------
[ 4170] Forward list
[ 4170] 5.0.0.1 at 6088
[ 4170] Originator list
[ 4170] Originator (#/255) Nexthop [outgoingIF]:
Potential nexthops
[ 4170] No batman nodes in range ...
[ 4170] ---------------------------------------------- END DEBUG
[ 4170]
[ 4170] Received BATMAN packet via NB: 5.0.0.1, IF: ath2
5.0.0.1 (from OG: 5.0.0.1, via old OG: 5.0.0.1, seqno 2, tq 255, TTL
50, V 5, IDF 0)
[ 4170] Is an internet gateway (class 49)
[ 4180] Drop packet: received my own broadcast (sender: 5.0.0.1)
[ 4180]
[ 6090]
[ 6100] Sending own packet (originator 5.0.0.1, seqno 3, TTL
50, IDF off) on interface ath2
[ 6100] schedule_own_packet(): ath2
[ 6100] ------------------ DEBUG ------------------
[ 6100] Forward list
[ 6100] 5.0.0.1 at 8109
[ 6100] Originator list
[ 6100] Originator (#/255) Nexthop [outgoingIF]:
Potential nexthops
[ 6100] No batman nodes in range ...
[ 6100] ---------------------------------------------- END DEBUG
[ 6100]
[ 6100] Received BATMAN packet via NB: 5.0.0.1, IF: ath2
5.0.0.1 (from OG: 5.0.0.1, via old OG: 5.0.0.1, seqno 3, tq 255, TTL
50, V 5, IDF 0)
[ 6100] Is an internet gateway (class 49)
[ 6100] Drop packet: received my own broadcast (sender: 5.0.0.1)
[ 6110]
^C[ 6610] Deleting route to 169.254.0.0/16 via 0.0.0.0 (table
254 - gate0)
[ 6610] Error - can't delete route to 169.254.0.0/16 via
0.0.0.0 (table 254): No such process
[ 6610] 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
root@Fonera:~#
In this log, a see "Adding route to 169.254.0.0/16 via 0.0.0.0 (table
254 - gate0)" but in the table 254, i don't have this route.
And when i stop BATMAN, the route can't be deleted because don't exist (
"Error - can't delete route to 169.254.0.0/16 via 0.0.0.0 (table 254):
No such process")
Someone can help me please ?
--
-----
FrancoFON CEO and Founder
Président de l'association FrancoFON
Communauté des foneros francophones - http://www.francofon.fr
Hi
I am trying to bring up open mesh with batman advanced. My network
configuration is as follows:
_____DSL cable_____Linksys Router____Cisco PIX______Switch______ open mesh 1
---------- open mesh 2 -------- client laptop
192.168.50.1 | _______ my PC
|_______
|_______
|_______
My IPs get automatically assigned by the PIX (In the subnet 192.168.50.0)
OPEN MESH 1 - configuration
===========================
1. I stop the routing daemons running on them. It has eth0, ath0, ath1 and
ath2 interfaces
where ath0 is in adhoc mode and ath1 and ath2 are in master mode
I create a bridge between all these interfaces (br0 - eth0, ath0, ath1,
ath2) and i run
udhcpc with br0 as an argument so that my bridge gets an IP from the
network
All other interfaces are given an IP of 0.0.0.0
My bridge gets an IP (192.168.50.5)
I have batman_core module and i update the
/proc/net/batman-adv/interfaces with br0 interface
echo br0 > /proc/net/batman-adv/interfaces
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 this node usign the same method of running udhcpc
but i am unable to
So I dont have an IP - but i dont worry about it now.
I have batman_core module and i update the
/proc/net/batman-adv/interfaces with br0 interface
echo br0 > /proc/net/batman-adv/interfaces
OBSERVATION
===========
Now when i check connectivity using battool i can ping between openmesh 2
and openmesh 1 using battool bp
My originators file indicate the mac of the other mesh node
E.g. on openmesh2
root@open-mesh:/proc/net/batman-adv# cat originators
Originator (#/255) Nexthop [outgoingIF]: Potential
nexthops ..
. [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: br0/00:18:0a:01:44:d0]
openmesh1 MAC (255) openmesh1 MAC [ br0]: openmesh1 MAC (255)
Associate a client
==================
I now try to associate a client to open mesh 2. Its IP request gets
forwarded to the wired network and it receives an IP
(192.168.50.6)
However i can't batping to it from either openmesh 2 or openmesh 1
Is something missing in my configuration?
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 the aggregation using the "--disable-aggregation"
option and verify whether it is related to the aggregation or not. Please
inform us about your experience.
- We noticed that quite some newly interested people have difficulties dealing
with batman since it requires NAT on the internet tunnel. Therefore the NAT on
the gate0 device will be configured by batman automatically. The iptables
binary is called to modify the outgoing NAT rules. This should make it easier
to get started with batman.
Regards,
Marek
Hi,
I could not find any type of "source" (aka batmand-howto.odt in this case) of
the batmand-howto written by Wesley Tsai and it seems to be partially
outdated. Because of that I decided to do a conversation of the PDF to LaTeX
so it can be changed more easily. It is quite rough at the moment, but I hope
that their is some kind of interest in it.
Current sources can be found at http://gitorious.org/projects/batmand-howto
and Simon and Marek have write access to mainline.
Best regards,
Sven
Hi,
the B.A.T.M.A.N. team is pleased to announce the availability of batman 0.3.1
a bugfix and maintenance release. As usual, we provide precompiled packages:
http://downloads.open-mesh.net/batman/stable/binaries/
as well as signed source tarballs:
http://downloads.open-mesh.net/batman/stable/sources/
As you may have noticed we slighty modified the folder structure to seperate
binaries and sources better. Also, we will keep providing older source
tarballs to support the various distributions better. In addition, we added a
release "bundle" folder which contains related source packages:
http://downloads.open-mesh.net/batman/releases/
Many people outside the B.A.T.M.A.N. team contributed to make this release
possible. Thanks to everyone that helped us.
Special thanks goes to Antonio and the open-mesh.com crew. They provided us
with bug reports, test beds and ideas to improve the overall batman
experience. Also, we wish to thank Sven Eckelmann for his endless stream of
patches and thoughtful hints.
During the past months the code received improvements all over the place.
Nearly all functions were touched. The packet aggregation was debugged and
improved. Areas with a high density of nodes suffered from bogus routing
information which was fixed. BSD compability was committed. Now, on a changing
route batman adds new routes to the kernel routing table before the old routes
are deleted to avoid race conditions. The batgat kernel module received many
fixes that improve stability. The makefile reduced the verbosity of its output
to allow easy distinctions between warnings and commands. The full changelog
can be retrieved here: http://open-mesh.net/log/trunk/batman?rev=1201
Happy routing,
Marek
Hello,
I apologize for the extremely naïve question. I have a couple of embedded devices (x86) running the latest version of OpenWRT. I would like to know if I could compile and run batman on these nodes and if so how.
Thanks in advance.
Kartik
Worried about the local copyright traffic cops slowing your internet
connection down? Concerned that your latest BitTorrent upload will get you
busted? The latest device from Leyio has
introduced<http://www.techradar.com/news/computing-components/storage/leyio-uwb-key-sh…>their
Personal Sharing Device (PSD) that lets you trade files with literally
a flick of the wrist.
Leyio's <http://www.leyio.com/> irritating website gives scant details on
the product, but there's enough information around to get a better
understanding of the device. It uses Ultra Wide Band (UWB) wireless
technology to transfer files between PSD users, and for us mere mortals with
only lowly USB sticks, it has support for those as well. There doesn't
appear to be any DRM restrictions, and Leyio's website appears to indicate
the just about any file can be shared.
So let's say this product takes off and many people own a PSD. If you wish
to share files with someone, just flick the device right at the person you
wish to share with, and that's it. Security concerns are addressed with
fingerprint technology. File-sharing doesn't get much easier than that.
Pricing hasn't been released yet. It's scheduled to be available in April of
2009, and Leyio's blog is scheduled to be launched in February.
http://www.slyck.com/story1825_FileSharing_with_a_Flick_of_the_Wristhttp://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://www.gulli.com/n…http://www.gulli.com/news/leyio-filesharing-offline-bald-2009-01-22/
Filesharing Leyio offline reality soon?
Eine interessante Entwicklung aus dem Hause Leyio, welche in naher Zukunft
auf den Markt gelangt, könnte die Filesharer-Szene aufmischen und zugleich
den schlimmsten Albtraum der Industrie wahr werden lassen. An interesting
development from the house Leyio, in the near future on the market, the
scene Fileshare it up at the same time, the worst nightmare of the industry
true.
Filesharing ohne PC, ohne P2P-Client und das höchste der Gefühle: Ohne der
immer währenden Furcht, die Piratenjäger der Content-Industrie auf sich
aufmerksam zu machen. Filesharing without a PC without P2P client, and the
highest of emotions without fear of ever-lasting, the pirate hunter of the
content industry to draw attention to itself.
All dies könnte womöglich bald so real sein, wie noch nie
zuvor.All this could possibly be real soon, as never before. Genauer
gesagt ab April 2009 - also in rund 3 Monaten. More precisely, from April
2009 - so in about 3 months. Aber tragen wir die bislang sehr spärlichen
Informationen erst einmal zusammen. But so far we have very scanty
information only once. Leyio hat ein kleines und handliches Gerät
entwickelt, welches an und für sich keine großartige Vielfalt bietet, da es
für sich allein relativ wenig kann. Leyio has a small and
handy<http://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://www.gulli.com/n…>device,
which in and of itself does not offer great diversity, because it
alone can be relatively low. Getauft wurde es auf den Namen "Personal
Sharing Device", was einige sicherlich zum Aufhorchen bringt. It was
baptized in the name of "Personal Sharing Device", which some certainly
Aufhorchen brings. Neben einem Touchscreen mit Fingerabdruckscanner verfügt
das Gerät über einen internen Speicher, welcher etwa 16 Gigabyte groß
ist.In addition to a touch screen with fingerprint
scanner<http://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://www.gulli.com/n…>,
the device has an internal memory, which is about 16 gigabytes in size. Des
Weiteren lassen sich USB-Sticks an das Gerät anschließen, ob weitere
Anschlüsse unterstützt werden, ist bislang unklar. In addition to
USB<http://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://www.gulli.com/n…>sticks
to the device, whether additional connections are supported, is so
far unclear. Das Herzstück des Geräts bildet jedoch die "Ultra-Wideband"
Funktechnologie, welche eine Reichweite von etwa zehn Metern bietet, auf
welchen mit 10 Megabyte pro Sekunde übertragen wird. The heart of the
device, however, the "Ultra-Wideband radio technology, which has a range of
about ten meters offers, what with 10 megabytes per second is transmitted.
Mit diesem Gerät könnte
Filesharing<http://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://www.gulli.com/f…>dorthin
wandern, wo die Content-Industrie wohl nie mehr dagegen vorgehen
kann. With this device could
Filesharing<http://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://www.gulli.com/f…>migrate
there, where the content industry on the other hand, probably never
can proceed. In öffentliche Parks, private Wohnzimmer, Schulen und sonstige
Plätze. In public parks, private living rooms, schools and other places. Der
User kopiert einfach zu Hause seine Daten auf den internen Speicher des
Geräts, oder alternativ auf einen (oder mehrere) mitgeführte USB-Sticks. The
user simply copied his data at home on the internal memory of the device, or
alternatively to one (or several) on board USB sticks. Trifft man einen
Freund, welcher unbedingt das Musikstück X haben möchte, so genügt eine
kurze Auswahl auf dem kleinen Gerät, um den Track mithilfe der
Funktechnologie zu senden - vorausgesetzt der Freund verfügt ebenfalls über
ein Gerät, welches diese Technik unterstützt. If you have a friend that is
necessarily the music piece X wants, suffice it to a short selection of the
small device to the track using the wireless technology to send - if the
friend also has a device that supports this technique. Falls nicht lässt
sich an das Personal Sharing Device einfach ein USB-Stick anschließen, auf
welchen die Daten dann kopiert werden. If not, is evident from the staff
sharing device simply connect the USB stick on which the data is then
copied. Man kann sich denken, wohin dies führen wird. One can imagine where
this will lead. "Personal Sharing Device Partys". "Personal Sharing Device
parties." Die ganze Clique bestückt ihre Geräte mit allen medialen Inhalten
und trifft sich zu einem gemütlichen Abend im Kino. The whole gang equipped
with all of their media content and meet for a leisurely evening at the
cinema. Beim Kaffee vor dem Film zücken alle ihre Geräte und der fleißige
Datenaustausch untereinander geht los - einzig begrenzt durch die Reichweite
des Funksignals. At the coffee before the film zücken all their equipment
and the hard data with each other is going on - only limited by the range of
the radio signal. Wer auf Nummer sicher gehen will, nutzt keinen USB-Stick
sondern nur den integrierten Speicher des Personal Sharing Device (PSD). Who
on the safe side, do not use a USB stick but the memory of the integrated
staff Sharing Device (PSD). Droht "Gefahr", so lässt sich das Gerät sperren,
und ist nur mithilfe des Fingerabdrucks des Besitzers wieder nutzbar zu
machen. Threaten "danger", it can disable the device, and is only using the
fingerprint of the owner to use again. Wie teuer das Gerät wird, ist bislang
nicht bekannt. How much the unit is not yet known. Eines dafür jedoch umso
mehr: Die Industrie hat Filesharing langsam aber sicher dorthin gebracht, wo
sie es nicht mehr bekämpfen können. One, however, even more so: The industry
has slowly but surely Filesharing there, where it can no longer fight. Mit
dem PSD von Leyio wird der Austausch so leicht, wie lange nicht mehr. The
PSD Leyio of the exchange so easily, like a long time. (
Firebird77<http://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://board.gulli.com…>)
(Firebird77)<http://74.125.43.100/translate_c?hl=de&sl=de&tl=en&u=http://board.gulli.com…>
http://www.slyck.com/story1825_FileSharing_with_a_Flick_of_the_Wrist