From: Martin/Geno <geno+dev@fireorbit.de>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: own interface address and peer address in same Subnet
Date: Tue, 29 May 2018 20:04:52 +0200 [thread overview]
Message-ID: <d0fe533f-de71-9446-ec2b-0da8cd0548f9@fireorbit.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 485 bytes --]
Hi,
i use at my wireguard 'server' ndp_proxy to announce - thats the reason
why i could use the same interface address subnet, then the endpoint is in.
Example client configuration:
[Interface]
Address = 2a01:1337::3/64
[Peer]
AllowedIPs = 0.0.0.0/0,::/0
PersistentKeepalive = 25
Endpoint = [2a01:1337::2]:48574
Is there a solution for this 'bug' - there should be a validation and
exclude of endpoint addresses on the routing table fwmark
A nice day
Geno
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-05-29 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 18:04 Martin/Geno [this message]
2018-05-29 18:16 ` own interface address and peer address in same Subnet Jason A. Donenfeld
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=d0fe533f-de71-9446-ec2b-0da8cd0548f9@fireorbit.de \
--to=geno+dev@fireorbit.de \
--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).