> The API should not be > affected Actually, scratch that. If we're bound to go public, it'd probably be a good idea to append a "jool_" prefix to the name of every exported function.
On Fri, Mar 6, 2020 at 11:15 AM Alberto Leiva <[email protected]> wrote: > > Oh, by the way: I'm currently working on a complete rewrite of the > Netlink code internals to patch issue #322. The API should not be > affected, but you might want to wait until Jool 4.0.8 just to be sure. > > On Fri, Mar 6, 2020 at 11:13 AM Alberto Leiva <[email protected]> wrote: > > > > > Where are jool's sessions saved? > > > > Nowhere, presently. They are kept in the RAM. > > > > > would it be of interest > > > to integrate jool's session support into our new daemon? > > > > Well, Jool presently pushes sessions to anyone listening on its > > Generic Netlink family if the `ss-enabled` global is true. > > And a daemon can similarly get the full table by performing the same > > Netlink request `jool session display` does under the hood. > > > > You can get access to these functions by importing Jool's Netlink > > library (https://github.com/NICMx/Jool/tree/master/src/usr/nl). > > Though, if you're using Debian, is presently exported privately into > > the package. But this could be upgraded with some work, and I don't > > see any objections for doing this. > > > > Here's the sample usage for querying the whole table: > > > > - Initialization: > > https://github.com/NICMx/Jool/blob/master/src/usr/argp/wargp/session.c#L112-L114 > > - Request: > > https://github.com/NICMx/Jool/blob/master/src/usr/argp/wargp/session.c#L127-L128 > > (You want to do this three times if you want all three protocols.) > > - Response handler: > > https://github.com/NICMx/Jool/blob/master/src/usr/argp/wargp/session.c#L55-L100 > > > > Am I answering your question? > > > > On Fri, Mar 6, 2020 at 10:54 AM Nico Schottelius > > <[email protected]> wrote: > > > > > > > > > Good morning list, > > > > > > we at ungleich are currently looking into writing a replacement for > > > conntrackd that works in IPv6 only environments. > > > > > > The basic concept is "get sessions, multicast them, from time to time > > > multicast the whole session table" - which plus/minus should be able to > > > create a multi master setup in the end. > > > > > > My question and reason why I post this here is: would it be of interest > > > to integrate jool's session support into our new daemon? From my point > > > of view jool's session entries are very similar in nature and thus we > > > could implement this as well - or even use joold as a basis. > > > > > > Looking forward to what you think about this. > > > > > > Best regards, > > > > > > Nico > > > > > > > > > > > > -- > > > Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch > > > _______________________________________________ > > > Jool-list mailing list > > > [email protected] > > > https://mail-lists.nic.mx/listas/listinfo/jool-list _______________________________________________ Jool-list mailing list [email protected] https://mail-lists.nic.mx/listas/listinfo/jool-list
