Damn thing wont connect, i've set it to Proxy and port 800 (even tho my proxy is set as transparent) and still it wont connect, tho i can ping seti. Any ideas ? TIA 🙂
Any hints on how to get my q to work behind my firewall ?
- Thread starter aberant
- Start date
it's a Smoothwall (linux distro), i cant set the ports that the proxy listens on, tho i can set external access / port forwarding, both of which are set up to forward UDP and TCP on 5517, not entirely sure if it does true proxy, tho i'm pretty sure it runs NAT as it works without the proxy turned on. i can find out what the proxy prog is called tho, it'll be a GPL linux thing. cheers for reply
Bigwoofer
Senior member
- Oct 18, 2001
- 329
- 0
- 0
I had to set two settings on my linksys: forward port 5517 to the internal ip address of your queue machine, and also set it up as a DMZ host which places that machine outside your firewall.
Oh yeah! Be sure to set your subnet mask in your queue settings to 0.0.0.0 🙂
Good luck and happy crunching! 🙂🙂
Oh yeah! Be sure to set your subnet mask in your queue settings to 0.0.0.0 🙂
Good luck and happy crunching! 🙂🙂
well, port is already forwarded (hence stats working), and i cant set it to be in the DMZ cos i dont have another nice to put in the box, and it's my only machine so it'd b pointless having the firewall. I'm totally confused - it works to connect it to OK's Q, just not direct to berkeley - does it use different ports or what ? Thanks for the help 🙂
Orange Kid
Elite Member
- Oct 9, 1999
- 4,435
- 2,211
- 146
nail........head........ yep yep u just hit it boys ! and now i'm off to forward port 80 to my box 😀 cross fingers !
damnit it still aint werkin ! i got 80 and 8080 open on UDP and TCP, damn thing still wont connect :'( whats going on !?!?!
Aberant,
Not sure what the problem is with your firewall. Can you provide us with a little more detail about your configuration so that we don't have to guess what the configuration is? Details are always good!
Bigwoofer,
Just wanted to let you know that you don't have to forward port 5517 to the internal IP address of your Q machine if you also have that machine in the DMZ. By placing the machine in the DMZ, you are opening all ports on that machine to the outside world. The entry you have in the port forwarding screen of your router is redundant and if you're like me, you need everyone of those port forwarding options provided on that screen!
Not sure what the problem is with your firewall. Can you provide us with a little more detail about your configuration so that we don't have to guess what the configuration is? Details are always good!
Bigwoofer,
Just wanted to let you know that you don't have to forward port 5517 to the internal IP address of your Q machine if you also have that machine in the DMZ. By placing the machine in the DMZ, you are opening all ports on that machine to the outside world. The entry you have in the port forwarding screen of your router is redundant and if you're like me, you need everyone of those port forwarding options provided on that screen!
well that's half the problem - i dont have any details myself :S here's what i know - the q will connect to OK's queue, so i know that the q itself is working. however, when i point it to wininet direct / wininet default / winsock direct it just wont communicate with seti. when i use the ping function in the gui, it doesnt work, yet when ping from the command line it resolves fine. I'm on win2k, and my firewall is a dedicated box. there's nothing in the logs indicating that it's dropped any packets from seti. i think that's about all i know. any ideas ?
Hmmm I don't know all that much about networking or win2k but it seems you are trying to make things more complicated than they have to be. I have no idea how much you know about Que or Smoothie so I'll just list my setup and some descriptions, however keep in mind that I am not running the web proxy.
Here is my setup:
Smoothwall ~ Not running the web proxy and have done absolutely nothing when it comes to all that porting and dmz pinholes you guys were talking about.
WinME ~ I have no connection options set at all I just told it that I connect through a Lan. The smoothie should pass you right through to the net without having to specify any kind of proxy settings or ports. 😀
SetiQ ~ Go to settings then click on Que Server. The Seti@home sever settings should be the addy and port that your Q is on. For example:
Your Que's IP xxx.xxx.x.x
Your Subnet Mask xxx.xxx.xxx.xxx
Port: 5517
This is the addy you will need to set your clients for if you want them to connect to the Q.
For connection type I am using WinSock Direct (since smoothie passes you directly through to the net there is no need to enter any proxy settings).
If you are running the client on the same machine as the Q then I think you need to set your client to use localhost as the addy when pointing it at the Q. (I'm not that familiar with all the aspects of the client on the Q machine, it still gives me fits sometimes.)
This setup should work fine. If you really want to run the smoothie's web proxy I will turn mine on and play around with the settings as soon as I get a chance and see what settings are needed to make it work (I had a bit of trouble with it before).
If you are running the web proxy without transparency turned on you have to set your browsers proxy settings to smoothie's ip and port 800. If you do this then you will need to select WinNet Proxy or WinSock Proxy from the Q sever settings and then enter the smoothie ip and port 800.
Supposedly if you are using transparency then there is no need to add any kind of proxy settings it should just pass right through just as I listed in my setup above.
Hehe sorry for the length but maybe something in there was helpful.
BTW you do know that you can run seti on your smoothie don't ya? I just found out earlier this week and now have my P2-233 @ 350 mhz happily crunching away. If you don't already have it crunching I'd happily attempt (I'm a linux newb myself) to help ya as would several others in #linux on the anandtech sever. 😉
Here is my setup:
Smoothwall ~ Not running the web proxy and have done absolutely nothing when it comes to all that porting and dmz pinholes you guys were talking about.
WinME ~ I have no connection options set at all I just told it that I connect through a Lan. The smoothie should pass you right through to the net without having to specify any kind of proxy settings or ports. 😀
SetiQ ~ Go to settings then click on Que Server. The Seti@home sever settings should be the addy and port that your Q is on. For example:
Your Que's IP xxx.xxx.x.x
Your Subnet Mask xxx.xxx.xxx.xxx
Port: 5517
This is the addy you will need to set your clients for if you want them to connect to the Q.
For connection type I am using WinSock Direct (since smoothie passes you directly through to the net there is no need to enter any proxy settings).
If you are running the client on the same machine as the Q then I think you need to set your client to use localhost as the addy when pointing it at the Q. (I'm not that familiar with all the aspects of the client on the Q machine, it still gives me fits sometimes.)
This setup should work fine. If you really want to run the smoothie's web proxy I will turn mine on and play around with the settings as soon as I get a chance and see what settings are needed to make it work (I had a bit of trouble with it before).
If you are running the web proxy without transparency turned on you have to set your browsers proxy settings to smoothie's ip and port 800. If you do this then you will need to select WinNet Proxy or WinSock Proxy from the Q sever settings and then enter the smoothie ip and port 800.
Supposedly if you are using transparency then there is no need to add any kind of proxy settings it should just pass right through just as I listed in my setup above.
Hehe sorry for the length but maybe something in there was helpful.
BTW you do know that you can run seti on your smoothie don't ya? I just found out earlier this week and now have my P2-233 @ 350 mhz happily crunching away. If you don't already have it crunching I'd happily attempt (I'm a linux newb myself) to help ya as would several others in #linux on the anandtech sever. 😉
IJump
Diamond Member
- Feb 12, 2001
- 4,640
- 11
- 76
I have that problem from work. I was never able to fix it. I currently have a Queue at home that I go through, rather than OKs. My queue at home can hit berkeley, but the one at work will hit only certain other SetiQueues. It is rather odd.
For outgoing traffic, most routers don't need ports forwarded. They will handle that. It is incoming traffic, like requests for work units from my home queue that need to have port forwarding turned on. If you are requesting WUs from berkeley and they are responding to that request, your router should handle it without any forwarding.
Are all of the clients of your queue within your local netwaork, or do you have some connecting from the outside world? If the ones connecting from the outside world are trying to connect on port 5517, that is the port you need forwarded on your router to your local ip.
The only way I have used the proxy setting successfully in SetiQ is to get WUs from another queue. Not to deal with my router/proxy server.
Not sure if ya ever got this going or not but I checked anyway. 😀
I just turned on smoothwall's web caching and set it to transparent and everything worked just fine without having to specify any ip's or ports. Smoothwall is designed to provide a seamless connection to the net. Basically making it seem to windows that you have a direct connection to the net so there shouldn't be any need to specify proxy settings in windows for anything to work including setiQ (I am assuming all of your clients are on your local network and not trying to connect from the outside).
The only thing I can really think of is maybe you are trying to use proxy settings in either your windows connection properties (such as IE connection) or are trying to set proxy settings in setiQ itself which you don't need when running smoothwall. If you would like I could meet you in irc sometime and go over all your smoothwall and windows settings and help you find out where the problem is.
Here is the Smoothwall Site for anyone that might want to read up on it and see if they have any other thoughts.
I just turned on smoothwall's web caching and set it to transparent and everything worked just fine without having to specify any ip's or ports. Smoothwall is designed to provide a seamless connection to the net. Basically making it seem to windows that you have a direct connection to the net so there shouldn't be any need to specify proxy settings in windows for anything to work including setiQ (I am assuming all of your clients are on your local network and not trying to connect from the outside).
The only thing I can really think of is maybe you are trying to use proxy settings in either your windows connection properties (such as IE connection) or are trying to set proxy settings in setiQ itself which you don't need when running smoothwall. If you would like I could meet you in irc sometime and go over all your smoothwall and windows settings and help you find out where the problem is.
Here is the Smoothwall Site for anyone that might want to read up on it and see if they have any other thoughts.
well damnit all to hell ! first, having proxying turned on was slowing down the net substantially :S guessing i dont have enough ram / cpu power in ma smoothie for it :S also, i had IE set as automatically detect proxy settings and it seems that was what was causing the problem. grrrrr ! lol, i know it'd be something daft like that. anyways thanks a lot for the help, hope to catch you in IRC at somepoint anyways jus for a chat 🙂 l8r
LOL glad I could be of help. 🙂
I guess since you are worried about having enough power for web caching then you definetly don't have enough power to spare for seti on your smoothie. 😀
I guess since you are worried about having enough power for web caching then you definetly don't have enough power to spare for seti on your smoothie. 😀
lol, well i turned off proxying since it was only on for the sake of it and the fact that it's a large hd in there and i thought i might as well use the space. since i've turned it off and discovered it's actually faster, i wouldnt mind putting seti on there, since it only uses spare cycles. fancy lettin me know how u did it ? i'm a complete newbie when it comes to linux so treat me like a gimp 😀 cheers bud.
Well I'm a Linux newb myself but I can tell ya what I learned from my experiences installing seti on the smoothie. 😀
This may seem like alot or a bit complicated but I tried to write everything out step by step since I know how confusing it is for the linux newb when someone tells ya to do something and you have absolutely no idea of where to even start. 🙂
First off you will need to download the seti client of course. The easiest way is to just download it to a windows machine then use a SSH File Transfer Program to move the client to the smoothwall. This will let you just drag and drop the seti client onto the smoothwall machine. You will need to use port 222 and login as root to connect to the smoothie. BTW one thing I ran into that puzzled most everyone was seti would only work right if i placed the client directly in /root. If I placed it in any other directory or even a subdirectory of root it wouldn't work right. 🙁
Now that you have the client actually on the smoothie you'll need to untar it. I did it everything using SSH since I don't have a vid card in my smoothwall though you could do it from the machine itself if you have a vid card, monitor & keyboard hooked up or you could just use SSH which is just as easy. If you choose to do it through SSH I would suggest using Putty from here on out. Most everyone I talked to said it was their favorite SSH program it just won't do the file transfer which you need to actually get the client on the box.
Once you login to the smoothwall as root you should be at the command prompt which will have you in /root where the seti client was saved to. Type ls and you should see the seti client you saved to the smoothwall. If I remember right you type: tar xvf seti (hit tab and it will autofill the rest of the file name for ya). This should extract the files. Type ls to verify that the files were extracted you should see the setiathome, xsetiathome and some readme files.
Now that the files are untarred you will want to setup a cron job to autostart seti as well as restart it if it dies. To do this type crontab -e which will open vi (which is a major pain to use to start with but isn't that bad once you get used to it). Type i then add the following:
0 * * * * cd /root; ./setiathome -proxy yoursetiQ's ip and port# -nice 19 > /dev/null 2> /dev/null
After you enter that hit the esc key. They type :wq and hit enter. This will save and exit your changes in vi. If you want to just quit and not save the changes type :Q!
Once you exit it should read installing new crontab or either no changes made to crontab depending on if you saved or not. Seti should start shortly. One of the mistakes I made was expecting seti to start immediatley so I kept going back and redoing things because I didn't think it had worked. So just give it a few minutes.
Once seti launches you will of course need to then enter your seti user info just like you do for the windows clients (the clients appearance is identical to the windows command line) and wait for it to download it's first wu.
After the first wu is downloaded and it's crunching away you will then need to re-edit the crontab and set seti up to run in the background. To exit seti hit ctrl c this will shut seti down. Then type crontab -e and edit the entry just like you did the first time so that it reads:
0 * * * * cd /root; ./setiathome -proxy yoursetiQ's ip and port# -nice 19 & > /dev/null 2> /dev/null
The only change that is being made is adding the & which will make seti run in the background. Once the entry has been edited save and exit just like before.
Reboot your smoothwall. Then login to your smoothie and type top and it will show you all of the programs running on the smoothie. It may take a few minutes for seti to start up after the reboot but you should see it running soon if not right away. 😀
If all went well seti should now be running on your smoothie. Seti uses right at 16 mb's of Ram on my smoothie and I think the machine uses a total of 43 mb's if I remember right.
This may seem like alot or a bit complicated but I tried to write everything out step by step since I know how confusing it is for the linux newb when someone tells ya to do something and you have absolutely no idea of where to even start. 🙂
First off you will need to download the seti client of course. The easiest way is to just download it to a windows machine then use a SSH File Transfer Program to move the client to the smoothwall. This will let you just drag and drop the seti client onto the smoothwall machine. You will need to use port 222 and login as root to connect to the smoothie. BTW one thing I ran into that puzzled most everyone was seti would only work right if i placed the client directly in /root. If I placed it in any other directory or even a subdirectory of root it wouldn't work right. 🙁
Now that you have the client actually on the smoothie you'll need to untar it. I did it everything using SSH since I don't have a vid card in my smoothwall though you could do it from the machine itself if you have a vid card, monitor & keyboard hooked up or you could just use SSH which is just as easy. If you choose to do it through SSH I would suggest using Putty from here on out. Most everyone I talked to said it was their favorite SSH program it just won't do the file transfer which you need to actually get the client on the box.
Once you login to the smoothwall as root you should be at the command prompt which will have you in /root where the seti client was saved to. Type ls and you should see the seti client you saved to the smoothwall. If I remember right you type: tar xvf seti (hit tab and it will autofill the rest of the file name for ya). This should extract the files. Type ls to verify that the files were extracted you should see the setiathome, xsetiathome and some readme files.
Now that the files are untarred you will want to setup a cron job to autostart seti as well as restart it if it dies. To do this type crontab -e which will open vi (which is a major pain to use to start with but isn't that bad once you get used to it). Type i then add the following:
0 * * * * cd /root; ./setiathome -proxy yoursetiQ's ip and port# -nice 19 > /dev/null 2> /dev/null
After you enter that hit the esc key. They type :wq and hit enter. This will save and exit your changes in vi. If you want to just quit and not save the changes type :Q!
Once you exit it should read installing new crontab or either no changes made to crontab depending on if you saved or not. Seti should start shortly. One of the mistakes I made was expecting seti to start immediatley so I kept going back and redoing things because I didn't think it had worked. So just give it a few minutes.
Once seti launches you will of course need to then enter your seti user info just like you do for the windows clients (the clients appearance is identical to the windows command line) and wait for it to download it's first wu.
After the first wu is downloaded and it's crunching away you will then need to re-edit the crontab and set seti up to run in the background. To exit seti hit ctrl c this will shut seti down. Then type crontab -e and edit the entry just like you did the first time so that it reads:
0 * * * * cd /root; ./setiathome -proxy yoursetiQ's ip and port# -nice 19 & > /dev/null 2> /dev/null
The only change that is being made is adding the & which will make seti run in the background. Once the entry has been edited save and exit just like before.
Reboot your smoothwall. Then login to your smoothie and type top and it will show you all of the programs running on the smoothie. It may take a few minutes for seti to start up after the reboot but you should see it running soon if not right away. 😀
If all went well seti should now be running on your smoothie. Seti uses right at 16 mb's of Ram on my smoothie and I think the machine uses a total of 43 mb's if I remember right.
hey blade - tried it and it wont let me edit crontab 🙁 says bad day-of-month and wont install the damn thing 🙁 any ideas ? btw wasnt sure which client to get - got i386 one - that good ? ta 🙂
Not sure about the error message, I'm still a linux newb myself.
As for the client it depends on your system if it's a 386 then you would need the 386 client.
Post what kind of system you've got and I can help ya find the right client if you don't already have the right one. Maybe one of the linux gurus can help ya on the error message your getting. 🙂
As for the client it depends on your system if it's a 386 then you would need the 386 client.
Post what kind of system you've got and I can help ya find the right client if you don't already have the right one. Maybe one of the linux gurus can help ya on the error message your getting. 🙂
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 20K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter