VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-28 Thread aaaaa
Dear,

I met the same problem and manage to solve it (thanks for your help) by replacing 
Connection/SSH/Tunnels/Destination/localhost:59XX by 
Connection/SSH/Tunnels/Destination/127.0.0.1:59XX.

regards,

Gilles
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-27 Thread Gilles JOLITON
Dear,

I met the same problem and manage to solve it (thanks for your help) by replacing 
Connection/SSH/Tunnels/Destination/localhost:59XX by 
Connection/SSH/Tunnels/Destination/127.0.0.1:59XX.

regards,

Gilles
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-05 Thread Jan Grant
On Thu, 4 Sep 2003, Scott I. Remick wrote:

 Figured I'd start with my FreeBSD friends first before bugging the VNC
 community.

 I used to have VNC tunneling over ssh just fine, but then had to redo my
 system drive. I used FreeBSD 5.1 before and still do now, however it's not
 working. I'm using the same PuTTY system so the config is the same as from
 before when it worked. So something is different at the FreeBSD end.

 The PuTTY log shows:

 2003-09-04 11:26:28   Opening forwarded connection to localhost:5901
 2003-09-04 11:26:28   Forwarded connection refused by server

 And /var/log/messages shows:

 Sep  4 11:26:28 scott sshd[37213]: error: getsockopt TCP_NODELAY:
 Connection reset by peer

 Maybe I'm just dumb and missed something I configured before, but I can't
 figure out what. Can someone offer insight? Thanks

Loks like the VNC srever isn't listening at that location. Is it
running?

-- 
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/
...You're visualising the _duck_ taped over my _mouth_..?

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-05 Thread Scott I. Remick
On Fri, 5 Sep 2003 11:58:16 +0100 (BST), Jan Grant wrote:

 Loks like the VNC srever isn't listening at that location. Is it
 running?

Yep:

-bash-2.05b$ ps
  PID  TT  STAT  TIME COMMAND
60273  p0- S  0:00.49 Xvnc :1 -desktop X -httpd
/usr/local/share/vnc/classes
60277  p0- S  0:00.20 /usr/X11R6/bin/blackbox
61709  p0  Is 0:00.03 bash
80005  p1  Is 0:00.02 bash
96020  p2  Ss 0:00.01 -bash (bash)
96025  p2  R+ 0:00.00 ps
  490  v0  I  0:00.01 -bash (bash)
61622  v0  I+ 0:00.01 /bin/sh /usr/X11R6/bin/startx
61634  v0  I+ 0:00.01 xinit /home/scott/.xinitrc -- -nolisten tcp
61640  v0  I  0:00.00 sh /home/scott/.xinitrc
61641  v0  I  0:01.31 /usr/X11R6/bin/gnome-session
61644  v0  S  0:01.62 /usr/X11R6/libexec/gconfd-2 13

Blackbox is the wm being started from ~/.vnc/xstartup since I normally use
gnome. And I'm forwarding the ports in PuTTY:

2003-09-05 09:02:56 Local port 7001 forwarding to localhost:5901
2003-09-05 09:02:56 Local port 7002 forwarding to localhost:5902
2003-09-05 09:02:56 Local port 7003 forwarding to localhost:5903

(the same port-forwarding that worked for me before).

