• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DnetC on a pProxy Machine?

A

Athlex

Golden Member
Is there an "optimal" setup for running a pProxy and D.Net client on the same machine? Right now I've got the proxy running on my TBird 800 (windows) and have the client set to retrieve keys from 127.0.0.1
Are the client and proxy programs aware of each other when they run? Is there a better setting I should use for this setup? Thanks
atx
 
The machine I have my pproxy on (Mother Cow) has two nics... one to the corporate lan, and the other to my cow lan. The cow lan nic's IP address is 192.168.1.1. The dnet client on Mother Cow gets its work from 192.168.1.1. Seems to work just fine!
 
I don't know of an optimal setup, I do have the dnet client and perproxy running on the same Win2Kpro machine which has a static IP addy, and I set the client just like the other clients, set to fetch/flush from that static IP addy. 🙂

One thing I did do, was to configure the clients so that under #2 Buffer Options, #6 keyserver<-->client connectivity options, #5 Keyserver is a personal proxy on a protected LAN is set to YES, and #6 Firewall/proxy protocol is set to none/transparent/mapped

I had originally set it to go through the firewall, but found it wasn't needed, and I had started using a perproxy stats program, and the only IP addy showing was the firewall, until I made the changes above, so that each cows IP addy was being shown. 🙂

If anyone else knows of any optimizations for the two, I would be interested to hear them too. 😀
 
Cool okay. So it doesn't really matter whether I use 127.0.0.1 or the regular IP address (192.168.1.24, in this case)?
 
I don't think so. I (finally) installed all the clients in the same place, under the same folder, so I can easily update the .ini via the logon script, and it makes it a lot easier to manage if all my cows are configured the same.
 
How does your setup work? Do they boot linux and run the client from the network while keeping packets locally?
 
Athlex, Can the rest of your machines see the pProxy machine? I always thought 127.0.0.1 was a loop back IP address. Your pProxy machine should work with that IP because it is that IP, but I don't know if the rest of the machines would be able to fetch/flush to it, because it would loop back to themselves.

Did I make any sence?
 
Nope. The slave nodes fetch/flush to 192.168.1.24 (the pproxy box.) I was just curious whether it's better to use 192.168.1.24 or the loopback IP address for running the client on the pproxy machine. I suppose there isn't a whole lot of difference there, but I was just curious...

<edit> Yep, you made sense 🙂 </edit>
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top