running saned in exagear

running saned in exagear

Postby penguinjeff » Sun Nov 12, 2017 3:54 pm

There is nothing running on the port yet saned will not bind to it.

root@raspberrypi:~:arm$ nmap 192.168.1.27

Starting Nmap 6.47 ( http://nmap.org ) at 2017-11-12 22:44 UTC
Nmap scan report for 192.168.1.27
Host is up (0.000091s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
9100/tcp open jetdirect



root@raspberrypi:~:x86$ saned -d128 -a saned
[saned] main: starting debug mode (level 128)
[saned] read_config: searching for config file
[saned] read_config: done reading config
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up
[saned] do_bindings: trying to get port for service "sane-port" (getaddrinfo)
[saned] do_bindings: [1] socket () using IPv6
[saned] do_bindings: [1] setsockopt ()
[saned] do_bindings: [1] bind () to port 6566
[saned] do_bindings: [1] listen ()
[saned] do_bindings: [0] socket () using IPv4
[saned] do_bindings: [0] setsockopt ()
[saned] do_bindings: [0] bind () to port 6566
[saned] do_bindings: [0] bind failed: Address already in use
[saned] run_standalone: spawning Avahi process
[saned] run_standalone: waiting for control connection
[saned] saned_avahi_callback: AVAHI_CLIENT_S_RUNNING
[saned] saned_create_avahi_services: adding service 'saned'
[saned] saned_avahi_group_callback: service 'saned' successfully established
penguinjeff
 
Posts: 5
Joined: Thu Sep 14, 2017 7:56 am

Return to ExaGear Desktop

Who is online

Users browsing this forum: No registered users and 5 guests