Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: wireguard@lists.zx2c4.com
Subject: Indefinite queuing for unconnected peers (Was: problem  wireguard + ospf + unconnected tunnels)
Date: Sat, 8 Jul 2017 16:21:56 +0200	[thread overview]
Message-ID: <20170708142156.GB13268@tuxmachine.polynome.dn42> (raw)
In-Reply-To: <1499116162.70598782@f401.i.mail.ru>

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

Hi,

The current approach is to queue all outgoing packets for an indefinite
amount of time when the peer is not connected or reachable.

I think it does not make much sense, and leads to the kind of issue you
mention here.  The initial goal was probably to queue packets just long
enough to be able to complete a handshake with the peer, which makes a lot
of sense (it would be annoying to drop the first packet of any outgoing
connection).  But the handshake should not take more than hundreds of
milliseconds.

Maybe Wireguard should drop packets from this queue after a few seconds?
Would it be hard to implement?

Baptiste

On Tue, Jul 04, 2017 at 12:09:22AM +0300, ae wrote:
> situation
> 2 tunnels
> 1 normal - 2nd with unconnected ending
> + ospfd quagge
> 
> At start everything works fine - but after ~ 30-60 seconds - the ospf stops working
> 
> This is due to the fact that the ospf daemon sends packets from the same socket on different interfaces - and in the tunnel interface everything goes fine - but in the 2nd packets accumulate
> And after a certain accumulation - the socket of the demon daemon stops working on sending completely "No buffer space available "
> 
> Is it possible to fix this with settings?
> 

> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-07-08 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 21:09 problem wireguard + ospf + unconnected tunnels ae
2017-07-04 15:55 ` Roelf "rewbycraft" Wichertjes
2017-07-04 17:10   ` Re[2]: " ae
2017-07-07 15:08     ` Roelf "rewbycraft" Wichertjes
2017-07-07 15:47       ` Re[2]: " ae
2017-07-10  0:46       ` Jason A. Donenfeld
2017-07-10 17:06         ` Re[2]: " ae
2017-07-10 17:09           ` Jason A. Donenfeld
2017-07-10 17:26             ` Re[4]: " ae
2017-07-08 14:21 ` Baptiste Jonglez [this message]
2017-07-08 18:51   ` Indefinite queuing for unconnected peers (Was: problem wireguard + ospf + unconnected tunnels) Roelf "rewbycraft" Wichertjes
2017-07-10  0:53   ` Jason A. Donenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170708142156.GB13268@tuxmachine.polynome.dn42 \
    --to=baptiste@bitsofnetworks.org \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).