Can't hit my home SETI QUEUE from internet - UPDATE: It works!

[conjur]

I have a Linksys four-port router and I have port forwarding turned on for port 5517 and it's pointed to my server that is running SETIQueue. However, I cannot connect to it from outside my internal network.

Well, SetiDriver will try to connect but comes back with some error code (unlike the 'cannot connect...will retry in one hour' message if I manually send to Berkeley but it's down).

Is there a trick to doing this?

The server on my internal network has a static, non-routable IP in the 192.168.x.x range and I can actually pull up the SetiQueue webpage on that box but just can't get/send WUs from/to it.

 

[Poof]

Are you using your ISP-assigned address (the one the linksys has, not the 192.x.x.x one) in the proxy field? Also, it could be there's no queue created for the external machines (queues are created, 1 per IP of incoming client). You might want to check the queue page in Setiqueue to see if it saw those external machines but just needed some WUs temporarily moved into the queue for them.

 

[conjur]

Hmmm...hadn't thought of that last point.

I may not be able to do this, then, as I would use my laptop via a dial-up connection (different IP everytime) to connect to send WUs.

Is there no way to have it look for a machine name?

Oh, and yeah, I *am* using the ISP-assigned address. It hasn't changed in the last two months and I can hit my webserver and hit the SetiQueue web page, too (two different servers).

 

[Confused]

You can dedicate a port to a client to enable SetiQ to identify the client if the IP address is always changing

Log in, and go to Clients and then Click to edit settings, and it's "Dedicate client port"

Then forward this port as well to the internal address.

Can you connect to the http bit of SetiQ from outside? If you want me to test PM me your address and details, and i'll test

ConfusedBW

 

[steell]

Is your SetiQ server subnet mask set to 0.0.0.0 ? That's what I had to do to allow outside access.

 

[conjur]

Confused,

I'll try the dedicated port thing. I do have one question, though. My end desire is to use my laptop to get three machines at work to connect to my home SetiQueue. I map drives from my laptop to the three PCs at work and then dial-up to my ISP. I can then run SetiDriver from the mapped drives and send/get WUs but I'd like that send/get to go to my home SetiQueue instead of directly to Berkeley. That way I can track all of my WUs better and lower the cache sizes on these PCs, too, and just make the overall reliability better.

That make sense?

Steell, the subnet mask is 255.255.255.0 all around on all of my boxes. 0.0.0.0, eh? Hmm...I'll try the dedicated port first.

UPDATE:
I set port 5518 for the dedicated port. I actually noticed that the WUs coming from my laptop show the gateway address so I should be cool for my situation stated above...I'll test it out tomorrow.

 

[steell]

This problem drove me crazy, until I found the answer was to set the SetiQ subnet mask to 0.0.0.0
Not in windows networking, just in SetiQ setup. I have a number of computers set up here with the 192.168.xx.xx
subnet 255.255.255.0 also, and they could all connect, but no one outside could connect, until I found the info (somewhere)
about changing SetiQ subnet.

 

[Bigwoofer]

YEP! Subnet mask 0.0.0.0

It's a filter, 0.0.0.0 allows all to connect to your server

 

[conjur]

Ah...not Windows networking...won't let me set it to 0.0.0.0 anyway.

But, where in the SetiQueue do I change the subnet mask? It doesn't show as an editable field when I login as admin and go to Settings.

 

[Poof]

I may be wrong but you may have to do that right at the Setiqueue machine itself (not via the web interface).

 

[conjur]

OH! I get ya!

From the SetiQueue app itself...gotcha...

/me kicks self in arse

Thanks!

I'll try and walk the Mrs. thru that when she's back from running errands...that should be fun

 

[Poof]

I'll try and walk the Mrs. thru that when she's back from running errands...that should be fun

LOL. She'll probably think that you've lost your mind!

 

[mgpaulus]

One thing I had to do on my Netgear. Not sure if it applies to LinkSys. I had to add 2 different items to my router. I needed to create a filter set that says I can pass the 5517 port packets, and then I had to create the routing rule, that would tell which internal machine to send the packets to.

Just my $0.02.

 

[conjur]

LOL @ Poof!

And, mgpaulus, the Linksys allows me to specify for a particular port range (in this case, 5518 to 5518) which IP address on my internal network gets those packets. So, I couldn't route to multiple machines for that port which is fine with me for a home network.

 

[mgpaulus]

I also only have one machine serving 5517 traffic. All I wanted to mention was that my netgear router needed 2 different configuration changes, and the second wasn't obvious. The filter set basically told the router that you now need to pay attention to 5517 traffic, and then the routing rules tells the router what to do with the traffic (forward it to setiq server, drop the packets, check the next rule, ignore certain subnets, etc, etc). The filter set wasn't an obvious thing, but if you didn't do it, the router would never look at the 5517 traffic.

 

[conjur]

I guess Linksys tries to make it a little simpler?

Anyway...it's working!

I walked the Mrs. through changing the subnet mask to 0.0.0.0 and I just sent/received a WU from laptop dialed into my ISP. Woo hoo!!

Of course, I'll now have to schedule some marriage counseling............