OK, this is weird. When I "ssh -X -A -p 8022 zooty8022" to connect to my system at home through a forwarded connection to my ssh server that is on port 8022 here on my system at work, running any X app generates the weird connection refused message:
zooty> strace -o xlogo.trace xlogo connect : Connection refused
Yet, the xlogo window does indeed show up on my screen at work, and more mysterious, no "write()" call in the strace of xlogo writes that message, so where the devil is it coming from? (And xlogo doesn't do any kind of a fork, so it isn't a child writing it either).
I've got fedora 14 x86_64 on my system at work and at home.
On 09/11/2010 14:17, Tom Horsley wrote:
I've got fedora 14 x86_64 on my system at work and at home.
I was just about to post about my ssh forwarding problems, but they could be related so adding my info to this thread.
Since installing F14 (after using F12) I've been unable to do any port forwarding when ssh'ing into that machine. I'd normally forward a couple of ports (VNC to localhost for x11vnc, proxy to another box on my home network) but none have worked since the update. Explicitly setting AllowTcpForwarding to Yes in /etc/ssh/sshd_config makes no difference.
When connecting to the forwarded port I get this message: channel 3: open failed: administratively prohibited: open failed
-Phil
On Tue, 09 Nov 2010 14:30:48 +0000 Philip Heron wrote:
I was just about to post about my ssh forwarding problems, but they could be related so adding my info to this thread.
I don't know if this is really the same. All the connection refused messages I've seen don't actually prevent anything from working, they just clutter up the terminal. I submitted this bug:
On Tue, 9 Nov 2010 09:48:19 -0500 Tom Horsley wrote:
I submitted this bug:
Which I now see is a duplicate of an already closed bug fixed in an update I haven't yet installed (I wish they'd leave bugs open for a few days after fixing them so you could search open bugs and have a chance of finding them :-).
On 11/09/2010 09:30 AM, Philip Heron wrote:
When connecting to the forwarded port I get this message: channel 3: open failed: administratively prohibited: open failed
I see this on f13 - it seems to happen when I use tunneled socks5 proxy via
ssh -D socksport ...
Some of the proxy'ed things (browser) fail and I see the above errors just as you do in the terminal where I started the ssh.
Killing and restarting browser gets things going again ... tho for reasons I cannot fathom when this happens some things work and some dont in same browser (I think sites with flash may be effected .. more/only).
gene/
On 09/11/10 17:35, Genes MailLists wrote:
On 11/09/2010 09:30 AM, Philip Heron wrote:
When connecting to the forwarded port I get this message: channel 3: open failed: administratively prohibited: open failed
I see this on f13 - it seems to happen when I use tunneled socks5 proxy via
ssh -D socksport ...Some of the proxy'ed things (browser) fail and I see the above errors just as you do in the terminal where I started the ssh.
Killing and restarting browser gets things going again ... tho for reasons I cannot fathom when this happens some things work and some dont in same browser (I think sites with flash may be effected .. more/only).
It turned out to be an selinux problem in my case, I had to run this:
# setsebool -P sshd_forward_ports 1
Now all is working.
-Phil
On 11/09/2010 12:39 PM, Philip Heron wrote:
On 09/11/10 17:35, Genes MailLists wrote:
It turned out to be an selinux problem in my case, I had to run this:
# setsebool -P sshd_forward_ports 1
Now all is working.
Good news!
Sounds diff than my case, which works fine and never has any AVCs. It just stops at some point with the errors ... and google shows others have similar problems going back some period of time.
-
Genes MailLists -
Philip Heron -
Tom Horsley