Development discussion of WireGuard
 help / color / mirror / Atom feed
From: nicolas prochazka <prochazka.nicolas@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [wireguard-dev] Ability to use one udp port for multiple wg interfaces
Date: Thu, 21 Sep 2017 15:14:45 +0200	[thread overview]
Message-ID: <CADdae-i+Ue8cLZhcNUZ__-DQzU7b+uC963VbENpgDV4TTsqGRg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qs_hyveXwUTU17gzri9Dwe+DgLj3Mzqu6dvZxuz57Jaw@mail.gmail.com>

internal dev = hack your code for our specifiq use, to multiplex
listening udp port .
I agree with you about configuration, it is possible, but we are using
"historical" private software, and it's difficult to deal with.
It is not a wireguard issue.

Regards,
Nicolas


2017-09-21 14:54 GMT+02:00 Jason A. Donenfeld <Jason@zx2c4.com>:
> Perhaps I'm not understanding your last message, but it's most
> certainly possible to bind to a particular IP address with a service.
> It's also possible to bind to _all_ IP addresses, and then use
> iptables to control which source networks have access to a particular
> port. Finally, within a service, if you only allow input from wg0
> since allowed-ips gives strong cryptographic binding, you can
> explicitly filter on the IP addresses you get from recvfrom.
>
> I don't understand your meaning of "internal dev".

  reply	other threads:[~2017-09-21 12:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  9:32 nicolas prochazka
2017-09-21 11:25 ` Jason A. Donenfeld
2017-09-21 11:46   ` nicolas prochazka
2017-09-21 11:54     ` Jason A. Donenfeld
2017-09-21 11:55 ` Jason A. Donenfeld
2017-09-21 12:17   ` nicolas prochazka
2017-09-21 12:54     ` Jason A. Donenfeld
2017-09-21 13:14       ` nicolas prochazka [this message]
2017-09-21 13:24         ` Jason A. Donenfeld
2017-09-21 15:29           ` nicolas prochazka
2017-09-21 15:36             ` 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=CADdae-i+Ue8cLZhcNUZ__-DQzU7b+uC963VbENpgDV4TTsqGRg@mail.gmail.com \
    --to=prochazka.nicolas@gmail.com \
    --cc=Jason@zx2c4.com \
    --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).