B.A.T.M.A.N November 2016

b.a.t.m.a.n@lists.open-mesh.org

19 participants
48 discussions

Re: [B.A.T.M.A.N.] i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) .
by Linus Lüssing 09 Nov '16

09 Nov '16

On Wed, Nov 09, 2016 at 04:50:45AM +0100, johnzeng via B.A.T.M.A.N wrote: > Date: Wed, 09 Nov 2016 11:50:30 +0800 > From: johnzeng <johnzeng2013(a)yahoo.com> > To: Simon Wunderlich <sw(a)simonwunderlich.de> > CC: b.a.t.m.a.n(a)lists.open-mesh.org, Sven Eckelmann <sven(a)narfation.org>, > Martin Hundebøll <martin(a)hundeboll.net> > Subject: Re: [B.A.T.M.A.N.] i have a question ? How many relay nodes can be > supported at NetworkCoding ( mtu 1546 ) . > > I can understand network coding , it will be > same as proxy or Intermediator at Layer 2 , Maybe there is a complete misunderstanding what "network coding" is? Maybe an easier expression would be "packet mixing" or "magic packet mangling" [1]. Any code that does something with networking is usually *not* "network coding" (at least in this context here). Have a look at the links Sven has provided earlier. > > > Your meaning : Batman-adv can build Similar > mechanism ( Intermediator ) via intermediator , it wil be relay based real > application packet ( not relay based Broadcast packet) Just try it :-). Compile batman-adv *without network coding* with your A-B-C scenario and see how it magically works, too :-). Regards, Linus [1]: Please no expert hit me :D. I know, ultimately, network coding would replace packet based networks, if I remember Frank's talk in Leipzig correctly https://www.youtube.com/watch?v=yluj7e_rfVE

2 1

Re: [B.A.T.M.A.N.] i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) .
by Linus Lüssing 09 Nov '16

09 Nov '16

On Wed, Nov 09, 2016 at 04:56:52AM +0100, johnzeng via B.A.T.M.A.N wrote: > Date: Wed, 09 Nov 2016 11:56:36 +0800 > From: johnzeng <johnzeng2013(a)yahoo.com> > To: Simon Wunderlich <sw(a)simonwunderlich.de> > CC: b.a.t.m.a.n(a)lists.open-mesh.org, Sven Eckelmann <sven(a)narfation.org>, > Martin Hundebøll <martin(a)hundeboll.net> > Subject: Re: [B.A.T.M.A.N.] i have a question ? How many relay nodes can be > supported at NetworkCoding ( mtu 1546 ) . > > if Relay mode is based on Layer 3 ( route or > >Nat ) , it will be very complex and Infeasible at large wifi network No, batman-adv has nothing to do with layer 3. For clients in batman-adv it all looks like one, big switch. It does that not by layer3 routing or layer3 NAT'ing, but by encapsulating frames in its own headers.

1 0

Re: [B.A.T.M.A.N.] i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) .
by Simon Wunderlich 09 Nov '16

09 Nov '16

