Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
09-28-2005, 02:37 PM
|
#1
|
Member
Registered: Sep 2005
Location: California
Distribution: Slackware & Debian
Posts: 264
Rep:
|
SSH Port Forwarding
Hi,
I am connecting to my home computer from a remote location via ssh. I am forwarding port 8080 dynamically (for the internet, using socks.)
My question is how do i forward outbound ports from the remote computer running the SSH client, meant to go to the internet, to the server at home, which should then forward them to the internet?
Do i have to use a proxy on my home computer or is there an other way of doing this task without needing an other proxy?
thanks
wwnexc
|
|
|
09-28-2005, 03:50 PM
|
#2
|
Senior Member
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380
Rep:
|
Conventionally ssh is on port 22 so you would require port forwarding of port 22 to the box on the lan. Make sure you have strong paswords and it is normally recommended that you disallow root access and login as a user and then su into a root shell.
|
|
|
09-28-2005, 04:39 PM
|
#3
|
Member
Registered: May 2004
Location: Montreal,QC,Canada
Distribution: Fedora Core 7
Posts: 210
Rep:
|
Well I am not sure I understand this correctly... Let me re phrase this :-)
you have a remote pc (let's call it remotePC) that connects to your home PC (now on called homePC) via ssh.
You want to know how you could browse Internet on remotePC using your homePC internet access...
Well I dont think you can not do that via port forwarding. It has to be at the IP level and involve routes.
Good luck!
|
|
|
09-28-2005, 09:19 PM
|
#4
|
Member
Registered: Sep 2005
Location: California
Distribution: Slackware & Debian
Posts: 264
Original Poster
Rep:
|
well, using dynamic port forwarding, virtual 8080, it works.
Yes, I am trying to connect from remotePC to my homePC to access the internet, which works, but i cannot get other ports to be forwarded.
Should i install some sort of a port forwarding application on the server or proxy?
|
|
|
09-29-2005, 02:26 AM
|
#5
|
Senior Member
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380
Rep:
|
Re: SSH Port Forwarding
Quote:
Originally posted by wwnexc
My question is how do i forward outbound ports from the remote computer running the SSH client, meant to go to the internet, to the server at home, which should then forward them to the internet?
Do i have to use a proxy on my home computer or is there an other way of doing this task without needing an other proxy?
|
The remote box should not require any forwarding if you have internet access from it. In order to access your home box from the internet you need to know it's ip address. As this is dynamic this can be difficult. You could use www.dyndns.org to setup a permanent address. Your home box would update their server with the ip address as it changes. You should be able to access the box then by either ip address or name resolution.
The alternate method would be to setup a dial-in facility on the home box and this would then route internet requests through a specified gateway. ssh shouldn't come into the scenario as this really a method of communicating with a box securely.
|
|
|
All times are GMT -5. The time now is 10:24 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|