Re: [Babel-users] Fastest convergence possible

Stanisław Drozd writes: > Hello, > I'm developing a project which uses Babel and for testing I would set up > some veth-connected Linux network namespaces to form a mesh of topology of > my choosing. Using `-C "default update-interval 1" I was able to trim down > my

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

Juliusz Chroboczek writes: >> Well, that is quite useful in any case. > > It's very useful, but it creates extra state, extra timers, and might > timeout over wireless (EIGRP style). So I'm not really sure how I feel > about it. Sure, it adds a bit of temporary state; but if it

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

Juliusz Chroboczek writes: >> My thinking on this is that you only need the host routes when a client >> actually roams. > > This is only going to work if you either use no hold time, or implement > the optional algorithm in Section 3.1 of rfc6126bis. I'm assuming you mean the

Re: [Babel-users] babeld interface

Juliusz Chroboczek writes: >> In this example, parsing the custom format in Python would be something like: > > No, parsing input using string.split is always incorrect. You really > want to write a proper lexer. > > The lexer I posted above is 70 lines of C, including full error >

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

Christof Schulze writes: > There are approaches to reduce the amount of routes per client > including using nat66 on each node. You certainly are making it sound > like there should be put some thought into reducing the amount of > routes. This will be the next step

Re: [Babel-users] babeld interface

Juliusz Chroboczek writes: >> Nils and I wrote such a daemon, called mmfd. It is able to forward >> multicast packets in the whole network. To learn about the topology and >> the relevant neighbours, it queries babeld: mmfd is listening via >> "monitor" on the babeld socket. > >

Re: [Babel-users] List-ID

Christof Schulze writes: > Hi Guys, > > I am aware that you might already feel spammed by my mailing activity. > May I ask for the list admin to include a List-ID header in the mails of > this mailing list for easier filtering? From: Christof Schulze

Re: [Babel-users] SOLVED - routes appearing later than hoped-for

Juliusz Chroboczek writes: >> The implementation does not have all the battle-tested optimisations of >> babeld at the protocol level. > > On the other hand, babeld suffers from having too many features (it > serves among others as a platform for student projects), which implies >

Re: [Babel-users] SOLVED - routes appearing later than hoped-for

Christof Schulze writes: > I wasn't aware of Toke's implementation of babel so far. Why are there > two? Why wouldn't you have two? ;) A good way to check whether an RFC is well-defined is by having someone else implement it without looking at the source code of the

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

Christof Schulze writes: > possible solutions that come to my mind are: > * making babel trigger updates on newly appeared routes Wait, it isn't doing that already? Yeah, this would be an obvious improvement :) Also, why isn't l3roamd detecting when the client

Re: [Babel-users] babeld building and binary size

Rodrigo Garcia writes: > Hello, i've been compiling babeld and modified versions of it using make > and to cross compile; make CC=mipsel-linux-gcc > PLATFORM_DEFINES='-march=mips32' > > Using gcc the size of the executable file is 361K and about the same > size when cross

Re: [Babel-users] Some notes on seqno requests in Babel

Juliusz Chroboczek writes: >>> Toke, David, what do you guys think -- shall we leave this undefined, or >>> should we add some values? > >> Hmm, suppose it wouldn't hurt to add it to appendix B? > > Add what? The values used by babeld? The values used by BIRD? The > optimal

Re: [Babel-users] About an authentication extension

