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 <[email protected]> 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 > > [email protected] > > https://lists.zx2c4.com/mailman/listinfo/wireguard > > _______________________________________________ > WireGuard mailing list > [email protected] > https://lists.zx2c4.com/mailman/listinfo/wireguard
signature.asc
Description: PGP signature
_______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
