Displaying 4 results from an estimated 4 matches for "jasdeep".
Did you mean:
jandeep
2014 Dec 03
0
tinc vpn: adding dscp passthrough (priorityinherit), ecn, and fq_codel support
...etty doable without modifying the protocol any, but I'm not sure of
> it's value until I saturate some cpu more.
I'd welcome any work in this area :)
> (and if you thought recvmsg was complex, look at recvmmsg)
It seems someone is already working on that, see
https://github.com/jasdeep-hundal/tinc.
> D)
>
> the bottleneck link above is actually not tinc but the gateway, and as
> the gateway reverts to codel behavior on a single encapsulated flow
> encapsulating all the other flows, we end up with about 40ms of
> induced delay on this test. While I have a bette...
2014 Dec 03
3
tinc vpn: adding dscp passthrough (priorityinherit), ecn, and fq_codel support
I have long included tinc in the cerowrt project as a lighter weight,
meshy alternative to conventional vpns.
I sat down a few days ago to think about how to make vpn connections
work better through fq_codel, and decided I should maybe hack on a vpn
to do the job. So I picked up tinc's source code for the first time,
got it working on IPv6 as a switch in a matter of minutes between two
2014 Dec 03
1
tinc vpn: adding dscp passthrough (priorityinherit), ecn, and fq_codel support
...eded to get to my lab in
los gatos from gf's in SF and
ssh tunneling and portforwarding was getting bothersome...
so I hacked on tinc. :) )
>> (and if you thought recvmsg was complex, look at recvmmsg)
>
> It seems someone is already working on that, see
> https://github.com/jasdeep-hundal/tinc.
Seemed to be mostly windows related hacking.
I am not ready to consider all the infrastructure required to
accumulate and manage packets inside of tinc, nor (after
fighting with recvmsg/sendmsg for 2 days) ready to tackle
recvmmsg... or threads and ringbuffers and all the headache
th...
2014 Dec 03
0
[Cerowrt-devel] tinc vpn: adding dscp passthrough (priorityinherit), ecn, and fq_codel support
...it's value until I saturate some cpu more.
>>
>>
>> I'd welcome any work in this area :)
>>
>>> (and if you thought recvmsg was complex, look at recvmmsg)
>>
>>
>> It seems someone is already working on that, see
>> https://github.com/jasdeep-hundal/tinc.
>>
>>> D)
>>>
>>> the bottleneck link above is actually not tinc but the gateway, and as
>>> the gateway reverts to codel behavior on a single encapsulated flow
>>> encapsulating all the other flows, we end up with about 40ms of
>&g...