From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: Will van Gulik <mailing-porcus@porcus.ch>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Maximum number of interfaces + Debug
Date: Wed, 11 Jan 2017 10:58:37 +0100 [thread overview]
Message-ID: <20170111095837.GB11399@tuxmachine.polynome.dn42> (raw)
In-Reply-To: <9F550D1D-A374-48D6-881E-D626BB250E8F@porcus.ch>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
Hi Will,
On Thu, Jan 05, 2017 at 11:49:03PM +0100, Will van Gulik wrote:
> Hi Everyone,
>
> I went a bit further and did compile the module with debug rather than using the repo's version, and I get a :
> wireguard: Invalid packet from xxxx:yyy
> in my dmesg. I would have hoped to get something more clear, but would a module version mismatch be an issue or does this mostly looks like a key issue ? I would be strange because I reissued them several times.
There have been backwards-incompatible changes recently: can you make sure
that you use the exact same wireguard version on all peers?
> Any clue, ideas, else ?
>
> Cheers,
>
> Will
>
> > On 03 Jan 2017, at 09:52, Will van Gulik <mailing-porcus@porcus.ch> wrote:
> >
> > Hi,
> >
> > I'm trying to use multiple wireguard tunnel in one VM at the same time, but it seems that only the first two I configured are working. I'm currently trying with 5 interfaces, I see the incoming packet in tcpdump but no reaction of the destination host with all the wg interfaces.
> >
> > I'm not sure there is a limitation on that, I could totally have missed that. Should I use 1 interface with multiple peers rather than multiple interface ?
> >
> > I'm testing that on a Debian with 4.8.7-1, running on a KVM host.
> >
> > Any insight ?
> >
> > Kind regards,
> >
> > Will
> > _______________________________________________
> > WireGuard mailing list
> > WireGuard@lists.zx2c4.com
> > https://lists.zx2c4.com/mailman/listinfo/wireguard
>
> _______________________________________________
> 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 --]
next prev parent reply other threads:[~2017-01-11 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 8:52 Maximum number of interfaces ? Will van Gulik
2017-01-05 22:49 ` Maximum number of interfaces + Debug Will van Gulik
2017-01-11 9:58 ` Baptiste Jonglez [this message]
2017-01-11 21:49 ` Will van Gulik
2017-01-11 23:57 ` Baptiste Jonglez
2017-01-11 23:59 ` Jason A. Donenfeld
2017-01-12 8:11 ` Will van Gulik
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=20170111095837.GB11399@tuxmachine.polynome.dn42 \
--to=baptiste@bitsofnetworks.org \
--cc=mailing-porcus@porcus.ch \
--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).