On Tuesday, November 8, 2016 11:55:14 AM CET johnzeng via B.A.T.M.A.N wrote: > Hello Dear Sven and Martin: > > Thanks for your advisement > > I hope to aviod Excavation > of underground pipeline in the smart community or Park . > > if Batman-adv can support > smart relay ( networking code ) at mesh network really , and it will be > very valuable for us . Hi Johnzeng, why are you insisting on using network coding? Batman-adv can do relay without network coding enabled, this is part of the basic mesh technology. Network Coding (or CATWOMAN) was research project/proof of concept implementation which isn't actively maintained right now. But from what I understood, your setups can be supported with "standard" batman-adv mesh. Thanks, Simon > > i think one of core > valuable point is relay mode and Client roaming > > i prepare to build more ap > evironment and test for the part later > > > > > As market competition intensifies, > > the gap between similar > productsis getting smaller and smaller, > > likewise the evolution of > growing homogenization trends within the industry. > > > > i hope we can find > valuable point for Blue Ocean each other . > > if you have some different > point , and I would be happy to be the first and build win-win mode each > other . > > > Best Regards > > Tiger > > > Hi, > > > >> When i compile the part , whether i need make > >> CONFIG_BATMAN_ADV_BATMAN_V=y at batman-adv-2016.2 > > > > 2016.2 is "old". And BATMAN_V has nothing to do with network coding. > > > >> i read some detail about NetworkCoding , my understanding : > >> > >> every relay node will detects neighbors packet at promisc mode and > >> combine these packet into a single transmission , > > > > I think Martin can help here. He also provided some documentation: > > > > * https://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding > > * > > https://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding-technica > > l * > > https://downloads.open-mesh.org/batman/papers/batman-adv_network_coding.p > > df * > > https://vbn.aau.dk/da/publications/catwoman(214ee21a-e786-495d-85c9-3efac > > 4718ead).html * > > https://downloads.open-mesh.org/batman/misc/wbmv4-network_coding.avi > > > > And it will not try to forward each packet is overheard. Instead it > > will try to find coding opportunities which it then uses to forward > > its own packets in less transmissions (by using packets which the > > other nodes should already know). > > > >> batctl nc 1 > >> echo 1 > /sys/class/net/bat0/mesh/network_coding > >> ip link set dev wlan0 promisc on > >> ip link set dev wlan0 mtu 1546 > > > > Your cards/drivers will most likely not even support promiscuous mode. > > Some of them require to have an monitor mode interface at the same time > > and > > some of them will simply not work. > > > > You can test it by simply checking what tcpdump is showing you on the > > underlying interface (wlan0). If it doesn't show you the packets between > > two other nodes then promiscuous mode is not working for you. > > > > The feature itself is not used very often (Martin, please correct me > > here). > > It is not enabled by default because it is not making things "better" all > > the time [1]. So it is also not tested as much as other components in > > batman-adv and you should think first if it is really useful for your > > scenario/HW. I knew at least from some Freifunk communities played around > > when it was enabled by default but had to revert when they experienced > > "non > > functional mesh links" (nothing more about it is known to me - sorry > > Martin).> > >> if i send a packet from host A to hostC via hostB, whether hostB will > >> open relay mode at layer2 . > > > > I completely failed to parse this. > > > > batman-adv will send your data from hostA to hostC via hostB when the TQ > > value for the link "from hostA to hostC via hostB" is higher than the TQ > > value for the link "hostA to hostC directly". This has nothing to do with > > network coding and is a standard feature of batman-adv (this is actually > > what it is about). > > > > network coding can only (when lucky) try to combine some packets - but > > this will only work when promiscuous mode is actually working and the > > nodes can overhear packets. Otherwise it will (in theory - Martin please > > correct me if I overlooked a safety mechanism) just create a lot of coded > > packets which cannot be decoded anymore. This seems to be especially > > problematic when some nodes are for example 2x2 MIMO devices and others > > are 3x3. At least this would be a good way to let the 2x2 miss important > > packets when the 3x3 devices talk between each other. > > > > I would even guess that things like dynamic transmission power would make > > overhearing packets also more problematic. > > > >> but i have a question ? How many relay nodes can be supported at > >> NetworkCoding ( mtu 1546 ) . > > > > I am not sure what you are asking here. The implementation in batman-adv > > can combine two packets into one. And this combining of these two packets > > is done by exact one relay node. The decoding is done by the two receiving > > nodes. What you can build with it is been shown in the documentation from > > Martin. The network coding used here is therefore done by a relay node and > > its neighbors. But there can be multiple relay nodes in the mesh doing > > network coding at the same time. > > > > > > I personally haven't used network coding with batman-adv. But since you've > > created multiple new threads on the mailing list [1,2,3,4] (beside the > > private mail *grml*) - here is at least a pseudo-answer. > > > > Kind regards, > > Sven > > > > [1] > > https://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding#Drawback > > s [2] > > https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2016-November/016586.ht > > ml [3] > > https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2016-November/016587.ht > > ml [4] > > https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2016-November/016588.ht > > ml [5] > > https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2016-November/016592.ht > > ml > End of encapsulated message

