can someone explain?

[Z24]

What are the different levels of dist.net?

What I mean is the different levels of proxying. You can have the client, then a personal proxy, etc...

What is TACube? Mika's proxy? Please explain...

Thanks,
Dave

 

[Russ]

<< What I mean is the different levels of proxying. You can have the client, then a personal proxy, etc... >>



The pproxy software is available for anyone to use. It is ideal when one has multiple systems on a network as all the systems can fetch and flush to one that acts as server and, in turn, updates to a keyserver.



<< What is TACube? >>



TA Cube is a mini team within Team AnandTech. There are several: The Federation, TWTA, The Crackheads, Nekkid Crackers...



<< Mika's proxy? >>



Mika's, aka teamanandtech.com, is the team pproxy and has constants stats updates. Many people flush there because they REALLY need lots of stats.😀 Others flush directly to Dnet.

Russ, NCNE

 

[Z24]

So, if you become a member of TA Cube, how are you identified individually? Or are you not?

And, Mika's proxy--it's just a personal proxy with a lot of logfile analysis? Can one personal proxy dump into another pproxy?

BTW, nice crack-rack 🙂

Dave

 

[Russ]

<< So, if you become a member of TA Cube, how are you identified individually? Or are you not? >>



If you become a member of any mini team you would no longer have individual stats.



<< And, Mika's proxy--it's just a personal proxy with a lot of logfile analysis? Can one personal proxy dump into another pproxy? >>



All the pproxies have the same log file analysis. Here is one of mine. (I actually have two). Yes, one P can update to another. I have an internal only one that fetches and flushes to the one I just linked.

Russ, NCNE

 

[ViRGE]

Z24, the hiarchy goes like this:
note: ~ means that there may be unknown steps in between


client~Baby Bovine-Mikas-Dnet Proxy~Master Keyserver

Since the client is the self obvious part, we'll skip to the first ~. A client can flush to a Dnet proxy, a Baby Bovine, or to a personal proxy. The PP is used when you have a large herd, and want to keep the traffic and hits on a BB or Dnet down(or in some cases, to keep packet fragmentation down). You then have the Baby Bovines, which collect blocks for the team's proxy, which we refer to as Mikas. By having the BBs colleck blocks, you gain some redundancy in case something higher in the chain goes out, along with all the advantages of using a PP. Anyways, we then have Mika's, which is the team's PP; that is used to collect blocks for stats purposes. You then have the Dnet PPs, which distribute and collect blocks from all of the end users; followed by a possible proxy above the Dnet PPs. Lastly, you have the master keyserver, which records what blocks have been done, and issues new blocks. Any questions?😉

 

[NicColt]

Russ, is there a way to view stats like the link you posted but for the entire 20,986,114 blocks that TACube posted to dnet?

 

[Russ]

Nic,

Nope. The Dnet stats don't go in to the detail level that the pproxy stats do. You can check daily submission history, but that's about it.

Russ, NCNE

 

[HomerSapien]

Russ, to get individual stats on a mini team you could setup your proxy sort them by IP. Several of the proxy stat generators have that option.

Could be a big hassle having 100,000 blocks traveling through your proxy everyday. At least if you get charged for bandwidth. Might be worth it so people could at least see how they are affecting the team....But individualism kind of goes against being in a collective..hehe

 

[Russ]

If you click the &quot;By Host&quot; in the link above, that's what you'll find.

Not worried about having a 100K blocks coming thru the pproxy each day. I have the bandwidth (512k) and the server's a beefy animal (dual P3-550Mhz, SCSI).

Problem is that I'm just now getting to the point where I've aquired BARELY enough skill to set up all the little details that go in to server management. I need a little higher comfort level with this stuff first.🙂

Russ, NCNE