Rodrigo Garcia writes: > I see, however the project has already been accepted so i will have to > do it anyway :( > > Maybe i can think not to use random numbers but something to make it > more difficult that a false ciphertext be accepted by other nodes. Well, the way you

Re: [Babel-users] About an authentication extension

Rodrigo Garcia writes: >> But if everyone knows how to decrypt all the tokens they are not really >> secret; so it basically becomes the same as a signature, no? Except if >> it's *not* signed you may be able to spoof other values by changing the >> ciphertext of a valid token

Re: [Babel-users] About an authentication extension

Rodrigo Garcia <str...@riseup.net> writes: > El 08/09/17 a las 05:28, Toke Høiland-Jørgensen escribió: >> Rodrigo Garcia <str...@riseup.net> writes: >> >>> Hello, i've been working on an extension to the babel protocol to >>> authenticate updates

Re: [Babel-users] About an authentication extension

Rodrigo Garcia writes: > Hello, i've been working on an extension to the babel protocol to > authenticate updates using RSA. It's mostly an academic excercise and i > have planned the first functional versions in a month or so. What are you trying to achieve? What is your

Re: [Babel-users] BabelWeb 2

Juliusz Chroboczek writes: > Dear all, > > BabelWeb has been rewritten almost from scratch in Go by Belynda Hamaz, > Edward Guyot and Fyodor Ryabinin. It's much more maintainable and > extensible code, and much easier to deploy, than the old BabelWeb. > > A prototype is running

Re: [Babel-users] [babel] draft-boutier-babel-source-specific-02

Juliusz Chroboczek writes: >> Does this mean whatever we decide for wildcard requests applies to >> wildcard updates as well? > > Yes, er, no, er, I have no idea. I do always enjoy your elucidating comments... ;) -Toke ___ Babel-users

Re: [Babel-users] [babel] draft-boutier-babel-source-specific-02

Matthieu Boutier writes: > About wildcard updates: they're used to retracts all routes, typically > before a node stops. I don't see any use case of source-specific > wildcard updates (which would mean "retraction of source-specific > routes")... Does this mean whatever we

Re: [Babel-users] [babel] source sub-tlv

Juliusz Chroboczek writes: > I support (3). Last time I spoke to him, Toke supported (4). I am > opposed to (2). I can live with (1). Well, I can see the point in retaining wildcard requests for speeding up convergence when a new node joins a network. Don't recall expressing a

Re: [Babel-users] [babel] draft-ietf-babel-rfc6126bis-02

Juliusz Chroboczek writes: > Both babeld and sbabeld have support for mandatory bits in their > "mandatory" branches. I'll wait a few days to see if there are any > flaws in this proposal, then merge into trunk. Please consider > implementing mandatory bits if you have an

Re: [Babel-users] [babel] draft-ietf-babel-rfc6126bis-02

Juliusz Chroboczek writes: > Dear all, > > I've just published a new version of the Babel protocol specification: > > https://tools.ietf.org/html/draft-ietf-babel-rfc6126bis-02 I read it, and I think the updates are an improvement. I think the specification of the extension

Re: [Babel-users] Main Loop Frequency

Lorenzo Ghiro writes: > Hi everybody! > > I would like to know how to schedule an operation (write to file) with > below-second frequency, any advise? > > My strategy up to now has been to check, in the main loop, how many > time passed from the last operation's

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

"L. D. Pinney" writes: > Go back to playing the guitar and smoking dopethat's what you do best. > > STOP CROSS POSTING YOU FSCKin' Clown Boy Dude, seriously? Lay off the abuse. Even if your argument had any merit, this kind of language is uncalled for... -Toke

Re: [Babel-users] [babel] A quick summary of babel@ietf

Juliusz Chroboczek writes: > My feeling right now -- unless we f*ck up really badly, this is going to > be a productive and fun working group. I agree. One thing that I would like to emphasise from the meeting was the direction Juliusz set out for the working

Re: [Babel-users] Version 1.6.0

Ondrej Zajicek <santi...@crfreenet.org> writes: > On Sun, May 01, 2016 at 03:32:58PM +0200, Toke Høiland-Jørgensen wrote: >> Ondrej Zajicek <santi...@crfreenet.org> writes: >> >> > - in some cases (e.g. babel_handle_route_request()), check for plen == 0 &g

Re: [Babel-users] Version 1.6.0

Juliusz Chroboczek writes: >> If this is not the case, I think the RFC needs to specify what, >> exactly, is meant by a "wildcard address". I've always thought of >> ::/0 as the wildcard address; and doesn't "default route" also mean >> "wildcard route"? > > Wow,

Re: [Babel-users] Version 1.6.0

Ondrej Zajicek writes: > Some comments to my changes. I originally thought that i would just do > some minor formatting changes, but i end with some heavy code changes and > plenty of bugfixes. Hopefully i did not make much more errors. Thanks for the overview. Some

