problem wireguard + ospf + unconnected tunnels
Roelf "rewbycraft" Wichertjes
mailings+wireguard at roelf.org
Tue Jul 4 17:55:48 CEST 2017
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
- 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
- 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:
> 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 at lists.zx2c4.com
More information about the WireGuard