Gnus development mailing list
 help / color / mirror / Atom feed
From: "Herbert J. Skuhra" <hskuhra@eumx.net>
To: ding@gnus.org
Subject: Re: Coaching to ssh port forward an NNTP connection
Date: Tue, 27 Aug 2013 19:13:17 +0200	[thread overview]
Message-ID: <87r4dfxdjm.wl%hskuhra@eumx.net> (raw)
In-Reply-To: <877gf7m5q8.fsf@newsguy.com>

On Tue, 27 Aug 2013 12:57:35 -0400
Harry Putnam wrote:

> Abramov Aleksey <levenson@mmer.org> writes:
> 
> 
> [...]
> 
> >> Trouble is I cannot remember the first thing about how it was done or
> >> find any notes I may have kept... this has been 10 or more yrs ago.
> >>
> >> Can anyone give an outline of how something like that might be done?
> >>
> >
> > To create an ssh tunnel is pretty easy. 
> >
> > # ssh -ANf -L5119:news.gmane.org:119 router.example.com
> >
> > # telnet localhost 5119
> > Trying 127.0.0.1...
> > Connected to localhost.
> > Escape character is '^]'.
> > 200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
> > Connection closed by foreign host.
> >
> > There could be only one problem, TCP forwarding shouldn't be disabled in
> > sshd which you are connecting to. 
> >
> > In my case the interesting thing is that, there is a http proxy before
> > router. =) 
> 
> In the command line you show above, what role does router.example.com
> play? Are -L and router.example.com the same host 

% man ssh

Have you tried?

> Do any of the participating hosts require root to do that?

Yes, e.g: if you try to listen to a privileged port.

-- 
Herbert



  reply	other threads:[~2013-08-27 17:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 19:44 Harry Putnam
2013-08-27  7:23 ` Abramov Aleksey
2013-08-27 16:57   ` Harry Putnam
2013-08-27 17:13     ` Herbert J. Skuhra [this message]
2013-08-27 22:29       ` Harry Putnam
2013-08-27 23:03         ` Adam Sjøgren
2013-09-17 17:00           ` Harry Putnam

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=87r4dfxdjm.wl%hskuhra@eumx.net \
    --to=hskuhra@eumx.net \
    --cc=ding@gnus.org \
    /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 NNTP newsgroup(s).