From: Daniel <tech@tootai.net>
To: wireguard@lists.zx2c4.com
Subject: Re: [Warning: DMARC Fail Email] Re: ipv6 connexion fail - ipv4 OK
Date: Mon, 30 Aug 2021 19:44:21 +0200 [thread overview]
Message-ID: <e949b3e2-eab7-fc4c-2b15-8820a2c17374@tootai.net> (raw)
In-Reply-To: <20210830223836.5384badd@natsu>
Le 30/08/2021 à 19:38, Roman Mamedov a écrit :
> On Mon, 30 Aug 2021 19:28:11 +0200
> Daniel <tech@tootai.net> wrote:
>
>> To be sure (and I think it is as I have no problem with ipv4):
>>
>> . my interfaces are named wig4tootai our wigserver Nothing wrong here ?
>>
>> . conf file are not named <interface name>.conf but server.conf or
>> anyname.conf Nothing wrong here too ?
> Interface names are arbitrary. As for proper .conf filenames on your system, I
> am not sure, but you can simply check whether everything looks fine by running
> the "wg" tool.
>
>> Conserning the setup, I made another one using one VPS (one public ipv4 and
>> one ipv6 /64 range) but get the same result. No FW involved at all :(
> 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.
--
Daniel
next prev parent reply other threads:[~2021-08-30 17:47 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 [this message]
2021-08-30 17:59 ` Roman Mamedov
2021-08-31 17:50 ` Daniel
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:
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=e949b3e2-eab7-fc4c-2b15-8820a2c17374@tootai.net \
--to=tech@tootai.net \
--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).