Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Will van Gulik <mailing-porcus@porcus.ch>
To: wireguard@lists.zx2c4.com
Subject: Re: Maximum number of interfaces + Debug
Date: Thu, 5 Jan 2017 23:49:03 +0100	[thread overview]
Message-ID: <9F550D1D-A374-48D6-881E-D626BB250E8F@porcus.ch> (raw)
In-Reply-To: <698F0489-3376-4D52-A48E-A4C9F344D817@porcus.ch>

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.

Any clue, ideas, else ?

Cheers,

Will

> On 03 Jan 2017, at 09:52, Will van Gulik <mailing-porcus@porcus.ch> =
wrote:
>=20
> Hi,
>=20
> 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.
>=20
> 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 ?
>=20
> I'm testing that on a Debian with 4.8.7-1, running on a KVM host.
>=20
> Any insight ?
>=20
> Kind regards,
>=20
> Will
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2017-01-05 22:40 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 ` Will van Gulik [this message]
2017-01-11  9:58   ` Maximum number of interfaces + Debug Baptiste Jonglez
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=9F550D1D-A374-48D6-881E-D626BB250E8F@porcus.ch \
    --to=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).