[Discussion] block Internet access [SOLVED]

[krissan]

Hey, I own F6-424 with latest TOS6 update, and I keep it detached from Internet on my MikroTik router, so it has drop rule on outgoing traffic.
But it constant is trying to access some IP's. Some on port 80, some on port 443.
I have auto updates turned off, no NTP sync, no remote access service, no DLNA or other fancy stuff, it is just NAS.
Services I use are: NFS, iSCSI, SMB. These connections are very frequent!
This is both annoying that it keeps on trying and disturbing in the same time





Does anybody observe such behavior or you rather do not care ?

[CursaYang]

Hello, have you enabled TNAS Online or related services? These IPs are for TNAS Online server.

[krissan]

Hello, have you enabled TNAS Online or related services? These IPs are for TNAS Online server.

Hey, no, nothing is enabled (TNAS.online, VPN nor DDNS are enabled), no Automatic updates selected, only thing I got is mobile app with local IP address selected. No notifications enabled,
Enabled services are: SNMP, SSH, SMB, NFS, iSCSI, Bonjour, Windows Discovery

TOS version: 6.0.794-01324




and if Internet enabled for a brief period, TNAS.online claims that all is disabled

[TMjack]

Hello! May I ask what the IP address of your TNAS device is? Additionally, I'd like to confirm whether you have already installed the Docker application on the device. Typically, the address 172.19.20.30 is a Docker address, and it might currently be the Docker application attempting to access the internet.

[krissan]

Hello! May I ask what the IP address of your TNAS device is? Additionally, I'd like to confirm whether you have already installed the Docker application on the device. Typically, the address 172.19.20.30 is a Docker address, and it might currently be the Docker application attempting to access the internet.

I installed Docker for a test long time ago, but as you saw it is not installed at all, and no even docker command is present in system.
172.19.20.30 is NAS IP form my LAN.

ps -ef command gives such for example:



this curl command accessing :80, TOSDaemon is accessing rest of :443. So question is still, what and why is trying to access internet :/ . Well what we partially already know, but "why" ?

[krissan]

I made few tests, and once I reboot TOS with Internet enabled it makes slight communication, and after a minute, once I block Internet access, my firewall is clean, meaning no more tries to communicate.
I found that each time it refreshes certificate for example, so probably this is just a beauty of TOS.

[RyanYang]

During system startup, the system may send requests to the internet to obtain connectivity status. For example, the following operations will trigger such requests:
1. When TOS starts, it will attempt to obtain public IPv4 and IPv6 addresses to test internet connectivity.
2. Any function that retrieves network interface information will repeat the operations performed during system startup to test internet connectivity, such as when opening the network interface or resource monitoring page.