2 2

[B.A.T.M.A.N.] [PATCH 00/17] pull request for net-next: batman-adv 2016-11-08
by Simon Wunderlich 08 Nov '16

08 Nov '16

Hi David, this is our first feature pull request for batman-adv. There is one more set pending after this one. Please pull or let me know of any problem! Thank you, Simon The following changes since commit a283ad5066cd63f595224c7476001cfc367fdf2e: Merge tag 'batadv-next-for-davem-20161027' of git://git.open-mesh.org/linux-merge (2016-10-29 16:26:50 -0400) are available in the git repository at: git://git.open-mesh.org/linux-merge.git tags/batadv-next-for-davem-20161108 for you to fetch changes up to 33581cefe4d182d99e9f8a66156507b06e7c9265: batman-adv: Reject unicast packet with zero/mcast dst address (2016-10-30 11:11:40 +0100) ---------------------------------------------------------------- This feature and cleanup patchset includes the following changes: - netlink and code cleanups by Sven Eckelmann (3 patches) - Cleanup and minor fixes by Linus Luessing (3 patches) - Speed up multicast update intervals, by Linus Luessing - Avoid (re)broadcast in meshes for some easy cases, by Linus Luessing - Clean up tx return state handling, by Sven Eckelmann (6 patches) - Fix some special mac address handling cases, by Sven Eckelmann (3 patches) ---------------------------------------------------------------- Linus Lüssing (5): batman-adv: Add wrapper for ARP reply creation batman-adv: Remove unnecessary lockdep in batadv_mcast_mla_list_free batman-adv: Remove unused skb_reset_mac_header() batman-adv: Use own timer for multicast TT and TVLV updates batman-adv: Simple (re)broadcast avoidance Sven Eckelmann (12): batman-adv: Introduce missing headers for genetlink restructure batman-adv: Mark batadv_netlink_ops as const batman-adv: Close two alignment holes in batadv_hard_iface batman-adv: use consume_skb for non-dropped packets batman-adv: Count all non-success TX packets as dropped batman-adv: Consume skb in batadv_frag_send_packet batman-adv: Consume skb in batadv_send_skb_to_orig batman-adv: Consume skb in receive handlers batman-adv: Remove dev_queue_xmit return code exception batman-adv: Disallow mcast src address for data frames batman-adv: Disallow zero and mcast src address for mgmt frames batman-adv: Reject unicast packet with zero/mcast dst address net/batman-adv/bat_iv_ogm.c | 30 ++++-- net/batman-adv/bat_v_elp.c | 25 +++-- net/batman-adv/bat_v_ogm.c | 66 +++++++++++- net/batman-adv/distributed-arp-table.c | 67 +++++++----- net/batman-adv/fragmentation.c | 70 ++++++++----- net/batman-adv/hard-interface.c | 52 ++++++++++ net/batman-adv/hard-interface.h | 16 +++ net/batman-adv/main.c | 11 +- net/batman-adv/main.h | 1 + net/batman-adv/multicast.c | 70 ++++++++++--- net/batman-adv/multicast.h | 6 -- net/batman-adv/netlink.c | 5 +- net/batman-adv/network-coding.c | 35 ++++--- net/batman-adv/originator.c | 13 ++- net/batman-adv/routing.c | 180 ++++++++++++++++++++------------- net/batman-adv/send.c | 140 ++++++++++++++++++------- net/batman-adv/send.h | 6 +- net/batman-adv/soft-interface.c | 6 +- net/batman-adv/tp_meter.c | 6 -- net/batman-adv/translation-table.c | 4 - net/batman-adv/tvlv.c | 5 +- net/batman-adv/types.h | 10 +- 22 files changed, 571 insertions(+), 253 deletions(-)

3 21

[B.A.T.M.A.N.] [PATCH v7] alfred: Check batadv interfaces via netlink
by Sven Eckelmann 08 Nov '16

08 Nov '16

