Code : Tout sélectionner
[root@julouhouse slyholborn]# systemctl status saned.socket
* saned.socket - saned incoming socket
Loaded: loaded (/usr/lib/systemd/system/saned.socket; enabled; vendor preset: disabled)
Active: active (listening) since Wed 2017-02-01 02:10:31 CET; 1 months 12 days ago
Listen: [::]:6566 (Stream)
Accepted: 0; Connected: 0
Feb 01 02:10:31 julouhouse systemd[1]: Listening on saned incoming socket.
Code : Tout sélectionner
scan-client.somedomain.firm
#192.168.0.1
192.168.0.1/29
#[2001:db8:185e::42:12]
#[2001:db8:185e::42:12]/64
# NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and
# /etc/services must also be properly configured to start
# the saned daemon as documented in saned(8), services(4)
# and inetd.conf(4) (or xinetd.conf(5)).
coté client : (sous F25 évidemment!)
mon /etc/saned/net.conf
Code : Tout sélectionner
# This is the net backend config file.
## net backend options
# Timeout for the initial connection to saned. This will prevent the backend
# from blocking for several minutes trying to connect to an unresponsive
# saned host (network outage, host down, ...). Value in seconds.
connect_timeout = 60
## saned hosts
# Each line names a host to attach to.
# If you list "localhost" then your backends can be accessed either
# directly or through the net backend. Going through the net backend
# may be necessary to access devices that need special privileges.
# localhost
192.168.0.23
julouhouse
