Hi all,
I've writed a batman-adv proto in according on new netifd system of
attitude adjustement release.
With this script the batman-adv configuration could be moved on
/etc/config/network file istead of /etc/config/batman-adv and the
/lib/batman-adv/config.sh is no longer required.
es.
config interface mesh
option proto bat
option device bat0
option interfaces 'wlan0 wlan1'
option gw_mode server
...
if someone think that my work could be useful and can provide a better
and elegant integration on openwrt please keep in touch.
--
Filippo Sallemi
Hi folks,
here the updated patchset conceived by Sven Eckelmann for netlink interface
creation. Since the first version the following has happened:
* the code has been rebased on top of master
* batadv_add_slave() / batadv_del_slave() / batadv_interface_free() were
renamed to follow general naming conventions
* introduced batadv_softif_destroy_netlink() dedicated to netlink deletion
* adding clear name separation between batadv_softif_init_early() /
batadv_softif_init_late()
Apparently, busybox "ip link" does not support creating interfaces through
netlink which is why I was unable to actually test the code in my OpenWrt
environments. If any if you know a way of making this work on OpenWrt or are
brave enough to run the code natively I'd be interested in getting feedback on
whether or not this works. I am certain the code was bug free and ran
perfectly fine before I touched it. :)
Cheers,
Marek
I'm a Computer Science Final Year Undergraduate student. We are a
group of Four students and are wanting to do our final group project
on B.A.T.M.A.N protocol. Can you help us with the simulating a simple
sample network.
Also I was thinking, If instead of Broadcasting the OGM Packets every
time into the network, we could broadcast them the first time a node
joins the network and then just Multicast the OGM packets to its
one-hop neighbours from the next time. So that their immediate nodes
are still informed about the existence of the node in the network.
This way we can reduce the unnecessary flooding of packets. Also when
a node moves out of the network its immediate node would know about it
much faster and can then broadcast it to other nodes.
Trying to do our final year project in this area.
Also can someone suggest us some ideas to work upon as our final year
Project. :)
--
Ashwin
All,
I am trying to create a WiFi repeater using hardware that cannot accommodate a
normal "bridged repeater" mode. Is it possible to create this type of repeater
using BATMAN adv?
Thanks
Rip
Hello David,
here you have just a single patch which is fixing a pesky bug that I introduced
within a patchset recently sent to net-next/linux-3.9.
It is not big, but I think it is worth fixing the new behaviour before it
gets released.
Please pull or let me know if there is any problem.
Thanks a lot,
Antonio
The following changes since commit cef401de7be8c4e155c6746bfccf721a4fa5fab9:
net: fix possible wrong checksum generation (2013-01-28 00:27:15 -0500)
are available in the git repository at:
git://git.open-mesh.org/linux-merge.git tags/batman-adv-for-davem
for you to fetch changes up to a7966d908ae8472e8183496916b7baec5f65b3a6:
batman-adv: fix local translation table output (2013-01-28 20:46:03 +0100)
----------------------------------------------------------------
Included changes:
- fix recently introduced output behaviour
----------------------------------------------------------------
Antonio Quartulli (1):
batman-adv: fix local translation table output
net/batman-adv/translation-table.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
I hereby bring you network coding in batman-adv (in its fourth revision).
This allows a relay to send two packets (to two destinations) in a single
transmission. Tests[1] have shown an increase in throughput up to 1.6
under the right circumstances.
For this to work, you will need to compile batman-adv with
CONFIG_BATMAN_ADV_NC=y and a wireless interface with working
promiscuous mode. The rest is taken care of by batman-adv and the
following patches.
Patch 5/6 depends on my previous patch on the mailing list:
"Return reason for failure in batadv_check_unicast_packet()"
[1] http://www.open-mesh.org/projects/open-mesh/wiki/2011-08-18-network-coding-…
Martin Hundebøll (6):
batman-adv: Add the initial code for network coding.
batman-adv: Detect coding nodes and remove these after timeout
batman-adv: Buffer unicast packets before forward.
batman-adv: Code and transmit packets if possible.
batman-adv: Save overheard and tx packets for decoding.
batman-adv: Receive coded packets and decode them.
Makefile | 2 +
Makefile.kbuild | 1 +
bat_iv_ogm.c | 5 +
compat.c | 10 +
compat.h | 1 +
debugfs.c | 18 +
gen-compat-autoconf.sh | 1 +
main.c | 6 +
main.h | 12 +-
network-coding.c | 1832 ++++++++++++++++++++++++++++++++++++++++++++++++
network-coding.h | 123 ++++
originator.c | 6 +
packet.h | 33 +
routing.c | 31 +-
send.c | 5 +
soft-interface.c | 14 +
sysfs-class-net-mesh | 8 +
sysfs.c | 6 +
types.h | 136 ++++
19 files changed, 2240 insertions(+), 10 deletions(-)
create mode 100644 network-coding.c
create mode 100644 network-coding.h
--
1.8.1.1