B.A.T.M.A.N October 2015

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

12 participants
27 discussions

[B.A.T.M.A.N.] Starting a cellular network
by Jesse 17 Oct '15

17 Oct '15

Hey guys, I tried the IRC and didn't get a response. I have limited time on the Internet each day so I thought I'd try here. I would like to develop a cellular network which runs off of ad hoced 802.11 technology. I'm kind of tired having to pay a $40 cellphone bill to keep in contact with two other people (at most). I see no justification in this since there are already so many more viable options available. I would like to develop an open standard which is free for everyone to implement and utilize for their own needs. Before I get people commenting on how it's already been done, I'd like to say, not like this. The system I'm proposing is built on top of 802.11 ad hoc. Messages are chopped into 4096 byte segments before delivery (I'm considering upping that to 10 kB). It's capable of delivering text messages, walkie-talkie, and files. I have used avahi-autoipd to implement an IPv4 connection over this network and have given all devices in the network, the same BSSID, SSID, and channel. This network uses two ports 4100 and 4200. 4100 is for broadcasts. 4200 is for TCP connections with surrounding peers. Each json message is stamped with a 30 character id. The first 15 characters are an sha512 hash of the message recipient's public key. The second are an sha512 hash of the message itself. Each node keeps up with the last 1000 segments it's been given (in RAM). Anything older than that is deleted. Every 30 seconds (timer starts when peer joins network) nodes send out a get broadcast for their messages via UDP (GET SHA-KEY-HASH UNIQUE ID). Each peer in the network rebroadcasts this message. Hashes of the last 1000 messages are kept in each server as well. If a message hash is already in server, it isn't rebroadcast (no loops). After the broadcast for messages, the network sends a json list back to them containing all the messages the network has which are addressed to that user. It is the user's discretion which messages to request from the group from there. Basically, they pick out the ones they don't already have. Another get request is sent GET HASHED-KEY-MESSAGE-HASH (the unique ID for the entire message). The particular message is sent back to the user (via TCP), using paths constructed from the GET requests. I would like to extend this to an online P2P network so recipients could be part of a global community. Imagine texting your friends in country-x for free because someone was kind enough to plug their tower into their wifi network. By default, this will not share an Internet connection, just texting, walkie-talkie, and file-sharing. I've heard so many people complaining about the B.A.T.M.A.N. network sharing their Internet connection and them routing it through a VPS to avoid any legal problems. I have a problem with my service though. If/When the numbers reach 10,000 users, I don't really see everyone in the network requesting their messages from everyone else in the network. The possibilities of this network would be endless. No more texting fees from major carriers for one. No Internet security risks from sharing the network. If the power and Internet went out in areas, people would still be able to chat via battery back-up towers they build themselves. Since there will be online gateways, there's the possibility that any device with wifi access can communicate with these open standard gateways and deliver messages to anyone on the network (direct Internet access or not). Friends could download your messages when you're offline. Then you just request them from others on your friend's list. Any help with this would be extremely appreciated. I want this to work out of the box. I have my own money making schemes for this service worked up already and would like to make an entire industry from it. Thank you all and sorry for the wall of text. Have a nice day guys.

2 1

[B.A.T.M.A.N.] Questions arised while iplementing NetJSON
by Germano Massullo 08 Oct '15

08 Oct '15

I have some questions about JSONDoc created by command <<batadv-vis --format=jsondoc>> In jsondoc_commented file there are a few addresses that are not shown in ip_addr file. I commented them using # non existing in file ip_addr What are exactly the addresses in "clients"? What do they represent? The procedure I followed to create the interfaces is available at [1] Thank you for your time [1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-September/013700.html

2 1

[B.A.T.M.A.N.] [dave.taht@gmail.com: [OpenWrt-Devel] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final]
by Linus Lüssing 06 Oct '15

06 Oct '15

As this is definitely of concern for us, forwarding it here. Maybe some people who are not on the battlemesh, openwrt-devel or any of the other mailinglists listed below, but are on the batman mailinglist here might be interested to sign it. This topic is vital for us to be able to keep developing robust mesh solutions in the future. Cheers, Linus ----- Forwarded message from Dave Taht <dave.taht(a)gmail.com> ----- Date: Tue, 6 Oct 2015 02:13:36 +0200 From: Dave Taht <dave.taht(a)gmail.com> To: fcc(a)lists.prplfoundation.org, "cerowrt-devel(a)lists.bufferbloat.net" <cerowrt-devel(a)lists.bufferbloat.net>, make-wifi-fast(a)lists.bufferbloat.net, cake(a)lists.bufferbloat.net, Battle of the Mesh Mailing List <battlemesh(a)ml.ninux.org>, bloat <bloat(a)lists.bufferbloat.net>, OpenWrt Development List <openwrt-devel(a)lists.openwrt.org> Subject: [OpenWrt-Devel] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final see: https://docs.google.com/document/d/1E1D1vWP9uA97Yj5UuBPZXuQEPHARp-AhRqUOeQB… for more details. We still have a boatload of footnotes (help?) to add back in properly, and there are no doubt other problems we will catch in the morning. Comment away! As we are hard up against deadlines, and I no longer expect substantial changes, all new offers of signature will be considered final. signatures are now being collected via: http://goo.gl/forms/WCF7kPcFl9 - the 70+ that have already committed need to be contacted again to approve this draft. -- Dave Täht Do you want faster, better, wifi? https://www.patreon.com/dtaht _______________________________________________ openwrt-devel mailing list openwrt-devel(a)lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ----- End forwarded message -----

1 0

[B.A.T.M.A.N.] Questions arised while iplementing NetJSON
by Germano Massullo 05 Oct '15

05 Oct '15

1 0

[B.A.T.M.A.N.] Alfred update-command
by Dominik Heidler 04 Oct '15

04 Oct '15

Hi, I tried to use the alfred update-command but it seems that the update-command is only triggered when data is purged but not when new data is received. The changed_data_type() method is only called from the purge_data() method. 169 while (NULL != (hashit = hash_iterate(globals->data_hash, hashit))) { 170 struct dataset *dataset = hashit->bucket->data; 171 172 time_diff(&now, &dataset->last_seen, &diff); 173 if (diff.tv_sec < ALFRED_DATA_TIMEOUT) 174 continue; 175 176 changed_data_type(globals, dataset->data.header.type); 177 178 hash_remove_bucket(globals->data_hash, hashit); 179 free(dataset->buf); 180 free(dataset); 181 } Is this the way the update-command should work or am I doing something wrong? Regards, Dominik Heidler

2 5

[B.A.T.M.A.N.] Batman-advanced-dkms + debian + kernel >4.1
by Christof Schulze 04 Oct '15

04 Oct '15

Hello Simon, when trying to run batman v14 on a current kernel (I noticed it for Version 4.1) I realized that batman will not build beause the netdev-structs have changed. The solution is fairly simple because the fix has already been implemented in newer batman versions. The function batadv_is_on_batman_iface can be copied from there and is working fine. I am running a system with kernel 4.1 that was patched in this manner and it has been working fine in a large mesh (Freifunk Frankfurt am Main) for a week. The patch should work well for older kernels too because the netdev-changes have been there for quite a while. Now: Where is the correct place to implement the patch: in batman-adv-dkms or in batman itself? Regards Christof --- hard-interface.c-orig 2015-09-25 09:58:07.123947197 +0200 +++ hard-interface.c 2015-09-25 10:04:34.611914938 +0200 @@ -74,29 +74,28 @@ * if it is a batman-adv interface itself), false otherwise */ static bool batadv_is_on_batman_iface(const struct net_device *net_dev) -{ - struct net_device *parent_dev; - bool ret; +{ + struct net_device *parent_dev; + bool ret; + + /* check if this is a batman-adv mesh interface */ + if (batadv_softif_is_valid(net_dev)) + return true; + + /* no more parents..stop recursion */ + if (dev_get_iflink(net_dev) == 0 || + dev_get_iflink(net_dev) == net_dev->ifindex) + return false; + + /* recurse over the parent device */ + parent_dev = __dev_get_by_index(&init_net, dev_get_iflink(net_dev)); + /* if we got a NULL parent_dev there is something broken.. */ + if (WARN(!parent_dev, "Cannot find parent device")) + return false; - /* check if this is a batman-adv mesh interface */ - if (batadv_softif_is_valid(net_dev)) - return true; + ret = batadv_is_on_batman_iface(parent_dev); - /* no more parents..stop recursion */ - if (net_dev->iflink == net_dev->ifindex) - return false; - - /* recurse over the parent device */ - parent_dev = dev_get_by_index(&init_net, net_dev->iflink); - /* if we got a NULL parent_dev there is something broken.. */ - if (WARN(!parent_dev, "Cannot find parent device")) - return false; - - ret = batadv_is_on_batman_iface(parent_dev); - - if (parent_dev) - dev_put(parent_dev); - return ret; + return ret; } static int batadv_is_valid_iface(const struct net_device *net_dev) -- () ascii ribbon campaign - against html e-mail /\ against proprietary attachments

2 1

[B.A.T.M.A.N.] [PATCH] batman-adv: Change ifconfig examples to iproute2
by Sven Eckelmann 04 Oct '15

04 Oct '15

Signed-off-by: Sven Eckelmann <sven(a)narfation.org> --- Documentation/networking/batman-adv.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Documentation/networking/batman-adv.txt b/Documentation/networking/batman-adv.txt index 58e4904..a846e37 100644 --- a/Documentation/networking/batman-adv.txt +++ b/Documentation/networking/batman-adv.txt @@ -115,14 +115,17 @@ The "bat0" interface can be used like any other regular inter- face. It needs an IP address which can be either statically con- figured or dynamically (by using DHCP or similar services): -# NodeA: ifconfig bat0 192.168.0.1 -# NodeB: ifconfig bat0 192.168.0.2 +# NodeA: ip link set up dev bat0 +# NodeA: ip addr add 192.168.0.1/24 dev bat0 + +# NodeB: ip link set up dev bat0 +# NodeA: ip addr add 192.168.0.2/24 dev bat0 # NodeB: ping 192.168.0.1 Note: In order to avoid problems remove all IP addresses previ- ously assigned to interfaces now used by batman advanced, e.g. -# ifconfig eth0 0.0.0.0 +# ip addr flush dev eth0 LOGGING/DEBUGGING -- 2.6.0

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

B.A.T.M.A.N October 2015