Unless your pproxy machine has 2 or more IPs, don't bother setting
listenaddress. Here's the blurb from the
Readme.txt:
[ports]/listenaddress: The IP address of the machine this personal proxy
is running on. This is optional and only needed if the machine has
multiple IP addresses. If you use one ip address for local connections,
and you have a dialup account that you use to fetch and flush blocks,
you do *not* need to set this.
Regarding whether a dnet client (dnetc or pproxy) must use the IP address instead of host name of the upstream keyserver, I thought the following setting might be relevant:
[ports]/advertisedaddres: This value is normally not needed and is only
needed if you are having problems serving HTTP clients and your personal
proxy machine has a different address by which it is reached on than
what it listens on. (This is usually the case when you are attempting to
serve clients with a machine behind a NAT firewall, or a port-redirected
environment.) This value should be the public IP address that is usuable
by clients to connect back to your personal proxy with. If you do not
specify this value, the value you specified for the listenaddress is
used, otherwise no address is used.
A while back while I was helping
HeavyIron with his setup, I noticed that his initial handshake was to my public IP but all subsequent packets was addressed to my private LAN IP which of course got nowhere. At the time, I did not know about this setting and
HeavyIron wound up dumping MS proxy and went with a NAT firewall himself. Ever since I found out about this setting, I've always wanted someone to try it out but no one volunteered to be a guinea pig.
RaySun2Be was supposed to help me out in this
thread but he never did. Perhaps he got upset cuz I called him
senile?
