search for: dtaht

Hello, Dave Taht, on Wed 02 Dec 2015 13:21:56 +0100, wrote: > I'd made a start on the send direction here: > https://github.com/dtaht/tinc/commits/master > > Perhaps that will help. Well, converting a sendto call into a sendmsg call is not really "hard" :) What will be really hard is getting multiple packet receive/send over the tap/tun device, because support for it has to be added at the kernel layer first....

On Wed, Dec 2, 2015 at 1:36 PM, Samuel Thibault <samuel.thibault at ens-lyon.org> wrote: > Hello, > > Dave Taht, on Wed 02 Dec 2015 13:21:56 +0100, wrote: >> I'd made a start on the send direction here: >> https://github.com/dtaht/tinc/commits/master >> >> Perhaps that will help. > > Well, converting a sendto call into a sendmsg call is not really "hard" > :) the "hard" bit was in trying to reliably extract the tos bits and then figure out how to deal with correct ecn encap/decap acc...

...f minutes between two endpoints (very impressed, thx!), and started hacking at it to see where I would get. This is partially the outgrowth of looking at an ietf document on ecn encapsulation and vpns.... https://tools.ietf.org/html/rfc6040 Experimental patches so far are at: https://github.com/dtaht/tinc I successfully converted tinc to use sendmsg and recvmsg, acquire (at least on linux) the TTL/Hoplimit and IP_TOS/IPv6_TCLASS packet fields, as well as SO_TIMESTAMPNS, and use a higher resolution internal clock. Got passing through the dscp values to work also, but: A) encapsulation of ecn c...

On Wed, Dec 03, 2014 at 12:07:59AM -0800, Dave Taht wrote: [...] > https://github.com/dtaht/tinc > > I successfully converted tinc to use sendmsg and recvmsg, acquire (at > least on linux) the TTL/Hoplimit and IP_TOS/IPv6_TCLASS packet fields, Windows does not have sendmsg()/recvmsg(), but the BSDs support it. > as well as SO_TIMESTAMPNS, and use a higher resolution interna...

Hello, Linux has a recvmmsg() system call which allows to achieve several recvfrom() at a time. The patch below makes tinc use it (patch against 1.1-pre11). Basically the patch turns the handle_incoming_vpn_data variables into arrays (of size 1 when recvmmsg is not available, and thus compiled the same as before), and makes the code index into the arrays. You may want to use interdiff -w

Oh, goodie! I'd made a start on the send direction here: https://github.com/dtaht/tinc/commits/master Perhaps that will help. I would not just pull that as it was just some late night hacking... and it turns out the posix time calls I upgraded to to get better than second resolution are not supported on OSX. My ultimate intent was to move to not bottlenecking or dropping pack...

On Wed, Dec 3, 2014 at 4:02 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Wed, Dec 03, 2014 at 12:07:59AM -0800, Dave Taht wrote: > > [...] >> https://github.com/dtaht/tinc >> >> I successfully converted tinc to use sendmsg and recvmsg, acquire (at >> least on linux) the TTL/Hoplimit and IP_TOS/IPv6_TCLASS packet fields, > > Windows does not have sendmsg()/recvmsg(), but the BSDs support it. > >> as well as SO_TIMESTAMPNS, and use...

...or, but I do not remember the reason off the top of my head." > > > > On Dec 3, 2014, Guus Sliepen <guus at tinc-vpn.org> wrote: >> >> On Wed, Dec 03, 2014 at 12:07:59AM -0800, Dave Taht wrote: >> >> [...] >>> >>> https://github.com/dtaht/tinc >>> >>> I successfully converted tinc to use sendmsg and recvmsg, acquire (at >>> least on linux) the TTL/Hoplimit and IP_TOS/IPv6_TCLASS packet fields, >> >> >> Windows does not have sendmsg()/recvmsg(), but the BSDs support it. >> >>&g...