Disabling vnetd service
- 4 years ago
Other than reviewing the log information I suspect not. Here is an extract from the vnetd log for the satrt of a backup
07:51:17.066 [1814.1814] <2> vnet_pbxAcceptSocket_ex: Accepted sock[17] from 10.240.100.52:51201
07:51:17.067 [2632418.2632418] <2> ProcessRequests: delaying version exchange until after proxy for sock_id 4
07:51:17.068 [2632418.2632418] <2> daemon_proxy_proto: Preparing to do daemon protocol for (10.240.100.14:1556 <- 10.240.100.52:51201)
07:51:17.068 [1814.1814] <2> vnet_pbxAcceptSocket_ex: Accepted sock[17] from 10.240.100.52:51202
07:51:17.069 [2632419.2632419] <2> ProcessRequests: delaying version exchange until after proxy for sock_id 3
07:51:17.069 [2632419.2632419] <2> daemon_proxy_proto: Preparing to do daemon protocol for (10.240.100.14:1556 <- 10.240.100.52:51202)You;ll notice that the connection comes in on the PBX port (as expected) and connects to vnetd via a socket. As such I do not think you will ever see network traffic using the vnetd port - even locally).
Your best bet will be to enable vnetd logging and review the logs. Also the vnetd proxy logs may also provide additional information, see this article on examining these logs - Viewing the vnetd proxy log files