Re: [Babel-users] Babel in Bird 1.6.0

Juliusz Chroboczek writes: >> Okay, actually trying to put this into code: Is the intention here that >> a null-router ID update is acceptable only on *wildcard* retractions or >> on *all* retractions? > > In RFC 6126, there's nothing special about a null

Re: [Babel-users] Babel in Bird 1.6.0

Juliusz Chroboczek writes: >> Why is babeld setting the 0x40 flag on those updates, though? > > It was supposed to clear the router-id. Recent versions no longer do. Ah, I see. But surely, having an update with AE 0 and the flag set would not be out of spec

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

Baptiste Jonglez <bapti...@bitsofnetworks.org> writes: > On Sat, Apr 30, 2016 at 04:15:46PM +0200, Toke Høiland-Jørgensen wrote: >> Baptiste Jonglez <bapti...@bitsofnetworks.org> writes: >> >> > Ah, I thought that this "interface" statement was spe

Re: [Babel-users] Babel in Bird 1.6.0

Juliusz Chroboczek writes: >> But those updates seem to set flag 0x40, so that's not "without a router >> ID" is it? > > Yeah, it was meant to clear the router-id. > >>> The plan is to explicitly allow such retractions in RFC 6126-bis, but >>> they are clearly not

Re: [Babel-users] Babel in Bird 1.6.0

Baptiste Jonglez writes: > Ah, I thought that this "interface" statement was specific to Babel, but > it's actually defined for all protocols. The syntax seems fairly complex: > > http://bird.network.cz/?get_doc=bird-3.html#ss3.3 > > IP prefixes are allowed for

Re: [Babel-users] Babel in Bird 1.6.0

Juliusz Chroboczek writes: >> I remember running into this. What happens here is that babeld sends an >> update without a preceding router_id TLV, with a wildcard address, but >> flag 0x40 set (meaning "infer the router ID from the address"). >> While I'm not sure

[Babel-users] Fwd: Version 1.6.0

Version 1.6 of the Bird routing daemon was just released and includes my Babel implementation :) -Toke Original Message From: Ondrej Filip Sent: 29 April 2016 18:35:33 CEST To: bird Subject: Version 1.6.0 Dear Bird users, the long

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

Juliusz Chroboczek writes: > For discovery, multicast is unavoidable -- there's simply no way you're > going to send a unicast to a node that you haven't discovered yet. Presumably the access point could transparently turn IP-level multicast into a unicast frame

Re: [Babel-users] babeld and systemd [was: babeld wishlist]

Juliusz Chroboczek writes: > Perhaps I'm confused, but are you trying to make it possible to run > multiple instances of babeld? Yes, exactly. > Are your users actually clamoring for that feature? My users being me in this case: yes. Basically this comes from

Re: [Babel-users] babeld and systemd [was: babeld wishlist]

Baptiste Jonglez writes: >> Awesome! Any chance of also including a 'babeld@.service' file to easily >> run babeld on a single interface without editing the configuration file? :) > > You mean, in the Arch package, in addition to the regular service > file? Yeah,

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

Gabriel Kerneis writes: > Baptiste: I don't really understand if I'm supposed to push to the > 'for-15.05' branch too. People seem to keep updating it, even though the > release has been done long ago. Any hint? I've always taken this to mean that 'if you want users of the

Re: [Babel-users] babeld and systemd [was: babeld wishlist]

Baptiste Jonglez writes: > Thanks, that did the trick! I have updated the service file to restart > babeld automatically in case of failure, if somebody is interested: Awesome! Any chance of also including a 'babeld@.service' file to easily run babeld on a single

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

