Date: Wed, 4 Nov 2020 18:04:28 -0400 From: D'Arcy Cain <darcy@druid.net> To: freebsd-net@freebsd.org Subject: Re: Network woes SOLVED! Message-ID: <a5b1d949-935b-d25c-91d1-49c2df4e6122@druid.net> In-Reply-To: <4598d9be-4be8-9b54-9128-d840c8283f73@druid.net> References: <c955de31-6ea9-318b-d5c7-fcfcb4463b03@druid.net> <4598d9be-4be8-9b54-9128-d840c8283f73@druid.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dCJOSf2SHfF77luToRzmFdbltyF44vszJ Content-Type: multipart/mixed; boundary="bLwQdM31CRH7E4O8hi133Kq9VvBybZLx3"; protected-headers="v1" From: D'Arcy Cain <darcy@druid.net> To: freebsd-net@freebsd.org Message-ID: <a5b1d949-935b-d25c-91d1-49c2df4e6122@druid.net> Subject: Re: Network woes SOLVED! References: <c955de31-6ea9-318b-d5c7-fcfcb4463b03@druid.net> <4598d9be-4be8-9b54-9128-d840c8283f73@druid.net> In-Reply-To: <4598d9be-4be8-9b54-9128-d840c8283f73@druid.net> --bLwQdM31CRH7E4O8hi133Kq9VvBybZLx3 Content-Type: multipart/mixed; boundary="------------44215635C1BC0920B3023C39" Content-Language: en-US This is a multi-part message in MIME format. --------------44215635C1BC0920B3023C39 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable On 10/29/20 7:02 AM, D'Arcy Cain wrote: > Turns out it has nothing to do with virtualization.=C2=A0 It never occu= rred to me=20 > to test that the host could access the Internet since I had no problem = > connecting and logging in.=C2=A0 However, everything I described for th= e VM=20 > applies to the host as well.=C2=A0 Here is my current setup. OMG!!! I can't believe how simple the fix was. Kind of embarrassing except that= =20 the error was not mine. To recap, my system has two networks, a public facing one and a private b= ack=20 channel. I put the public address on the public side and the private=20 address on the back one. Simple. It is unless the person installing the= =20 hardware switches the ethernet cables. The surprising thing is not that = it=20 failed but that it worked at all. The one system that this server could connect to was also a VM system alb= eit=20 set up differently. It must have somehow routed the public address to th= e=20 back channel into what the host thought was the public side. The world makes sense again. --=20 D'Arcy J.M. Cain <darcy@druid.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: darcy@VybeNetworks.com, VoIP: sip:darcy@druid.net Disclaimer: By sending an email to ANY of my addresses you are agreeing that: 1. I am by definition, "the intended recipient". 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. In particular, I may quote it where I please. 3. I may take the contents as representing the views of your company if I so wish. 4. This overrides any disclaimer or statement of confidentiality that may be included or implied in your message. --------------44215635C1BC0920B3023C39-- --bLwQdM31CRH7E4O8hi133Kq9VvBybZLx3-- --dCJOSf2SHfF77luToRzmFdbltyF44vszJ Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wnsEABYIACMWIQSQJTNYM0vv3aTmBCs/5DDweYZnXQUCX6MlbAUDAAAAAAAKCRA/5DDweYZnXYdY AQCZQ4td2LdsP2KnOH0DzJyqZtVjHWwmkLtwecOaL40pRgD7BSVCdEjMqrc+611quYEBjVyhEaGL HJnOnfjKUfhvGwo= =upG3 -----END PGP SIGNATURE----- --dCJOSf2SHfF77luToRzmFdbltyF44vszJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5b1d949-935b-d25c-91d1-49c2df4e6122>