Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: altamaiz on January 27, 2006, 07:06:06 AM

Title: Non standard port forwarding
Post by: altamaiz on January 27, 2006, 07:06:06 AM

I have a server running behind my SME server listening for SSH requests on a non standard port, let's say 8050.
The port forwarding feature in the server-manager is not forwarding outside requests as I would like.
I don't really know why this is, I imagine it's because SSH is not transmitting the requests on TCP or UDP.
Can anyone advise me how to forward this?

Also port forwarding related;
I have a phone instance listening on a non-standard port, and likewise I'm not able to forward the requests. but this I know is listening for TCP requests. I would guess this is not forwarding as I would like because rather than listening for http://domain:9000/ it's expecting http://domain:9000/something.

Can anyone confirm this?

Thanks for your help

Title: Non standard port forwarding
Post by: tog on February 05, 2006, 10:04:14 PM

You have confirmed that the ssh server can be accessed on the non-standard port?  You've connected from local computers?

Do you have other port-forwarding rules that are working correctly?

Title: Non standard port forwarding
Post by: tog on February 05, 2006, 10:07:33 PM

As for the second issue, if port 9000 is being successfully forwarded, the "/something" in the url of the http request should not be an issue.

Quote

http://domain:9000/something.

Perhaps the forwarding rules are not set up correctly or the fw service needs a reload?

Title: Re: Non standard port forwarding
Post by: CharlieBrady on February 05, 2006, 11:19:18 PM

Quote from: "altamaiz"

Also port forwarding related;
I have a phone instance listening on a non-standard port, and likewise I'm not able to forward the requests. but this I know is listening for TCP requests. I would guess this is not forwarding as I would like because rather than listening for http://domain:9000/ it's expecting http://domain:9000/something.

Port forwarding doesn't do anything to the content of requests, it just passes them on perfectly intact. If the device expects an http request ending in /something, then you need to provide an http request ending in /something.

Quote

Can anyone confirm this?

You want someone to confirm what your unnamed "phone instance" expects in requests? I don't know how anyone could do that.

Title: Non standard port forwarding
Post by: altamaiz on February 13, 2006, 07:21:28 PM

Please excuse my miskey- I meant "plone instance", not "phone instance".
 :-D

Thanks for the responses. Yes I can access my server with the nonstandard ssh port locally, and I can access SME via ssh remotely. I just can't access the nonstandard port remotely.

Has anyone else used port forwarding to redirect ssh requests? I guess I'm still not sure if this is even possible?

By "Can anyone confirm this?" I simply meant "is this assumption correct?". I'm sorry this wasn't clear.
I wasn't asking about the Plone instance, but rather my assumptions concerning how port forwarding would work. And I see now that my assumptions were not correct, thanks for the response.

Title: Non standard port forwarding
Post by: CharlieBrady on February 13, 2006, 07:39:03 PM

Quote from: "altamaiz"

Has anyone else used port forwarding to redirect ssh requests?

Yes.

Title: Non standard port forwarding
Post by: altamaiz on February 13, 2006, 07:57:47 PM

thanks CharlieBrady