Juliusz Chroboczek writes: > All of your requests are reasonable. (But please distinguish between > Babel, which is a protocol, and babeld, which is just one of the > available implementations of Babel. And not necessarily the bestest -- > Toke's implementation,

Re: [Babel-users] babeld wishlist

Dave Taht writes: > ** full debian/ubuntu/fedora/arch support > ** clean restarts and other reconfiguration > *** openwrt procd support > *** systemd support There's a package for Arch in the AUR: https://aur.archlinux.org/packages/babeld/ That also includes a systemd unit

[Babel-users] [PATCH] Add the Babel routing protocol to Bird

protocol's logic is needed. And of course documentation of the configuration options. But since I expect to have to do at least another iteration on this, I decided to defer that in the interest of keeping the ball rolling. Signed-off-by: Toke Høiland-Jørgensen <t...@toke.dk> Cc: babel

[Babel-users] [PATCH] Fix restoring sysctls on shutdown.

The previous patch to only write sysctls when needed failed to restore values that was 0 before being set by babeld. This fixes that. Signed-off-by: Toke Høiland-Jørgensen t...@toke.dk --- kernel_netlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel_netlink.c b

[Babel-users] [PATCH v4 1/2] Rework sysctl writing to only write when needed.

This reworks the sysctl handling to only write a sysctl if it is not already the desired value. In addition, the Linux sysctl knobs are now stored in a lookup table which is looped through, to avoid code duplication in the setup routine. Signed-off-by: Toke Høiland-Jørgensen t...@toke.dk

[Babel-users] [PATCH v4 2/2] Add configuration flag to skip initial kernel setup.

This adds a configuration flag to skip kernel (sysctl) setup on daemon startup. This can be useful if running in, e.g., a container environment where setting sysctls are not allowed. Signed-off-by: Toke Høiland-Jørgensen t...@toke.dk --- babeld.c | 1 + babeld.h | 1 + babeld.man

Re: [Babel-users] [PATCH v3 1/2] Rework sysctl writing to only write when needed.

On 20 August 2015 02:25:19 BST, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr wrote: +if(s-was != s-want) { +rc = write_proc(s-name, s-want); +if(rc 0) { +perror(Couldn't write sysctl); +return -1; +

[Babel-users] Implementing Babel in the Bird routing daemon

Hi everyone I've been amusing myself with doing a clean-slate implementation of Babel in the Bird routing daemon. It is now at a stage where I think it is useful to solicit some feedback. I've just posted a patch to the Bird mailing list with the code and a description of the state and

[Babel-users] [PATCH v3 2/2] Add configuration flag to skip initial kernel setup.

This adds a configuration flag to skip kernel (sysctl) setup on daemon startup. This can be useful if running in, e.g., a container environment where setting sysctls are not allowed. Signed-off-by: Toke Høiland-Jørgensen t...@toke.dk --- babeld.c | 1 + babeld.h | 1 + babeld.man

[Babel-users] [PATCH v3 1/2] Rework sysctl writing to only write when needed.

This reworks the sysctl handling to only write a sysctl if it is not already the desired value. In addition, the Linux sysctl knobs are now stored in a lookup table which is looped through, to avoid code duplication in the setup routine. Signed-off-by: Toke Høiland-Jørgensen t...@toke.dk

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

the daemon fail to start. Signed-off-by: Toke Høiland-Jørgensen t...@toke.dk --- babeld.c | 8 ++-- babeld.h | 1 + babeld.man | 12 configuration.c | 3 +++ kernel_netlink.c | 7 ++- 5 files changed, 28 insertions(+), 3 deletions(-) diff --git

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

Toke, wouldn't it be better instead of your patch: 1. to follow Dave's suggestion by default; 2. to add a new config file option that doesn't set any sysctls unconditionally? I'm also dubious about the command-line option -- shouldn't this be just a config file directive, which

Re: [Babel-users] [Cerowrt-devel] ipv6 confusion with source specific gateways.

Juliusz Chroboczek j...@pps.univ-paris-diderot.fr writes: default from :: via fe80::201:5cff:ee62:b646 dev ge00 proto static metric 1024 # should I even have a default route at all? The source on this is actually ::/128 You mean ::/0. No, I do not, actually. That would make it just a

Re: [Babel-users] Lookingfor

Dave Taht dave.t...@gmail.com writes: There is a budget available in a public institution to sponsor a PhD student who would work on babel. Sounds like it could be interesting; what's the time frame for getting the position filled? :) -Toke pgp1J0UOGrs2j.pgp Description: PGP signature