All of lore.kernel.org
 help / color / mirror / Atom feed
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:28:11 +0200	[thread overview]
Message-ID: <e620ed11-2664-fa06-1497-a0f18facac7e@tootai.net> (raw)
In-Reply-To: <20210830214312.6a332333@natsu>


Le 30/08/2021 à 18:43, Roman Mamedov a écrit :
> On Mon, 30 Aug 2021 12:24:01 +0200
> Daniel <tech@tootai.net> wrote:
>
>> Using tcpdump -i any I see the trafic coming to the gre interface and
>> that's all. But netstat show
>>
>> udp6       0      0 :::12345 :::*
>> 0          125391     -
>>
>> and ps aux output is
>>
>> dh@peech:~$ ps ax|grep wg
>>      6969 ?        I<     0:00 [wg-crypt-wig4to]
>>      7026 ?        I      0:00 [kworker/1:2-wg-kex-wig4tootai]
>>
>> Question: is wireguard really listening on all ipv6 addresses ? If not,
>> how is the address choosen ?
> Yes it does.
>
>
> You seem to have some very complex setup, I suggest to look into whether you
> send replies from the interface you expect them to. If you use wg-quick, maybe
> switch to just wg and set up manually and with careful intent of each action,
> as wg-quick might not have in mind some aspect of your setup.

I don't use wg-quick: interface setup is done in interfaces file and 
reading conf file from there.

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 ?

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 :(
-- 
Daniel

  reply	other threads:[~2021-08-30 17:30 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 [this message]
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
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=e620ed11-2664-fa06-1497-a0f18facac7e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.