I'm using ssh-1.2.26 on linux 2.0.36 connecting to linux boxen running
different kernels and ssh-1.2.26.
I'm connecting through a firewall and setting up some remote and
local forwards. I've recently changed firewalls and now my LocalForward
settings won't work (the remote forwards work ok). It used to work just
fine under the following setup:
Host nyar4
Hostname myhost.domain.com
ProxyCommand ~/bin/sshproxy.pl bastion 80 %h %p
LocalForward 6667 irc.cerf.net:6667
The sshproxy.pl is the one found in many places around the net - it just
tunnels the connections through a fwtk http-gw in this case. When the
connection was established, netstat -a would show the following info:
tcp 0 0 *:6667 *:* LISTEN
The new firewall setup is a SOCKS4 server and I'm trying the following
config (with the proper environment variables):
Host nyar4
Hostname myhost.domain.com
LocalForward 6667 irc.cerf.net:6667
After a period of about 3 minutes with the following output from "-v":
.
.
.
localhost: Connections to local port 6667 forwarded to remote
address irc.cerf.net:6667
Local: listen: Bad file descriptor
During the delay, another netstat -a shows the following info:
tcp 0 2 localhost:6667 proxyhost:1080 SYN_SENT
I've tried using different hosts, different ports (both local and remote)
and I get the same results. Am I missing something obvious here? It looks
like the LocalForward is trying to setup a seperate channel through the
firewall instead of through an established ssh connection.
--
| The nexus between nested levels of symbolic reality
Mike Loseke | and the field of human subjectivity, the extensible
[EMAIL PROTECTED] | domain of human consciousness, haunts me.
