From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: ssh tunnel (one more time)
Date: 09 Jul 1999 13:01:47 -0700 [thread overview]
Message-ID: <m1hfnd8udw.fsf@halfdome.holdit.com> (raw)
In-Reply-To: Michael Piotrowski's message of "Wed, 07 Jul 1999 14:50:58 +0200"
>>>>> "Michael" == Michael Piotrowski <m.piotrowski@springer.de> writes:
Michael> Hi,
Michael> I'm trying to use ssh with nntp-open-rlogin in the gnus-select-method
Michael> (instead of setting up a tunnel by starting ssh manually, as I'm
Michael> currently doing it):
Michael> (setq gnus-select-method
Michael> '(nntp "newsserver"
Michael> (nntp-open-connection-function nntp-open-rlogin)
Michael> (nntp-address "intermediate-host")
Michael> (nntp-rlogin-program "ssh")
Michael> (nntp-end-of-line "\n")
Michael> (nntp-rlogin-parameters
Michael> ("-x" "telnet" "newsserver" "nntp"))))
Michael> When I start gnus with this select method, it hangs while trying to
Michael> fetch the list of newsgroups from the server. However, when I start
Michael> gnus with gnus-no-server and then use `j' in the Group buffer
Michael> everything works as it should.
Michael> I know that the connection works. I know that the select method is
Michael> ok, otherwise gnus-group-jump-to-group wouldn't work, right? I seem
Michael> to remember that I once had it working with an older version of Gnus,
Michael> and it seems to work for other people, too. Any ideas what the
Michael> problem could be?
Something to always test would be going to a commandline and typing:
ssh newsserver -x date
and making sure that the date and *only* the date comes out.
And once that works:
ssh newsserver -x telnet newsserver nntp
should give you the NNTP connection message.
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
next prev parent reply other threads:[~1999-07-09 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-07 12:50 Michael Piotrowski
1999-07-09 17:45 ` Lars Magne Ingebrigtsen
1999-07-09 18:32 ` Andrew Markebo
1999-07-09 18:53 ` Lars Magne Ingebrigtsen
1999-07-09 20:02 ` Andrew Markebo
1999-07-09 20:01 ` Randal L. Schwartz [this message]
1999-07-13 6:48 ` Michael Piotrowski
1999-07-13 21:36 ` Andrew Markebo
1999-07-13 22:18 ` ssh tunnel (one more time) Solution? Andrew Markebo
1999-07-14 0:40 ` Stainless Steel Rat
1999-07-14 6:50 ` Michael Piotrowski
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=m1hfnd8udw.fsf@halfdome.holdit.com \
--to=merlyn@stonehenge.com \
--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).