Has anyone dealth with Firewalls and Seti service or seti driver?

[dxkj]

Has anyone dealt with firewalls before, and might possibly know a way to get through them without directly changing settings on the firewall?

I can reach the html page for the Seti Queues from here, but Seti driver cant get through to download directly. Ive also tried changing ports etc.

Sorry for the semi-repost but I figured this is asking a more direct question directly related to firewalls.


Thanks if you can help, might be able to throw another 70 machines worth of processing power into the TeAm if we can get it working.

 

[SoulAssassin]

Can you explain a little more about your environment and what's on what side of the fw?

 

[dxkj]

Sorry Im a bit new to this but Ill do my best.


The computers Im attempting to run Seti on are on a college campus.

My computer at home is running Seti Queue so I can change all the settings I want.

There is a firewall on campus that I dont know a lot about. I understand what it blocks via http is mainly triggered by words, and that ftp is pretty much wide open.

Unfortunately when trying to connect via Seti Driver to the queue at home, or even not using a proxie, directly to berkley, the program stalls after entering the email address and gives this error messaing:

"Email address: aaasmoke@bellsouth.net
recv fd=68 n=-1, errno=2"

The email address is valid, and it works fine for me from my home. This is the point at which it should be downloading data, but instead gets stuck there.


Thats about all I can think about, if you have any ideas or more direct questions let me know.

 

[Shuxclams]

Where ever your trying to access from try putting a SETIQ and have that connect directly with Berkeley, if I am reading that correctly. OR Set your SETIQ to listen on port 80. It may be a case of filtering Berkeley from behind the firewall or filtering non-standard ports. So one way of getting around it is having your clients directed at a Q on port 80 since I doubt they would catch traffic destined outbound to a standard HTTP port with no real recogonizable DNS would be ok.







Hope that helps.




SHUX

 

[dxkj]

I've tried setting the Q at 80 before, but then it doesnt even work on my computers in the same room. Same with 21. I think perhaps because of reserved ports it doesnt work quite right?

I will try putting a Q up here and see if it works

 

[Engineer]

Try setting your queue to port 443 (SSH). I had one similiar to what you describe and 443 is the only port that I could get it to work on!

Good luck!

 

[SoulAssassin]

Originally posted by: dxkj
I've tried setting the Q at 80 before, but then it doesnt even work on my computers in the same room. Same with 21. I think perhaps because of reserved ports it doesnt work quite right?

I will try putting a Q up here and see if it works

After reading your updated post, I was going to recommend moving setiq to port 80 as well. Once you do that you should be able to connect to setiq internallly by just going to http://machinename. If you can't do that, then you haven't properly moved setiq to port 80. Once that is working, you should be able to modify the machines behind the college fw to use port 80.

When it really comes down to it, if you're using setiq then you're adequately caching w/u's. Worst come to worst, just have it connect directly to Berkeley and forget about setiq.