7 replies to this topic

[gusto]

Today I wanted to remotely send to the box via DBE channels and DBE shows a connection error.

I found that port 21 is not open.

 

Host is up (0.073s latency).
Not shown: 994 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
80/tcp   open  http
111/tcp  open  rpcbind
2049/tcp open  nfs
8001/tcp open  vcom-tunnel
8888/tcp open  sun-answerbook

It looks like vsftpd is not running

ps | grep vsftpd
 7875 root      2660 S    grep vsftpd

It looks like vsftpd is not running. Does OpenPLi use VSFTPD at all?

 

[linus]

Hello:

 

https://forums.openp...vailable/page-9

 

Even that point, do you really need ftp?
You could use sftp (on ssh) with client like filezilla to transfert files from computer.
(but perhaps you need ftp for tv or other box? )

[gusto]

I also have the feeling that the FTP server in the box is not running. I can only access that box remotely via the Internet. The box worked without problems for more than 2 years. However, now there is a problem with port 21. I assume that OpenPLi uses VSFTPD.

 

IMG is an OpenPLi 8

Another box uclan, also OpenPLi 8 and without problems

Here are the nmaps from the boxes

 

bad box

Starting Nmap 7.80 ( https://nmap.org ) at 2024-11-07 06:48 CET
Nmap scan report for 10.8.0.175
Host is up (0.064s latency).
Not shown: 994 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
80/tcp   open  http
111/tcp  open  rpcbind
2049/tcp open  nfs
8001/tcp open  vcom-tunnel
8888/tcp open  sun-answerbook

good box

Starting Nmap 7.80 ( https://nmap.org ) at 2024-11-07 06:49 CET
Nmap scan report for 10.8.0.174
Host is up (0.079s latency).
Not shown: 990 closed ports
PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
23/tcp   open  telnet
80/tcp   open  http
111/tcp  open  rpcbind
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
2049/tcp open  nfs
8001/tcp open  vcom-tunnel
8888/tcp open  sun-answerbook

Edited by gusto, 7 November 2024 - 06:55.

[WanWizard]

ftp runs via the inetd daemon, so you shouldn't see an ftp daemon running unless there is an active session. But inetd should be running, and show up in "netstat -lnpt".

 

Check your logs after the box has booted, or see what happens if you start inetd manually:

/etc/init.d/inetd.busybox start

btw, you know that having ftp accessable from the internet is asking for trouble?

[gusto]

netstat -lnpt

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:46822           0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:54667           0.0.0.0:*               LISTEN      1465/rpc.mountd
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      1438/rpcbind
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      2145/inetd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1427/dropbear
tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN      2145/inetd
tcp        0      0 0.0.0.0:43644           0.0.0.0:*               LISTEN      1465/rpc.mountd
tcp        0      0 0.0.0.0:2049            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:55298           0.0.0.0:*               LISTEN      1465/rpc.mountd
tcp        0      0 0.0.0.0:58467           0.0.0.0:*               LISTEN      1443/rpc.statd
tcp        0      0 :::45445                :::*                    LISTEN      1465/rpc.mountd
tcp        0      0 :::37740                :::*                    LISTEN      1465/rpc.mountd
tcp        0      0 :::12013                :::*                    LISTEN      1497/oscam
tcp        0      0 :::111                  :::*                    LISTEN      1438/rpcbind
tcp        0      0 :::80                   :::*                    LISTEN      1505/enigma2
tcp        0      0 :::47155                :::*                    LISTEN      1443/rpc.statd
tcp        0      0 :::45396                :::*                    LISTEN      1465/rpc.mountd
tcp        0      0 :::3702                 :::*                    LISTEN      1478/wsdd
tcp        0      0 :::22                   :::*                    LISTEN      1427/dropbear
tcp        0      0 :::8888                 :::*                    LISTEN      1497/oscam
tcp        0      0 :::44060                :::*                    LISTEN      -
tcp        0      0 :::8001                 :::*                    LISTEN      1505/enigma2
tcp        0      0 :::2049                 :::*                    LISTEN      -

The box uses OpenVPN and is not accessible from the Internet.

 

Today I got physically to box. This is uClan Ustym 4K Pro.

There is a problem, because I cannot install a new IMG through the recovery menu. I tried the latest OpenPLi multiboot (from a USB stick). Next, I tried to install from the Internet in recovery mode, it was installed, but the box does not boot.

 

[WanWizard]

FTP is running just fine on this box, both 21 and 23 are listened to?

 

What image exactly did you try to install? And why the recovery menu, and not the flash option in the menu?

[gusto]

Yes, now I can see open ports and FTP works. Apparently this helped

/etc/init.d/inetd.busybox start

Nmap scan report for 10.8.0.175
Host is up (0.055s latency).
Not shown: 992 closed ports
PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
23/tcp   open  telnet
80/tcp   open  http
111/tcp  open  rpcbind
2049/tcp open  nfs
8001/tcp open  vcom-tunnel
8888/tcp open  sun-answerbook

I must have flashed wrong. I downloaded multiboot from downloads and saved the zip file on a USB key. Then I used the USB multiboot IMG upgrade option in the recovery menu.

Apparently I need to download the USB version. Unzip the files to the USB key and use the Flash recovery IMG option.

[WanWizard]

The USB version is used to flash the box. All flash storage will be erased, you will lose all multiboot slots. The multiboot version is used to flash a multiboot slot. I does not update the recovery partition, it does not touch the other slots.

 

As to the inetd issue, you need to check the logs ( dmesg output, /var/log/messages ) after the box has booted, as if it doesn't run, it must have failed to start for some reason. Assuming you haven't removed any symlinks for /etc/rc3.d or changed the the standard runlevel.