iptables -t nat -A PREROUTING -p tcp -d 10.0.0.1 --dport 9616 -j DNAT --to-destination 192.168.0.2
iptables -A POSTROUTING -o eth1 -j SNAT --to-source 10.0.0.1
{endcode}
-The first rule above says that inbound connections to 10.0.0.1 on port 9617 will be rewritten to be connections to 192.168.0.1, port 9617. The second line states a similar rule for 192.168.0.2, port 9616. The third rule is probably superfluous, as it is likely already in the firewall rules: all outbound connections from 10.0.0.1 will look like they emanate from 10.0.0.1.
+The first command causes inbound connections to 10.0.0.1 on port 9617 to be rewritten to be connections to 192.168.0.1, port 9617. The second is a similar command, but for 192.168.0.2, port 9616. The third is probably superfluous, as it is likely already in the firewall rules. It causes all outbound connections from 10.0.0.1 to appear as if they emanate from 10.0.0.1.
-Finally, run =condor_reconfig= on S and E to incorporate the configuration changes.
+After making the configuration changes, run =condor_reconfig= on S and E to incorporate the changes.
-One may well ask how this works for HTCondor. Simply put, HTCondor wraps all the information in an string with all the address information. =condor_status -schedd -l= will return a Schedd ClassAd, which will contain a line that looks something like:
+This works within HTCondor by wrapping all the information within a string with all the address information. To observe the string, issue the command =condor_status -schedd -l=, which will output a scheduler ClassAd. This ClassAd will contain a line that looks something like:
{code}
MyAddress = "<10.0.0.1:9617?PrivAddr=%3c192.168.0.1:9617%3fsock%3d936_480b_8%3e&PrivNet=mydomain.net&noUDP&sock=936_480b_8>"
{endcode}
-This string contains the needed information for another HTCondor client or daemon to contact the schedd and begin using high throughput computing. Examining this string may be helpful in debugging if you are unable to connect to remote HTCondor services.
+This string contains the needed information for another HTCondor client or daemon to contact the condor_schedd daemon and begin using high throughput computing. Examining this string may be helpful in debugging, if you are unable to connect to remote HTCondor services.
