public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: ssh forwarding question
Date: Mon, 24 Oct 2005 22:41:19 -0400	[thread overview]
Message-ID: <000001c5d90d$94b68900$6701a8c0@QUARK> (raw)
In-Reply-To: <20051024205636.GA11242@lava-net.com>

Hi Igore,

Thanks for your reply.

Yes, this is OpenSSH, and it's not working because everytime I try to
actually access it via using whatever port I am trying to tunnel, I get the
following.

channel 1: open failed: connect failed: Connection refused 

Take care,
Sina

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Igor Gueths
Sent: Monday, October 24, 2005 4:57 PM
To: Speakup is a screen review system for Linux.
Subject: Re: ssh forwarding question

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi. By 'its not working', what errors/what makes you determine the fact that
it's not working? The configuration you have supplied should work; the only
thing I think may be throwing the whole thing off is your -f option...I'm
not sure how authentication is handled when that option is used since I've
never tried it. Also, I assume you are using the Openssh version of Ssh? The
above assumes yes. Hth.
On Mon, Oct 24, 2005 at 12:00:29PM -0400, Sina Bahram wrote:
> Hi all,
> 
> I believe we have a ton of ssh users on this list, and I figured that 
> I should turn to the practical experts, since I believe I'm following 
> the documentation, and it's not working.
> 
> Here is what I am trying to do:
> 
> I have a server that is running sshd. That server, for the sake of 
> argument, is somewhere on the web, and completely accessible remotely. 
> In other words, it has a public IP.
> 
> I have my laptop right here in my lap, and I want to be able to have 
> absolutely every single http request go over the ssh tunnel and come 
> back through again of course.
> 
> Is this possible to do with ssh?
> 
> The reason I ask is because, I won't know the IP that I want to 
> connect to ahead of time, so I can forward to that particular ip address.
> 
> I want to be able to do the following:
> 
> ssh -L 12345:localhost:12345 -N -f username@server
> 
> Then, I simply tell my browser to use a proxy or to use port 12345 
> always, rather than using some random high port.
> 
> Any thoughts, folks?
> 
> Take care,
> Sina
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iQIVAwUBQ11KhKe2pgKIdGq4AQr6AhAAjBkIDUtMA/8y+GIlhywHP0Wl9jz2hVmz
sjxZ5+G6YyIPXMmikYd73zTikbRLOskOyv+093QgMUtgNnIQ08pZmyCWeLK+mdAK
ehj8tF2GTL08DvevKxTjJdayIMzVfKqQI0C/dtFBujifImieYh06G8H8aD6HGNsN
y8r4EsE3SLQ/gNOgtnF2J87X1yNwsFkt503Xiwt1xPwUiGTzZJwkbNI79mCq5uuk
0/zzOAElrFlZuvLY687Tv1AVDq2lVL/4/f85ThaUAQH0jKno0YGySPLb4dt87+JY
GnXQWTfTrlWgE1lBDmlqohyHyy4gdorC3tBWu7xALypKQQhqT5vUFwkOZNObLSwa
i4OZspTo0NtZZzWxSNr1X6v26DfXbjP/TjjL/HaeZBKhX7vWEQbKMG1+brwfEFD+
XMUzqHHnIRhItO5FZcPJjrGyLrhfK+X1NOd+gkCpoTOB2dyVOt3ijJAQRe5PU2sd
65XZUOqNz7/j5yPcG89fYHEWfOPfohuA1YlsxZvvcLH2EkgyJ01MS4istTh2jkGm
rmIB2Fqk8C0BKpxLynp+bhJRDooacyUIrnfzhJ6IR+pkjnAW7J0znRWQOYwtoXUG
TnAutdY4Z0RaKCP89awbXLArAadFMaVDVoNTScakUu7qp6Q9XDfR/dBnuI02ReJ0
vO6HLDiS57Y=
=+3YO
-----END PGP SIGNATURE-----

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Sina Bahram
 ` Igor Gueths
   ` Sina Bahram [this message]
     ` Adam Myrow
       ` Gregory Nowak
         ` Adam Myrow
       ` Sina Bahram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001c5d90d$94b68900$6701a8c0@QUARK' \
    --to=sbahram@nc.rr.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).