Bah! you all got me hooked on rc5.

[Dag]

I am expanding my herd to some computers I have laying around not doing anything anyway. So far here is what I have.

1 PIII 600
1 PIII 500
2 cel 500's
1 cel 433
1 P233 mmx

Working on:
1 Cel 366
1 Cel 333
1 P100
1 P90
and 3 or 4 p60's.

Here is my question. I run most of these behind a proxy here at work (only the 600 has a NAT). I have to put my local proxy info into the network portion of the dnetc.ini. I want to push it through a team proxy, but can't figure out how to do it with my local one in there. If someone has this working could you drop your dnetc.ini here so I could take a look?

Thanks!
Dag

 

[SYST3M]

you could set up a pproxy on your LAN and fetch/flush to it, then have it flush to Mika's, that would work.

 

[Jator]

We hooked another one!!!! Woooohooooo!!!!

 

[Dag]

Explain the pproxy idea more. Like I said I have my main machine here that is on a NAT. I can do pretty much anything to it I want. The others will be 24/7, but are behind a fairly restrictive proxy.

Dag

 

[JonB]

On the 600, you would install a "personal proxy server" from Distributed Net. This would be where all your computers, even the 600, would fetch and flush their RC5 blocks. The Personal Proxy will try to keep 3 days worth of work cached to allow for Internet loss, but you can configure it to refresh itself at a smaller interval, like 180 or 720 minutes, etc...

If your other comps can get through the LAN proxy to see your 600, you are in great shape. If your LAN proxy is picky, you may have to get creative about which ports to allow traffic thru. Port 2064 is the standard DNet PProxy port, but most LAN proxies block it. You can use 23 or 80, since most LAN proxies let that traffic pass. (but, if your 600 comp is running an HTTP server, port 80 is busy).

So, first thing I would do is install the PProxy, see if it works with default settings, and if it doesn't, one of us can help you get it talking. There have only been a few proxies/firewalls that have kicked our collective butts.

D Net Proxy downloads are here !!!

 

[Dag]

Ok its dowloaded and running, but how do I know if it is working right?

The other computers can access mine through the LAN, that shouldn't be a problem.

Here is the text from the pproxy:

[2000-10-13 15:21:23] distributed.net Personal Proxy (build 318)
[2000-10-13 15:21:23] Visit http://www.distributed.net/ for details.
[2000-10-13 15:21:23] Proxy starting up.
[2000-10-13 15:21:23] Verbosity set to: general stats keyblock server client buf
fers timestamp attention errlow errsevere (3519)
[2000-10-13 15:21:23] rc564-in: limits adjusted to min 1, max 20
[2000-10-13 15:21:23] desII-in: limits adjusted to min 1, max 20
[2000-10-13 15:21:23] csc-in: limits adjusted to min 1, max 20
[2000-10-13 15:21:23] Notice: connectivity mode is normal
[2000-10-13 15:21:23] Notice: Loaded 0 ignoredip addresses from ini file
[2000-10-13 15:21:23] Notice: Loaded 0 allowedip addresses from ini file
[2000-10-13 15:21:23] Notice: Primary listener bound to (all devices):2064
[2000-10-13 15:21:23] Notice: Test listener bound to (all devices):3064
[2000-10-13 15:21:24] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:21:24] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:21:24] Status: Uptime: 0.00:00:00, 2 listeners, 0 uplinks
[2000-10-13 15:21:24] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:21:54] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:21:54] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:21:54] Status: Uptime: 0.00:00:31, 2 listeners, 0 uplinks
[2000-10-13 15:21:54] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:22:25] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:22:25] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:22:25] Status: Uptime: 0.00:01:02, 2 listeners, 0 uplinks
[2000-10-13 15:22:25] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:22:56] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:22:56] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:22:56] Status: Uptime: 0.00:01:33, 2 listeners, 0 uplinks
[2000-10-13 15:22:56] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:23:27] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:23:27] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:23:27] Status: Uptime: 0.00:02:04, 2 listeners, 0 uplinks
[2000-10-13 15:23:27] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:23:58] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:23:58] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:23:58] Status: Uptime: 0.00:02:35, 2 listeners, 0 uplinks
[2000-10-13 15:23:58] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:24:29] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:24:29] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:24:29] Status: Uptime: 0.00:03:06, 2 listeners, 0 uplinks
[2000-10-13 15:24:29] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:25:00] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:25:00] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:25:00] Status: Uptime: 0.00:03:37, 2 listeners, 0 uplinks
[2000-10-13 15:25:00] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:25:31] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:25:31] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:25:31] Status: Uptime: 0.00:04:08, 2 listeners, 0 uplinks
[2000-10-13 15:25:31] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:26:02] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:26:02] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:26:02] Status: Uptime: 0.00:04:39, 2 listeners, 0 uplinks
[2000-10-13 15:26:02] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 15:26:33] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 15:26:33] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 15:26:34] Status: Uptime: 0.00:05:10, 2 listeners, 0 uplinks
[2000-10-13 15:26:34] Status: 0 active clients (peak: 0, mean: 0.00)

 