From: Jean-Jacques Sarton <jj.sarton(a)t-online.de> alfred is checking the status of the mesh interface before it starts. The mesh interface has to have accessible debugfs files "transtable_global" and "originators" before alfred will accept it. batman-adv will not create debugfs entries for network namespaces. Thus this check has to be modified to first check via netlink if the interface is providing the same information without debugfs. If it does then no check for the debugfs files is necessary anymore. Signed-off-by: Jean-Jacques Sarton <jj.sarton(a)t-online.de> [sven(a)narfation.org: fixed commit message, mark debugfs function static, fix whitespaces, fix unused init of variable, only fallback to debugfs on EOPNOTSUPP, rewritten batadv_interface_check_netlink, fix return of batadv_interface_check] Signed-off-by: Sven Eckelmann <sven(a)narfation.org> --- v7: - rewritten commit message - mark batadv_interface_check_debugfs static - fix whitespaces - fix unused init of variable ret - fix return of batadv_interface_check - only fallback to debugfs on -EOPNOTSUPP - introduce check_nlcmd_cb to stop netlink processing early - rewritten batadv_interface_check_netlink to not misuse get_tq_netlink_cb v6: - sixth submission from Jean-Jacques - dropped basically the complete patch (doesn't apply) v5: - fifth submission from Jean-Jacques - rewritten commit message v4: - fourth submission from Jean-Jacques - rewritten commit message - introduced check for BATADV_CMD_GET_TRANSTABLE_GLOBAL v3: - third submission from Jean-Jacques (corrupt) v2: - second submission from Jean-Jacques (corrupt) v1: - first submission from Jean-Jacques (corrupt) --- batadv_query.c | 16 +++++++++++++++- netlink.c | 25 +++++++++++++++++++++++++ netlink.h | 1 + 3 files changed, 41 insertions(+), 1 deletion(-) diff --git a/batadv_query.c b/batadv_query.c index a671b79..c17132f 100644 --- a/batadv_query.c +++ b/batadv_query.c @@ -136,7 +136,7 @@ int ipv6_to_mac(const struct in6_addr *addr, struct ether_addr *mac) return 0; } -int batadv_interface_check(const char *mesh_iface) +static int batadv_interface_check_debugfs(const char *mesh_iface) { char full_path[MAX_PATH + 1]; FILE *f; @@ -166,6 +166,20 @@ int batadv_interface_check(const char *mesh_iface) return 0; } +int batadv_interface_check(const char *mesh_iface) +{ + int ret; + + enable_net_admin_capability(1); + ret = batadv_interface_check_netlink(mesh_iface); + enable_net_admin_capability(0); + + if (ret == -EOPNOTSUPP) + ret = batadv_interface_check_debugfs(mesh_iface); + + return ret; +} + static int translate_mac_debugfs(const char *mesh_iface, const struct ether_addr *mac, struct ether_addr *mac_out) diff --git a/netlink.c b/netlink.c index 1b5695c..73fab28 100644 --- a/netlink.c +++ b/netlink.c @@ -365,3 +365,28 @@ int get_tq_netlink(const char *mesh_iface, const struct ether_addr *mac, return 0; } + +static int check_nlcmd_cb(struct nl_msg *msg __unused, void *arg __unused) +{ + return NL_STOP; +} + +int batadv_interface_check_netlink(const char *mesh_iface) +{ + struct nlquery_opts opts = { + .err = 0, + }; + int ret; + + ret = netlink_query_common(mesh_iface, BATADV_CMD_GET_ORIGINATORS, + check_nlcmd_cb, &opts); + if (ret < 0) + return ret; + + ret = netlink_query_common(mesh_iface, BATADV_CMD_GET_TRANSTABLE_GLOBAL, + check_nlcmd_cb, &opts); + if (ret < 0) + return ret; + + return 0; +} diff --git a/netlink.h b/netlink.h index b08e872..9bc75a1 100644 --- a/netlink.h +++ b/netlink.h @@ -49,6 +49,7 @@ int translate_mac_netlink(const char *mesh_iface, const struct ether_addr *mac, struct ether_addr *mac_out); int get_tq_netlink(const char *mesh_iface, const struct ether_addr *mac, uint8_t *tq); +int batadv_interface_check_netlink(const char *mesh_iface); extern struct nla_policy batadv_netlink_policy[]; -- 2.10.2

2 1

[B.A.T.M.A.N.] [PATCH 0/6] batman-adv: Revert coccinelle compat support
by Sven Eckelmann 08 Nov '16

08 Nov '16

Hi, it seems that the coccinelle package in Debian Jessie is not able to parse semantic patches [1]. This basically breaks the batman-adv build on many stable systems and thus makes the out-of-tree module unusable on these systems. I have currently no better idea than reverting these patches. Kind regards, Sven PS: Linus, do you want to try to get rid of replacement.sh? [1] https://www.open-mesh.org/issues/303

3 10

i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) .
by johnzeng 08 Nov '16

