wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Daniel <tech@tootai.net>
To: wireguard@lists.zx2c4.com
Subject: Re: ipv6 connexion fail - ipv4 OK
Date: Tue, 31 Aug 2021 19:50:16 +0200	[thread overview]
Message-ID: <d7095107-050f-2075-00cb-fdaa86d6daf5@tootai.net> (raw)
In-Reply-To: <20210830225927.6df90edb@natsu>


Le 30/08/2021 à 19:59, Roman Mamedov a écrit :
> On Mon, 30 Aug 2021 19:44:21 +0200
> Daniel <tech@tootai.net> wrote:
>>> Do you get WG working at all, between some other two hosts (not involving this
>>> particular server for now)?
>> Yes. Clients are shown on both sides as connected, trafic seems to go
>> out on each side but other one as received near to nothing.
> I mean not just "shown as connected", but have you got actual traffic working
> between any two hosts. Even just forgetting this server for a while. So that
> you can rule out some general issue and concentrate on just the particular
> machine setup.

I went a step further. Server has a /64 on eth0, his address being .1/64 
Interface I gave to wireguard is called wigserver and get .a2/64 as 
address when up. Now I start the client which is a .24/64 while tcpdump 
-ni any udp and port 38194 is running on the server. Output is

19:28:45.790295 eth0  In  IP6 2001:db8:16e:10::24.50012 > 
2001:db8:c2c:7c50::a2.38194: UDP, length 148
19:28:45.790629 eth0  Out IP6 2001:db8:c2c:7c50::a2.38194 > 
2001:db8:16e:10::24.50012: UDP, length 92
19:29:06.572059 eth0  Out IP6 2001:db8:c2c:7c50::1.38194 > 
2001:db8:16e:10::24.50012: UDP, length 148
19:29:11.947969 eth0  Out IP6 2001:db8:c2c:7c50::1.38194 > 
2001:db8:16e:10::24.50012: UDP, length 148
19:29:17.324065 eth0  Out IP6 2001:db8:c2c:7c50::1.38194 > 
2001:db8:16e:10::24.50012: UDP, length 148

As you can see, the original request is going to the right IP which 
respond with the right source IP (line 1 and 2) From here, all packets 
are going out with the IP of eth0 not the one from wigserver which is 
.a2/64. The client has "allowed ips =, ::/0"

Remember, no FW involved. Before this test I bring up interfaces without 
wireguard configuration and did server/client test like nc -lu IP PORT 
on the server while on the client I used nc -u IP PORT Everything worked 
well. I also started the client while server was not running and got the 
ICMP6 respons "unreachable port" sended to the client. I also tried to 
tell to the client to connect to the .1/64 insteed of the .a2/64, didn't 

If someone had an idea on what's going on here, would be helpful ;)


  reply	other threads:[~2021-08-31 17:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 15:25 ipv6 connexion fail - ipv4 OK Daniel
2021-08-26 11:14 ` Daniel
2021-08-27 16:14   ` Roman Mamedov
2021-08-27 17:16     ` Daniel
2021-08-27 21:35       ` [Warning: DMARC Fail Email] " Mike O'Connor
2021-08-27 21:44         ` Roman Mamedov
2021-08-27 21:54           ` Mike O'Connor
2021-08-30 10:24           ` Daniel
2021-08-30 12:55             ` Skyler Mäntysaari
2021-08-30 16:43             ` Roman Mamedov
2021-08-30 17:28               ` Daniel
2021-08-30 17:38                 ` Roman Mamedov
2021-08-30 17:44                   ` Daniel
2021-08-30 17:59                     ` Roman Mamedov
2021-08-31 17:50                       ` Daniel [this message]
2021-09-01 17:44                         ` Daniel
2021-09-03 13:59                       ` ipv6 connexion fail - ipv4 OK (SOLVED) Daniel

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d7095107-050f-2075-00cb-fdaa86d6daf5@tootai.net \
    --to=tech@tootai.net \
    --cc=wireguard@lists.zx2c4.com \


* 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).