[JonB]

Dag, have you configured any clients to go to the PProxy for new RC5 blocks? In that logfile, I never saw any access, but that could be because there wasn't any.

Now that you have a proxy running, the individual clients must be redirected from the old keyserver to the new keyserver (which is your 600 and its PProxy). You can use the LAN DNS name or just the IP address. You're doing good so far.

 

[Dag]

Ok this look better?

[2000-10-13 16:08:24] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 16:08:55] rc564 r=64/20, d=0/3, 0.0 Mkeys/sec, tot=0
[2000-10-13 16:08:55] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 16:08:55] Status: Uptime: 0.00:47:32, 2 listeners, 0 uplinks
[2000-10-13 16:08:55] Status: 0 active clients (peak: 0, mean: 0.00)
[2000-10-13 16:09:20] Client: Accepted connection from 10.1.1.16:1999
[2000-10-13 16:09:21] Client: 10.1.1.16 (client ver: 463) is connecting
[2000-10-13 16:09:21] Client: 10.1.1.16 <-- rc564 x 24 dc0fa5ee:00000000
[2000-10-13 16:09:21] Client: 10.1.1.16 <-- rc564 x 16 dc0fa5ef:80000000
[2000-10-13 16:09:21] Client: 10.1.1.16 <-- rc564 x 8 dc0fa5f0:80000000
[2000-10-13 16:09:21] Client: 10.1.1.16 --> rc564 x 8 dce60025:80000000
[2000-10-13 16:09:21] Client: 10.1.1.16 --> rc564 x 8 dce60023:f0000000
[2000-10-13 16:09:21] Status: Uplink needed... (thresholds exceeded)
[2000-10-13 16:09:21] Status: Creating uplink (outgoing server) connection.
[2000-10-13 16:09:22] Uplink: [1] connection to 134.53.131.135 changed state
from 0 (ESTNONE) to 1 (ESTCONNWAIT)
[2000-10-13 16:09:22] Client: 10.1.1.16 --> rc564 x 5 dcfd1b25:00000000
[2000-10-13 16:09:23] Uplink: [1] connection to 134.53.131.135 changed state
from 1 (ESTCONNWAIT) to 50 (ESTREADY)
[2000-10-13 16:09:23] Uplink: [1] Establishing handshake with 134.53.131.135..
[2000-10-13 16:09:23] Client: 10.1.1.16 has ended communications.
[2000-10-13 16:09:23] Client: Closing client connection with 10.1.1.16
[2000-10-13 16:09:24] Uplink: [1] Server is running version 319.
[2000-10-13 16:09:24] Uplink: [1] Server is running version 319.
[2000-10-13 16:09:24] Uplink: [1] Got permission acknowledgement.
[2000-10-13 16:09:24] Uplink: [1] The fullserver says: &quot;moo is short for moose
(moose)&quot;
[2000-10-13 16:09:21] server: --> uplink rc564 x 8 dce60025:80000000
[2000-10-13 16:09:21] server: --> uplink rc564 x 8 dce60023:f0000000
[2000-10-13 16:09:21] server: --> uplink rc564 x 5 dcfd1b25:00000000
[2000-10-13 16:09:21] server: Sending rc564 request, iter 64.
[2000-10-13 16:09:21] server: <-- ack OK rc564 x 8 dce60025:80000000
[2000-10-13 16:09:21] server: <-- ack OK rc564 x 8 dce60023:f0000000
[2000-10-13 16:09:21] server: <-- ack OK rc564 x 5 dcfd1b25:00000000
[2000-10-13 16:09:21] server: Received rc564 dc128da2:60000000, iter 64
[2000-10-13 16:09:23] rc564 r=80/20, d=0/3, 2.0 Mkeys/sec, tot=21
[2000-10-13 16:09:23] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 16:09:23] Status: Uptime: 0.00:48:03, 2 listeners, 1 uplink
[2000-10-13 16:09:23] Status: 0 active clients (peak: 1, mean: 0.50)
[2000-10-13 16:09:51] Uplink: [1] 134.53.131.135 disconnected (reading).
[2000-10-13 16:09:51] Uplink: [1] Closed connection to 134.53.131.135.
[2000-10-13 16:09:51] rc564 r=80/20, d=0/3, 1.9 Mkeys/sec, tot=21
[2000-10-13 16:09:51] Status: rc564: Last uplink sent 21 and received 64
[2000-10-13 16:09:51] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 16:09:51] Status: ogr: Last uplink sent 0 and received 0
[2000-10-13 16:09:51] Status: Uptime: 0.00:48:31, 2 listeners, 0 uplinks
[2000-10-13 16:09:51] Status: 0 active clients (peak: 1, mean: 0.08)
[2000-10-13 16:09:54] rc564 r=80/20, d=0/3, 1.9 Mkeys/sec, tot=21
[2000-10-13 16:09:54] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 16:09:54] Status: Uptime: 0.00:48:34, 2 listeners, 0 uplinks
[2000-10-13 16:09:54] Status: 0 active clients (peak: 1, mean: 0.08)
[2000-10-13 16:10:25] rc564 r=80/20, d=0/3, 1.9 Mkeys/sec, tot=21
[2000-10-13 16:10:25] ogr r=20/20, d=0/3, 0.0 Mnodes/sec, tot=0 stubs
[2000-10-13 16:10:25] Status: Uptime: 0.00:49:05, 2 listeners, 0 uplinks
[2000-10-13 16:10:25] Status: 0 active clients (peak: 1, mean: 0.04)

 

[LeBlatt]

[orc voice]Your soundcard is working perfectly ![/orc voice]

Err.. no, wrong game ! It's your pproxy.

Now if you want to, you can have your proxy to TeamAnandtech round robin, instead of dnet's. So you'll get stats every 30 mn instead of daily.

 

[Dag]

Hehe ok, I am in the process of changeing over my other clients to go through the pproxy. I would like to push it through a TA proxy, I am guessing that is a change in the pproxy ini somewhere?

 

[JonB]

Much better. I see a client connected, sent some blocks, took some blocks, then your PProxy sent some blocks to DNet and took some blocks.

The version of PProxy you're running, 318, will automatically change the size of the input buffers as traffic changes. It's calculations try to find the buffer size you'll need to support 3 days of work. Each time you shutdown and restart the PProxy, it goes back through the setup. I believe it takes a minimum of 30 minutes before it will adjust the size.

your client (PC with 10.1.1.16) did this and took 48 blocks (24+16+18), then flushed 29 (8+8+8+5)

2000-10-13 16:09:21] Client: 10.1.1.16 (client ver: 463) is connecting
[2000-10-13 16:09:21] Client: 10.1.1.16 <-- rc564 x 24 dc0fa5ee:00000000
[2000-10-13 16:09:21] Client: 10.1.1.16 <-- rc564 x 16 dc0fa5ef:80000000
[2000-10-13 16:09:21] Client: 10.1.1.16 <-- rc564 x 8 dc0fa5f0:80000000
[2000-10-13 16:09:21] Client: 10.1.1.16 --> rc564 x 8 dce60025:80000000
[2000-10-13 16:09:21] Client: 10.1.1.16 --> rc564 x 8 dce60023:f0000000
[2000-10-13 16:09:22] Client: 10.1.1.16 --> rc564 x 5 dcfd1b25:00000000