08 Nov '16

Hello Dear Sir : i read some detail about NetworkCoding , my understanding : every relay node will detects neighbors packet at promisc mode and combine these packet into a single transmission , and every relay mode will keep some usaful ( Ingoing: c8:3a:35:c9:ce:71 .... ) and they will add some encoded information into packet ( will send destination ) So we will run the part --- ip link set dev wlan0 mtu 1546 ( more than 1532 ) but i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) . Thanks Tiger batctl nn Node: c8:3a:35:c9:ce:71 Ingoing: c8:3a:35:c9:ce:71 Outgoing: c8:3a:35:c9:ce:71 [root@alarmpi ~]# batctl nc enabled [root@alarmpi ~]# batctl statistics tx: 18 tx_bytes: 2076 tx_dropped: 32 rx: 767 rx_bytes: 33993 forward: 0 forward_bytes: 0 mgmt_tx: 7956 mgmt_tx_bytes: 542012 mgmt_rx: 3132 mgmt_rx_bytes: 222572 frag_tx: 0 frag_tx_bytes: 0 frag_rx: 0 frag_rx_bytes: 0 frag_fwd: 0 frag_fwd_bytes: 0 tt_request_tx: 0 tt_request_rx: 1 tt_response_tx: 1 tt_response_rx: 0 tt_roam_adv_tx: 0 tt_roam_adv_rx: 0 dat_get_tx: 2 dat_get_rx: 0 dat_put_tx: 0 dat_put_rx: 4 dat_cached_reply_tx: 0 nc_code: 0 nc_code_bytes: 0 nc_recode: 0 nc_recode_bytes: 0 nc_buffer: 17 nc_decode: 0 nc_decode_bytes: 0 nc_decode_failed: 0 nc_sniffed: 0

3 4

[B.A.T.M.A.N.] Batman an more than one Gateway
by Jean-Jacques Sarton 08 Nov '16

08 Nov '16

