MIME-Version: 1.0
References: <CALODqpr-W+K0Kt+opc-sX8DV5EFgFyZBd_mt6Ea7dZ9M2oEO6g@mail.gmail.com>
 <229c8ae0-9566-3fad-e5b9-b63173847b98@riseup.net>
In-Reply-To: <229c8ae0-9566-3fad-e5b9-b63173847b98@riseup.net>
From: Banibrata Dutta <banibrata.dutta@gmail.com>
Date: Sun, 21 Feb 2021 20:10:41 +0530
Message-ID: <CALODqpo-+yUzSYQdvUgZrnNL6thMtVN+=Ax2wanSkBMpH52dRA@mail.gmail.com>
Subject: Re: Orig eth0 was bridged, changed to NAT, but dhcp not working
To: donoban <donoban@riseup.net>
Cc: ~alpine/users@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="0000000000000c0f3f05bbd9ac20"

--0000000000000c0f3f05bbd9ac20
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Looks like I wasn't very clear. I wasn't referring to a VPN server on host,
but a VPN endpoint on the host, setup by the VPN client running on host.
The VPN server is remote.

regard

On Sun, Feb 21, 2021 at 5:40 PM donoban <donoban@riseup.net> wrote:

> Hi,
>
> On 2/21/21 10:18 AM, Banibrata Dutta wrote:
> > Have Alpine 3.13 installed in an Oracle Virtualbox VM as a guestOS. It
> > was originally setup with a single bridged LAN interface configured as
> > eth0 with dhcp. However post installation, I had changed the interface
> > settings to have eth0 setup with static-IP. The guestOS has a second
> > interface (of type Host-Only, from Virtualbox standpoint) configured as
> > eth1, which I use to login to the VM.
> >
> > Later, I realized that from within this guestOS, I needed to access a
> > VPN setup in the host, and read a FAQ indicating that in such cases,
> > Virtualbox network type of NAT should be used. However, after I changed
> > the network type from bridged to NAT, and configured eth0 to take
> > IP/config thru dhcp, I can no longer get an IP address assigned to eth0=
.
>
> I don't think NAT is the right choice for connecting to a VPN server on
> the host. Or do you mean to a remote VPN server?
>
> When you said "configured as eth1, which I use to login to the VM.", did
> you mean a ssh connection? If yes the same setup and interface that work
> fine for the ssh connection should work too for a VPN connection (to the
> host). The problem could be your host setup, =C2=BFis the VPN server
> listening on that interface? =C2=BFdo you have some kind of firewall whic=
h
> could be blocking INPUT connections to the host?
>
> I will try to go back and restore direct communication between your Host
> and guest.
>
> NAT configuration is fine if you want to connect the Guest to the
> Internet without manual routing configuration.
>
>

--0000000000000c0f3f05bbd9ac20
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Looks like I wasn&#39;t very clear. =
I wasn&#39;t referring to a VPN server on host, but a VPN endpoint on the h=
ost, setup by the VPN client running on host.<br></div><div>The VPN server =
is remote.</div><div><br></div><div>regard</div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb 21, 2021 at 5:4=
0 PM donoban &lt;<a href=3D"mailto:donoban@riseup.net">donoban@riseup.net</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi=
,<br>
<br>
On 2/21/21 10:18 AM, Banibrata Dutta wrote:<br>
&gt; Have Alpine 3.13 installed in an Oracle Virtualbox VM as a guestOS. It=
<br>
&gt; was originally setup with a single bridged LAN interface configured as=
<br>
&gt; eth0 with dhcp. However post installation, I had changed the interface=
<br>
&gt; settings to have eth0 setup with static-IP. The guestOS has a second<b=
r>
&gt; interface (of type Host-Only, from Virtualbox standpoint) configured a=
s<br>
&gt; eth1, which I use to login to the VM.<br>
&gt; <br>
&gt; Later, I realized that from within this guestOS, I needed to access a<=
br>
&gt; VPN setup in the host, and read a FAQ indicating that in such cases,<b=
r>
&gt; Virtualbox network type of NAT should be used. However, after I change=
d<br>
&gt; the network type from bridged to NAT, and configured eth0 to take<br>
&gt; IP/config thru dhcp, I can no longer get an IP address assigned to eth=
0.=C2=A0<br>
<br>
I don&#39;t think NAT is the right choice for connecting to a VPN server on=
<br>
the host. Or do you mean to a remote VPN server?<br>
<br>
When you said &quot;configured as eth1, which I use to login to the VM.&quo=
t;, did<br>
you mean a ssh connection? If yes the same setup and interface that work<br=
>
fine for the ssh connection should work too for a VPN connection (to the<br=
>
host). The problem could be your host setup, =C2=BFis the VPN server<br>
listening on that interface? =C2=BFdo you have some kind of firewall which<=
br>
could be blocking INPUT connections to the host?<br>
<br>
I will try to go back and restore direct communication between your Host<br=
>
and guest.<br>
<br>
NAT configuration is fine if you want to connect the Guest to the<br>
Internet without manual routing configuration.<br>
<br>
</blockquote></div><div dir=3D"ltr" class=3D"gmail_signature"><br></div></d=
iv>

--0000000000000c0f3f05bbd9ac20--