All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roelf \"rewbycraft\" Wichertjes" <mailings+wireguard@roelf.org>
To: wireguard@lists.zx2c4.com
Subject: Re: problem wireguard + ospf + unconnected tunnels
Date: Tue, 4 Jul 2017 17:55:48 +0200	[thread overview]
Message-ID: <740cb9af-aba8-c610-c1b7-0a7c69396e46@roelf.org> (raw)
In-Reply-To: <1499116162.70598782@f401.i.mail.ru>

 From what you said, I surmise the following setup:
- Three devices, A, B and C.
- A talks ospf to B over wireguard.
- A talks ospf to C over wireguard.
- The connection between A and C has gotten interrupted. (maybe C is a 
laptop)
- The error causes the entire ospf process to fail for all interfaces.
   In other words: A will suddenly also stop talking B when the 
connection A<->C fails?

If I am correct in that, there are a few things to note:
  - The "No buffer space available" error is normal from wireguard when 
an interface cannot reach the peer.
  - A single "failing" interface shouldn't kill the ospf process for all 
interfaces.
  - This sounds more like a quagga problem, as I have a similar setup (I 
use my laptop for device C in my case) except I use the BIRD routing 
daemon instead of quagga (and this setup works fine for me).

Of course, before any definitive conclusions can be made, we'll need a 
bit more information. Could you possibly provide us with the following 
pieces of information:
  - What distribution are you using?
  - What kernel (version) are you using?
  - What wireguard version are you using?
  - What quagga version are you using?
  - Please provide the kernel logs.
  - Please provide the quagga logs.

On 07/03/2017 11:09 PM, 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
> 

  reply	other threads:[~2017-07-04 15:38 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 [this message]
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 ` Indefinite queuing for unconnected peers (Was: problem wireguard + ospf + unconnected tunnels) Baptiste Jonglez
2017-07-08 18:51   ` 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=740cb9af-aba8-c610-c1b7-0a7c69396e46@roelf.org \
    --to=mailings+wireguard@roelf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.