Hello, I have take a look to the configuration of our gateways. Inho there are some points which are not OK, Broadcasts are rebroadecasted on a wired connection, this seem for me to be an issue. Our network has two gw which are interconnected. I have listed the interfaces and the output from batctl on the GW and also what batxtl said on a node ================================================================= Interfaces for gateway Q0: br0: 12:e8:ef:7f:0d:c7 bat0: 12:e8:ef:7f:0d:c9 ftun-q1: 12:e8:ef:7f:0d:c8 mesh-vpn: aa:ff:ca:ca:fe:03 ------------------- # batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2014.3.0, MainIF/MAC: ftun-q1/12:e8:ef:7f:0d:c8 (bat0)] ca:b1:f2:63:f3:cf (251) ca:b1:f2:63:f3:cf [ ftun-q1]: 50.0/50.0 MBit -------------------------------------- On node (connected with Q0): # batctl n [B.A.T.M.A.N. adv 2016.4, MainIF/MAC: mesh0/92:fb:53:11:44:f1 (bat0/90:f6:52:11:44:f1 BATMAN_IV)] IF Neighbor last-seen mesh-vpn aa:ff:ca:ca:fe:03 3.342s --------------------- # batctl gwl [B.A.T.M.A.N. adv 2016.4, MainIF/MAC: mesh0/92:fb:53:11:44:f1 (bat0/90:f6:52:11:44:f1 BATMAN_IV)] Router ( TQ) Next Hop [outgoingIf] Bandwidth * ca:b1:f2:63:f3:cf (240) aa:ff:ca:ca:fe:03 [ mesh-vpn]: 50.0/50.0 MBit 12:e8:ef:7f:0d:c8 (255) aa:ff:ca:ca:fe:03 [ mesh-vpn]: 50.0/50.0 MBit Translated Interface/Location ftun-q1/Q0 (255) mesh-vpn/Q0 * ftun-q0/Q1 (240) mesh-vpn/Q0 ================================================================= Interfaces for gateway Q1: br0: ca:b1:f2:63:f3:cd bat0: ca:b1:f2:63:f3:cd ftun-q0: ca:b1:f2:63:f3:cf mesh-vpn: aa:ff:ca:ca:fe:01 --------------------- # batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2014.3.0, MainIF/MAC: ftun-q0/ca:b1:f2:63:f3:cf (bat0)] 12:e8:ef:7f:0d:c8 (255) 12:e8:ef:7f:0d:c8 [ ftun-q0]: 50.0/50.0 MBit -------------------------------------- On node (connected with Q1): # batctl n [B.A.T.M.A.N. adv 2016.4, MainIF/MAC: mesh0/92:fb:53:11:44:f1 (bat0/90:f6:52:11:44:f1 BATMAN_IV)] IF Neighbor last-seen mesh-vpn aa:ff:ca:ca:fe:01 4.413s --------------------- # batctl gwl [B.A.T.M.A.N. adv 2016.4, MainIF/MAC: mesh0/92:fb:53:11:44:f1 (bat0/90:f6:52:11:44:f1 BATMAN_IV)] Router ( TQ) Next Hop [outgoingIf] Bandwidth ca:b1:f2:63:f3:cf (255) aa:ff:ca:ca:fe:01 [ mesh-vpn]: 50.0/50.0 MBit * 12:e8:ef:7f:0d:c8 (240) aa:ff:ca:ca:fe:01 [ mesh-vpn]: 50.0/50.0 MBit Translated Interface/Location ftun-q0/Q1 (255) mesh-vpn/Q1 * ftun-q1/Q0 (240) mesh-vpn/Q1 =================================================================== Regards, Jean-Jacques

5 11

[B.A.T.M.A.N.] [[PATCH] Alfred not working within network name space add static to function declaration
by Jean-Jacques Sarton 06 Nov '16

06 Nov '16

Fix scope of function to static Signed-off-by: Jean-Jacques Sarton <jj.sarton(a)t-online.de> --- batadv_query.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batadv_query.c b/batadv_query.c index dc8a042..69f5a48 100644 --- a/batadv_query.c +++ b/batadv_query.c @@ -136,7 +136,7 @@ int ipv6_to_mac(const struct in6_addr *addr, struct ether_addr *mac) return 0; } -int batadv_interface_check_debugfs(const char *mesh_iface) +static int batadv_interface_check_debugfs(const char *mesh_iface) { char full_path[MAX_PATH + 1]; FILE *f; -- 2.7.4

2 1

[B.A.T.M.A.N.] [PATCH v2] Alfred not working within network name space
by Jean-Jacques Sarton 06 Nov '16

06 Nov '16

scope of function corrected, has to be static Signed-off-by: Jean-Jacques Sarton <jj.sarton(a)t-online.de> --- batadv_query.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batadv_query.c b/batadv_query.c index dc8a042..69f5a48 100644 --- a/batadv_query.c +++ b/batadv_query.c @@ -136,7 +136,7 @@ int ipv6_to_mac(const struct in6_addr *addr, struct ether_addr *mac) return 0; } -int batadv_interface_check_debugfs(const char *mesh_iface) +static int batadv_interface_check_debugfs(const char *mesh_iface) { char full_path[MAX_PATH + 1]; FILE *f; -- 2.7.4

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

B.A.T.M.A.N November 2016