virtualbox
Beiträge von skunkos
-
-
No, the FTP daemon is unstable. After systemctl start command, the port is not open, journalctl contains only some informatic lines, no warnings etc., once it somehow happened that the 21 port was open in nmap an connetion worked, but after machine reboot, again, not ports open.
-
I will probably go with standard Arch system, closes to my heart...
It is just interesting that when any network service is started, the daemon executable is not running. Samba, ftp, nfs, ... And as I said, this is reproducible in standard VirtualBox machine. There is no testing done before the release is made?
-
Of that I have tried that one...
The command goes through -> no change.
-
Yes, FTP server starts correctly this way. I think the problem is located somewhere in the way the service is started by init.d/systemd.
Note that, for example when I start SAMBA, the symptoms are exactly the same! No SAMBA-related ports open and probably NO SAMBA daemon running either. And this is reproducible for me. I tried on two VirtualBox virtual machines on two different physical hosts which are on two completely different networks.
-
Code
/etc/init.d proftpd starthangs.
-
It even seems that no *proft* executable is running atm. At least proftpd daemon should be running, right?
-
-
Yes, even the service reports to be active and started.
-
I installed latest OMV into VirtualBox machine:
- latest OMV,
- bridged working networking with all ports open on that virtual machine (tested with FreeNas and Arch).I configured OMV, added shares, added users, enabled FTP on port 21. Then I tried to read that FTP from the HOST machine and it did not work. It seems that FTP server is not running at all despite web GUI says otherwise.
I logged into OMV and ran
Codenmap localhostand the outcome was that the only enabled ports are 22/tcp and 80/tcp - SSH and web GUI. Nmap says that no ports are open even if in the web gui I have enabled FTP, SSH, SAMBA.
Am I missing anything?