> > We are not tuning for fragmentation, nor are we setting mtu on
> > the endpoint.
>
> Doing that might be worth a try. i.e. try to avoid sending UDP packets
> that require extra kernel work (i.e. fragmentation) seeing as openvpn can
> handle that itself.
We messed around with MTU, inside OpenV
On 2014/07/20 22:15, Darryl Wisneski wrote:
> > How is fragmentation being handled? In OpenVPN or relying on the kernel
> > to do it? Or are you using small mtu anyway to avoid frags?
>
> We are not tuning for fragmentation, nor are we setting mtu on
> the endpoint.
Doing that might be worth a tr
On Fri, Jul 18, 2014 at 09:36:23AM +, Stuart Henderson wrote:
> On 2014-07-17, Darryl Wisneski wrote:
> > netstat -s -p udp |grep "dropped due to full socket"
> > 345197 dropped due to full socket buffers
>
> We're assuming this relates to openvpn packets but you can check which
> sockets ha
On 2014-07-17, Darryl Wisneski wrote:
> netstat -s -p udp |grep "dropped due to full socket"
> 345197 dropped due to full socket buffers
We're assuming this relates to openvpn packets but you can check which
sockets have queues: (the sendq/recvq counters).
netstat -an | grep -v ' 0 0'
So
5 and we
have new hardware) we started to notice dropped segments of SIP calls and
we discovered we simultaneously are dropping UDP packets on the endpoint.
We can watch the counter netstat increase as the sip dropout occurs.
netstat -s -p udp |grep "dropped due to full socket"
345197 drop
5 matches
Mail list logo