Date: Sat, 15 Aug 2020 12:55:31 -0600 From: "@lbutlr" <kremels@kreme.com> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: can a domain name config point to a vlan tag at the host Message-ID: <09402B7E-49F0-4320-9C7E-82068EBF8651@kreme.com> In-Reply-To: <8986e63b-6c0a-58bb-f51e-ec9ad03e12cc@radel.com> References: <5F37E329.3000903@gmail.com> <9a027a2c-3575-25ac-6ccc-0f186a3d6820@qeng-ho.org> <5F37F4BD.5030301@gmail.com> <66b05a60-69f0-5634-1f1a-3f1f7d5a53d9@qeng-ho.org> <8986e63b-6c0a-58bb-f51e-ec9ad03e12cc@radel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 Aug 2020, at 12:42, Jon Radel <jon@radel.com> wrote: > 17.17.17.17:2022 =3D=3D> 192.168.1.2:22 > 17.17.17.17:2023 =3D=3D> 192.168.2.2:22 > 17.17.17.17:2024 =3D=3D> 192.168.3.2:22 This is what I have been doing for years to get ssh access (an other = ports) into my LAN, though I go with the easier to remember method of 2202 =3D> lan.2:22 2212 =3D> lan.12:22 22107 =3D> lan.107:22 (So 192.168.0.2 or 10.0.32.12 or however you have your LAN setup) > What is not available is to somehow map >=20 > 17.17.17.17:22 =3D=3D> 192.168.1.2:22 or 192.168.2.2:22 or = 192.168.3.2:22 That way to do that, of course, is to VPN into your LAN, then all those = addresses are local to you (assuming you've setup the VPN correctly). = But that is out of the scope of what the OP seems to want. --=20 Anyhoo, they hung me. Fen out bitches.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?09402B7E-49F0-4320-9C7E-82068EBF8651>