To: Banibrata Dutta <banibrata.dutta@gmail.com>
Cc: ~alpine/users@lists.alpinelinux.org
References: <CALODqpr-W+K0Kt+opc-sX8DV5EFgFyZBd_mt6Ea7dZ9M2oEO6g@mail.gmail.com>
 <229c8ae0-9566-3fad-e5b9-b63173847b98@riseup.net>
 <CALODqpo-+yUzSYQdvUgZrnNL6thMtVN+=Ax2wanSkBMpH52dRA@mail.gmail.com>
 <f86e4c64-df1b-a122-3601-4e207f56f16c@riseup.net>
 <CALODqpr2h2MxYjgMTtwcU_L5Q8TXCFtKyHi4BLL0tH-VUKKDgQ@mail.gmail.com>
From: donoban <donoban@riseup.net>
Subject: Re: Orig eth0 was bridged, changed to NAT, but dhcp not working
Message-ID: <a6467733-75fe-364a-663a-f852494ffa14@riseup.net>
Date: Sun, 21 Feb 2021 18:23:23 +0100
MIME-Version: 1.0
In-Reply-To: <CALODqpr2h2MxYjgMTtwcU_L5Q8TXCFtKyHi4BLL0tH-VUKKDgQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="MQI26eqasAmdoLnvAWKY7vGaI1pMCbSl3"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--MQI26eqasAmdoLnvAWKY7vGaI1pMCbSl3
Content-Type: multipart/mixed; boundary="vVNcsIABldVYfSV0WmWP2hGhp9gcscLzX";
 protected-headers="v1"
From: donoban <donoban@riseup.net>
To: Banibrata Dutta <banibrata.dutta@gmail.com>
Cc: ~alpine/users@lists.alpinelinux.org
Message-ID: <a6467733-75fe-364a-663a-f852494ffa14@riseup.net>
Subject: Re: Orig eth0 was bridged, changed to NAT, but dhcp not working
References: <CALODqpr-W+K0Kt+opc-sX8DV5EFgFyZBd_mt6Ea7dZ9M2oEO6g@mail.gmail.com>
 <229c8ae0-9566-3fad-e5b9-b63173847b98@riseup.net>
 <CALODqpo-+yUzSYQdvUgZrnNL6thMtVN+=Ax2wanSkBMpH52dRA@mail.gmail.com>
 <f86e4c64-df1b-a122-3601-4e207f56f16c@riseup.net>
 <CALODqpr2h2MxYjgMTtwcU_L5Q8TXCFtKyHi4BLL0tH-VUKKDgQ@mail.gmail.com>
In-Reply-To: <CALODqpr2h2MxYjgMTtwcU_L5Q8TXCFtKyHi4BLL0tH-VUKKDgQ@mail.gmail.com>

--vVNcsIABldVYfSV0WmWP2hGhp9gcscLzX
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 2/21/21 6:03 PM, Banibrata Dutta wrote:
> Thanks much.
>=20
> Yes, the regular NAT mode is now working fine (chose the
> paravirtualized-network i.e. 'virtio-net' driver).
>=20
> The trick (seems rather obvious, come to think of it) is to have the VP=
N
> tunnel setup prior to starting the VM. What doesn't seem to work (or at=

> least didn't in my case) is to setup the VPN tunnel in the host, after
> the VM is already up and running. In the latter case, doing a restart o=
f
> the networking service doesn't help. Also, I had to manually add the
> VPN-server specific DNS servers, in the resolv.conf.
>=20
> Right now struggling to add the private root-CA certificates for a
> remote lab network, reachable only over this VPN.

Maybe the VPN software is overriding some firewall and routing rules and
conflicting with Virtualbox. Respect DNS have you tried with 10.0.2.3 ?
(or 10.0.X.3), theoretically it should redirect to your host DNS and
maybe do some caching.


--vVNcsIABldVYfSV0WmWP2hGhp9gcscLzX--

--MQI26eqasAmdoLnvAWKY7vGaI1pMCbSl3
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAmAylwsFAwAAAAAACgkQFBMQ2OPtCKUO
BBAAn7ZogBoP13ZWjQLIkrHcfMoKvBoV1LET+kIuheCE+IL9j30Tp+91iwe4uSKQS8Wl+M4BUjrN
F/iOd4MgzN8Poa4GoKr+Ck6MuESZlM7PEvgMUXaZ/Ss35UDJC1ez2WSuBJMBwijRYA2jvQPMt9kK
kyuwV1WhbDqf/7lS4Tw+fqelbApQwV9gRwRO9OSwlobfM3apdUjP1kRlAN3ZPAVOWj3usfnzNHVX
aWmPGz3GxxN/47I5iQeoeDjwW41A8mWJYQBwvm5heKNbwDtZcCASXOngzrVKRPjEE3ZCpTTiEDhM
mqXlNpUJ5SX24pxwvY71EF7DIT8rmeAEMOJiSgGaVOFgZS75j7EiZpuDlVuwUxWCmdB/2D/H3Uch
tL+jZeEHGeqoTI7oZvxSdppAq0Yfr4JIU1CqP2s1PkWiCxGRoPPngh4erwqA+EACX7QAxeIZ8SVa
NDJAd7cOdvIr0q1vVXEsy760SUgSrDgXO/avCohNh/j4H/MHrVjE7T7DCi9mv3YWYfoDJIDVX7qO
9QPnMx1QWpfDYXswxe2fi6Muy5mRoMNhRXTU/GlxemfxG/d1VwNDe4OVqu9JSnvqKmwGPwTSqVYb
e6wo/PTiv2TRLizwzLJwEMjbUmx5RRibbKYhwVD219PMDzUOeUm89GlR4/3mL1rMiahmK0keST8H
YdI=
=dkkw
-----END PGP SIGNATURE-----

--MQI26eqasAmdoLnvAWKY7vGaI1pMCbSl3--