Re: [wireguard-devel ] traffic shapping

2017-03-08 Thread Nicolas Prochazka
in doubt i add all ipv6 kernel options ... and i'm using tc filter , not iptables fwmark. Regards, Nicolas 2017-03-08 17:00 GMT+01:00 Baptiste Jonglez : > Hi Nicolas, > > For posterity, can you be more specific about how you solved your issue? > You were simply

Release monitoring (Was: Wireguard added to Alpine Linux)

2017-03-08 Thread Baptiste Jonglez
Hi Stuart, On Thu, Mar 02, 2017 at 09:49:53PM +, Stuart Cardall wrote: > To monitor releases @ Alpine we use https://release-monitoring.org/ - if > it doesn't pick up the changes I'll subscribe. Thanks for mentioning this, it's a nice tool! I started using it for other projects. By the

Re: [wireguard-devel ] traffic shapping

2017-03-08 Thread Baptiste Jonglez
Hi Nicolas, For posterity, can you be more specific about how you solved your issue? You were simply missing traffic shaping support for IPv6 in your kernel? Which symbols were needed? Thanks, Baptiste On Wed, Mar 08, 2017 at 02:39:23PM +0100, Nicolas Prochazka wrote: > hello, > to close, it's

Re: [wireguard-devel ] traffic shapping

2017-03-08 Thread Nicolas Prochazka
Hello again, So i verify my configuration, - on a virtual tap , traffic shaping is ok with same configuration - on physical card, traffic shaping is ok - on wg0 , all traffic are going to default queue,filter seems to be not applied , tcpdump on wg0 is ok with my queue definition, only difference