• 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.

does pproxy work through a modem. **UPDATE** WAHOO! ITS WORKING!!!ITS WORKING!!!

Adul

Elite Member
Can it get it to dial out when it needs to fetch/flush packets? If I can, then I think I will be adding a few dozen more comps to the cause. Hey michael, PM if I get this to work.



**Updated**

Got the pproxi up and running through a free ISP connection. I request 4k blocks. I dont think it will last long with enough comps running rc5. 🙂 Time to assimulate more now. MUAHAHHAHAHA
Resistance is futile!
 
Best thing to do is set up the pproxy for lurkonly. THat way when a connection is made, then it will fetch new blocks and flush the completed ones. Good rule of thumb is to have enough for 3 days, unless these machines don't make a connection that quickly.

Jay
 
Adul,

As long as you have your OS set up to autodial when a TCP/IP connection is needed, then it will work fine. Otherwise, it's relatively easy to set up a pProxy to buffer enough blocks for it to save several days of work and then you can do a fetch/flush whenever it's possible for you to do it manually.

Give us some more details on your OS and I'm sure we can help you get it configured to auto-dial. 🙂

-Brian
 
It will be a box dedicated to that task only(and cracking blocks). It will be using Win2k and a 56k modem. So if I had it dial out once a night and dump and flush a bunch of blocks it should be ok then. How much time would it take to download 4000 blocks on let say a 3KBs speed?
 
Well, that's a good question that's rather tough to answer. If all goes well, it should take less than a minute for it to get everything done, but if there is congestion on the proxy that you're fetch/flushing to or if you get a whole ton of really tiny WU's to equal the 4000 you need, then it could take longer.

If I were you, I'd set up your tcp/ip dial-up to auto-connect and then auto-disconnect after 5 minutes of no activity. Then I'd let the pProxy just operate like it's got a full-time connection and set it to flush it's buffers at a level that should be about a days work for all of your machines.

If you require a specific time of day to make the connection, then I'd use task scheduler (or whatever it's equivalent is in Win2K) to initiate the dial-up and set the proxy to "lurk-only" like Jay suggested.

You might be able to set up the proxy to attempt the fetch/flush at a specific time interval and use this in conjunction with the auto-dial to time things, but I'm not sure if this feature is in the pProxy (and mine isn't in front of me to check). 🙂

Ask more questions if you need to, but I'm sure with the setup you described that you can pull this off. 😉

-Brian
 
It should be relitively fast. As far as I know of, the blocks themselves are tiny, so you don't need a lot of bandwidth. The only thing that will slow you down is that pproxies(and clients) allways make sure the blocks they send/recieve are undamaged, before they'll send another block(it's not bandwidth intensive, but it'll keep your modem from being the culprit🙂).
 
I see. well I try it on monday and hope it works. If it does then I think we can have at least another 10 comps to add.
 
Adul!!! Adul!!! Adul!!! Adul!!! Adul!!! The crowd is chanting wildly!!!!!

YOU ROCK!!!!

Way to think outside the box.
We'll get that nasty firewall issue settled yet too! 🙂
 
If your pproxy idea works and I can see it from my machines, I'll be able to add about 10 PII's to the cause from my office as well.

Michael
 
Out of interest, have you tried using a SocksCap program to bypass the firewall?? I dont know all the technical details of how it works (so dont ask me) but from what I remember, they can sometimes allow programs to go through firewalls that really dont want to play ball.

I found this page - it might be useful
 
sockscap is just a sort of tunneling system. you need to have sockscap server installed to machine which is not behind firewall in your internal network.
 
The fact of the matter is that if Adul can get the Perproxy installed on a machine that can use a modem to connect to the Internet, it will work.

A study of the Perproxy readme is in order. Just download the Perproxy program, print out the readme, sit down with a cold __ or a cup of coffee and a highlighter, and you can figure it out. The perproxy is very versatile.