Here's a good line from your log:

[2000-10-13 16:09:51] rc564 r=80/20, d=0/3, 1.9 Mkeys/sec, tot=21
[2000-10-13 16:09:51] Status: rc564: Last uplink sent 21 and received 64

It clearly shows that blocks were sent and received from D.Net

You are cookin' Dag. Way to go.

 

[JonB]

Assbolutely, you change the proxyper.ini

to look like


[KeyServer]
ipaddress=proxy.teamanandtech.com

 

[Dag]

Ok I got it!

Just need to push my home machines through the TA proxy and finish configuring a few clients here at work.

This is what I have cracking so far.

P3 600
p3 500
P2 450
2 cel 500's
cel 433
cel 366
cel 333
P 233

Anything else I should tweak or know? Maybe I should join a mini team hehe.

Dag

 

[HeavyIron]

You could open the pproxy on you 600, then start flushing your home herd through it.
Then set up some stats and you'll be able to keep track of every single block that you crack!! Hmmm. more stats!

 

[dennilfloss]

You would make a great Borg!!!

 

[JHutch]

Oh, yeah, you're truly one of the addicted now!

JHutch

 

[MrAtheist]

Rc5 is a legal drug

 

[Adul]

A cheap drug too

 

[RaySun2Be]

JonB,
Do you have to restart the pproxy for it to go through recalcing what it needs for three days? I have mine running on a Win2K Pro machine that I haven't shut down or even messed with for several months, and I've recently added a significant amount of cow power to the work herd.

Adul,
My wife would disagree on the &quot;cheap&quot; part of your statement! :Q



Dag
Welcome to the club!

 

[Jator]

Dag,

If you are internetsed in setting up your own stats page, let me know. For some examples, check out my web page in my sig. I have several versions of the stats running on my machine.

Jay

 

[Dag]

Everyone: Thanks for the help, everything seems to be working, I can even see my name on Mikea's page. Course I am like 5th to last but hey give me time hehe.

HeavyIron: My 600 is still inside our firewall, with the 10.1.1.16 addy you see in the logs above. I would have to figure out someway into our LAN to hit my machine, prolly not worth it for no more blocks than I will have coming from the house. I will just let them dump through mikea's directly.

dennilfloss: I may just have to do that, we shall see.

Jator: I will take a look and see what I can come up with.

Dag

 

[JonB]

Ray, no you don't have to restart. It checks itself on some kind of period, probably every 30 minutes.

Dag, glad to help. That was pretty painless. You must not be some &quot;wet behind the ears newbie.&quot;

Heard someone called a &quot;Twelve O'Clock Flasher&quot; today. Didn't know what it meant.











they explained later that it is someone so technically illiterate that all their clocks are flashing 12:00



rofl

 

[Dag]

Sounds like 95% of the people that I get to support all day.

I have had the RC client on before, but never did much with it. I recently installed it and got it to shoot out the proxy, but decided to expand it today too all these machines not doing anything (mostly notebooks waiting on one thing or another).

It seems my celerons are a good deal faster than the P3's I have. Is this fairly consistent with what others see? Sorry, no Athlons running around to use for this to get the good times with.

 

[JonB]

From 5th from the bottom, you are now halfway up on Page two. Pretty good climb. You must have a little bit of Borg in you.