On the Windows system, I then VNC to localhost:7001 which triggers that
error on the VNC box.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-05 Thread Jan Grant
On Fri, 5 Sep 2003, Scott I. Remick wrote:

 On Fri, 5 Sep 2003 11:58:16 +0100 (BST), Jan Grant wrote:

  Loks like the VNC srever isn't listening at that location. Is it
  running?

 Yep:

 -bash-2.05b$ ps
   PID  TT  STAT  TIME COMMAND
 60273  p0- S  0:00.49 Xvnc :1 -desktop X -httpd
 /usr/local/share/vnc/classes
 60277  p0- S  0:00.20 /usr/X11R6/bin/blackbox
 61709  p0  Is 0:00.03 bash
 80005  p1  Is 0:00.02 bash
 96020  p2  Ss 0:00.01 -bash (bash)
 96025  p2  R+ 0:00.00 ps
   490  v0  I  0:00.01 -bash (bash)
 61622  v0  I+ 0:00.01 /bin/sh /usr/X11R6/bin/startx
 61634  v0  I+ 0:00.01 xinit /home/scott/.xinitrc -- -nolisten tcp
 61640  v0  I  0:00.00 sh /home/scott/.xinitrc
 61641  v0  I  0:01.31 /usr/X11R6/bin/gnome-session
 61644  v0  S  0:01.62 /usr/X11R6/libexec/gconfd-2 13

 Blackbox is the wm being started from ~/.vnc/xstartup since I normally use
 gnome. And I'm forwarding the ports in PuTTY:

 2003-09-05 09:02:56   Local port 7001 forwarding to localhost:5901
 2003-09-05 09:02:56   Local port 7002 forwarding to localhost:5902
 2003-09-05 09:02:56   Local port 7003 forwarding to localhost:5903

 (the same port-forwarding that worked for me before).

 On the Windows system, I then VNC to localhost:7001 which triggers that
 error on the VNC box.

I'd still recommend double-checking with sockstat on the BSD box, (and
netstat -an on the windows box, but I don't think that's the problem).

-- 
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/
Random act of violence against bread: whole pint.
  -- extract from the Hawk the Slayer drinking game

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-05 Thread Scott I. Remick
On Fri, 5 Sep 2003 14:51:08 +0100 (BST), Jan Grant wrote:

 I'd still recommend double-checking with sockstat on the BSD box, (and
 netstat -an on the windows box, but I don't think that's the problem).

Sure... you help me, I help you help me. :)

-bash-2.05b$ sockstat -l | grep vnc
scottXvnc   60273 0  tcp4   *:6001*:*
scottXvnc   60273 1  stream /tmp/.X11-unix/X1
scottXvnc   60273 3  tcp4   *:5901*:*
scottXvnc   60273 4  tcp4   *:5801*:*

So it IS listening on 5901. Also:

su-2.05b# strobe -b 5900 -e 5910 localhost
strobe 1.05 (c) 1995-1999 Julian Assange [EMAIL PROTECTED].
localhost  5901 unassigned   unknown
- RFB 003.003\n

Amongst other things, netstat -ab reports on the Windows machine:

TCP127.0.0.1:7001 0.0.0.0:0  LISTENING
TCP127.0.0.1:7002 0.0.0.0:0  LISTENING
TCP127.0.0.1:7003 0.0.0.0:0  LISTENING

...which makes sense, since I'm getting through enough to trigger the error
on the FreeBSD system.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-05 Thread Jan Grant
On Fri, 5 Sep 2003, Scott I. Remick wrote:

 Sure... you help me, I help you help me. :)

 -bash-2.05b$ sockstat -l | grep vnc
 scottXvnc   60273 0  tcp4   *:6001*:*
 scottXvnc   60273 1  stream /tmp/.X11-unix/X1
 scottXvnc   60273 3  tcp4   *:5901*:*
 scottXvnc   60273 4  tcp4   *:5801*:*

 So it IS listening on 5901. Also:

 su-2.05b# strobe -b 5900 -e 5910 localhost
 strobe 1.05 (c) 1995-1999 Julian Assange [EMAIL PROTECTED].
 localhost  5901 unassigned   unknown
 - RFB 003.003\n

OK, two other things (increasingly bizarre) occur to me; after that, I'm
stumped:

1. tcp wrappers or similar on your vnc?
2. The localhost is (as I recall) resolved on the putty side and the
   IP to connect to sent to the sshd. Does localhost resolve to anything
   other than 127.0.0.1 on your windows machine?

-- 
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/
The Java disclaimer: values of 'anywhere' may vary between regions.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-05 Thread Scott I. Remick
On Fri, 5 Sep 2003 16:03:21 +0100 (BST), Jan Grant wrote:

 OK, two other things (increasingly bizarre) occur to me; after that, I'm
 stumped:
 
 1. tcp wrappers or similar on your vnc?

