View Single Post
Old 01-10-2019, 07:51 PM   #6
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,460
Karma: 27757440
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
It should say all available interfaces in one protocol family. Basically, the server has a single listening socket. A single socket can listen on either single interface or all interfaces in one protocol. It cannot as far as I know listen on multiple protocols.

Quote:
Originally Posted by pk1966 View Post
OK, thanks for the swift response. I'll do as you suggest.

Do you have plans to enable it to listen on more than one interface?

I would point out that the docs suggest it is possible:

--listen-on
The interface on which to listen for connections. The default is to listen on all available interfaces. You can change this to, for example, "127.0.0.1" to only listen for connections from the local machine, or to "::" to listen to all incoming IPv6 and IPv4 connections.
kovidgoyal is offline   Reply With Quote