From: Brian Candler <b.candler@pobox.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Sending just ssh traffic via wg
Date: Sat, 6 Oct 2018 11:28:51 +0100 [thread overview]
Message-ID: <16654517-3717-065a-f48e-9c6470fc6999@pobox.com> (raw)
In-Reply-To: <20181006152715.2f8e83b4@natsu>
[-- Attachment #1.1: Type: text/plain, Size: 485 bytes --]
On 06/10/2018 11:27, Roman Mamedov wrote:
>> (Aside: I wish ssh had a feature like SNI, so that you could build an
>> ssh proxy that forwards incoming connections to the right host. I have
>> done this before using an inbound SOCKS proxy, but it's messy to use)
> What insane things people invent only not to use IPv6:)
Quite the opposite: I want it so that I can reach my IPv6-addressable
devices when I'm on an IPv4-only network. Which means, almost
everywhere :-)
[-- Attachment #1.2: Type: text/html, Size: 995 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-10-06 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1538820001.22807.wireguard@lists.zx2c4.com>
2018-10-06 10:21 ` Sending just ssh traffic via wg Brian Candler
2018-10-06 10:27 ` Roman Mamedov
2018-10-06 10:28 ` Brian Candler [this message]
2018-10-06 13:41 ` Konstantin Ryabitsev
2018-10-04 15:53 Konstantin Ryabitsev
2018-10-04 18:56 ` Jason A. Donenfeld
2018-10-05 10:03 ` Toke Høiland-Jørgensen
2018-10-05 15:41 ` Jason A. Donenfeld
2018-10-05 15:53 ` Konstantin Ryabitsev
2018-10-05 16:32 ` Matthias Urlichs
2018-10-05 21:01 ` Konstantin Ryabitsev
2018-10-05 17:34 ` 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=16654517-3717-065a-f48e-9c6470fc6999@pobox.com \
--to=b.candler@pobox.com \
--cc=rm@romanrm.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).