Battlemesh allowed me to finally track down a bug in the address compressor
of olsrd2, which sometimes depending on the order and pattern of addresses
made tlvs vanish... Not sure this helps explaining it, but I consider this
Battlemesh a good success.
Henning
Am 16.06.2017 10:32 schrieb
On Thu, Apr 28, 2016 at 9:29 PM, Juliusz Chroboczek
wrote:
>> I must admit I have been thinking about switching off Duplicate
>> Address Detection for mesh interfaces automatically...
>
> What problem are you trying to solve?
Less useless overhead on slow-speed
I must admit I have been thinking about switching off Duplicate
Address Detection for mesh interfaces automatically... it makes not
much sense on non-transitive interfaces anyways.
Henning
On Thu, Apr 28, 2016 at 8:54 PM, Juliusz Chroboczek
wrote:
>> I believe
On Thu, Apr 28, 2016 at 6:52 PM, Dave Taht wrote:
>> Why not just sending IP multicast (not 802.11 management frames) with
>> a higher rate (lowest best linkspeed to all known neighbors)?
>
> )I've always liked this idea as an enhancement to the existing 802.11
> spec. It is
mail/openwrt-devel/2015-June/033398.html
Why not just sending IP multicast (not 802.11 management frames) with
a higher rate (lowest best linkspeed to all known neighbors)?
Henning Rogge
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
h
On Sun, Apr 24, 2016 at 11:12 PM, Juliusz Chroboczek
wrote:
>> http://stackoverflow.com/questions/7225888/how-can-i-monitor-the-nic-statusup-down-in-a-c-program-without-polling-the-ker
>
> Babeld is already monitoring netlink messages (see funciton filter_netlink
>
On Tue, Apr 19, 2016 at 8:32 PM, Dave Taht wrote:
> I finally got around to reading these papers. I liked the compression
> techniques used by bmx6...
>
> I can't help but want to also increase babel's update rate from 2sec
> to .5sec as in bmx6 for comparison.
OLSRd (and
On Fri, Dec 18, 2015 at 11:13 AM, Juliusz Chroboczek
wrote:
>> We forked babeld and have included an ipc process which allows us to add
>> and remove interfaces while babeld is running:
>> github.com/sudomesh/babeld
>
> Nice.
>
> My plan is a little different: I
On Fri, Dec 18, 2015 at 9:29 PM, Juliusz Chroboczek
wrote:
>> Just a crazy idea. Could both OLSR2 and Babel share the same language
>> on this interface? ;-)
>
> Both Henning and I intend to reflect accurately the internal
> implementation details, many of which
his?
https://en.wikipedia.org/wiki/Link_Layer_Discovery_Protocol
Not sure how well it is supported by consumer grade switches.
Henning Rogge
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
On Mon, Dec 14, 2015 at 8:15 PM, Dave Taht wrote:
> Is there a reliable way of determining that an underlying interface is a
> bridge?
A local bridge/wifi? Sure...
just look into the source of the brctl tool... it can give you a list
of all bridge interfaces.
A "wifi
No,
I just setup 2 routes on a VM (1 IPv4, 1 IPv6), imported
them into OLSRv2 and watched them appearing on the other VM.
It helped me to find quite a few bugs, both in packet
generation/fragmentation and in the netlink routing code.
Henning
On Fri, Nov 13, 2015 at 12:46 PM,
Hi,
I would suggest doing some "stress" test where Babel has to set LOTS
of routes at once.
I had once a race condition in the OLSRv2 netlink code that only
happend with 1000+ routes on the way to the kernel.
Henning Rogge
On Thu, Nov 12, 2015 at 11:37 PM, Juliusz Chroboczek
<
Yes,
copying the routes with a second service just to put some of them into
a different routing table sounds like a lot of unnecessary complexity.
Henning
On Thu, Aug 27, 2015 at 3:16 PM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Why not having a separate service which
On Thu, Aug 27, 2015 at 12:49 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Then we can have the following order of routing tables on routers:
babel
olsr
babel_default
olsr_default
Mitar,
I'll be glad to implement the hack that you require, but let's please
think whether
for Standard Track Babel and get an unpleasant surprise.
Henning Rogge
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
On Sun, Jul 12, 2015 at 10:53 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Please do not make this option available in the OpenWRT config file.
Unfortunately hnetd babeld communication occurs solely through
configuration file (Fragment).
Ah merde.
Therefore at least for
The iw code is quite straightforward I think.
I used it as an inspiration for my nl80211_listener plugin
Henning
On Thu, Jun 18, 2015 at 8:55 PM, Dave Taht dave.t...@gmail.com wrote:
The iw package appears canonical, and BSD licensed, and uses
nl80211.h (exported from the linux kernel, also
If you work with atomic route replacement even putting ALL of them
into a netlink message (or as many as you can fit in) works.
Henning
On Tue, Apr 7, 2015 at 12:19 PM, Matthieu Boutier
bout...@pps.univ-paris-diderot.fr wrote:
I agree, but I would like to know how many packets we lose. Since
On Tue, Apr 7, 2015 at 3:57 PM, Dave Taht dave.t...@gmail.com wrote:
Interface index is not a problem... metric-change is.
I am sorry, I do not understand, once again.
If the route has the same destination and metric, you will overwrite
it with an atomic update, regardless of the outgoing
On Mon, Apr 6, 2015 at 7:22 PM, Dave Taht dave.t...@gmail.com wrote:
Well, I tried the patches and they did not work (as expected), but I
think we are closer. I will try to create some test cases using ip
route to do what I want, and get back to folk when I have time. I have
a ton of other
On Mon, Apr 6, 2015 at 11:03 AM, Matthieu Boutier
bout...@pps.univ-paris-diderot.fr wrote:
I think the unique key for the route is destination, routing table
and metric. The metric part is important, if you put the routing
protocol path cost into the route, atomic replacement will not work.
routing API. ;)
On Mon, Mar 16, 2015 at 11:32 AM, Henning Rogge hro...@gmail.com wrote:
On Mon, Mar 16, 2015 at 7:25 PM, Dave Taht dave.t...@gmail.com wrote:
got code?
I just used the same code I use for IPv4 (which has been working for
atomic replacement for ages).
I got confused when someone
Good as a reference... not that good for copying code directly.
Henning
On Mon, Apr 6, 2015 at 6:58 PM, Julien Cristau jcris...@debian.org wrote:
On Mon, Apr 6, 2015 at 10:56:41 +0200, Matthieu Boutier wrote:
Is there anywhere a good reference to netlink?
iproute2, libnl, kernel sources ?
that atomic overwriting of IPv6 routes
wasn't working for older kernels.
The only thing I know (at the moment) is debian Wheezy: BAD and
Ubuntu 14.10: GOOD.
IPv4 atomic overwriting has been working forever... at least 5-8
years. Maybe even during Kernel 2.4 times.
Henning Rogge
towards the router.
So check:
- can I ping between two different mesh routers?
- can I ping between the mesh router and a local AP client?
- can I ping an AP client from a different mesh router?
- can I ping between two AP clients attached to different mesh routers?
Henning Rogge
On Wed, Mar 25
obviously nothing yet for source routing, but
should be complete otherwise).
I would suggest building a generic wrapper that converts UCI into
babel configuration without knowing the names of the variables if
possible. This way you don't need to change the openwrt scripts with
every release.
Henning
=oonf.git;a=blob;f=src-plugins/subsystems/os_linux/os_routing_linux.c;h=4194fd04f8f259b686a1343cc906fc8649c6a7b6;hb=master
If I understand it correctly you just need to set the routes with
NLM_F_CREATE | NLM_F_REPLACE to get the atomic replacement.
Henning Rogge
On Mon, Mar 16, 2015 at 11:24 AM
thing about 802.11s is that you can use it as a wifi
adhoc mode that can be bridged to an ethernet connection... if you
switch of the mesh part of the protocol. ;)
Henning Rogge
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http
to 240-254 ? This
way experimental plus reserved would be 0xf0 - 0xff.
And it would give you a continuous Specification Required range.
Henning Rogge
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
Maybe a parameter to tell babeld don't stop with SIGHUP ? So a
startup script can prevent the restart from happening?
Henning Rogge
On Sun, Sep 22, 2013 at 8:26 PM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
What about quitting on SIGHUP only if babeld is run on non-daemon mode
You can use uname() to get the kernel version. We already use it in
Olsrd to sidestep a semantic change in the procfile system.
Henning
On Thu, Aug 22, 2013 at 12:01 AM, Dave Taht dave.t...@gmail.com wrote:
I've got this in the next version of cerowrt and it looks like it is also
targetted for
If you tag all versions in your repository, it should be easy to get a
version string from the last relevant tag.
We use the following command in the OLSRv2 makefile system:
git describe --always --long --tags --dirty --match v[0-9]*
Henning
On Sun, Jul 21, 2013 at 1:16 PM, Juliusz Chroboczek
Maybe they can do it as long as the tunnel destination is different on
both sides?
Henning
On Tue, Jul 2, 2013 at 8:31 PM, Michael Richardson m...@sandelman.ca wrote:
Baptiste Jonglez baptiste.jong...@ens-lyon.fr wrote:
2) I would guess that the NAT has been setup with your host as the
On Fri, Jun 21, 2013 at 7:25 PM, Dave Taht dave.t...@gmail.com wrote:
On Fri, Jun 21, 2013 at 10:04 AM, Henning Rogge hro...@googlemail.com wrote:
At the lowest timescale possible on a given link you are
either at capacity 1 or 0.
Same problem for packetloss based metrics in mesh networks
On Sun, May 5, 2013 at 5:59 PM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
2. When was NLM_F_REPLACE introduced?
I think we have been using it on Olsr.org for years... so the feature
was already present in kernel 2.4.
Henning Rogge
--
We began as wanderers, and we are wanderers
. He ran into some trouble
and we switched to IPIP tunnels, but I have to contact him if he
remembers how well RTA_SRC worked. There is also (as you most likely
know) a Policy Rule selector based on the src-ip prefix. Not sure if
this one is working correctly.
Henning Rogge
--
We began as wanderers
networking
research.
Yes, it is... it might become a good raw data source for the metric
calculation of any kind of mesh routing protocol.
Henning Rogge
--
Steven Hawkings about cosmic inflation: An increase of billions of
billions of percent in a tiny fraction of a second. Of course
On Wednesday 06 April 2011 10:41:05 Gabriel Kerneis wrote:
http://www.rfc-editor.org/rfc/rfc6126.txt
Congratulations Juliusz!
A can only agree to this... gratulation, its always a hard and boring work to
write down the exact specifications of a protocol AFTER one got it working. :)
Henning
On Thursday 14 October 2010 01:48:14 Mitar wrote:
http://www.tropos.com/technology/scalability.html
Oh dear... another on of those we are the ultimate answer to live, the
universe and the rest of MANET technology...
Google for order one networks if you want to look at another one.
Henning
--
this is
easy -- just use link-local addresses.
Why not use link-local addresses in IPv4? The we-all-know-and-love
169.254.* addresses?
Because there are not enough of them to generate them from MAC. With only 2^16
IPs it's a lot easier to get a collision.
Henning Rogge
--
1) You can't win.
2) You
Am Donnerstag 22 April 2010 20:47:24 schrieb Dave Taht:
I concur about secure BGP's limitations. It's what I meant by halfway
decent. As for OSPFv3 + IPsec + IPv6, it's actually, well, not
horrible. I had never heard of anyone getting it to work before today,
actually.
IPv6 and IPsec should be
about it or
this is a list of IPs you should NOT use. This way you could adapt ipv4-
stateless AHCP to situations where a different instance in the mesh node has
insider knowledge about the used IPs.
Henning Rogge
signature.asc
Description: This is a digitally signed message part
nodes. In particular,
it would make sense to do server-based DAD for stateful configuration,
and client-based for stateless.
Interesting idea.
Henning Rogge
signature.asc
Description: This is a digitally signed message part.
___
Babel-users mailing
separation of servers. Or maybe to distribute the
leases to other AHCP-servers so you have some redundancy ?
Henning Rogge
signature.asc
Description: This is a digitally signed message part.
___
Babel-users mailing list
Babel-users
).
Henning Rogge
--
Wo kämen wir hin, wenn alle sagten, wo kämem wir hin, und niemand
ginge, um einmal zu schauen, wohin man käme, wenn man ginge. (Kurt
Marti)
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org
people just use RFC compatible OLSR.
I would be interested what config file you used for the test. If you plan to
redo the test we (the olsr.org team) would be very interested in getting
feedback what kind of problems you have so that we can improve our software.
Henning Rogge
signature.asc
On Fri, Sep 4, 2009 at 03:58, Harald Geyerhar...@lefant.net wrote:
Henning Rogge hro...@googlemail.com:
The problem is that link-local do not always work in manets because manet
broadcast domains are not 'closed'.
Can you be more explicit on that problem?
I can't think of a situation where
traffic ?
According to my knowledge you cannot insert a routing entry into linux with
IPv6 as destination and IPv4 as gateway (next hop).
Henning Rogge
signature.asc
Description: This is a digitally signed message part.
___
Babel-users mailing list
Babel
On Mittwoch 29 April 2009 19:11:32 Juliusz Chroboczek wrote:
Sorry to follow-up on myself.
In version 2, the neighbour is identified with the link-local IPv6
address, so multiple adjacencies between the same two nodes are okay.
Just to be clear: there is no issue at all with conflicting
On Mittwoch 29 April 2009 20:51:38 Juliusz Chroboczek wrote:
Theoretically two nodes in two-hop range might get the same linklocal
IP, because they don't share a link, but the node between them would be
in trouble.
Yep. A possible workaround would be to assign random IPv6 interface-ids
On Thu, Apr 23, 2009 at 1:08 AM, Juliusz Chroboczek
juliusz.chroboc...@pps.jussieu.fr wrote:
http://hackerspace.be/wbm2009#toc8
Mmmm... purty pictures.
If you want to know why it's difficult to do right,
http://www.cse.yorku.ca/course_archive/2006-07/F/6590/Papers/yang2.pdf
and if you
52 matches
Mail list logo