OS/2, eCS & ArcaOS - Technical > Networking

Using FTP client from OS/2 guest installation in Virtualbox run. on win10 host

(1/3) > >>

Lars:
I am trying to use an ftp client within a OS/2 guest running on win 10 host.
Using Virtualbox, I "selected bridged networking" for the guest. The guest receives it's IP address via DHCP. By the way, I am using a WiFi connection from the host to the router and therefore, the selected adapter for the "bridged networking" connection is the WiFi adapter.

From the guest I can ping the outside world, let's say "www.microsoft.com". I can also use a web browser.
What I cannot get to work is using an ftp client from the guest. I tried the standard OS/2 ftp client and also "nftp" but both ftp clients eventually fail to communicate with port 21 (I guess that is the target port of the ftp server I attempt to connect to ?).

Can anyone tell me what I need to change either in my router or on my Win 10 host so that I can run an ftp client from the guest ?

ivan:
Hi Lars,

A quick question, where is the FTP server you are trying to connect to - on the local network or outside?  I ask this because I find it easier to to use the IP address of the host if on the local network.

For going outside the local network, again I will use the IP address if I know it and I have the tcp port 21 open as well as the udp port 21 open - if using ssh you also need port 22 open for tcp and udp.

Sorry I can't be specific about VirtualBox  because I can't get an OS/2 host to work on my Ryzen based computers.

Andreas Schnellbacher:
Have you also tried NAT?

This AN Wiki page may be useful.

Roderick Klein:

--- Quote from: Andreas Schnellbacher on October 22, 2020, 11:16:19 pm ---Have you also tried NAT?

This AN Wiki page may be useful.

--- End quote ---

I would recommend not doing that you place two NAT layers in a row. And I know the port translation does not go very well.
Using bridge mode is better then NAT of a VM,

Roderick

Lars:

--- Quote from: ivan on October 22, 2020, 09:39:53 pm ---Hi Lars,

A quick question, where is the FTP server you are trying to connect to - on the local network or outside?  I ask this because I find it easier to to use the IP address of the host if on the local network.

For going outside the local network, again I will use the IP address if I know it and I have the tcp port 21 open as well as the udp port 21 open - if using ssh you also need port 22 open for tcp and udp.

Sorry I can't be specific about VirtualBox  because I can't get an OS/2 host to work on my Ryzen based computers.

--- End quote ---

What I wanteed to do is to upload my updated USB driver set to Hobbes, so yes, I tried to access a remote FTP server.
1) why would I need to open port 21 (and possibly 20 also) at all ? I mean, after all, I am running an FTP client and not an FTP server ?
2) in my desperation, I did open ports 20 and 21 in my router but that did not make a difference. When doing so, I found out that the router only sees the IP address of the host OS (Windows 10) but it does not see the IP address of the guest OS (OS/2) and therefore I could not really open the ports for the guest IP address. On the other hand, it makes sense that the router only sees the host IP address. As far as I understand, "bridged networking" makes VirtualBox assign an IP address to the guest and when the guest sends or receive an ethernet packet, the guest IP address is silently replaced by the host IP address (on send) or vice versa (on receive).

As I said, I am runnning OS/2 as a guest in Virtualbox and not as a Virtualbox host.

Navigation

[0] Message Index

[#] Next page

Go to full version