03-04-2019 05:13 AM - edited 03-04-2019 05:13 AM
There are two network adapters on the server (eth0 and eth1). I need to transfer interaction with UNMS (web interface and communication with devices) from eth0 to eth1. I tried changing the ip address in Settings / UNMS and Settings / Devices-Ping, but this does not help. The server continues to listen TCP 443 at eth0 address.
03-11-2019 10:03 AM
@makonrus Hello Максим. UNMS should be listening on both eth interfaces. How are you testing that it only listens on eth0, please? Can you describe the methodology behind that so that we have a better picture of the situation? Also, do I understand properly that you need the UNMS server to only listen on eth1?
03-12-2019 02:00 PM
@makonrus Thank you for the info, Максим. Please SSH into your UNMS server and run this command
sudo netstat -tulpn | grep 443
We will need the output of that command to get a better picture of what is going on.
03-14-2019 06:28 AM
@makonrus Hello Максим. The line
tcp6 0 0 :::443 :::* LISTEN 2237/docker-proxy means that UNMS is listening on all interfaces on the port 443. The most likely reason why you are getting a failed result on command
telnet eth1_ip_address 443 is that there is an issue on the way between a computer from which you are trying to connect and the UNMS server. Our guess is that your computer is in a different network than eth1 on the server and therefore it cannot connect there.
03-14-2019 07:05 AM
Well. We need to go deeper.
Let's see what happens with wireshark.
(My comp -> target) SYN
(target -> My comp) PSH, ACK
(target -> My comp) FIN
This server also has a UniFi controller.
telnet eth1_ip_address 8443 ... success!
There are no firewalls, ACLs, or any other services that filter packets
03-19-2019 06:53 AM
@makonrus Hello Максим. Thank you for the info. Can you please send me the file '/home/unms/app/docker-compose.yaml'? Be aware that file contains sensitive data and should be only transferred via a secure channel. Please, send it to the email radek.skrivan(at)ubnt.com, and include your forum name and URL of this thread in the message.