weird!

[randy48]

I just noticed something strange! The client on this box just finished a send and it has the key server IP backward! This is from the client screen:

[Sep 29 02:57:36 UTC] 4 RC5 packets (24 work units) are in buff-out.rc5
[Sep 29 02:57:36 UTC] Connected to 177.9.72.24.in-addr.arpa:8080...
[Sep 29 02:57:36 UTC] The perproxy says: "Soon, Pinky, I plan to conquer the
OGR World!"


This is from the configuration screen:

distributed.net client configuration: Keyserver<->client connectivity options
--------------------------------------------------------------------------
1) Network Timeout (seconds) ==> 60 (default)
2) Automatically select a distributed.net keyserver? ==> no
3) Keyserver hostname ==> 24.72.9.177
4) Keyserver port ==> 8080
5) Keyserver is a personal proxy on a protected LAN? ==> no
6) Firewall/proxy protocol ==> none/transparent/mapped
7) Use HTTP encapsulation even if not using an HTTP proxy? ==> no
8) Always use UUEncoding? ==> no
9) Dialup-link detection ==> Normal mode

0) Return to Buffer and Buffer Update Options

Choice -->

I have it configured the same as my other box, why the different format/reversed IP address? The only difference is the other box goes through a proxy on this box to share my cable modem.

Anyone have an idea?

Thanks

Randy48

[socalgal]

I don't know why, but mine's like that also.

[Ultima]

Same here!!

Maybe they encrypted it??? ROFLMAO

I wouldn't know why that is, you'd have to ask someone who helped designing the client I guess.

Pim

[skippy]

in-addr.arpa

Thats why. If you want to know why in-addr.arpa does that, post to the networking forum.

[socalgal]

Oh, Skippy...
http://sysopt.earthweb.com/forum/Forum6/HTML/001403.html