Using REMOTE BUFFERS is a less effective option. It uses NETBios permissions and shares, so it is visible on the network. If a system is not logged on, it may not be able to fetch/flush (with Win 9X anyway) The perproxy system can be totally invisible as it uses Hosts or just plain old IP addresses to communicate. It is the best solution overall.

Totally confused? I am. 🙂

viz
 
Adul and I work for the same company (completely different business units and different states, but the same company). We both should be inside the firewall, so any of my machines should be able to see his machine and avoid the firewall problems we're both having.

From an IT security point of view, I do think there might be an issue with a machine that has a modem and is connected to our WAN as it might create an entry point that bypasses our firewall. I bet it isn't really an issue, especially if the modem doesn't accept calls.

Michael
 
yes a pproxy works on dialup. I am using it and have it flush 800 blocks (about once a day) and retrieve to fill up buffers to max (2000). It dials on demand and then does not keep the connection alive by flushing each block afterward. if you want, I can copy my ini over to you so you can see it. Note, this is the box with the modem on it, I could not get my other boxes on an ICS setup to flush w/o this pproxy.
 
Very true Michael.

Some points to consider
Don't have file and printer sharing bound to the modem TCP/IP connection.
The disconnect on 5 minutes of inactivity may not work, as the perproxy will continue to flush/fetch as they come in when a connection is detected. There should be a couple of work arounds if this occurs.

Pardon me if this has come up before, but have you tried port 80? Ray had a heck of a time with his firewall until he pointed his clients/proxy to Clueless's IP address on port 80.

Apparently his firewall was blocking DNS resolution, so flushing to a static IP proxy was the best solution.

good luck, and feel free to ask for further help.

viz
 
vistech, you are wrong on the autodisconnect. I have mine set to flush only when reaching a certain amount of blocks in the outbuffer, or only when it is below a certain point in the in buffer (that way I can make sure it gets more blocks before I run out completly). Btw, it takes about 30 seconds to dl/upload 800 blocks over 56k dialup. Much much faster than if I was using the client to fetch/flush.
 
PF

You have the proxy initiate the connection then, and the logic to dial up and disconnect is with the proxy program.

Where the potential problem would lie, is with the 'Lurk only' or dial-up detection mode and using Task Scheduler to initiate the dial up, where on a connection the proxy (or clients would work the same) will flush whenever there is a conection AND there is anything in the out-buffer OR the in-buffer is below the max buff-in setting.

For instance, my proxy has a new client connection every couple of minutes when cracking RC5 and when only tiny blocks are available. If I was using lurk only, and set to disconnect on 5 minutes of inactivity, it would flush the new incoming blocks as they arrived. Since this occurs on average every 2 minutes, the 5 minute countdown starts over again, and it would never disconnect.

Obviously some of the workarounds would be to have clients build up prior to flushing. This cuts down on the connection frequency, thus lessening the chances that this scenario would occur.

Obviously you have your proxy and the clients set to work very well together. I was just pointing out the potential that this could happen using task scheduler in combination with a high rate of client connections to the proxy.

The key that I saw in Adul's post was to connect to the Internet only once overnight. I don't think that the proxy can schedule that on it's own, but maybe I am wrong. That forces having to use Task Scheduler.

viz
 
hrmmm I would have to think on that one... How about this... set it to not initiate dialup (lurk only) set min buffout to be 200+ blocks (so it will autodiconnect via time out)

would that work?
 
You might be on to something there, PF. But would that hold 200 completed blocks all the time?

Can you test that on yours and let us know. It sounds like you're the man to test this out PF. 🙂

BTW, I am on cable modem, so none of the dial up settings apply to me. Heck, I don't even have a modem in most of my computers.

viz
 
Ok, I got the Pproxy installed and I am using netzero for the isp (why pay). Anyways, how do I set up my clients to connect to the Pproxy?
 
Adul-

In the client config enter the IP of the pproxy machine for the keyserver address. I believe it is option #2, #6, #3.

Osmo.
 
Back
Top