linux connecting to a setiq machine thru proxy

[cory]

well i am tired of losing output when the seti site goes
down so i want to run setiq on a win machine.

the problem i have is that currently a bunch of my linux
diskless nodes connect to a linux server and use
its proxy server to talk to seti server.

i have been using the proxy setting to do that up
until now but the machine running setiq is on the
other side of the diskless nodes and has to use the
proxy to get to it.

where do i put the ip address of the machine it should
get the w/u from?

 

[Michael]

Cory - you're using a linux proxy server instead of NAT to connect to the internet?

The clients have one proxy setting, and I set it to my Win machine with SETIQ, but I use NAT to get through to the internet. It sounds like you need two settings - one to the proxy server and then one to the setiq server. Don't know how that would work.

Can you run SETIQ under WINE on your Linux machine. That might solve the problem.

Michael

 

[cory]

my linux server has 2 nics it.

one local and one on the public side.

the win 98 has a ip address on the public side.

i could move the win 98 to the other side and have it connect
thru the proxy but then i would not be able
to use pc anywhere to connect to the win98 box.

i dont want my nodes to access the web for anything except seti.

 

[JHutch]

Cory,

You put the IP address of the SETIQ server in the command line for the seti executable. I.E., on a Windows machine, you would type:

SETI.EXE -proxy 192.168.0.1:5512

The problem is, there is no way to tell the client to route through a proxy to ANOTHER proxy (SETIq). In your case, you need the data to route through your Linux server and THEN to the Windows machine.

There are two things I can think of that might work. One is Michael suggestion below. Try running the SETIq program under WINE. I don't know if this works, though, as I haven't tried it.

The other is to write a quick and dirty batch file that downloads a work unit, copies the file into a "backup" directory then copies another. There is little automation to this, but it might provide a way to get around the problem you're seeing.

Also, there might be some of the Unix guys around with a better solution, though a quick search by me didn't turn up anything substantive...

Good luck!

JHutch

***EDIT*** Some of this is probably more basic than you need, Cory, but I thought a quick and dirty tutorial might help some others "lurking" around...

 

[cory]

yea i was already doing the proxy.

i might see if a can create a static route
from the node to the linux box and the win98 box
and back.

 

[Michael]

My TCL programming is fairly weak, but I bet you could create a small script that passed the request for the WU from the node through the server to the Win machine.

You would just have the script watching for activity on port 5512 and then pass that request on to SETIQ. It might take a couple of e-mails to the person who wrote SETIQ to get the handshake right.

Of course, if you had enough info on the actual SETI handshake and send unit, it shouldn't be that hard to write a Linux version of SETIQ. Does anyone know if the person who wrote SETIQ has been approached about this?

The Linux cacheing method that I have seen is a script with nested directories/instances of SETI. I don't think that will work on your diskless nodes.

Is there a stong security reason why you have your nodes on a private subnet so that they need to use a proxy server? If they could see the Win machine then all problems would be solved.

Michael

 

[ColinP]

Can't you just turn on IP forwarding on the Linux server ????

My Suns are all on a 192.x.x.x network, One has 2 nics, 192.x.x.x and 87.x.x.x, my SETIQ server is on 87.x.x.x.

I just turn on IP forwarding and give the Suns a static route to the 87.x.x.x network via the Sun with two Nics.

You have to do the same backwards on the Windows box.

Takes 10 minutes...



Col

 

[cory]

what command did you use for ip forwarding?

i know how to do it on unix boxes.
and i know the route commands on win98 and linux.

 

[ColinP]

Cory,

you can do it in linuxconf, just put an x in the box.

You can start linuxconf from the command line or GUI.

Go into,

config
routing and gateways
defaults

and put the x in the box,

then quit and activate changes...

cheers,

Col.

 

[cory]

thanks colinp.

i am so used to doing everything by hand
that i rarely go thru the menus

(had to run the char version of it cause i havent
been home in 6 weeks, but it worked)