Axel Neumann wrote:
> > Does that mean that your svn directories and git repositories at
> > open-mesh.org can be dropped
>
> In the long term yes! But please not right now. I want to update links in
> other repositories like openWrt first and give users some time to update
> their checkout as well so that the build process does not fail. Lets say
> in February.
Ok, sounds good.
> > (at least it seems that no branch has common
> > ancestors with your branches)?
>
> For branches/bmx-0.3.x/ I used git-svn to create the git repository which
> I expected to create common ancestors. Some confusion leaked in when I
> moved the directory from trunk/batman-experimental to branches/bmx-0.3.x
> (some deleted files like LIESMICH,.. were not deleted which I fixed with
> the last git commit).
The problem is that you (sry, no offence meant) did a quite bad job to convert
it. bmxd.git has these weird git-svn-id lines in the commit messages, "random"
commiter names+mails, missing parts of the history, dangling symlinks, ...
Please take a look at git://git.open-mesh.org/ecsv/test/bmx.git
I don't say that it is the holy grail of svn-to-git conversation, but I think
it could be a better conversation than your bmxd.git
Best regards,
Sven
Hi all,
as promised, I have completed the analysis of the protocol overhead
providing also simulation results with and whitout the OGM aggregation
mechanism activated. As anticipated the results shows that aggregation
works well in reducing the overhead. In attachment the report
(OGMoverhead.pdf).
In attachment you will also find a draft/proposals of a new routing
approach. It is based on the collection of more link parameters (the
current TQ, bit-rate and node-load) to write in OGM at each hop. This
permit to develop a more thorough metric and can open new room of
improvement such multi-path routing.
Any comment/suggestion is welcome!
Regards.
--
Daniele Furlan
Hello..
I succesfully configured a batman-adv mesh to add access points to our
existing wired lan. I am using Openwrt 10.04 and batman-adv 2010.1.0.
DHCP and everything works as expected. Any wired or wireless client
connecting to the network gets an IP from a DHCP server hooked into the
switch etc etc.
Our Network configuration:
8 batman-adv routers with a wireless mesh with two or more of the
routers having a wired connection directly to the switch. In this case,
the 8 routers decide to pick one of the "plugged in" routers as a
gateway to avoid bridge loops. This is fine.
I have been running into issues with wired clients however.
When a wired client plugged into the switch tries to contact a wired
client plugged into the same switch, the packets manage to get lost. I
believe they are are going through the wireless routers plugged into the
same switch.
Instead of going like this..
PC 1 ----> switch1 ---> PC 2
they seem to be going like this... (my guess).
PC 1 ---> switch1 ---> wireless router 1 ----(wireless mesh link)---->
wireless router 2 ----> switch1 ---> PC 2.
I think this is because the translation tables on the bat node are
announcing that even the wired clients are connected to them.
This is causing extreme delays even in wired clients. Any help will be
appreciated. Should I enable STP in on the switch ports ?
- Vinay
On Monday 28 February 2011 20:15:05 hlabishi kobo wrote:
> Thanks again for your reply sven, but i think my code might have maybe
> you a different view of wht i want to do, see below.
> The idea is to prioritize recently received OGM's thus giving them
> more weight for the routing decisions. suppose you have sliding window
> of 10, a link A records [1111100000]= 5 and link B records
> [0000001111] = 4, currently this will be used towards the calculation
> of local TQ. in the proposed method we want to add the indexes on
> which an OGM was received in that interval. from the example above we
> would have link A 1+2+3+4+5+6= 21 and link B 7+8+9+10 = 34. this
> actually what i meant by counting and adding indexes.
I know what you want, but it seems (judging from your "implementation") that
you don't know how to write that down. I hope that I gave you enough
information to show you why your implementation isn't what you want.
The last part should help you to implement it the right way and to understand
what the values represent and how you should operate on them.
Best regards,
Sven
---------- Forwarded message ----------
From: hlabishi kobo <hlabishik(a)gmail.com>
Date: Sun, 28 Nov 2010 22:06:01 +0200
Subject: Fwd: BATMAN routing
To: lindner_marek(a)yahoo.de
Hi
Thank you very much for your reply. The reason why i sent this to you and
your colleague is that i have tried the mail list before and all my post
kept on being returned, i used this address
b.a.t.m.a.n-owner(a)lists.open-mesh.org. I would really appreciate it if this
can reach the mailing list public (i will keep on trying). i will send you a
follow up on the full explanation of the concept like you requested.
Regards
Hlabishi
---------- Forwarded message ----------
From: <b.a.t.m.a.n-owner(a)lists.open-mesh.org>
Date: Sat, Nov 27, 2010 at 12:58 AM
Subject: Fwd: BATMAN routing
To: hlabishik(a)gmail.com
Message rejected by filter rule match
---------- Forwarded message ----------
From: hlabishi kobo <hlabishik(a)gmail.com>
To: b.a.t.m.a.n(a)lists.open-mesh.org
Date: Sat, 27 Nov 2010 00:58:09 +0200
Subject: Fwd: BATMAN routing
---------- Forwarded message ----------
From: Marek Lindner <lindner_marek(a)yahoo.de>
Date: Fri, Nov 26, 2010 at 5:23 PM
Subject: Re: BATMAN routing
To: hlabishi kobo <hlabishik(a)gmail.com>, Linus Lüssing <
linus.luessing(a)web.de>
Cc: siwu(a)hrz.tu-chemnitz.de
Hi,
welcome to the project! :-)
> Firstly my apologies for sending this email to your personal email. My
name
> is Hlabishi Isaac Kobo at the, an Msc computer science student at the
> University of the Western Cape in South Africa, I am doing a research on
> routing in a hybrid (combination of static and mobile dynamic routers)
> mesh.
I don't see a good reason to apologize, just wondering why you are not
sending
this mail to the public list ?
> I want to use the mesh potatoes as well as the batphone (android
> version of batman) to create a mesh model.
What is the "batphone" ? A project name or a nick name you invented ? :-)
Note: Various tests have shown that running a mobile device
(smartphone/tablet/etc) in adhoc mode plus running a mesh protocol on top is
a
battery killer, hence not practical in real world scenarios (in addition of
the hassle to install and configure the mesh software on each and every
device). This was one of the main reasons to start developing batman-adv as
it
allows mobile devices to take advantage of the mesh (e.g. roaming) without
having to run the mesh on the device itself.
You might be aware of this - I am just mentioning it because many people are
not.
> First we say the recently received OGMs will give a clear indication on
the
> reliability on the link, so we give the recently received OGMs from the
> sliding window a priority in deciding the best next hop link towards a
> destination. We want to count and add the indexes were an OGM was recorded
> in an interval (seconds), (hence the recently received OGM will have more
> weight). At the end the link with more recent OGMs will have more weight
> and hence become the current best link.
This is a good idea. We are in the process of redesigning the current
protocol
and welcome any input. Giving older OGMs less "weight" was also one of the
ideas we had. Would you mind explaining your concept in greater detail ?
> I went through the source code so many times and I got few questions about
> this:
Are we talking about the batman daemon source code or the batman-adv kernel
module ? All my answers will refer to the kernel module as this is the place
where most of the development is going on at the moment.
> 1. What structure is used to keep track of the sliding window? If its the
> has how does it get updated based on the sliding packet range?
Each "struct orig_node" has a bitarray to keep track of its own seqnos
repeated by its neighbors (bcast_own) and each "struct neigh_node" having a
bitarray for its own OGMs (real_bits).
> 2. How are the OGM's recorded, is in a form of binary where 1 will
> represent the received OGM and 0 otherwise?
Correct.
> 3. I looked in the source and still not sure of where the ranking
decisions
> are made, can you enlighten me on that?
You mean which function changes the route when a better neighbor was found ?
That would be update_orig() in routing.c.
> On the second approach we want to use mac layer stats to estimate the
> signal strength and probably the congestion rate of the top N ranked
links.
> We acknowledge the fact that usually links with lower signal strength will
> loose more OGM's which results in an automatic low rank, however in a
> frequently changing topology, current signal strength is crucial. We plan
> to use SNR or RSSI in this case.
The concept is known since a while but nobody has implemented it so far
because its implementation is fairly complex. Do you have an idea how it
should work in the end ?
> 1. How can i get the RSSI/LQI of th neighbor links?
I don't get this question. You intend to use RSSI but you don't know how ?
> I would really appreciate your opinions and advices in this regard more
> specially how to go about implementing changes in BATMAN protocol.
This is a little abstract. Usually, we discuss specific concepts / ideas in
our
IRC channel or on the mailing list long before starting to implement them.
The
past has shown it is often better to let other people dive into your ideas
and
comment because routing is a rather complex subject.
As I mentioned above: We are in a redesign phase right now and welcome
anyone
interested to join. As the next step we envisioned a collection of routing
scenarios in which the current implementation behaves poorly. All routing
protocol changes have to go through this collection of scenarios to estimate
its impact. What do you think about this idea ?
Regards,
Marek
Hi,
Linus has some problems sending mails to the list, so I forward his reply.
Cheers,
Marek
============================================
Hi Vinay,
On Fri, Feb 25, 2011 at 08:44:33AM -0500, Vinay Tharigopula wrote:
> Marek..
>
> I got the binaries from the openwrt prebuilt packages. However,
> now
> I rebuilt the image and built batman-adv 2011.myself. I will try
> this now and let you know.
>
> However, now I am running into a much bigger issue. If two
> routers
> are plugged in to the same switch, bridge loop avoidance doesnt
> work
> and both of them are stopping responding to pings.
Could you try "batctl ping" too and check whether this is working
or not.
If that's working but the normal pinging is not, then it should be
a layer 3 problem - in that case we'd need the outputs of "ip
route show" and "ip address show".
If batctl ping is already not working then "batctl o" and "batctl
if" output will be interesting.
>
> Here is my config.
>
> bat0 if:
> wlan1: active.
>
> wlan1: Mesh Network.
>
> wlan0: Infrastructure network.
> eth0 : 4 lan ports
> eth1: 1 wan port
>
> br-lan : wlan0 eth0 eth1 bat0
Hmm, that looks sane and correct, should work like that.
Is there anything weird in the output of "dmesg"? Any errors or
warnings?
Cheers, Linus
Hello *,
I set up batman-adv-2010 on OpenWRT (backfire 10.3.x). Mesh interface
is wlan0 and another non-batman-LAN is connected to eth0. non-batman
clients should connect via the eth0 interface. (Full description and
network diagram here:
https://forum.openwrt.org/viewtopic.php?pid=129226#p129226 ).
After setting up batman-adv 2010.x with
batctl if add wlan0
ifconfig wlan 0 0.0.0.0
ifconfig bat0 192.168.10.2 (previous ip address of wlan0)
ifconfig bat0 up
I have to configure a bridge (according to quick start guide
http://www.open-mesh.org/wiki/batman-adv-quick-start-guide) because I
want batman-adv to announce MAC-addresses connected to eth0 (see network
diagram):
brctl addbr mesh-bridge
brctl addif mesh-bridge eth0
brctl addif mesh-bridge bat0
ifconfig eth0 up
ifconfig bat0 up
ifconfig mesh-bridge up
Although the translation tables (global and local) seem fine in this moment, at the same momentof bringing up the bridge I cannot send any more packets through bat0 or ent0.
Both don't even reply to a ping.
Network setup and outputs of ifconfig onhttp://www.open-mesh.org/wiki/batman-adv-quick-start-guide
Any hint is appreciated.
Stefan
Wireless Battle Mesh v4 - Call for papers
=========================
Wireless Battle Mesh v4 is at hand and it is time to bring together the
agenda. To avoid last year's dynamic process which gave us a true talk
marathon on the very last day of WBMv3 all talks / workshops / panel
discussions shall be announced beforehand.
Tracks
====
In order to broaden the horizon of the event we are going to split the event
into different tracks:
* The technical track is taking place throughout the week (monday till friday)
which mainly focuses on rather technical topics like:
=> routing protocol internals
=> implementations / development of "cool" algorithms
=> hands-on routing / multicast / roaming / convergence speed / etc
=> secuity aspects in mesh networks
=> your idea here
* The weekend (saturday & sunday) is reserved for the applications track which
aims to showcase applications that run on top of the mesh. It is not important
whether protocol X or Y is deployed and how it is implemented, the question
is: What can we do with the mesh once it is there ?
=> VoIP in the mesh ?
=> fast desaster recovery ?
=> artistic projects ?
=> your idea here
The idea of these tracks is to provide a ground for the different developers /
projects to exchange ideas on technical aspects of algorithms /
implementations / optimizations as well as organizing an exchange with mesh
network users who care less about how the mesh itself works as long as their
application can do its job. On the other hand the weekend serves as an entry
point for people to learn about what you can actually do with mesh networks.
Submission
=======
To allow an efficient handling of your submission, please provide the following
information and send them to me directly in form of an email:
* your name
* the track you are interested in
* the type of your slot (talk/workshop/panel discussion)
* your topic headline
* your topic description which can brief (does not need to exceed a couple of
lines) but should provide a reasonable summary of your talk
* the dates of your stay at the event + (optional) preferred day for your slot
* length of the slot if you wish to do a workshop (all other slots will be
limited to one hour - notify me in advance if you think that is not enough for
you)
Deadlines
======
Submissions are accepted until and including the 28th of February. Everyone
missing this deadline still has the opportunity to apply for a lightening talk
slot. These slots can be acquired by simply contacting me during the event.
The list of registered lightening talks will be published in the battlemesh
wiki.
The final program will be made available in the aforementioned wiki during the
first week of March.
If you have any question or suggestion, please let me know.
Regards,
Marek
Hi,
due to popular request I'm proposing 2 patches to rename "batman_if" to
"hard_iface". The former was rather confusing/misleading whereas the latter
expresses its function clearly.
Note: As this struct is used all over the code it will create quite a rebase
effort for everyone with external patches. Keep in mind that "sed" is your
friend. ;-)
Cheers,
Marek
Hi,
here comes the next batch of changes to make the code "rcu safe". It won't be
the last one but should make all follow-ups much easier.
Regards,
Marek