Re: [Babel-users] Route-dete :wq

On Fri, Mar 9, 2018 at 3:29 PM, Christof Schulze wrote: >> I start running into trouble with 1000+ routes using 1Mbit mcast. >> Sooner if I seriously >> slam the network with flent or something else that abuses mcast like mdns. >> YMMV. > > So what is the culprit here?

[Babel-users] [PATCH] Always specify linux route metric to defaults

cea7e11152b0a7cebd3572c63ccc9454e6840277 Mon Sep 17 00:00:00 2001 From: Dave Taht <d...@taht.net> Date: Thu, 8 Mar 2018 13:00:01 -0800 Subject: [PATCH] Always specify linux route metric to defaults The original code would export -1 into the linux kernel routing table for unreachable routes, in addition to s

Re: [Babel-users] Route-dete :wq

thing else that abuses mcast like mdns. YMMV. > The right way to reduce the amount of routing traffic in Babel is not to > increase the update interval (which can at best yield a linear reduction), > but to use aggregation and filtering (which can yield an exponential > decrease in a well

Re: [Babel-users] Heads up: merged rfc6126bis into master

While not exactly a flag day from a protocol perspective, the commit removing keep-unfeasible will break existing startup scripts and conf files that have it enabled. https://github.com/jech/babeld/commit/0111f5c1d69ce643a6a76a811eb8f89fb4deb936 -- Dave Täht CEO, TekLibre, LLC

Re: [Babel-users] [babel] routing tables of death

I too may be able to visit Paris in late march. also, a start at an alternative to shortest path metrics, with so many problems that I'd run off this page writing them up, but I was happy to read it this morning. http://ieeexplore.ieee.org/abstract/document/8025937/

[Babel-users] routing tables of death

I confess curiosity, now that we have quagga, bird, and mainline babeld versions, and nifty new stuff like unicast hellos, as to how well they interoperate at this point, as well as perform, under a stress test like: https://github.com/dtaht/rtod -- Dave Täht CEO, TekLibre, LLC

[Babel-users] [PATCH 5/6] gitignore tags TAGS emacs and vi temp files and bad patch attempts

From: Dave Taht <d...@taht.net> Quiet git more. --- .gitignore | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index 635e60b..d298e6e 100644 --- a/.gitignore +++ b/.gitignore @@ -2,6 +2,13 @@ babeld babeld.html version.h -cscope.out +

[Babel-users] [PATCH 6/6] babeld-whole: Enable single unit compilation of all of babeld

From: Dave Taht <d...@taht.net> This adds compile guards and Makefile support to building all of babeld in a single shot, as "babeld-whole". This has compelling advantages: - It lets you A/B two versions with different compilation options such as debugging on or off, or se

[Babel-users] [PATCH 4/6] Tests: Add subdir and test for structure packing

From: Dave Taht <d...@taht.net> An initial run of this test on x86_64 shows suboptimal packing for the filter structure (can be 96), and kernel_route (can be 64). Other things, such as kernel_rule, buffered_update and xroute could be padded to more natural 8 byte boundaries for this arch.

[Babel-users] [PATCH 3/6] Quiet the compiler on two uninitialized variable warnings

From: Dave Taht <d...@taht.net> When compiled on arm and gcc 4.9.2, the compiler picks out two sets of variables passed by reference that "might be used uninitialized". They aren't, but certainly in the getnet case it was not immediately obvious to either me or the compiler. Qu

[Babel-users] [PATCH 1/6] Improve Makefile

From: Dave Taht <d...@taht.net> - Add INCLUDES variable for headers - Add support for tags and TAGS - create "reallyclean" to get rid of tags, TAGS, gmon.out, cscope.out - remove TAGs and gmon.out from "clean" - Add full and correct dependencies on internal

[Babel-users] Misc cleanups to the babeld build system

This patch series makes it easier to work on babeld's source code in a variety of ways. [PATCH 1/6] Improve Makefile [PATCH 2/6] Make v4prefix a shared constant between util.c and [PATCH 3/6] Quiet the compiler on two uninitialized variable warnings [PATCH 4/6] Tests: Add subdir and test for

[Babel-users] [PATCH 2/6] Make v4prefix a shared constant between util.c and message.c

From: Dave Taht <d...@taht.net> Share the data better. --- message.c | 3 +-- util.c| 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/message.c b/message.c index fdc1999..f8c4ad2 100644 --- a/message.c +++ b/message.c @@ -54,8 +54,7 @@ unsigned char *unicast_

[Babel-users] [PATCHes] Misc cleanups to the babeld build system

I am not particularly huge on posting and reviewing patches in-line on mailing lists, but I can repost this pull request here, if desired. https://github.com/jech/babeld/pull/9 This patch series consists of a bunch of miscellaneous improvements to the babeld build system: improving the makefile

[Babel-users] risc-v

I've been fiddling with risc-v stuff here and there of late. http://bellard.org/riscvemu/ Amazingly babel "just builds" and with a little fiddling merely crashes on the lack of ipv6 support in the supplied fedora25 kernel. I guess I should go build a better kernel. root@nemesis:/tmp/babeld#

[Babel-users] babeldStyle

Is there a specific emacs or vi "c-style" setting I should use while hacking on babeld? (.el file would be helpful) I see: functions typically start with the { on the first line 4 character indent 8 characters are usually characters, but there are tabs -- Dave Täht Let's go make home routers

Re: [Babel-users] Debugging unreachable routes - IPv6 as next hop?

I have been chasing a similar set of bugs for months now. Routes would be unreachable for no reason I could see, updates to the kernel would fail[1]. How big is the total route table? Does it stay unreachable? Can you try reverting to babeld-1.7.1 for lede? ... I finally got heads down on it

Re: [Babel-users] [LEDE-DEV] Babeld now has procd support on OpenWRT/LEDE

I will gladly comply. I hope you get your caps-lock key fixed. I'm going to just filter out all further postings from you into my trash folder. > > On Saturday, January 14, 2017 12:06 AM, Dave Taht <dave.t...@gmail.com> > wrote: > > > On Fri, Jan 13, 2017 at 4:08 AM,

Re: [Babel-users] Babeld now has procd support on OpenWRT/LEDE

On Thu, Jan 12, 2017 at 1:01 PM, Baptiste Jonglez wrote: > Hi, > > Here is yet another OpenWRT-related change for babeld: I just merged procd > support for babeld [2], after more than two years of lingering [1]. > > The only user-visible changes should be: > > -

Re: [Babel-users] unicast attempt breaks timestamping

On Mon, Jan 9, 2017 at 6:03 AM, Baptiste Jonglez <bapti...@bitsofnetworks.org> wrote: > Hi again, > > On Fri, Jan 06, 2017 at 11:02:05AM -0800, Dave Taht wrote: >> Based on the patch juliusz supplied me to enable unicast IHU, and >> >> default enable-timest

[Babel-users] automating route injection

what I've typically done to export a single IP is add it to the babel configuration file, and I also use covering routes a lot, essentially the same method. redistribute local ip fd99::66/128 eq 128 allow redistribute ip 172.26.130.0/23 eq 23 allow redistribute local deny While this works, as

[Babel-users] unicast attempt breaks timestamping

Based on the patch juliusz supplied me to enable unicast IHU, and default enable-timestamp true this stops sending timestamps (which apparently relies on hellos and IHUs being bundled together) (aside from that unicast IHU is working fine, am still deploying stuff around the testbed, not

Re: [Babel-users] some thoughts towards babel-1.9

On Mon, Jan 2, 2017 at 3:35 PM, Juliusz Chroboczek wrote: >> For the wired link case, I am surprised babel considers it "interfering"! > > It doesn't. > > https://github.com/jech/babeld/blob/master/interface.c#L210 If that is the only error in two highly speculative documents

Re: [Babel-users] some thoughts towards babel-1.9

On Mon, Jan 2, 2017 at 6:28 AM, Benjamin Henrion <zoo...@gmail.com> wrote: > On Mon, Dec 12, 2016 at 6:25 PM, Dave Taht <dave.t...@gmail.com> wrote: >> I've long been testing a few out of tree patches for babel and long >> have had the intent to try a few more once the

Re: [Babel-users] [babel] some thoughts towards babel-1.9

I added a todo list for my "rabel" branch of babel covering some of the stuff I'd like to try. https://raw.githubusercontent.com/dtaht/rabeld/master/todo.org ___ Babel-users mailing list Babel-users@lists.alioth.debian.org

[Babel-users] essentially atomic updates

In my seemingly once yearly attempt at working on babel (admittedly the year is young!), here's my latest attempt at gently switching routes. https://github.com/dtaht/rabeld/commit/6ca4b0fa60dbbd25eb5d7e792d8f8058941d4cdb -- Dave Täht Let's go make home routers and wifi faster! With better

Re: [Babel-users] dropping CS6

On Thu, Dec 15, 2016 at 1:10 AM, Henning Rogge <hro...@gmail.com> wrote: > On Mon, Dec 12, 2016 at 6:03 PM, Dave Taht <dave.t...@gmail.com> wrote: >> diffserv CS6 (I am the original author of the patch) has turned out to >> be generally a lose on wifi, putting thi

Re: [Babel-users] babel on an otherwise transparent bridge

On Wed, Sep 7, 2016 at 5:00 PM, Juliusz Chroboczek wrote: >> like it to do is have a dedicated ipv6 ULA ip address for management >> purposes (not using a vlan here), and announce that to the network, but >> never offer itself as a routing opportunity to anything >

[Babel-users] babel on an otherwise transparent bridge

I have a box setup to be a transparent wifi/ethernet bridge. What I'd like it to do is have a dedicated ipv6 ULA ip address for management purposes (not using a vlan here), and announce that to the network, but never offer itself as a routing opportunity to anything on any side of the bridge,

[Babel-users] alternate source specific encoding?

is that in a branch somewhere yet? I am doing some builds in the yurtlab for the latest and greatest make-wifi-fast code, and can try this, if available. -- Dave Täht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org

Re: [Babel-users] Some minor incompatible changes to the configuration language

On Sun, Jul 31, 2016 at 6:19 PM, Juliusz Chroboczek wrote: > I've just pushed some changes that could, in some edge cases, break your > configuration files. Since I'd like to release 1.8 before the end of the > summer, I'll be grateful if you could test. > > First

Re: [Babel-users] [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...]

On Thu, Jun 23, 2016 at 4:20 PM, Jonathan Morton wrote: > >> On 24 Jun, 2016, at 01:57, Juliusz Chroboczek >> wrote: >> >>> the long slow EABI changeover that was obsoleted almost overnight by the >>> armhf work the raspian folk did, and so

Re: [Babel-users] Cross-compiling to armhf [was: beaglebone green wireless boards...]

On Thu, Jun 23, 2016 at 3:57 PM, Juliusz Chroboczek wrote: >> the long slow EABI changeover that was obsoleted almost overnight by the >> armhf work the raspian folk did, and so on. > > I am pretty positive that armhf predates raspbian. Let's please give > credit

Re: [Babel-users] Cross-compiling to armhf [was: beaglebone green wireless boards...]

On Thu, Jun 23, 2016 at 3:10 PM, Juliusz Chroboczek wrote: >> (does a working cross compiler exist for the aarch64 in the c2?) > > apt-get install gcc-aarch64-linux-gnu d@osx: apt-get install gcc-aarch64-linux-gnu Not found. ... One of the bigger mistakes I

Re: [Babel-users] Cross-compiling to armhf [was: beaglebone green wireless boards...]

On Wed, Jun 22, 2016 at 4:31 AM, Juliusz Chroboczek wrote: >> The preinstalled OS has sufficient compiler and onboard flash space to >> build a current babeld from git, and I'm happy to report IPV6_SUBTREES >> is compiled in by default. > > Dave, > > It's not the

Re: [Babel-users] rib out of sync

I stepped back to 1.6.3 and the kernel and babel ribs stayed correct no matter how much I upped or downed the usb0 interface while keeping the wifi alive. This by itself does not mean enough (because source specific routing is not in 1.6 as best I recall) In terms of bisecting between babel

[Babel-users] beaglebone green wireless boards now available

I just got two of 'em and getting usbnet up was a snap. I got 'em because they have dual 2.4ghz 802.11n antennas and I figured the wifi would be faster than the getchip stuff. (there is no adhoc support. another reason for looking at this board is to look at the structure of the drivers for

Re: [Babel-users] Babel-users Digest, Vol 103, Issue 12

As for "interesting items on the agenda", there are a wide variety of things that appeal to *someone*, if you browse the agenda and working groups available. If you plan to attend all week, the sunday newcomers orientation is quite helpful. In my case for example I am very interested in the

Re: [Babel-users] Babel-users Digest, Vol 103, Issue 12

On Tue, Jun 21, 2016 at 12:47 PM, Jehan Tremback wrote: > I might be interested in participating in IETF 96. Are there more details > about how much it costs etc.? How much of the event will be Babel-related? About 1/1th.

[Babel-users] rib out of sync

I have definitively proven that on at least one of the arm boxes we are using (the getchip) that there is either a new babel bug in git, and/or arm related issue with forming the netlink message, or a kernel bug, or excessive gamma radiation in the atmosphere. I am going to step back to 1.6.1 and

[Babel-users] unicast IHU patch works... but

tested against stock daemons running 1.7.1, 1.6, and all patches to 1.8pre to date on an admittedly too complex network, over ethernet, usbnet, and wifi in ap/sta mode. (not adhoc yet) I have not entirely got around to testing the main circumstances (blocked on other factors) I wanted to look at

Re: [Babel-users] [BUG] Route "deadlocks" under load due to non-atomic kernel route updates

On Thu, Jun 16, 2016 at 1:40 PM, Kirill Smelkov <k...@nexedi.com> wrote: > On Thu, Jun 16, 2016 at 08:38:49AM -0700, Dave Taht wrote: >> On Thu, Jun 16, 2016 at 4:17 AM, Kirill Smelkov <k...@nexedi.com> wrote: >> > On Wed, Jun 15, 2016 at 12:56:34PM +0200, Juliusz C

[Babel-users] the costs of periodic disassociation in conventional ap/sta mode

In the new lab I ended up connecting up a bunch of machines in sta mode over wpa... (partially because adhoc was unavailable - and *mostly* because that's what normal homenet users would do, and lastly because it improved throughput by 50x in some cases) ... with bad results for babel behavior in

Re: [Babel-users] [BUG] Route "deadlocks" under load due to non-atomic kernel route updates

s interest to look into. > > I will see what can be done. > >> > Quagga, at least, switched to atomic updates some time ago, I think. >> > >> > http://patchwork.quagga.net/patch/1234/ >> >> I see. I'm busy right now, but I'll be grateful for a

Re: [Babel-users] Golang implementation

aha. This seems further along. https://github.com/sh3rp/gabel On Wed, Jun 15, 2016 at 7:40 PM, Dave Taht <dave.t...@gmail.com> wrote: > If this is it? > > https://github.com/casarez/gabel > > It looks like a bit more work is required to get to a decent implementation. >

Re: [Babel-users] Golang implementation

If this is it? https://github.com/casarez/gabel It looks like a bit more work is required to get to a decent implementation. On Wed, Jun 15, 2016 at 5:18 PM, Jehan Tremback wrote: > Someone posted in April that they were working on a Golang implementation of > Babel.

Re: [Babel-users] [BUG] Route "deadlocks" under load due to non-atomic kernel route updates

> https://lab.nexedi.com/kirr/iproute2/blob/bd480e66/t/rtcache-torture > (also attached to this email) > > which reproduces the problem in several minutes just on one computer and > retested it locally: I can reliably reproduce the issue on pristine > Debian 3.16.7-ckt25-2 (on both Atom

Re: [Babel-users] [BUG] Route "deadlocks" under load due to non-atomic kernel route updates

On Fri, Jun 10, 2016 at 11:47 AM, Juliusz Chroboczek wrote: > Dear Kirill, > > Thank you very much for the detailed analysis. > > If I read you correctly, this looks like a kernel bug: incorrect > invalidation of the route cache. While we have seen some similar

Re: [Babel-users] Babel in Bird 1.6.0

I can confirm that toke's current set of fixes compiles on a rpi3, AND that I am too stupid to figure out how to create a correct, basic, babeld .conf file for bird. On Sat, Apr 30, 2016 at 10:39 AM, Toke Høiland-Jørgensen wrote: > Juliusz Chroboczek

Re: [Babel-users] Babel in Bird 1.6.0 (documentation)

I would like to see bird itself grow a finer knowledge of time smaller than 1sec. -- Dave Täht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org ___ Babel-users mailing list Babel-users@lists.alioth.debian.org

Re: [Babel-users] Multicast IHUs [was: perverse powersave bug with sta/ap mode]

On Thu, Apr 28, 2016 at 10:10 AM, Juliusz Chroboczek wrote: >> 4) And ya know - it might merely be a (sadly common) bug. Everybody's >> supposed to wake up for the multicast beacons and get a notification >> there's more data to come. > > Yes, it's obviously a

Re: [Babel-users] Multicast IHUs [was: perverse powersave bug with sta/ap mode]

On Thu, Apr 28, 2016 at 10:10 AM, Juliusz Chroboczek wrote: >> 1) Well, I have suggested that IHU messages actually be unicast rather >> than bundled with the hello. > > Yes, you have suggested that before. I answered I would implement that if > somebody

Re: [Babel-users] [Make-wifi-fast] [Cerowrt-devel] perverse powersave bug with sta/ap mode

On Thu, Apr 28, 2016 at 9:05 AM, Henning Rogge wrote: > On Thu, Apr 28, 2016 at 5:04 PM, moeller0 wrote: >> >>> On Apr 28, 2016, at 15:43 , Toke Høiland-Jørgensen wrote: >>> Presumably the access point could transparently turn IP-level multicast

Re: [Babel-users] [Make-wifi-fast] perverse powersave bug with sta/ap mode

On Thu, Apr 28, 2016 at 8:44 AM, Dave Taht <dave.t...@gmail.com> wrote: > On Thu, Apr 28, 2016 at 7:59 AM, Juliusz Chroboczek > <j...@pps.univ-paris-diderot.fr> wrote: >>> Discovery is a special case, that is not quite multicast. [...] So you >>> don't nee

Re: [Babel-users] [Make-wifi-fast] perverse powersave bug with sta/ap mode

On Thu, Apr 28, 2016 at 7:59 AM, Juliusz Chroboczek wrote: >> Discovery is a special case, that is not quite multicast. [...] So you >> don't need any facility to "reach all" in one message. > > Are we speaking of the IP Internet, or of some other network? Heh.

[Babel-users] bug in ^C in -G

this is repeatable on all platforms. root@apu2:/etc# telnet ::1 33123 Trying ::1... Connected to ::1. Escape character is '^]'. BABEL 1.0 version babeld-1.7.1-59-gb648a17-dirty host apu2 my-id 02:0d:b9:ff:fe:41:6c:2c ok ^C dump ^C^C^C dump dump, darn it ^C dump dump dump dump please dump dump,

[Babel-users] perverse powersave bug with sta/ap mode

Pain shared, reduced, joy shared increased... for weeks now I've been puzzling over why a variety of links flapped the way they did, routes coming and going, failing over to weird paths, and I think I have finally isolated one part of the problem. In an age where adhoc does not work particularly

Re: [Babel-users] failing over faster?

On Mon, Apr 25, 2016 at 4:33 PM, Juliusz Chroboczek wrote: >> A good question would be, what would the ideal time between tests be >> for the network to stablize? 3 minutes? At least in one series I'd >> started tests back to back, and didn't kick in the drop link

Re: [Babel-users] failing over faster?

and in other news the odroid c2's current kernel, and the rpi3 and rpi2, now all do IPV6_SUBTREES correctly. ___ Babel-users mailing list Babel-users@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] failing over faster?

Tee-hee! Don't overanalyze yet!, that was not a strictly repeatable test, as yet. (if you want access to the testbed send me a ssh key) A good question would be, what would the ideal time between tests be for the network to stablize? 3 minutes? At least in one series I'd started tests back to

Re: [Babel-users] failing over faster?

Thank ghu we aren't homenet! Wires are dead! :) I will incorporate your comments later today. Until then, there's pictures and data now up at: http://blog.cerowrt.org/post/failing_over_faster/ I am quite puzzled as to how long it takes to fail over even in the good cases. I guess I gotta take

Re: [Babel-users] failing over faster?

This ended up being a deeply philosophical digression into routing behaviors that I think I'll have to blog about, with pictures, to fully describe. What I want is a world of ubiquitous always-on connectivity[1] - where you can be at your desk with 20 connections nailed up, listening to an audio

Re: [Babel-users] failing over faster?

groovy. I will try it as soon as I can This showed some potential for doing it faster than that: http://stackoverflow.com/questions/7225888/how-can-i-monitor-the-nic-statusup-down-in-a-c-program-without-polling-the-ker On Sun, Apr 24, 2016 at 1:21 PM, Juliusz Chroboczek

[Babel-users] failing over faster?

I am fiddling with a rasberry pi3 with a usb ethernet (making it a 100mbit router), the onboard wifi, and 2 usb wifi sticks... with all the interfaces up I do a ping over ethernet 64 bytes from 172.26.64.231: icmp_seq=56 ttl=63 time=1.45 ms 64 bytes from 172.26.64.231: icmp_seq=57 ttl=63

Re: [Babel-users] New paper on Babel, BMX6 and OLSR: Evaluation of mesh routing protocols for wireless community networks

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. On Tue, Apr 12, 2016 at 12:46 PM, Baptiste Jonglez wrote: > Hi

Re: [Babel-users] babeld crashes

I eliminated the -l option from all my boxes and thus far I have not seen it crash. But I am not trying too hard to make things on my network come and go right now, I'm busy on other things: http://blog.cerowrt.org I will put a couple boxes under valgrind the next time I re-org the network,

Re: [Babel-users] babeld crashes

;\n", ifp=0x0, packet=0x1 , packetlen=) at message.c:644 #7 0x000126d8 in main (argc=, argv=) at babeld.c:675 On Fri, Apr 15, 2016 at 6:39 PM, Dave Taht <dave.t...@gmail.com> wrote: > I have been experiencing babeld crashes since starting to use git head > a few weeks a

Re: [Babel-users] IPV6_SUBTREES vs policy routing

I can confirm this patch does the right thing on x86_64, and that the current kernels on the pi3 and pi2 now also support IPV6_SUBTREES correctly. The wifi on the pi3 *sucks rocks* in adhoc mode from a bufferbloat perspective, even worse than the ath9k. It does support a usb ethernet and a few

Re: [Babel-users] IETF news

On Sat, Apr 9, 2016 at 11:07 AM, Juliusz Chroboczek wrote: >> attending remotely was not quite satisfactory. > > We'll need to think about how to make the babel WG as friendly to remote > participation as possible. Obviously, having a competent Jabber scribe is >

Re: [Babel-users] IETF news

On Sat, Apr 9, 2016 at 10:17 AM, Juliusz Chroboczek wrote: >> IETF is boring without Markus. And without Henning. And without Steven. > > And without Dave. (But I'm in touch with Dave more often than the other > three.) Tee-hee. I have to admit that I longed to

[Babel-users] breaking the ath9k in adhoc mode with the new fq_codel implementation

So, thank you for exposing a bug in my code today. The new ath9k fq_codel code at the 802.11 mac layer bypasses the qdisc... root@dancer:~/Pictures# tc -s qdisc show dev wlp2s0 qdisc noqueue 0: root refcnt 2 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 and

Re: [Babel-users] Control socket language [wass Babel on itty bitty boxes]

On Mon, Mar 28, 2016 at 9:27 AM, Gabriel Kerneis wrote: > > > On Mon, Mar 28, 2016, at 17:53, Juliusz Chroboczek wrote: >> > PS: I am loving the new "dump" functionality. Tons easier to read than >> > a logfile. echo 'dump' | nc ::1 33123. >> >> Thanks for the kind words. >>

Re: [Babel-users] Babel on itty bitty boxes

On Mon, Mar 28, 2016 at 8:35 AM, Matthieu Boutier wrote: >> Why don't you write to the netdev list to ask what's a reliable way to >> detect IPv6_SUBTREES? > > Yes, I'm asking myself if the Dave's "invalid argument" are for > source-specific routes. In which

Re: [Babel-users] Babel on itty bitty boxes

On Mon, Mar 28, 2016 at 8:26 AM, Matthieu Boutier wrote: >> I put a babel debug 3 log up at: >> >> http://www.taht.net/~d/babeld_pi3.log > > Strange, there is no more "kernel_route(ADD): invalid argument" lines. Is it > really the same node, with the same

Re: [Babel-users] Babel on itty bitty boxes

On Fri, Mar 25, 2016 at 2:41 AM, Matthieu Boutier wrote: >> I checked and IPV6_SUBTREES is disabled in the raspbian kernel >> build. I filed a bug. > > Good to know. What if you specify explicitly to babeld not to use subtrees: > > ipv6-subtrees false

Re: [Babel-users] Babel on itty bitty boxes

So I set up ipv6-subtrees false for the pi3 also, did get rules, still got kernel errors. Turned off the internal wifi (so it's no longer trying to be a router), but it is still getting kernel errors from the traffic on the ethernet interface, so I suspect that ipv6 support on the pi has, until

Re: [Babel-users] Babel on itty bitty boxes

On Thu, Mar 24, 2016 at 4:30 PM, Juliusz Chroboczek wrote: >> I wish I lived in a world where more of the weird things "just worked" > > You'd be bored. Ha. At least compiling stuff on these boxes is slow enough to get in a song or two on the piano. Filed a bug

Re: [Babel-users] Babel on itty bitty boxes

and I filed this bug too. https://github.com/raspberrypi/linux/issues/1371 I wish I lived in a world where more of the weird things "just worked" ___ Babel-users mailing list Babel-users@lists.alioth.debian.org

[Babel-users] Babel on itty bitty boxes

On Thu, Mar 24, 2016 at 1:16 AM, Matthieu Boutier wrote: >> my gateway (routerA) is a source specific babel, without a version >> number but from an openwrt build about 2 months back. RouterB is a >> cerowrt box. > > On routerA: > > 1. How did you redistribute

Re: [Babel-users] Ready for 1.8.0?

A) I take it that "diversity routing" now matches the draft but does not use the right stuff to get the channel(s)? /me hides. I know, patches gladly accepted, (but ooh, have we made some progress on bufferbloat in wifi lately) B) I have been staring at a puzzling thing for the last few days

Re: [Babel-users] Some thoughts about Babel (feature requests)

I guess I am puzzled about the need for tunnels in the architecture. (I found the usage of "vpn" confusing, to me a vpn offers additional features like encryption). You connect to each node (all 1400 of them?) to gather data via nodewatcher? (Why not just have a dedicated "control" port?) or

[Babel-users] [RFC patch] linux perf support for libmusl

-perf-fixes-for-musl.patch @@ -0,0 +1,143 @@ +From 9673ba5369408008deef840e21edab3fa7a575fd Mon Sep 17 00:00:00 2001 +From: Dave Taht <dave.t...@bufferbloat.net> +Date: Tue, 15 Dec 2015 17:19:14 +0100 +Subject: [PATCH] perf fixes for musl + +--- + tools/lib/api/fs/tracing_path.c| 3 +++ + to

Re: [Babel-users] Detecting bridges

the resulting nanog conversation on detecting wireless bridged ended up interesting - with several clever techniques proposed - all probably futile. http://mailman.nanog.org/pipermail/nanog/2015-December/082902.html I fear the default for babel should become etx or rtt as most of the world

Re: [Babel-users] Detecting bridges

On Mon, Dec 14, 2015 at 8:44 PM, Juliusz Chroboczek wrote: > Wrong thread? Nope. > >> Is there a reliable way of determining that an underlying interface is >> a bridge? > > https://github.com/jech/babeld/blob/master/kernel_netlink.c#L723 > > However, this only

[Babel-users] latency in WLAN-SI

I tend to fork convos, sorry. On Tue, Dec 15, 2015 at 12:33 AM, Mitar wrote: > Hi! > > On Mon, Dec 14, 2015 at 11:39 AM, Juliusz Chroboczek > wrote: >> I'd like more evidence that this is needed. Estimating packet loss is >> very slow (since

Re: [Babel-users] Detecting bridges

On Tue, Dec 15, 2015 at 11:00 AM, Henning Rogge <hro...@gmail.com> wrote: > On Tue, Dec 15, 2015 at 10:35 AM, Dave Taht <dave.t...@gmail.com> wrote: >> On Mon, Dec 14, 2015 at 8:44 PM, Juliusz Chroboczek >>>> Is there a reliable way of determining that an unde

Re: [Babel-users] latency in WLAN-SI

In pouring through the astonishing *wealth* of data available via nodewatcher, I finally scrolled down to the chart next to the very bottom to find rtt measurements. so are you really seeing real-world peaks in the 7 second range or is that an artifact of something else? zoomed in:

Re: [Babel-users] Bucket full, dropping packet

On Sun, Dec 13, 2015 at 2:52 PM, Juliusz Chroboczek wrote: >> Ok, I can do some profiling on the babeld that is running on the VPN >> server with the large number of links. Just tell me what profiling data >> do you want? Should I just compile a debug build and run

Re: [Babel-users] Bucket full, dropping packet

On Tue, Dec 8, 2015 at 5:58 PM, Jernej Kos wrote: > Hello! > > On 07. 12. 2015 17:14, Juliusz Chroboczek wrote: >> Yes, that's expected. Please increase the limits, be bold, multiply them >> by 20. > > It seems that raising the limits solved the problem. Thanks! > > We are still

Re: [Babel-users] Low level rewrite, install filters

in the march towards 1.7 process... 0) What other features do you plan for 1.7? 1) Not clear to me if this does atomic route updates instead of delete/add? 2) can I try to get the "version" number into the telnet interface and command line in this go around? 3) fixing up wifi channel awareness