On the FreeBSD system? No. Well, not that I know of. I have not configured
to use tcp wrappers w/ VNC so if it's happening, it's doing so without me
having asked it to. 

 2. The localhost is (as I recall) resolved on the putty side and the
IP to connect to sent to the sshd. Does localhost resolve to anything
other than 127.0.0.1 on your windows machine?

Nope:

C:\ping localhost

Pinging SCOTT [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time10ms TTL=128
Reply from 127.0.0.1: bytes=32 time10ms TTL=128
Reply from 127.0.0.1: bytes=32 time10ms TTL=128

Of course, now that I think about it, plugging another workstation in at
home and seeing if I can VNC to the FreeBSD system on the local LAN would
be rather enlightening. Why haven't I done this already? Duh. Will have to
try it later... 

Incidentally, I'm not the first to have this problem:

http://groups.google.com/groups?selm=20030129114855.D5796-10_geri.cc.fe
r.hr%40ns.sol.netoe=UTF-8output=gplain

I tried emailing him but haven't heard back.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-04 Thread Scott I. Remick
Figured I'd start with my FreeBSD friends first before bugging the VNC
community.

I used to have VNC tunneling over ssh just fine, but then had to redo my
system drive. I used FreeBSD 5.1 before and still do now, however it's not
working. I'm using the same PuTTY system so the config is the same as from
before when it worked. So something is different at the FreeBSD end. 

The PuTTY log shows:

2003-09-04 11:26:28 Opening forwarded connection to localhost:5901
2003-09-04 11:26:28 Forwarded connection refused by server

And /var/log/messages shows:

Sep  4 11:26:28 scott sshd[37213]: error: getsockopt TCP_NODELAY:
Connection reset by peer

Maybe I'm just dumb and missed something I configured before, but I can't
figure out what. Can someone offer insight? Thanks

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-04 Thread Andrew L. Gould
On Thursday 04 September 2003 11:28 am, Scott I. Remick wrote:
 Figured I'd start with my FreeBSD friends first before bugging the VNC
 community.

 I used to have VNC tunneling over ssh just fine, but then had to redo my
 system drive. I used FreeBSD 5.1 before and still do now, however it's not
 working. I'm using the same PuTTY system so the config is the same as from
 before when it worked. So something is different at the FreeBSD end.

 The PuTTY log shows:

 2003-09-04 11:26:28   Opening forwarded connection to localhost:5901
 2003-09-04 11:26:28   Forwarded connection refused by server

 And /var/log/messages shows:

 Sep  4 11:26:28 scott sshd[37213]: error: getsockopt TCP_NODELAY:
 Connection reset by peer

 Maybe I'm just dumb and missed something I configured before, but I can't
 figure out what. Can someone offer insight? Thanks


Is PuTTY expecting the server's key from the previous installation?

Just a guess.

Andrew Gould

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-04 Thread Scott I. Remick
On Thu, 4 Sep 2003 11:31:56 -0500, Andrew L. Gould wrote:

 Is PuTTY expecting the server's key from the previous installation?
 
 Just a guess.

Nope, that happens earlier in the process. I can ssh to my PC just fine,
and already dealt with the message about the server's key having changed.
Shouldn't be any special new key for tunnelling a protocol over an
already-established ssh session (right?).

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error

2003-09-04 Thread Ronny Hippler
On Thu, 4 Sep 2003 12:48:40 -0400, Scott I. Remick wrote:

 Is PuTTY expecting the server's key from the previous installation?
Nope, that happens earlier in the process. I can ssh to my PC just fine,
and already dealt with the message about the server's key having changed.
Shouldn't be any special new key for tunnelling a protocol over an
already-established ssh session (right?).

Well I don't have an answer but I am doing this with no special setup on the 
bsd side. it just works. Only diff is that I am running 4.8


--


Life Is A Series Of Rude Awakenings



Ronny Hippler || Spartanburg SC
http://www.vr5.dyndns.org:8008/ || ftp://ftp.vr5.dyndns.org:2112/
For PGP key email with PGPKey in the subject


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]