ssh tunneling client settings

Christoph Höger choeger at cs.tu-berlin.de
Wed Feb 24 18:28:04 UTC 2010


Am Mittwoch, den 24.02.2010, 19:23 +0100 schrieb Christoph Höger:
> Am Mittwoch, den 24.02.2010, 15:57 +0000 schrieb Andrew Haley:
> > On 02/24/2010 02:41 PM, Christoph Höger wrote:
> > > Hi guys,
> > > 
> > > are there any special client settings one needs to have for ssh
> > > tunneling?
> > > 
> > > I have the classical setup: machines A1 and A2 (both fedora 12) should
> > > access C which is only accessible from B1 (kerberos) or B2 (private key)
> > > 
> > > So on A1 I used to
> > > 
> > > ssh -L 10080:C:80 B1
> > > 
> > > or
> > > 
> > > ssh -L 10080:C:80 B2
> > > 
> > > Both work fine.
> > > 
> > > But on A2:
> > > 
> > > ssh -L 10080:C:80 B1/B2
> > > 
> > > logs me in to the machine but every connection attempt returns:
> > > 
> > > channel 3: open failed: administratively prohibited: open failed
> > > 
> > > Why? What kind of weird setting is this?
> > 
> > Anything in the logs?  Looks like a policy issue to me.
> 
> What logs do you mean? This is a client issue. Does the ssh client write
> to local log files?

Nvermind. Just found out that I had a typo in the Host URI.

Somehow I'd expected to get an unknown host message, though ...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20100224/1774ac2e/attachment.bin 


More information about the users mailing list