[Babel-users] Last call for signatures to the FCC on the wifi lockdown issue

?usp=sharing The principal signers (Dave Taht and Vint Cerf), are joined by many network researchers, open source developers, and dozens of developers of aftermarket firmware projects like OpenWrt. Prominent signers currently include: Jonathan Corbet, David P. Reed, Dan Geer, Jim Gettys, Phil

Re: [Babel-users] [PATCH] Add option to consider sysctl write failures as non-fatal.

Well, it would be better if babel checked to see if the (sometimes read-only) sysctl value was already correct, instead of blithely trying to write it. On Mon, Aug 10, 2015 at 9:43 AM, Jernej Kos jer...@kos.mx wrote: Hello! +1 for this patch. We are also running babeld in a Docker container

Re: [Babel-users] Fwd: Specify router-id explicitly

I just did a pull of your head, built it, started a new babel... waited 2 minutes (I was assuming the calculation for the routerid had changed?)... and did not get a working route to elsewhere until I tried talking to another route. (note I did not update the other 2 babelds in operation on this

[Babel-users] redistribute local prune?

Instead of adding a covering route, and explicitly denying other routes from being distributed, would it be possible to have a smarter filter with syntax like redistribute local prune That would cut something like this down from: 2601:696:8300:2cb0:dc9f:abff:fe06:1a24 via

[Babel-users] a cautionary note on setting up new babel nodes

As I am rolling out a bunch of new babel nodes, I decided to get a cluster (2 nanos and a pico) up in the lab, where I have good connectivity to the rest of the network, to replace an aging cluster by the pool. So I booted it up and configured it for the right channels and a new set of ip

Re: [Babel-users] Diversity routing in a many channeled world

The iw package appears canonical, and BSD licensed, and uses nl80211.h (exported from the linux kernel, also BSD licensed), and it's 3 netlink calls to derive the channel and other info. http://pastebin.com/JXqcLNfX root@davedesk2:~# strace -f -v iw dev wlan0 info 2 netlink.txt Interface wlan0

[Babel-users] Diversity routing in a many channeled world

On Wed, Jun 17, 2015 at 3:38 PM, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr wrote: To somewhat answer my own question, when babel is used on a standalone AP interface, it is unable to automagically determine the channel it is on. So I guess whatever it uses can only figure out a adhoc

Re: [Babel-users] ANNOUNCE: babeld-1.6.1

On Wed, Jun 17, 2015 at 1:28 AM, Gabriel Kerneis gabr...@kerneis.info wrote: Le 2015-06-17 05:41, Dave Taht a écrit : I did notice, in finally attempting to switch off of the old babels package in openwrt to the new babel package updated for 1.6.1, that there is no option in openwrt to enable

Re: [Babel-users] ANNOUNCE: babeld-1.6.1

another configuration example... given that the openwrt firewall is default-deny. config rule option name 'Allow-Babel' option family 'ipv6' option src 'wan' option dest_port '6696' option proto 'udp' option target 'ACCEPT' -- Dave Täht What will

Re: [Babel-users] ANNOUNCE: babeld-1.6.1

I build this and configured it on three systems, no issues. was about to attempt an openwrt build now that dnsmasq-2.73 has landed also... where... I did notice, in finally attempting to switch off of the old babels package in openwrt to the new babel package updated for 1.6.1, that there is no

  1   2   3   >