[HTCondor-users] Windows ignoring HIGHPORT/LOWPORT?

[Ben Cotton <ben.cotton@xxxxxxxxxxxxxxxxxx>]

One of our customers noticed their Windows machines don't seem to be
respecting HIGHPORT/LOWPORT settings, in that the condor_startd ends
up listening on a port outside that range. This is a problem, since
the hosts are behind a firewall with port restrictions that match the
HIGHPORT/LOWPORT settings.

>From the StartLog:
02/12/16 10:15:20 Daemoncore: Listening at <0.0.0.0:63539> on TCP
(ReliSock) and UDP (SafeSock).
02/12/16 10:15:20 DaemonCore: command socket at
<172.20.130.210:63539?addrs=172.20.130.210-63539>
02/12/16 10:15:20 DaemonCore: private command socket at
<172.20.130.210:63539?addrs=172.20.130.210-63539>

The host has the following defined:
HIGHPORT = 25100
LOWPORT = 10000
(shared port is not in use. Version 8.4.3)

After a few restarts, the startd ends up listening within the desired
range. Digging through the code, I saw comments referencing
https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4711 . I'm not
sure if the behavior here is related or not. Is disabling
BIND_ALL_INTERFACES and binding to a single interface a reasonable
solution here?


Thanks,
BC

-- 
Ben Cotton

Cycle Computing
Better Answers. Faster.

http://www.cyclecomputing.com
twitter: @cyclecomputing