Bcfg2 server can't be bound to a specific network interface

[https://www.google.com/accounts/o8/id?id=AItOawlP6DRBvIJ7NLpLWILbgzURvGbMtGEyd8U]

The bcfg2.conf(5) man page says:

COMPONENT OPTIONS
       Specified in the [components] section.

       bcfg2  URL of the server.  On the server this specifies which interface
              and port the server listens on.  [...]

However, the server always listens on all available network interfaces, regardless of this setting.

[solj]

Can you try this and see if it fixes the problem for you?

diff --git a/src/lib/SSLServer.py b/src/lib/SSLServer.py
index a89beab..871b502 100644
--- a/src/lib/SSLServer.py
+++ b/src/lib/SSLServer.py
@@ -97,9 +97,9 @@ class SSLServer (SocketServer.TCPServer, object):
 
         """
 
-        all_iface_address = ('', server_address[1])
+        listen_address = (server_address[0], server_address[1])
         try:
-            SocketServer.TCPServer.__init__(self, all_iface_address,
+            SocketServer.TCPServer.__init__(self, listen_address,
                                             RequestHandlerClass)
         except socket.error:
             self.logger.error("Failed to bind to socket")

[https://www.google.com/accounts/o8/id?id=AItOawlP6DRBvIJ7NLpLWILbgzURvGbMtGEyd8U]

Thanks! This solves the reported problem, but if the interface to listen on is not specified, the server now listens only on the loopback interface. I guess that's not desired.

[solj]

Replying to https://www.google.com/accounts/o8/id?id=AItOawlP6DRBvIJ7NLpLWILbgzURvGbMtGEyd8U:

Thanks! This solves the reported problem, but if the interface to listen on is not specified, the server now listens only on the loopback interface. I guess that's not desired.

Yeah, this will need to be a workaround until we can add an option for this. We may have cases where we want the server to listen on all available interfaces also so we need to add an option for that case.

[https://www.google.com/accounts/o8/id?id=AItOawlP6DRBvIJ7NLpLWILbgzURvGbMtGEyd8U]

IMO, such an option isn't really needed, as the current behavior of listening on all available interfaces by default is perfectly fine. My suggestion would be to change the patch to listen on all interfaces unless the user explicitly specified a URL via the bcfg2 option in the [components] section (or via the -S flag on the command line).

[solj]

Added this in 5a31e049ee342ec5874447796bc3978310306afb. The server can now listen either on a specific interface or all interfaces.