My server has 2 network interfaces, eth0 and dummy0. eth0 is the interface used with the iscsi server and dummy0 is used for the network output with the rest of the world. If I configure distcc to listen on eth0, with DISTCCD_OPTS="${DISTCCD_OPTS} --listen 192.168.0.1", it doesn't want to start and I get the following error : distccd[23650] (dcc_socket_listen) ERROR: listen address "192.168.0.1" is not a valid IPv4 address. 192.168.0.1 is corresponding to my dummy0 interface. If i'm using eth0 ip it's working. Sounds like it's related to its name but i'm not sure about it. Reproducible: Always Steps to Reproduce: 1. Configure distcc to listen on the ip of a network interface having a name different than ethX 2. Start distcc Actual Results: distcc refuse to start. Expected Results: distcc should have been started.
It's not related to the network interface name. I found this in src/srv.net (line 190) : if (!inet_aton(listen_addr, &sock.sin_addr)) { rs_log_error("listen address \"%s\" is not a valid IPv4 address", listen_addr); return EXIT_BAD_ARGUMENTS; } Here's my real ip addresses : zoolook ~ # ifconfig dummy0 Link encap:Ethernet inet addr:87.98.139.X Bcast:0.0.0.0 Mask:255.255.255.255 eth0 Link encap:Ethernet inet addr:91.121.194.X Bcast:91.121.194.255 Mask:255.255.255.0
hmm, i cannot reproduce. btw, Could you try it on distcc-3.0?
(In reply to comment #2) > hmm, i cannot reproduce. > > btw, Could you try it on distcc-3.0? > Sorry i don't have that server anymore. I'll look if i can find another one in this case to test it.
if you still have the issue, please reopen this bug.
