How is my vnc getting started at boot
Hi! I am unable to figure how vncserver is being launched during local package initialization of my FreBSD 8.2 Release boot. Can anyone help or point me in right direction to figure where my vncserver is being launched from? I need to change my vnc root window size. Thanks, Akshay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How is my vnc getting started at boot
2011-08-30 04:47, akshay sreeramoju skrev: Hi! I am unable to figure how vncserver is being launched during local package initialization of my FreBSD 8.2 Release boot. Can anyone help or point me in right direction to figure where my vncserver is being launched from? I need to change my vnc root window size. Thanks, Akshay Check /usr/local/etc/rc.d/* where 3:d party programs normally is started from. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How is my vnc getting started at boot
Thank you Bernt. You are right. I found vncserver.sh there. Regards, Akshay On Mon, Aug 29, 2011 at 8:01 PM, Bernt Hansson b...@bananmonarki.se wrote: 2011-08-30 04:47, akshay sreeramoju skrev: Hi! I am unable to figure how vncserver is being launched during local package initialization of my FreBSD 8.2 Release boot. Can anyone help or point me in right direction to figure where my vncserver is being launched from? I need to change my vnc root window size. Thanks, Akshay Check /usr/local/etc/rc.d/* where 3:d party programs normally is started from. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
net/vnc fails to build vnc.so on 8.1 Prerelease amd64
Hi, I want to be able to run a vnc server to share my real X-session. I use kdm. I've been trying to build vnc with vnc.so module. However, it fails to build this file. Any idea on how to resolve this? Outputs: FreeBSD mario 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #2: Tue Jun 1 10:09:28 CEST 2010 st...@mario:/usr/obj/usr/src/sys/mario amd64 c++ -o vnc.so -Bshareable -R /usr/local/lib vncExtInit.o vncHooks.o xf86vncModule.o XserverDesktop.o ../../../../../../common/rfb/librfb.a ../../../../../../common/Xregion/libXregion.a ../../../../../../common/network/libnetwork.a ../../../../../../common/rdr/librdr.a /usr/lib/crt1.o(.text+0x88): In function `_start': : undefined reference to `main' vncExtInit.o(.text+0x33d): In function `ProcVncExtGetClientCutText(_Client*)': : undefined reference to `WriteToClient' vncExtInit.o(.text+0x357): In function `ProcVncExtGetClientCutText(_Client*)': : undefined reference to `WriteToClient' vncExtInit.o(.text+0x469): In function `vncQueryConnect(XserverDesktop*, void*)': : undefined reference to `WriteToClient' vncExtInit.o(.text+0x4ab): In function `vncQueryConnect(XserverDesktop*, void*)': : undefined reference to `TimerSet' vncExtInit.o(.text+0x4d8): In function `vncQueryConnect(XserverDesktop*, void*)': : undefined reference to `TimerCancel' vncExtInit.o(.text+0x575): In function `ProcVncExtApproveConnect(_Client*)': : undefined reference to `screenInfo' vncExtInit.o(.text+0x5b1): In function `ProcVncExtApproveConnect(_Client*)': : undefined reference to `screenInfo' vncExtInit.o(.text+0x6a6): In function `vncClientCutText(char const*, int)': : undefined reference to `GetTimeInMillis' vncExtInit.o(.text+0x720): In function `vncClientCutText(char const*, int)': : undefined reference to `WriteToClient' signature.asc Description: OpenPGP digital signature
Re: Can display be shared through VNC using xorg vnc module?
In the last episode (Dec 16), Yuri said: I read here: http://en.gentoo-wiki.com/wiki/X11VNC that in Gentoo xorg can load vnc module and it will make it also a vnc server. But I can't find any relevant ports in FreeBSD port tree. I only found net/x11vnc which is a standalone program that connects to xorg server and serves as it's vnc server. Does this meant that vnc module isn't supported on FreeBSD? Or it was replaced by x11vnc? Try the net/vnc port instead. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Why VNC server crashes when client disconnects?
I used vnc while ago without this problem. Now I see that when client gracefully exits (window close) server crashes with exception: terminate called after throwing an instance of 'rdr::EndOfStream' knotify: Fatal IO error: client killed kwin: Fatal IO error: client killed ksmserver: Fatal IO error: client killed kaccess: Fatal IO error: client killed Is this something temporary, or somethig's wrong with my system? vnc-4.1.3_2 on vnc-4.1.3_2 Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can display be shared through VNC using xorg vnc module?
I read here: http://en.gentoo-wiki.com/wiki/X11VNC that in Gentoo xorg can load vnc module and it will make it also a vnc server. But I can't find any relevant ports in FreeBSD port tree. I only found net/x11vnc which is a standalone program that connects to xorg server and serves as it's vnc server. Does this meant that vnc module isn't supported on FreeBSD? Or it was replaced by x11vnc? Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
BREAK_TO_DEBUGGER in VNC-client
Hi, folks. Is there any VNC-client able to throw ctrl-alt-esc event in order to break to debugger? I need this feature to control a guest FreeBSD which console is exported via VNC. Thanks. -- wbr, pluknet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Share X instance with VNC?
Is it possible to access a normal (connected to vga) Xorg instance from VNC as well? I'd like to remotely access my X desktop at home without having to run multiple sessions. Thanks, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VNC server embedded into Xorg server
Laszlo Nagy wrote: Hi All, There was a port called net/vnc that contained a vnc.so file. That file could be loaded into the Xorg server and then I was able to monitor the X desktop with VNC. Now I'm using gnome, and gnome2-fifth-toe installs tightvnc. It conflicts with net/vnc. So I cannot install net/vnc. What other options I have to run an X server? The only extra wish is that the X server must be able to start automatically, e.g. without logging into gnome. I need this because the X server will be located at a distant location and I have to be able to use it after a system restart. I use x11vnc (net/x11vnc), as it doesn't require loading anything into the X server itself--it's a standard X client. From there, it wouldn't be difficult to hack together something that starts x11vnc when the X server starts up. XDM and GDM tend to store their X authority files in easy-to-find locations. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC server embedded into Xorg server
Hi, Sorry for jumping in the middle of the thread. There was a port called net/vnc that contained a vnc.so file. That file could be loaded into the Xorg server and then I was able to monitor the X desktop with VNC. Now I'm using gnome, and gnome2-fifth-toe installs tightvnc. It conflicts with net/vnc. So I cannot install net/vnc. What other options I have to run an X server? I would: - deinstall net/vnc - install gnome and let it install tinyvnc - manually deinstall tinyvnc - install net/vnc The only extra wish is that the X server must be able to start automatically, e.g. without logging into gnome. I need this because the X server will be located at a distant location and I have to be able to use it after a system restart. Especially with gnome, the X server starts before you do any authentication, when gnome present the loggin window, X has already started. To do X over vnc remotely, you need quite some amount of bandwidth. Are you sure you need a graphical access? X protocol is designed natively to run over the network, so you may not need vnc. With X you can have an application running on your remote computer, with the display coming to your desktop machine (if your desktop machine is some Windows thing, there are good X emulators for Windows). If you really want to keep your setting, there should exist a gnome startup script that you can hack to run vnc somewhere between the line starting X and the line starting gnome authentication. Best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC server embedded into Xorg server
Hi All, There was a port called net/vnc that contained a vnc.so file. That file could be loaded into the Xorg server and then I was able to monitor the X desktop with VNC. Now I'm using gnome, and gnome2-fifth-toe installs tightvnc. It conflicts with net/vnc. So I cannot install net/vnc. What other options I have to run an X server? The only extra wish is that the X server must be able to start automatically, e.g. without logging into gnome. I need this because the X server will be located at a distant location and I have to be able to use it after a system restart. Thanks, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Custmoize VNC
On Mon, Jul 28, 2008 at 10:08 PM, Greg Larkin [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Paul Natola wrote: | I know there are two apps (open source) that will allow you to customize vnc | but I just cant remember, in essence I want the remote users (outside the | lan) to be able to download the file click run and it will automatically, | upon launch connect to the viewer here at HQ (ip add encryption port # etc..) | | I was looking at this a few weeks ago and like a fool I didn't bookmark the | page, any help would be appreciated google: - Ultra VNC SC ( free as in beer ) - Helpdesk VNC ( commercial ) regards, usleepless ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
OT: Custmoize VNC
I know there are two apps (open source) that will allow you to customize vnc but I just cant remember, in essence I want the remote users (outside the lan) to be able to download the file click run and it will automatically, upon launch connect to the viewer here at HQ (ip add encryption port # etc..) I was looking at this a few weeks ago and like a fool I didn't bookmark the page, any help would be appreciated TIA JP ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Custmoize VNC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Paul Natola wrote: | I know there are two apps (open source) that will allow you to customize vnc | but I just cant remember, in essence I want the remote users (outside the | lan) to be able to download the file click run and it will automatically, | upon launch connect to the viewer here at HQ (ip add encryption port # etc..) | | I was looking at this a few weeks ago and like a fool I didn't bookmark the | page, any help would be appreciated | | | TIA | JP Hi Jean-Paul, I Googled for VNC connection manager and this site was on the first page: http://www.s-code.com/products/vncmanager/compare.aspx Is that something like what you're looking for? Best regards, Greg - -- Greg Larkin http://www.sourcehosting.net/ http://www.FreeBSD.org/ - The Power To Serve -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIjidT0sRouByUApARAiN/AKCBtdJajfcP+KiMfen69UK+pnMJkQCgxwSL osLEeFxovY0w89v/KVWYB9o= =EQ7G -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: OT: Customize VNC
One of the apps is opensource application that allows you to create/customize an application - It was not specific to vnc I know everyone here has probably heard of it- I just cant remember what it was -Original Message- From: Zyumbilev, Peter [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2008 1:55 PM To: Jean-Paul Natola Cc: FreeBSD Questions Subject: Re: OT: Custmoize VNC I guess this is what you look for: http://www.uvnc.com/pchelpware/download/index.html Kind regards, Peter Zyumbilev IT Manager for Convergent Media Pty Ltd t +61-290-374-211 e [EMAIL PROTECTED] w www.convergentmedia.com.au Jean-Paul Natola wrote: I know there are two apps (open source) that will allow you to customize vnc but I just cant remember, in essence I want the remote users (outside the lan) to be able to download the file click run and it will automatically, upon launch connect to the viewer here at HQ (ip add encryption port # etc..) I was looking at this a few weeks ago and like a fool I didn't bookmark the page, any help would be appreciated TIA JP ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Annoying FreeBSD 6.2 behavior - takedown of VNC sessions
Since I've upgraded to 6.2-RELEASE, I've noticed that every few disconnects (especially putting my laptop to sleep while still connected) while connecting remotely to a VNC hosted on FreeBSD, it tanks my gnome-session entirely. I've tried a couple variations (exec, background or not), but this never used to happen with 5.4-STABLE. I use VNC specifically for the purpose of being able to disconnect and not have it crash my windowing sessions. Any suggestions would be appreciated. FreeBSD belle.0lsen.net 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 Thanks, -Clint ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with VNC on AMD64
Hi Josh and others Has anybody been able to solve this problem yet? I pulled in a friend who has a zillion years of experience with BSD and was not able to solve the problem. It looks like it is not even possible to start the X when the machine has a monitor attched to it. I installed FreeBSD 7.0 Beta with xorg 7.3.1, but there the problem seems to be the same... Greetings, D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with VNC on AMD64
What version of VNC are you running.. ? Anyone here tried Ultra VNC ? Thanks Hakan http://dominor.com On 10/28/07, Josh Carroll [EMAIL PROTECTED] wrote: So VNC server will run, and I can connect to it from a VNC-client, but the window manager fails to start correctly. I am having the same problem. My vnc log looks similar: *snip* X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 102 (X_ChangeKeyboardControl) Value in failed request: 0x3c Serial number of failed request: 7 Current serial number in output stream: 9 /usr/local/bin/wmaker fatal error: it seems that there is already a window manager running Of course, there's no window manager running (I get the default X gray screen with a generic X cursor). If I try to run wmaker against the VNC display, I get the same message: % wmaker -display localhost:1 wmaker fatal error: it seems that there is already a window manager running Like you, I've tried other window managers, but I have the same problem. I'll wait to see if anyone has any ideas, otherwise I'm going to go ahead and submit a PR for this. Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with VNC on AMD64
What version of VNC are you running.. ? vnc-4.1.2_2 from ports. I wonder if this is related to it compiling against ancient XFree86 source? Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with VNC on AMD64
vnc-4.1.2_2 from ports. I wonder if this is related to it compiling against ancient XFree86 source? The tightvnc port has the same problem, actually. Same message in the vnc log, but also another: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 102 (X_ChangeKeyboardControl) Value in failed request: 0x3c Serial number of failed request: 6 Current serial number in output stream: 8 Xlib: sequence lost (0x1 0x8) in reply type 0x0! X Error of failed request: 0 Major opcode of failed request: 0 () Serial number of failed request: 0 Current serial number in output stream: 8 Would it matter that the window manager itself is linked against/compiled against X.org, while these VNC ports use old XFree86? I wouldn't think so, unless Xlib is different enough. Perhaps this should be posted to freebsd-x11 instead? Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with VNC on AMD64
So VNC server will run, and I can connect to it from a VNC-client, but the window manager fails to start correctly. I am having the same problem. My vnc log looks similar: *snip* X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 102 (X_ChangeKeyboardControl) Value in failed request: 0x3c Serial number of failed request: 7 Current serial number in output stream: 9 /usr/local/bin/wmaker fatal error: it seems that there is already a window manager running Of course, there's no window manager running (I get the default X gray screen with a generic X cursor). If I try to run wmaker against the VNC display, I get the same message: % wmaker -display localhost:1 wmaker fatal error: it seems that there is already a window manager running Like you, I've tried other window managers, but I have the same problem. I'll wait to see if anyone has any ideas, otherwise I'm going to go ahead and submit a PR for this. Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem with VNC on AMD64
Hi David, I have been experiencing some issues with VNC myself and after a few tries I decided to give up on it, I am stock back into shell mode, but that's find hence the machie most of the time is close to me. in any way, i am confident someone here would be able to help you, yet the problems I experience if i recall correctly were similar to the ones you outline in your log. Lisandro Grullon Date: Fri, 19 Oct 2007 14:19:58 +0200 From: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Subject: Problem with VNC on AMD64 Hi I have been using FreeBSD for several years now on intel32. Now I installed it on my new server which is a AMD64. Most things go well, but I can't get a Window Manager working under VNC anymore. Here you find the VNC log: --- Xvnc Free Edition 4.1.2 - built Oct 21 2006 03:26:51 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Underlying X server release 4030, The XFree86 Project, Inc Fri Oct 19 08:13:28 2007 vncext: VNC extension running! vncext: Listening for VNC connections on port 5901 vncext: Listening for HTTP connections on port 5801 vncext: created VNC server for screen 0 Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! wmaker fatal error: it seems that there is already a window manager running So VNC server will run, and I can connect to it from a VNC-client, but the window manager fails to start correctly. I've tried a different window manager (TWM), but here a similar error message occurs: twm: another window manager is already running. on screen 0? twm: unable to find any unmanaged video screens. Anybody suggestions how I can solve this? Greetings, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] _ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with VNC on AMD64
Hi I have been using FreeBSD for several years now on intel32. Now I installed it on my new server which is a AMD64. Most things go well, but I can't get a Window Manager working under VNC anymore. Here you find the VNC log: --- Xvnc Free Edition 4.1.2 - built Oct 21 2006 03:26:51 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Underlying X server release 4030, The XFree86 Project, Inc Fri Oct 19 08:13:28 2007 vncext: VNC extension running! vncext: Listening for VNC connections on port 5901 vncext: Listening for HTTP connections on port 5801 vncext: created VNC server for screen 0 Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! wmaker fatal error: it seems that there is already a window manager running So VNC server will run, and I can connect to it from a VNC-client, but the window manager fails to start correctly. I've tried a different window manager (TWM), but here a similar error message occurs: twm: another window manager is already running. on screen 0? twm: unable to find any unmanaged video screens. Anybody suggestions how I can solve this? Greetings, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC ??
what are some of the more current ways to do remote desktop functions w/ FreeBSD 6.2 host and WinXP client . . googled, but alot of stuff out there seems to be awful old . . TIA Pete C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ??
On 14/05/07, Pete C [EMAIL PROTECTED] wrote: what are some of the more current ways to do remote desktop functions w/ FreeBSD 6.2 host and WinXP client . . googled, but alot of stuff out there seems to be awful old . . What about NX or X11? You can use a free X-Server such as Cygwin X on your Windows PC to connect to your FreeBSD Box. HTH Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ??
On 5/14/07, Pete C [EMAIL PROTECTED] wrote: what are some of the more current ways to do remote desktop functions w/ FreeBSD 6.2 host and WinXP client . . googled, but alot of stuff out there seems to be awful old . . xrdp is the newest buzzword: http://www.freshports.org/net/xrdp/ X11, all kinds of VNC, NX and other protocols are all viable alternatives. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ??
I don't dare to ask why you send a mail to a mailing list without supplying a valid sender adress that can be replied to... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: VNC ??
uh, since he's blocking my emails, here is info if anyone else is interested. -- Forwarded message -- From: Jack Barnett [EMAIL PROTECTED] Date: May 14, 2007 1:58 PM Subject: Re: VNC ?? To: Pete C [EMAIL PROTECTED] The way I have mine setup is with Tight VNC (fairly new) [tightvnc.org] Then run it with the local option (so it binds to 127.0.0.1 instead of outside interface (for security reasons). Then I use Putty to SSH in and use that to port forward. Then after I have SSH session I do VNC to localhost:10 which drops me to the unix desktop. The advantages of this are: Secure encrypted connection. Ability to use compression (either via SSH or TightVNC) Compression allows it to be really fast, it's fairly responsive even over a DSL or cable line. Also secure in the fact that your VNC port isn't hanging wide open (just SSH) If your on the local unix box you can also just start a desktop then do 'vncviewer 127.0.0.1:1' and get your remote desktop (so it moves around with you, regardless if your local or remote) On 5/14/07, Pete C [EMAIL PROTECTED] wrote: what are some of the more current ways to do remote desktop functions w/ FreeBSD 6.2 host and WinXP client . . googled, but alot of stuff out there seems to be awful old . . TIA Pete C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ??
Quoting Jack Barnett [EMAIL PROTECTED]: uh, since he's blocking my emails, here is info if anyone else is interested. so sorry for the bad reply-to addy, new web-mail client ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Xvfb + VNC
Hello, I could install gdm with Xorg and vnc.so module loaded. This is fine, now I can access that X server with vnc. The problem is that the Xorg server needs a video card. So if somebody connects a montior to that server while I'm working from home then he/she will see what I'm doing. (I cannot restrict physical access to that computer, but I do not want others to see my desktop...) My idea is to create a virtual framebuffer server with Xvfb, and load vnc.so module there. Since vnc.so can be password protected, in theory, nobody will have access to that X session, except me. But I cannot do this. Xvfb(1) tells me that it has the same options that Xserver(1) has. The Xserver(1) does not tell me anything about loadable modules, but X is a symlink to Xorg. Well, Xorg has a -config option but Xvfb does not. :-( Does it mean that I cannot load vnc.so into the virtual framebuffer server? Is there a better solution? In my dreams: 1. I would run a virtual X server, that is not visible directly (not requiring any video card) 2. I would access this X server with some program remotely (preferrably VNC) 3. This remote access needs to be secure to some extent 4. This remote access should be fast enough to use through a DSL connection Can my dreams come true? Thanks, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thursday 22 June 2006 17:06, pete wright wrote: Did you try to build/install a 32bit version of VNC? Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. -pete How do you do cross-compilation on amd64? I looked through the mailing list archives and couldn't find a method. Also, VNC, slow as it is, tends to be faster than running X apps directly, at least over high-latency networks. NX runs rings around both of them, though. -- Jonathan Fosburgh AIX and Storage Administrator UT MD Anderson Cancer Center Houston, TX pgpNDUVUVewrD.pgp Description: PGP signature
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
screen? /usr/port/sysutils/screen My users need up to 20 instances of a graphical analysis package which has a text-based control window that spawns two graphical windows. They run a window manager with 24 virtual desktops, each running an instance of this program. As much as I love screen (I use it constantly for sysadmin-type work and I have mutt running constantly on one of my screens), it doesn't quite fulfill our needs for this task. What about xorg-dmx? It seems. it's provide what you need :) Does it test someone? -- Best regards, Arseny Nasokin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Does anyone run VNC with 64-bit FreeBSD (amd64)?
G'day everyone, I recently had to replace a disk and took the opportunity to upgrade from 5-stable to 6-stable. I also changed from the 32-bit to the 64-bit version. I have a dual Opteron server. VNC installed from ports (4.2.1) doesn't work on the 64-bit machine. The same version installed on my home machine (32-bit) with the .vnc directory copied over exactly from my work 64-bit machine runs fine. So in what sense does it fail If I create a blank .vnc/xstartup, then I get the usual grey screen. Then if I try and run X commands on that display, some work, like xsetroot -solid blue, but others, xterm, icewm, twm, etc don't. 130~/.vnc$ icewm -display :9 IceWM: using /home/xx/.icewm for private configuration files X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Value in failed request: 0x0 Serial number of failed request: 9 Current serial number in output stream: 10 131~/.vnc$ xterm -display :9 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x21 Serial number of failed request: 41 Current serial number in output stream: 49 If they are in the xstartup file they give the exact same errors in the vnc log file. I was only running them interactively above to troubleshoot it. Google has failed me for once, so I seek your experience and advice... Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
I have the same ,problem,But I have never run on other version,I use RELENG_6_1, AMD64 On 6/22/06, Greg Lane [EMAIL PROTECTED] wrote: G'day everyone, I recently had to replace a disk and took the opportunity to upgrade from 5-stable to 6-stable. I also changed from the 32-bit to the 64-bit version. I have a dual Opteron server. VNC installed from ports (4.2.1) doesn't work on the 64-bit machine. The same version installed on my home machine (32-bit) with the .vnc directory copied over exactly from my work 64-bit machine runs fine. So in what sense does it fail If I create a blank .vnc/xstartup, then I get the usual grey screen. Then if I try and run X commands on that display, some work, like xsetroot -solid blue, but others, xterm, icewm, twm, etc don't. 130~/.vnc$ icewm -display :9 IceWM: using /home/xx/.icewm for private configuration files X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Value in failed request: 0x0 Serial number of failed request: 9 Current serial number in output stream: 10 131~/.vnc$ xterm -display :9 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x21 Serial number of failed request: 41 Current serial number in output stream: 49 If they are in the xstartup file they give the exact same errors in the vnc log file. I was only running them interactively above to troubleshoot it. Google has failed me for once, so I seek your experience and advice... Greg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thu, Jun 22, 2006 at 04:04:34PM +0300, Alex Savovski [EMAIL PROTECTED] wro I have the same ,problem,But I have never run on other version,I use RELENG_6_1, AMD64 On Thu, Jun 22, 2006 at 11:29:15AM -0500, Jonathan Fosburgh [EMAIL PROTECTED] wrote: VNC (tightvnc included) as well as NXWindows (IMHO, much better than VNC) are based on old versions of XFree86 that don't support AMD64. I have had some success running the i386 package of tightvnc and starting only twm from the xstartup script. Some applications (just about anything using gtk) crash the VNC server, and some (KDE) work all right. YMMV. I have tried to make NXWindows work on amd64 but there is just too much patching that needs to be done for my meager skills. Thanks for the info. I had figured something like this. I installed the 64-bit system anticipating a future memory upgrade from the current 4GB to 8GB. However, VNC is essential for various members of my group, as is ports/devel/root (which doesn't compile on amd64) and there is some of our own (also essential) custom software which is not 64-bit clean. Since this holds up a number of people from their work and my patching skills are VERY meager, I will have to roll back to the 32-bit OS. Thanks again! Greg P.S. Yes, I should have tested more before the upgrade. I did some tests, but obviously not enough! In my defence, I was hastened by the disk dying and the need to get the machine back up and running. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On 6/22/06, Greg Lane [EMAIL PROTECTED] wrote: On Thu, Jun 22, 2006 at 03:06:46PM -0700, pete wright [EMAIL PROTECTED] wrote: Did you try to build/install a 32bit version of VNC? Thanks for the suggestion. I thought about doing that, but there is still other essential software that is not 64-bit clean and our entire group needs this machine back up ASAP since currently we are sitting on our hands doing nothing till I get it back up. If I had a spare machine I could potentially spend some time getting this sorted. But we don't have a spare machine, we don't have any money to buy one, there is only me to fix it, and I have to get some real work done the usual story. hmm, so there is no way to run the app's which are not 64bit clean in 32bit mode in your environment? Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. What about the other 10%? We use VNC because it saves state for those of my users who work from multiple locations, at home, at work and some are even based overseas. They don't want to restart up to 20 windows every time they logon. Remote access in this form is essential for their productivity. screen? /usr/port/sysutils/screen I hope this is taken as friendly advice to save you work -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thu, Jun 22, 2006 at 03:06:46PM -0700, pete wright [EMAIL PROTECTED] wrote: Did you try to build/install a 32bit version of VNC? Thanks for the suggestion. I thought about doing that, but there is still other essential software that is not 64-bit clean and our entire group needs this machine back up ASAP since currently we are sitting on our hands doing nothing till I get it back up. If I had a spare machine I could potentially spend some time getting this sorted. But we don't have a spare machine, we don't have any money to buy one, there is only me to fix it, and I have to get some real work done the usual story. Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. What about the other 10%? We use VNC because it saves state for those of my users who work from multiple locations, at home, at work and some are even based overseas. They don't want to restart up to 20 windows every time they logon. Remote access in this form is essential for their productivity. Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On Thu, Jun 22, 2006 at 04:15:47PM -0700, pete wright [EMAIL PROTECTED] wrote: hmm, so there is no way to run the app's which are not 64bit clean in 32bit mode in your environment? I did test one of them. It works, but I don't have time to mess with all of them, and finding the 32-bit libraries and putting them in the right place took me forever. I am afraid I am not a great programmer... However, I can quickly do a reinstall safely since I have a recent backup and all my /data and /home file systems are on separate disks I can just unplug. It comes down to a how much time do I have to spare issue and in the end the machine has to be back up today. I already have my own instant-server meta-port that installs all my standard ports. It only takes a couple of hours and I can do some other work while I wait. Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. What about the other 10%? We use VNC because it saves state for those of my users who work from multiple locations, at home, at work and some are even based overseas. They don't want to restart up to 20 windows every time they logon. Remote access in this form is essential for their productivity. screen? /usr/port/sysutils/screen My users need up to 20 instances of a graphical analysis package which has a text-based control window that spawns two graphical windows. They run a window manager with 24 virtual desktops, each running an instance of this program. As much as I love screen (I use it constantly for sysadmin-type work and I have mutt running constantly on one of my screens), it doesn't quite fulfill our needs for this task. I hope this is taken as friendly advice to save you work No drama! Friendly advice is always gratefully received. Especially if it is aimed at saving me work! Unfortunately I think rolling back the OS is the least work for me at this point in time. Thanks again, I do appreciate the advice. Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does anyone run VNC with 64-bit FreeBSD (amd64)?
On 6/22/06, Greg Lane [EMAIL PROTECTED] wrote: On Thu, Jun 22, 2006 at 04:04:34PM +0300, Alex Savovski [EMAIL PROTECTED] wro I have the same ,problem,But I have never run on other version,I use RELENG_6_1, AMD64 On Thu, Jun 22, 2006 at 11:29:15AM -0500, Jonathan Fosburgh [EMAIL PROTECTED] wrote: VNC (tightvnc included) as well as NXWindows (IMHO, much better than VNC) are based on old versions of XFree86 that don't support AMD64. I have had some success running the i386 package of tightvnc and starting only twm from the xstartup script. Some applications (just about anything using gtk) crash the VNC server, and some (KDE) work all right. YMMV. I have tried to make NXWindows work on amd64 but there is just too much patching that needs to be done for my meager skills. Thanks for the info. I had figured something like this. I installed the 64-bit system anticipating a future memory upgrade from the current 4GB to 8GB. However, VNC is essential for various members of my group, as is ports/devel/root (which doesn't compile on amd64) and there is some of our own (also essential) custom software which is not 64-bit clean. Since this holds up a number of people from their work and my patching skills are VERY meager, I will have to roll back to the 32-bit OS. Did you try to build/install a 32bit version of VNC? Also, if you are running a Unix like OS why use VNC? You can achive %90 of the same features (with less of a memory/cpu impact) by running X apps remotely. -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Next VNC related question ... recording
On 5/7/06, Marc G. Fournier [EMAIL PROTECTED] wrote: What are ppl using for this? I'm trying vnc2swf, but wonder if there is something that records to a better (ie. non windows) format that works well under FreeBSD? Thx Marc G. Fournier Hub.Org Networking Services (http://www.hub.org ) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Search freshmeat,there are others i thing..I am sure of one that takes snapshots in jpg.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Next VNC related question ... recording
What are ppl using for this? I'm trying vnc2swf, but wonder if there is something that records to a better (ie. non windows) format that works well under FreeBSD? Thx Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC forwarding over sshd issue
I'm having a weird problem that surfaces sometimes and I am having trouble pinning down the cause. What I do is use VNC to remote-control my home FreeBSD box remotely. Most of the time, this works fine. My home router forwards the external port to my FreeBSD (6.0R) box. I use PuTTY as a Windows ssh client, and have a saved session that does the VNC port-forwarding (local port 7000 forwards over ssh to remote port 5900). I run Gnome (2.12.2) and vino as my VNC server and connect to my home desktop. Sshd is OpenSSH 2.6.1, PuTTY 0.53b, TightVNC 1.2.9 But every now and then (like right now), the VNC side of things fails. I can still connect via SSH just fine. The PuTTY logs show the port is successfully being forwarded with no error: 2006-02-17 09:38:58 Local port 7000 forwarding to localhost:5900 But when I try to launch a VNC client on the remote PC (in this case, TightVNC) I get a Connection closed error. The PuTTY logs show: 2006-02-17 09:52:42 Opening forwarded connection to localhost:5900 2006-02-17 09:52:42 Forwarded port closed On the FreeBSD box, no log files seem to get changed after the attempt. In particular, I check messages and auth.log but doing a listing sorted by time, I see nothing logged. What I DO know is if I went home and restarted the FreeBSD box, it'd work. I've tried -HUP on both sshd and vino-server to no avail. I cannot find any docs for vino-server to determine additional params I could pass it for more-detailed logging. Enabling additional debugging info on sshd with the -d option seems to not be an option remotely since it prevents it from going into daemon mode and it'll only handle one connection, and I can't make the problem surface on-request in order to test it while at home. The problem is particularly annoying because I can't MAKE it happen. It just sometimes does, with no settings changes, and will work again after rebooting the FreeBSD system, again with no settings changes. SSH never stops working... it's always the VNC-port-forwarding side of things. Any suggestions? Somewhere else to look for info? Some way to get more debug info from sshd or vino-server? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC forwarding over sshd issue
Scott I. Remick wrote: I'm having a weird problem that surfaces sometimes and I am having trouble pinning down the cause. What I do is use VNC to remote-control my home FreeBSD box remotely. Most of the time, this works fine. My home router forwards the external port to my FreeBSD (6.0R) box. I use PuTTY as a Windows ssh client, and have a saved session that does the VNC port-forwarding (local port 7000 forwards over ssh to remote port 5900). I run Gnome (2.12.2) and vino as my VNC server and connect to my home desktop. Sshd is OpenSSH 2.6.1, PuTTY 0.53b, TightVNC 1.2.9 But every now and then (like right now), the VNC side of things fails. I can still connect via SSH just fine. The PuTTY logs show the port is successfully being forwarded with no error: 2006-02-17 09:38:58 Local port 7000 forwarding to localhost:5900 But when I try to launch a VNC client on the remote PC (in this case, TightVNC) I get a Connection closed error. The PuTTY logs show: 2006-02-17 09:52:42 Opening forwarded connection to localhost:5900 2006-02-17 09:52:42 Forwarded port closed On the FreeBSD box, no log files seem to get changed after the attempt. In particular, I check messages and auth.log but doing a listing sorted by time, I see nothing logged. What I DO know is if I went home and restarted the FreeBSD box, it'd work. I've tried -HUP on both sshd and vino-server to no avail. I cannot find any docs for vino-server to determine additional params I could pass it for more-detailed logging. Enabling additional debugging info on sshd with the -d option seems to not be an option remotely since it prevents it from going into daemon mode and it'll only handle one connection, and I can't make the problem surface on-request in order to test it while at home. The problem is particularly annoying because I can't MAKE it happen. It just sometimes does, with no settings changes, and will work again after rebooting the FreeBSD system, again with no settings changes. SSH never stops working... it's always the VNC-port-forwarding side of things. Any suggestions? Somewhere else to look for info? Some way to get more debug info from sshd or vino-server? Thanks I'm assuming you try to connect several times and it fails each time. I use TightVNC to connect to KDE's desktop sharing and it gives the same error sometimes (not through SSH though). If I keep trying it will eventually get through. Some basic troubleshooting ideas: Eliminate SSH port forwarding as a suspect by connecting directly to the VNC port from your LAN the next time the error comes up. Eliminate TightVNC as a suspect by trying another VNC client, such as RealVNC. Eliminate Vino as a suspect trying another VNC server. A -HUP wont necessarily do anything to a daemon that is responding oddly. You can try restarting sshd completely by doing /etc/rc.d/sshd restart. This can be done remotely, just don't close your existing connection until you know the daemon came back up. Close your connection and reconnect. You can probably do the same to vino by killing it and then bringing it back up (not familiar with vino). Once you know where the problem originates maybe you can figure out how to fix it, or at least how to work around it. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vnc server problems/amd64
FreeBSD 6.0 amd64 i tried to run it but crashes on first X client started as i386 version works i replaced Xvnc with i386 version - now works as long as i don't run any gtk/gdk based program then i got: The program 'gimp' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 294 error_code 10 request_code 129 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) is anyone running VNC with FreeBSD here? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sharing desktop witn VNC
On Thu, Sep 22, 2005 at 10:41:37PM -0700, Garrett Cooper wrote: On Sep 22, 2005, at 7:31 PM, Micah wrote: stan wrote: I'm trying to use tighvnc to share a desktop with a friend, for educational purposes. I've been able to run vncserver on my local machine, and connect to it with vncviewer. I've also been able to ssh to his machine (with X forwarding turned on) and do the same thing, but this is really slow. In the case of his FreebSD machine I just got the simple session that xstart produces. How can I star vncserver on his FreebSD machine, such that I get a full blown KDE desktop? This is BTW what he gets when he logs in via kdm. Is there a way to share an already running X session with vnc? Or do I have to start a new session using vncserver? KDE provides a VNC server that allows you to connect to an already running KDE session. From the KDE control center select Internet Network -- Desktop Sharing. Adjust the settings to your liking. I've had keyboard problems with it when connecting from the RealVNC client (massively repeated characters making it impossible to type anything). Later, Micah Running ssh -C is wise as it compresses the ssh stream. I don't suggest straight VNC as it's all plaintext data going across a network, where using port forwarding via SSH would decrease your problems to near nil in terms of someone sniffing your traffic. -Garrett Thanks, that sounds like good advice. Can you point me to some documnetation as to how ot do this? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sharing desktop witn VNC
On Thu, Sep 22, 2005 at 07:31:17PM -0700, Micah wrote: stan wrote: I'm trying to use tighvnc to share a desktop with a friend, for educational purposes. I've been able to run vncserver on my local machine, and connect to it with vncviewer. I've also been able to ssh to his machine (with X forwarding turned on) and do the same thing, but this is really slow. In the case of his FreebSD machine I just got the simple session that xstart produces. How can I star vncserver on his FreebSD machine, such that I get a full blown KDE desktop? This is BTW what he gets when he logs in via kdm. Is there a way to share an already running X session with vnc? Or do I have to start a new session using vncserver? KDE provides a VNC server that allows you to connect to an already running KDE session. From the KDE control center select Internet Network -- Desktop Sharing. Adjust the settings to your liking. I've had keyboard problems with it when connecting from the RealVNC client (massively repeated characters making it impossible to type anything). I just looked on his machine, which is running KDE version 3.4.2, and I can't find that choice in his control center. Now I _do_ see it on a machine I have here that is runnig KDE version 3.3.2. His machine machine is FreebSD 4.11 STABLE, and the machine I happen to have KDE on is Debian. Could it be in a different place on his? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sharing desktop witn VNC
stan wrote: On Thu, Sep 22, 2005 at 07:31:17PM -0700, Micah wrote: stan wrote: I'm trying to use tighvnc to share a desktop with a friend, for educational purposes. I've been able to run vncserver on my local machine, and connect to it with vncviewer. I've also been able to ssh to his machine (with X forwarding turned on) and do the same thing, but this is really slow. In the case of his FreebSD machine I just got the simple session that xstart produces. How can I star vncserver on his FreebSD machine, such that I get a full blown KDE desktop? This is BTW what he gets when he logs in via kdm. Is there a way to share an already running X session with vnc? Or do I have to start a new session using vncserver? KDE provides a VNC server that allows you to connect to an already running KDE session. From the KDE control center select Internet Network -- Desktop Sharing. Adjust the settings to your liking. I've had keyboard problems with it when connecting from the RealVNC client (massively repeated characters making it impossible to type anything). I just looked on his machine, which is running KDE version 3.4.2, and I can't find that choice in his control center. Now I _do_ see it on a machine I have here that is runnig KDE version 3.3.2. His machine machine is FreebSD 4.11 STABLE, and the machine I happen to have KDE on is Debian. Could it be in a different place on his? Make sure he has kdenetwork installed (pkg_info kdenetwork\*). If he has kdenetwork try running krfb from a command prompt. Later Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sharing desktop witn VNC
I'm trying to use tighvnc to share a desktop with a friend, for educational purposes. I've been able to run vncserver on my local machine, and connect to it with vncviewer. I've also been able to ssh to his machine (with X forwarding turned on) and do the same thing, but this is really slow. In the case of his FreebSD machine I just got the simple session that xstart produces. How can I star vncserver on his FreebSD machine, such that I get a full blown KDE desktop? This is BTW what he gets when he logs in via kdm. Is there a way to share an already running X session with vnc? Or do I have to start a new session using vncserver? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sharing desktop witn VNC
stan wrote: I'm trying to use tighvnc to share a desktop with a friend, for educational purposes. I've been able to run vncserver on my local machine, and connect to it with vncviewer. I've also been able to ssh to his machine (with X forwarding turned on) and do the same thing, but this is really slow. In the case of his FreebSD machine I just got the simple session that xstart produces. How can I star vncserver on his FreebSD machine, such that I get a full blown KDE desktop? This is BTW what he gets when he logs in via kdm. Is there a way to share an already running X session with vnc? Or do I have to start a new session using vncserver? KDE provides a VNC server that allows you to connect to an already running KDE session. From the KDE control center select Internet Network -- Desktop Sharing. Adjust the settings to your liking. I've had keyboard problems with it when connecting from the RealVNC client (massively repeated characters making it impossible to type anything). Later, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sharing desktop witn VNC
On Sep 22, 2005, at 7:31 PM, Micah wrote: stan wrote: I'm trying to use tighvnc to share a desktop with a friend, for educational purposes. I've been able to run vncserver on my local machine, and connect to it with vncviewer. I've also been able to ssh to his machine (with X forwarding turned on) and do the same thing, but this is really slow. In the case of his FreebSD machine I just got the simple session that xstart produces. How can I star vncserver on his FreebSD machine, such that I get a full blown KDE desktop? This is BTW what he gets when he logs in via kdm. Is there a way to share an already running X session with vnc? Or do I have to start a new session using vncserver? KDE provides a VNC server that allows you to connect to an already running KDE session. From the KDE control center select Internet Network -- Desktop Sharing. Adjust the settings to your liking. I've had keyboard problems with it when connecting from the RealVNC client (massively repeated characters making it impossible to type anything). Later, Micah Running ssh -C is wise as it compresses the ssh stream. I don't suggest straight VNC as it's all plaintext data going across a network, where using port forwarding via SSH would decrease your problems to near nil in terms of someone sniffing your traffic. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC + SSH question..
Hey guys had a SSH forward question so here goes... I have 2 computers on my lan one of them is a server and the other is my desktop. Desktop 192.168.1.104 Server 192.168.1.103 Now I have port forwarding setup on my crappy linksys router so 22 is pointing to my Server (192.168.1.103) My question is this... I would like to tightVNC to my Desktop (192.168.1.104) forwarding it through SSH. Now from what I understand If my router was pointing to my desktop this would not be a problem at all. All I would have to do is SSH to my IP while forwarding 22 to 5900. However I cant do it this way since 22 is pointing to my server. So I figured I would ssh into my server and issue a command such as ssh 192.168.1.103 -L22:192.168.1.104:5900 however once im in and I run vncview it obivoiusly can be displayed becuase Im not running X on the server. Am I way off here? Is there a way to do this? Will I need to forward 22 on my router to the desktop as well as server? Is there a way to connect to my server thats not running X and some how vnc into my desktop? On the remote machines I'd be useing PuTTY for windows and SSH on Linux box's. Prehaps someone can give me a step by step guide? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC + SSH question..
On Aug 31, 2005, at 9:22 AM, Eric Murphy wrote: Hey guys had a SSH forward question so here goes... I have 2 computers on my lan one of them is a server and the other is my desktop. Desktop 192.168.1.104 Server 192.168.1.103 Now I have port forwarding setup on my crappy linksys router so 22 is pointing to my Server (192.168.1.103) My question is this... I would like to tightVNC to my Desktop (192.168.1.104) forwarding it through SSH. Now from what I understand If my router was pointing to my desktop this would not be a problem at all. All I would have to do is SSH to my IP while forwarding 22 to 5900. However I cant do it this way since 22 is pointing to my server. So I figured I would ssh into my server and issue a command such as ssh 192.168.1.103 -L22:192.168.1.104:5900 however once im in and I run vncview it obivoiusly can be displayed becuase Im not running X on the server. Am I way off here? Is there a way to do this? Will I need to forward 22 on my router to the desktop as well as server? Is there a way to connect to my server thats not running X and some how vnc into my desktop? On the remote machines I'd be useing PuTTY for windows and SSH on Linux box's. Prehaps someone can give me a step by step guide? Thanks. To my knowledge TightVNC doesn't support access to X via the :0'th display. That may be your problem and not your port forwarding setup, because it appears-at least to me-that it is correct. So, try a different display or if you want access via display :0 try x11vnc. Note that it may be considered more of a security issue since it would connect directly to your desktop's display. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC + SSH question..
Hey guys had a SSH forward question so here goes... I have 2 computers on my lan one of them is a server and the other is my desktop. Desktop 192.168.1.104 Server 192.168.1.103 Now I have port forwarding setup on my crappy linksys router so 22 is pointing to my Server (192.168.1.103) My question is this... Not sure this will help since I'm not sure where exactly you're viewer is, but maybe it will... http://www.pjkh.com/wiki/vnc_through_an_ssh_proxy -philip ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC + SSH question..
On 8/30/05, Eric Murphy [EMAIL PROTECTED] wrote: Hey guys had a SSH forward question so here goes... I have 2 computers on my lan one of them is a server and the other is my desktop. Desktop 192.168.1.104 Server 192.168.1.103 Now I have port forwarding setup on my crappy linksys router so 22 is pointing to my Server (192.168.1.103) My question is this... I would like to tightVNC to my Desktop (192.168.1.104) forwarding it through SSH. Now from what I understand If my router was pointing to my desktop this would not be a problem at all. All I would have to do is SSH to my IP while forwarding 22 to 5900. However I cant do it this way since 22 is pointing to my server. So I figured I would ssh into my server and issue a command such as ssh 192.168.1.103 -L22:192.168.1.104:5900 however once im in and I run vncview it obivoiusly can be displayed becuase Im not running X on the server. Am I way off here? Is there a way to do this? Will I need to forward 22 on my router to the desktop as well as server? Is there a way to connect to my server thats not running X and some how vnc into my desktop? Why not just forword it to a diffrent port, at the router forward port 23 (any port) to 192.168.1.104:22? On the remote machines I'd be useing PuTTY for windows and SSH on Linux box's. Prehaps someone can give me a step by step guide? http://www.maths.utas.edu.au/People/Hill/vnc/vnc.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC + SSH question..
On 8/30/05, Eric Murphy [EMAIL PROTECTED] wrote: Can you give me an example at what that would look like if im useing a linux box...can you giev me the command line santax? I used port to point to 192.168.1.104:22 Umm? I'm talking about simple NAT port forwarding: VNC Putty SSL Tunnel:23 -- Internet -- [Port23 - (NAT/Router/Firewall) - Port22] -- FreeBSD Desktop. Something like this; just change the Ext. port to 23 and Int. to 192.168.1.104:22: http://www.m0n0.ch/wall/screens/firewall_nat.png Why can't you do that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC multiplexer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 30 Jun 2005 21:59:14 -0700 (PDT) Philip Hallstrom [EMAIL PROTECTED] wrote: On 6/26/05, Anthony Chavez [EMAIL PROTECTED] wrote: I've got a client that would like to be able to connect to VNC servers behind a FreeBSD gateway. Said servers are assigned dynamic IPs via DHCP, so port mapping (via pf) is not an option (AFAIK). However, we intend to make use of dynamic DNS, so they will at least have hostnames. I missed the first part of this, but would proxying the VNC connections through an intermediate SSH server help at all? http://www.pjkh.com/wiki/vnc_through_an_ssh_proxy You could setup individual SSH tunnels for each machine in question. The tunnel would stay the same regardless of the IP... and the VNC viewer would connect to localhost so you'd never really need the server IP. This *might* work. I think that my client wants to be as non-intrusive on the users' workstations as possible, but we could always script up something to mass-deploy openssh and tightvnc invisibly to the users. Thanks! - -- Anthony Chavez http://anthonychavez.org/ mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Darwin) iQEVAwUBQsThsPAIdTFWAbdTAQoZVAgAjIbnkbKMiCZ4/BfIPFxx4bvLGnDUOjOY JuhMJf/maDB7HDnAipZ8I8cd1BpE1JW+P8+EM2+wje6bA+SdcfDzy6WFJTIkc0er SqVjsAj82JwBfOXE7tKbNZaw+R7JYazPVc5Kz4eliTIJxw/PnkJSjz3Io8F+Q5Vv rMbkX04y7mu4O/T1NRSG7jyvmW9E+3wlrtSdhWAD+7HeQwsaLBiZDcw6Ln5t3Jp+ PTFzYFlyGHKQ7e6qiVWyxyIeHc0JWb2sHFZk/quDqfUe8bOeyf1Uyxpy6T1CTWxv R6JpjHCM8wKbKX6KPSKyxPf7UzNVxg37a3A/P2waCaC2+qs00McPFw== =+2Xo -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC multiplexer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 27 Jun 2005 01:42:53 -0500 Nikolas Britton [EMAIL PROTECTED] wrote: On 6/26/05, Anthony Chavez [EMAIL PROTECTED] wrote: I've got a client that would like to be able to connect to VNC servers behind a FreeBSD gateway. Said servers are assigned dynamic IPs via DHCP, so port mapping (via pf) is not an option (AFAIK). However, we intend to make use of dynamic DNS, so they will at least have hostnames. Why can't you just give them static mappings. On my networks I use DHCP for everything. I then tell my DHCP/DNS server (m0n0wall) to reserve and only give this ip address to server x or printer y etc.to put it bluntly... Static IPs would certainly work, but this particular subnet is expected to see a large degree of growth over the next few years, and my client specificially asked for dynamic IPs. One solution we've considered is setting up a multiplexer of sorts that would enable users of VNC client apps to pick and choose which machine to connect to inside the LAN per session, but I'm curious to know if such a thing (or something similar) exists already. I've never heard of such a device And after researching it, I'm discovering that even *making* such a device would be extremely difficult because the VNC protocol itself does not lend itself well to proxying. So there's my answer: write a multiplexer myself. I'd be very interested in knowing what solutions any of you may have come with to tackle this problem. DNS. u what about setting up a web page where the user can click on which server to connect to (you will still need DNS or Static mappings) and then it opens up in a java VNC client? We've considered doing that. However, my client has been somewhat unimpressed by the Java VNC client, and is not terribly interested in using it either. Nevertheless, I appreciate your response. - -- Anthony Chavez http://anthonychavez.org/ mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Darwin) iQEVAwUBQsSwxvAIdTFWAbdTAQoEIwf/YwL4SLjpI/78wqvaGcwIXwQGXsSOfaJb t3U3Jitjov6wnYgq26YxMGQoFknXpAtPzqAR8Rn9ceJdEt4AtJ1S7vo7NyD0GrRm dqKnfVvUYUUPWNk1cuDmVbEH8HDXQllInQ/aeRaXTNDONACUtFxH/lKF+rEs0nV9 N7UhyFKeAHZAjd4FYBIlCbdw4rQkoFc1Ke8LLbi6LdK3ZuYTrLHIinLy2lcY4zkf 2E023tALJHh1+K0Ks82NmX7zLxbh2GqRKAlZ01Iy414vBSeGe9Yuz0jvwQ2YYZx2 g2mwvLdrujz3mVtOmn14tmFr9t/BrVq3NBONPSKKQaq4FawbX8bRqw== =6iXs -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC multiplexer
On 6/26/05, Anthony Chavez [EMAIL PROTECTED] wrote: I've got a client that would like to be able to connect to VNC servers behind a FreeBSD gateway. Said servers are assigned dynamic IPs via DHCP, so port mapping (via pf) is not an option (AFAIK). However, we intend to make use of dynamic DNS, so they will at least have hostnames. I missed the first part of this, but would proxying the VNC connections through an intermediate SSH server help at all? http://www.pjkh.com/wiki/vnc_through_an_ssh_proxy You could setup individual SSH tunnels for each machine in question. The tunnel would stay the same regardless of the IP... and the VNC viewer would connect to localhost so you'd never really need the server IP. Anyway, just a thought... -philip ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC multiplexer
On 6/26/05, Anthony Chavez [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, all. Slightly off-topic here, but I thought I might get a better (and more relevant) response from here rather than a more general VNC list/newsgroup. I've got a client that would like to be able to connect to VNC servers behind a FreeBSD gateway. Said servers are assigned dynamic IPs via DHCP, so port mapping (via pf) is not an option (AFAIK). However, we intend to make use of dynamic DNS, so they will at least have hostnames. Why can't you just give them static mappings. On my networks I use DHCP for everything. I then tell my DHCP/DNS server (m0n0wall) to reserve and only give this ip address to server x or printer y etc.to put it bluntly... One solution we've considered is setting up a multiplexer of sorts that would enable users of VNC client apps to pick and choose which machine to connect to inside the LAN per session, but I'm curious to know if such a thing (or something similar) exists already. I've never heard of such a device I'd be very interested in knowing what solutions any of you may have come with to tackle this problem. DNS. u what about setting up a web page where the user can click on which server to connect to (you will still need DNS or Static mappings) and then it opens up in a java VNC client? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC multiplexer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, all. Slightly off-topic here, but I thought I might get a better (and more relevant) response from here rather than a more general VNC list/newsgroup. I've got a client that would like to be able to connect to VNC servers behind a FreeBSD gateway. Said servers are assigned dynamic IPs via DHCP, so port mapping (via pf) is not an option (AFAIK). However, we intend to make use of dynamic DNS, so they will at least have hostnames. One solution we've considered is setting up a multiplexer of sorts that would enable users of VNC client apps to pick and choose which machine to connect to inside the LAN per session, but I'm curious to know if such a thing (or something similar) exists already. I'd be very interested in knowing what solutions any of you may have come with to tackle this problem. Cheers! - -- Anthony Chavez http://anthonychavez.org/ mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Darwin) iQEVAwUBQr58tfAIdTFWAbdTAQpPnggAmDPem80aanSH+L3ig0/Emo4y42NRqiWb CUFRSaE0tAXpnsh75QGJrHqBW6Tzhmw/2ukA6oGHc79NJLMJPBE4s1LzkYM2Xg42 WI1E2985ISfqhQEjnTBCDQ+vfby1WsWG8Byf3EBPKVIFAR9t0pVbLbIpJDOjfZF/ AWQlUvLK3IOOdwauImBfDsIgZ+4RnCBOsizsoJpC1BXVAAJErCFYWBsKUek0MBdj irQYqALglceIGC5britOHbz2dOL7qdOFnZ4Sh5hdovMM00OOlddHJdjCzRkENHOr kAF6ClX7KpeFD/6TNC/5P+dOv6UqqOlcYBw2hTHgCEVMKssr+14Dnw== =vZNY -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vnc server install fails on Xorg code
Hi all! I wonder if anyone wants to weigh in on this one. I am trying to get a skeleton X up on a headless 5.3 box. To this end I installed tinywm (/usr/ports/x11-wm/tinywm) then went on to install vnc server, and the build failed - rather spectacularly- as follows: [screenfuls of stuff, then...] NARROWPROTO-DMITSHM -DXFT -DXFREE86_FT2 -DXRENDER -c do_traps.c do_traps.c:113: error: syntax error before '*' token do_traps.c:113: warning: type defaults to `int' in declaration of `traps' do_traps.c:113: error: ISO C forbids data definition with no type or storage class do_traps.c: In function `InitFixedTraps': do_traps.c:129: error: `XTrap' undeclared (first use in this function) do_traps.c:129: error: (Each undeclared identifier is reported only once do_traps.c:129: error: for each function it appears in.) do_traps.c:129: error: `curTrap' undeclared (first use in this function) do_traps.c:130: warning: ISO C90 forbids mixed declarations and code do_traps.c:144: error: syntax error before ')' token do_traps.c:207: warning: value computed is not used do_traps.c: In function `DoFixedTraps': do_traps.c:248: warning: implicit declaration of function `XRenderAddTraps' *** Error code 1 Stop in /usr/ports/x11/xorg-clients/work/xc/programs/x11perf. *** Error code 1 Stop in /usr/ports/x11/xorg-clients/work/xc/programs. *** Error code 1 Stop in /usr/ports/x11/xorg-clients. *** Error code 1 Stop in /usr/ports/net/vnc. Any ideas how I can workaround this? Regards to all, -Colin -- Colin J. Raven FreeBSD 5.3-RELEASE - http://www.FreeBSD.org - There can be only One Mon Jan 31 21:20:00 CET 2005 9:20PM up 11 days, 10:10, 9 users, load averages: 0.00, 0.00, 0.03 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vpnc and vnc question
Hello list, I am trying to connect to my work desktop (Windows 2003 Server) using vnc on my FreeBSD 5.3 box. I have been able to connect to the vpn using vpnc but it seems that my freebsd box is still using my local network for name resolution because I can't get to my work computer. I'm trying to use the machine name but it can't resolve that name. Any ideas? I'm very new to this technology. Thanks, Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: RDEsktop/VNC questions
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Olaf Hoyer Sent: Saturday, November 13, 2004 1:20 AM To: Butterworth, Thaddaeus (Manpower Contract) Cc: [EMAIL PROTECTED] Subject: RE: RDEsktop/VNC questions On Wed, 10 Nov 2004, Butterworth, Thaddaeus (Manpower Contract) wrote: So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? snip I've used the rdesktop client for connecting to a Windows 2003 Server (/usr/ports/net/rdesktop). I wasn't that impressed but then again it could have been a PEBKAC situation. I could not get the screen resolution of the Windoze 2003 server to go anything beyond 640x480 and it looked horribly grainy. Other than that, it did actually connect and allowed me to do all that I needed to. I just couldn't handle the graphic element, which again may have been more a user issue than an issue with the program. Other than that, I have used the Windows RDC programs and they work ok. Thad I use rdesktop regularly to administer some of our Win2003 Servers, and it works well. Special trick is, that I need to hop first on a jumppad, where an extra NIC is attached to the dedicated management VLAN of the Win boxes, and then hop on them via X-forwarded rdesktop- works well, despite that jumppad is a small old crappy Pentium-II, which is also busy doing some other things... so: ssh -X jumppad rdesktop -g 1024x768 win-server That shall give you some window in 1024x768, normal is 800x600 in standard mode. when its smaller, I guess you havent configured the Graphics driver, or its set to standard VGA. Win (also for remote connections) sometimes looks after that settings... HTH Olaf -- Olaf Hoyer[EMAIL PROTECTED] Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese) Thanks. I'll have to try that. Thad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: RDEsktop/VNC questions
On Wed, 10 Nov 2004, Butterworth, Thaddaeus (Manpower Contract) wrote: So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? snip I've used the rdesktop client for connecting to a Windows 2003 Server (/usr/ports/net/rdesktop). I wasn't that impressed but then again it could have been a PEBKAC situation. I could not get the screen resolution of the Windoze 2003 server to go anything beyond 640x480 and it looked horribly grainy. Other than that, it did actually connect and allowed me to do all that I needed to. I just couldn't handle the graphic element, which again may have been more a user issue than an issue with the program. Other than that, I have used the Windows RDC programs and they work ok. Thad I use rdesktop regularly to administer some of our Win2003 Servers, and it works well. Special trick is, that I need to hop first on a jumppad, where an extra NIC is attached to the dedicated management VLAN of the Win boxes, and then hop on them via X-forwarded rdesktop- works well, despite that jumppad is a small old crappy Pentium-II, which is also busy doing some other things... so: ssh -X jumppad rdesktop -g 1024x768 win-server That shall give you some window in 1024x768, normal is 800x600 in standard mode. when its smaller, I guess you havent configured the Graphics driver, or its set to standard VGA. Win (also for remote connections) sometimes looks after that settings... HTH Olaf -- Olaf Hoyer[EMAIL PROTECTED] Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
On Nov 10, 2004, at 6:14 PM, Louis LeBlanc wrote: Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? I've used them both (RDP protocol client and various VNC clients on different platforms), and they're for two different things. RDP (the RDC client) is for connecting to Windows Terminal Services; you get a desktop login of your own in your own session. VNC takes remote control of a desktop running the server application. RDP is a hack to turn Windows into a multi user system, while VNC is single-user implementation. Which one should you start with? Depends on the platform and what you're trying to do. If you have a Windows Terminal Server, an RDP client is the way to go. If you don't...VNC is the way to go :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
On Nov 10, 2004, at 6:45 PM, Matthew T. Lager wrote: rdesktop (net/rdesktop) is flawless. Use it everday to manage my Windows 2000 Servers. Supports many many many different features. Highly recommened. I'd also add that the WTS is encrypted. I don't believe VNC does much to encrypt the connection, so it should be wrapped in SSH if possible or used over only a trusted network. At least that's my understanding of it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
On Nov 10, 2004, at 6:14 PM, Bart Silverstrim wrote: Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) Virtual Network Computing Regards, Gary Hayers IT Support Unix Administrator WENN.com World Entertainment News Network ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
On 11/10/04 06:14 PM, Louis LeBlanc sat at the `puter and typed: Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou Very cool feedback. Thank you all. I'll start looking into the terminal service (it didn't get installed with W2K, but I haven't checked out XP Pro yet) and use VNC in the meantime. I'll be using it to write Word docs mostly, and if it's efficient enough, I might just see how well Escape Velocity works (I know, probably not at all). Network security isn't an issue because it's all my personal network behind a firewall. Thanks again. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ There is an old time toast which is golden for its beauty. When you ascend the hill of prosperity may you not meet a friend. -- Mark Twain ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
On Thursday 11 November 2004 10:38 am, Louis LeBlanc wrote: On 11/10/04 06:14 PM, Louis LeBlanc sat at the `puter and typed: Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou Very cool feedback. Thank you all. I'll start looking into the terminal service (it didn't get installed with W2K, but I haven't checked out XP Pro yet) and use VNC in the meantime. I'll be using it to write Word docs mostly, and if it's efficient enough, I might just see how well Escape Velocity works (I know, probably not at all). Network security isn't an issue because it's all my personal network behind a firewall. Thanks again. Lou I'm entering this thread late; so please forgive me if I'm duplicating someone else's input. One of TightVNC's enhancements over VNC is the ability to access the server from a web browser. TightVNC listens on port 5800 + the display number. Therefore, if you would normally use a vncviewer to access the TightVNC server 192.168.0.1:1, you could also access the desktop using any gui internet browser at: http://192.168.0.1:5801/ (I have NOT tested this from browser on a pda or cell phone.) TightVNC is available for many operating systems including FreeBSD (it's in the ports), Windows and Linux. I don't think it's available for Mac OSX. Best of luck, Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
Louis LeBlanc wrote: Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou In my experience, vnc is painfully slow. rdesktop on the other hand has always performed to my full satisfaction. On Unix machines (and IIRC OSX, as well) you can also use X11 (preferrably tunneled through ssh). Kind regards, Benjamin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
On Thursday 11 November 2004 02:27 pm, Benjamin Walkenhorst wrote: Louis LeBlanc wrote: Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou In my experience, vnc is painfully slow. rdesktop on the other hand has always performed to my full satisfaction. On Unix machines (and IIRC OSX, as well) you can also use X11 (preferrably tunneled through ssh). Kind regards, Benjamin In addition to being secure, tunnelling apps through ssh allows you to minimize the number of ports you leave open in your firewall. (In fact, I think rsync works through ssh by default. You can also start a ssh connection from within kermit for a secure kermit connection.) Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: RDEsktop/VNC questions
use /usr/ports/net/tsclient too if you're on rdp more than vnc GUI to rdesktop (still got some limitation than CLI) James H -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Louis LeBlanc Sent: Thursday, November 11, 2004 10:15 AM To: FreeBSD Questions Subject: RDEsktop/VNC questions Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Pickle's Law: If Congress must do a painful thing, the thing must be done in an odd-number year. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RDEsktop/VNC questions
Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Pickle's Law: If Congress must do a painful thing, the thing must be done in an odd-number year. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
On Thu, 2004-11-11 at 10:14, Louis LeBlanc wrote: Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou VNC is great - been using it since 2000 we use the windows version for M$ hosts and I can grab my FreeBSD workstation (XFree86/FBSD4.9) from my laptop and can grab the laptop and other hosts from the FBSD box just as easily the current versions are very light on bandwidth too (useful as I often hook machines in Sydney from our Melbourne office via our frame relay link. Used to clobber the link but now is mostly un-noticable) -- Murray Taylor Special Projects Engineer - Bytecraft Systems Entertainment P: +61 3 8710 2555 F: +61 3 8710 2599 D: +61 3 9238 4275 M: +61 417 319 256 E: [EMAIL PROTECTED] or visit us on the web http://www.bytecraftsystems.com http://www.bytecraftentertainment.com --- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --- This Email has been scanned for Viruses by MailMarshal. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RDEsktop/VNC questions
rdesktop (net/rdesktop) is flawless. Use it everday to manage my Windows 2000 Servers. Supports many many many different features. Highly recommened. Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Pickle's Law: If Congress must do a painful thing, the thing must be done in an odd-number year. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: RDEsktop/VNC questions
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd-[EMAIL PROTECTED] On Behalf Of Louis LeBlanc Sent: Wednesday, November 10, 2004 4:15 PM To: FreeBSD Questions Subject: RDEsktop/VNC questions Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Pickle's Law: If Congress must do a painful thing, the thing must be done in an odd-number year. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-[EMAIL PROTECTED] I've used the rdesktop client for connecting to a Windows 2003 Server (/usr/ports/net/rdesktop). I wasn't that impressed but then again it could have been a PEBKAC situation. I could not get the screen resolution of the Windoze 2003 server to go anything beyond 640x480 and it looked horribly grainy. Other than that, it did actually connect and allowed me to do all that I needed to. I just couldn't handle the graphic element, which again may have been more a user issue than an issue with the program. Other than that, I have used the Windows RDC programs and they work ok. Thad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: RDEsktop/VNC questions
Hmm, I havn't used it with Windows 2003 server yet, good to know. Thanks! -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd-[EMAIL PROTECTED] On Behalf Of Louis LeBlanc Sent: Wednesday, November 10, 2004 4:15 PM To: FreeBSD Questions Subject: RDEsktop/VNC questions Quick question about interconnectivity. You OSX users may be familiar with a very slick little utility called RDC (Remote Desktop Connection). Some of you other *BSDers may also be familiar with one called VNC (Visual Network Connection ?) or RDP (?). The purpose of said utilities is to provide a sort of graphical shell similar to an X session from a remote machine in a window. There are several rdesktop and vnc clients in the ports, so rather than go through the flurry of install-tryout-uninstall/repeat, I figured I'd go to the place to ask questions. Here. So, who's using these clients, and how effective have you been finding them? Any gotchas? How cool is it? Do they just plain suck? And more to the point, which one(s) should I start with on the short list? All feedback is welcome - and appreciated. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Pickle's Law: If Congress must do a painful thing, the thing must be done in an odd-number year. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-[EMAIL PROTECTED] I've used the rdesktop client for connecting to a Windows 2003 Server (/usr/ports/net/rdesktop). I wasn't that impressed but then again it could have been a PEBKAC situation. I could not get the screen resolution of the Windoze 2003 server to go anything beyond 640x480 and it looked horribly grainy. Other than that, it did actually connect and allowed me to do all that I needed to. I just couldn't handle the graphic element, which again may have been more a user issue than an issue with the program. Other than that, I have used the Windows RDC programs and they work ok. Thad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: anyone gotten vnc 4.0 to compile yet?
I got it to compile by placing #include sys/types.h in vncsrc/xc/programs/Xserver/vnc/XserverDesktop.h on line 34 (just after the #include os.h) I built this against the X430src- tree on FreeBSD 4.7. I then copied the vnc.so module to a FreeBSD 4.10-STABLE box running Xorg 6.7. The 4.10 box is running with i810 drivers. I also tried the module on a 5-latest laptop with DRM enabled and ATI Radeon drivers. When I connected, the laptop screen started flickering and the laptop locked up hard. Power cycle to recover. I haven't tried it with the DRM disabled. I modified the XF86Config file as per the instructions on RealVNC's page: http://www.realvnc.com/v4/x0.html If your native X server is an XFree86 version 4 server, then the vnc.so module should be copied to the /usr/X11R6/lib/modules/extensions directory. It can be enabled like any other module by adding a Load vnc line to the Module section of XF86Config. The parameters listed in the Xvnc manual page can be set as options in XF86Config. You will need to set either the passwordFile parameter or set the securityTypes parameter to None if you really don't want any authentication. Note that options cannot be set in the Module section of XF86Config - try the Screen section. For example: Section Module ... Load vnc EndSection ... Section Screen ... Option passwordFile /root/.vnc/passwd EndSection -- Alan Edmonds +44 20 8762 5195 Office +44 7950 203 918 Mobile Infrastructure Specialist T-Mobile International ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vnc and nat
Hi, My brain feels a little fuzzy right now and I need to have this working a few hours ago. I need to connect to some vnc servers behind a natd/ipfw machine. The setup is: me(10.10.10.10)-~-rl0(20.20.20.20) nat/ipfw rl1(192.168.0.1)--(192.168.0.4)vnc On the nat/ipfw machine here's an except from ipfw rules: 01350 14 728 allow log tcp from 10.10.10.10 to me dst-port 5900-5999 keep-state 01500 65005 34232225 divert 8668 ip from any to any via rl0 1550429 163094 allow log tcp from any to 192.168.0.4 And here's the nat config file: # cat /etc/natd.conf interface rl0 redirect_port tcp 192.168.0.4:5900-5999 5900-5999 redirect_port udp 192.168.0.4:5900-5999 5900-5999 use_sockets same_ports unregistered_only log log_denied log_ipfw_denied But the packets are not redirected: kernel: ipfw: 1350 Accept TCP 10.10.10.10:64010 82.76.1.117:5900 in via rl0 kernel: Connection attempt to TCP 20.20.20.20:5900 from 10.10.10.10:64010 fla gs:0x02 kernel: ipfw: 1350 Accept TCP 20.20.20.20:5900 10.10.10.10:64010 out via rl0 Telneting from nat/ipfw machine to 192.168.0.4 connects to the vnc server. What am I doing wrong ? Thanks, -- IOnut Unregistered ;) FreeBSD user 5.3-BETA4 - try `sysctl debug.witness_watch=0` and prepare to fly :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
anyone gotten vnc 4.0 to compile yet?
im getting the following error. making all in programs/Xserver/vnc... rm -f vncExtInit.o LD_LIBRARY_PATH=../../../exports/lib c++ -c -O2 -I../include -I../../../include/extensions -I.. /../../exports/include/X11 -I../../../include/fonts -I../mfb -I../mi -I../../../. . -I../../../../vncconfig -I../../.. -I../../../exports/include -DCSRG_BASED -DCSRG_BASED -DSH APE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPAN ORAMIX -DRENDER -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -D X_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DGC_HAS_COMPOSITE_CLIP -UXFree86LOADER vncExtInit.cc In file included from vncExtInit.cc:51: XserverDesktop.h:64: `fd_set' was not declared in this scope XserverDesktop.h:64: `fds' was not declared in this scope XserverDesktop.h:64: variable or field `blockHandler' declared void XserverDesktop.h:65: `fd_set' was not declared in this scope XserverDesktop.h:65: `fds' was not declared in this scope XserverDesktop.h:65: syntax error before `)' XserverDesktop.h:65: variable or field `wakeupHandler' declared void XserverDesktop.h:65: ANSI C++ forbids initialization of member `wakeupHandler' XserverDesktop.h:65: making `wakeupHandler' static XserverDesktop.h:65: ANSI C++ forbids in-class initialization of non-const static member `wakeupH andler' vncExtInit.cc: In function `void vncBlockHandler(void *, timeval **, void *)': vncExtInit.cc:219: `fd_set' undeclared (first use this function) vncExtInit.cc:219: (Each undeclared identifier is reported only once vncExtInit.cc:219: for each function it appears in.) vncExtInit.cc:219: `fds' undeclared (first use this function) vncExtInit.cc:219: syntax error before `)' vncExtInit.cc: In function `void vncWakeupHandler(void *, int, void *)': vncExtInit.cc:251: syntax error before `)' *** Error code 1 Stop in /usr/home/jason/temp/vnc-4.0-unixsrc/xc/programs/Xserver/vnc. *** Error code 1 Stop in /usr/home/jason/temp/vnc-4.0-unixsrc/xc/programs/Xserver. [EMAIL PROTECTED] Xserver $ Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC on different port
[EMAIL PROTECTED] wrote: How would I set up the encrypted port tunneling? Something like: ssh -L 5900:your.host.name:5900 your.host.name should work. You can then connect to port 5900 on the local machine, and it will be forwarded to your.host.name. Note also that you can forward X11 connections like this as well. The ssh man page has more. With your setup, you'll still need the nat forwarding on the FreeBSD firewall, unless you're able to ssh directly to the machine running vnc. Thomas G. Knight ADP - Data Center Team [EMAIL PROTECTED] (801) 956-7449 Don't worry if you're a kleptomaniac, you can always take something for it. -- Unknown -Original Message- From: Bill Moran [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 1:59 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: VNC on different port [EMAIL PROTECTED] wrote: My configuration is as follows: --- --- - -- | VNC | --- --- | FreeBSD | --- --- | Work Firewall | --- --- | ME | --- --- - -- I am trying to redirect ports so I can get out through my works firewall into my VNC Server. I can get it to work on port 8080 but not on 80 or 20 or 21. My work only allows 20, 21, 22, 80 through the firewall. Please see the example below. This does work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:8080 This does not work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:80 Any one have any idea's? If your work uses a transparent proxy for port 80, it's going to see the VNC traffic as invalid HTTP data and probably mangle it or drop it. You'd actually be better off using ssh to do encrypted port tunnelling, since your firewall allows it already. Running VNC unencrypted across the Internet is dangerous. Either way, try one of the other available ports. Port 22 unlikely to be proxied in any case. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC on different port
My configuration is as follows: --- --- - -- | VNC | --- --- | FreeBSD | --- --- | Work Firewall | --- --- | ME | --- --- - -- I am trying to redirect ports so I can get out through my works firewall into my VNC Server. I can get it to work on port 8080 but not on 80 or 20 or 21. My work only allows 20, 21, 22, 80 through the firewall. Please see the example below. This does work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:8080 This does not work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:80 Any one have any idea's? Thanks, Thomas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC on different port
[EMAIL PROTECTED] wrote: My configuration is as follows: --- --- - -- | VNC | --- --- | FreeBSD | --- --- | Work Firewall | --- --- | ME | --- --- - -- I am trying to redirect ports so I can get out through my works firewall into my VNC Server. I can get it to work on port 8080 but not on 80 or 20 or 21. My work only allows 20, 21, 22, 80 through the firewall. Please see the example below. This does work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:8080 This does not work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:80 Any one have any idea's? If your work uses a transparent proxy for port 80, it's going to see the VNC traffic as invalid HTTP data and probably mangle it or drop it. You'd actually be better off using ssh to do encrypted port tunnelling, since your firewall allows it already. Running VNC unencrypted across the Internet is dangerous. Either way, try one of the other available ports. Port 22 unlikely to be proxied in any case. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: VNC on different port
How would I set up the encrypted port tunneling? Thomas G. Knight ADP - Data Center Team [EMAIL PROTECTED] (801) 956-7449 Don't worry if you're a kleptomaniac, you can always take something for it. -- Unknown -Original Message- From: Bill Moran [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 1:59 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: VNC on different port [EMAIL PROTECTED] wrote: My configuration is as follows: --- --- - -- | VNC | --- --- | FreeBSD | --- --- | Work Firewall | --- --- | ME | --- --- - -- I am trying to redirect ports so I can get out through my works firewall into my VNC Server. I can get it to work on port 8080 but not on 80 or 20 or 21. My work only allows 20, 21, 22, 80 through the firewall. Please see the example below. This does work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:8080 This does not work: redirect_port tcp 10.0.3.21:5900 166.70.126.172:80 Any one have any idea's? If your work uses a transparent proxy for port 80, it's going to see the VNC traffic as invalid HTTP data and probably mangle it or drop it. You'd actually be better off using ssh to do encrypted port tunnelling, since your firewall allows it already. Running VNC unencrypted across the Internet is dangerous. Either way, try one of the other available ports. Port 22 unlikely to be proxied in any case. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Terminal VNC server
I have setup a terminal VNC server, and half-documented the way I did it at http://oxo.rucus.net/docs/Terminal-Vnc-HOWTO I am the sysadmin of a multi-user box and I am doing this for the plebs who are members of the computer society (RUCUS http://rucus.ru.ac.za/). What I want is an easy way of making vnc connections secure. The machine is firewalled from outside the LAN, but obviously not from inside it. I still don't like unencrypted data flowing over the network. For my own use, I use ssh tunnels to do the encryption, but that is far beyond your Random Joe Fuc^WUser. How can I make the connections over vnc secure? I would prefer not to delve into the source code, but will if I have to. TIA, -Ox -- /~\ The ASCII ASCII stupid question, get a EBCDIC ANSI. \ / Ribbon Campaign John Oxley X Against HTMLhttp://oxo.rucus.net/ / \ Email! oxo at rucus.ru.ac.za Personally, I'd rather pay for my freedom than live in a bitmapped, pop-up-happy dungeon like NT. -- Thomas Scoville ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
howto serve vnc ipv4
on freebsd 4.9 kde 3.2 or less for that matter i only get desktop sharing (vnc:5[98]00) on ipv6 does anyone now how to get this to work on ipv4 thanx mario; - - - - - - - - House Of Sites - - - - - - - - Web Design :: Programming :: Hosting :: Maintenance Web site: http://www.HouseOfSites.net Email: [EMAIL PROTECTED] Tel: 415-242-3376 Do you schmut!? http://www.schmut.com http://blog.schmut.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vnc-4.0b4
FreeBSD team, anyone gotten the Xvnc server out of this to compile correctly from source on 4.9-STABLE? if so, whats the secret? ;) Ive tried building with make and gmake and get errors both ways. Googling didnt seem to get me any answers. regards, Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Differences between net/vnc ports ?
On Sun, 8 Feb 2004 22:07:44 +1100 Tony Frank [EMAIL PROTECTED] wrote: Hi, On Sun, Feb 08, 2004 at 02:15:11AM +0200, Ion-Mihai Tetcu wrote: In ports/net/ there are 6 vnc ports. Leaving alone vnc2swf could someone tell from experience the difference between them ? For now I am interested in vnc clients to access a mixture of 98/xp/2000 machines, but any other info would be appreciated. I personally have had great success with TridiaVNC. Although it is a little old now I can get the same feature set on all platforms - w32, freebsd, solaris and they all interwork just fine. Thank you, that is what I'm after. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Differences between net/vnc ports ?
Hi, On Sun, Feb 08, 2004 at 02:15:11AM +0200, Ion-Mihai Tetcu wrote: In ports/net/ there are 6 vnc ports. Leaving alone vnc2swf could someone tell from experience the difference between them ? For now I am interested in vnc clients to access a mixture of 98/xp/2000 machines, but any other info would be appreciated. I personally have had great success with TridiaVNC. Although it is a little old now I can get the same feature set on all platforms - w32, freebsd, solaris and they all interwork just fine. In other experience most versions will interwork with the basic features. If you want some fancy specific features then you need to investigate the offerings of each individual version. Best regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Differences between net/vnc ports ?
Hi, In ports/net/ there are 6 vnc ports. Leaving alone vnc2swf could someone tell from experience the difference between them ? For now I am interested in vnc clients to access a mixture of 98/xp/2000 machines, but any other info would be appreciated. Thanks. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgraded 5.1 - 5.2, now VNC over SSH fails w/ TCP_NODELAY
On Tue, 20 Jan 2004 11:42:28 -0500, Scott I. Remick wrote: Well crap, everything was going so well. I upgraded from 5.1 to 5.2 using cvsup, recompiled (nearly) all my ports (some KDE stuff is still complaining, but that shouldn't be relevant here). I have openssh installed via ports: su-2.05b# pkg_info | grep ssh openssh-3.6.1_5 OpenBSD's secure shell client and server (remote login prog And my /etc/rc.conf contains: sshd_enable=YES sshd_program=/usr/local/sbin/sshd Under 5.1, I'd SSH in (via PuTTY), then use port-forwarding to forward localhost:7001 to remote:5901. I could then run VNC, connect to localhost:7001, and tunnel my VNC session over SSH. Since upgrading to 5.2 (nothing else has changed), while I can still SSH in, attempting to tunnel VNC fails and I get the following error in my PuTTY log: 2004-01-20 11:34:21 Opening forwarded connection to localhost:5901 2004-01-20 11:34:22 Forwarded connection refused by server On the FreeBSD box, I see: Jan 20 11:33:57 scott sshd[78580]: error: getsockopt TCP_NODELAY: Connection reset by peer This is using the same configs, profiles, etc. Nothing has changed except the upgrade of the FreeBSD box from 5.1 to 5.2. Any thoughts? Sorry to reply to my own post, but I'm still stuck and had more info to offer. I've also tried adding the following line to my rc.conf: sshd_flags=-f /usr/local/etc/ssh/sshd_config And in that sshd_config file, I added the following lines: GatewayPorts yes Although I'm not sure this applies. It's definitely using that config: su-2.05b# ps -ax | grep sshd 426 ?? Is 0:00.07 /usr/local/sbin/sshd -f /usr/local/etc/ssh/sshd_config 1807 ?? Is 0:00.03 sshd: scott [priv] (sshd) 1809 ?? R 0:00.07 sshd: [EMAIL PROTECTED] (sshd) vncserver is definitely running: su-2.05b# ps -ax | grep vnc 1798 p0- S 0:00.23 Xvnc :1 -desktop X -httpd /usr/X11R6/share/tightvnc/classes -auth /home/scott Also: su-2.05b# strobe -b 5900 -e 6000 localhost strobe 1.05 (c) 1995-1999 Julian Assange [EMAIL PROTECTED]. localhost 5901 unassigned unknown - RFB 003.003\n I've also confirmed that I can VNC in using another PC on the local network. But none of this has helped and I still get the error when I try to tunnel VNC over ssh. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgraded 5.1 - 5.2, now VNC over SSH fails w/ TCP_NODELAY
Well crap, everything was going so well. I upgraded from 5.1 to 5.2 using cvsup, recompiled (nearly) all my ports (some KDE stuff is still complaining, but that shouldn't be relevant here). I have openssh installed via ports: su-2.05b# pkg_info | grep ssh openssh-3.6.1_5 OpenBSD's secure shell client and server (remote login prog And my /etc/rc.conf contains: sshd_enable=YES sshd_program=/usr/local/sbin/sshd Under 5.1, I'd SSH in (via PuTTY), then use port-forwarding to forward localhost:7001 to remote:5901. I could then run VNC, connect to localhost:7001, and tunnel my VNC session over SSH. Since upgrading to 5.2 (nothing else has changed), while I can still SSH in, attempting to tunnel VNC fails and I get the following error in my PuTTY log: 2004-01-20 11:34:21 Opening forwarded connection to localhost:5901 2004-01-20 11:34:22 Forwarded connection refused by server On the FreeBSD box, I see: Jan 20 11:33:57 scott sshd[78580]: error: getsockopt TCP_NODELAY: Connection reset by peer This is using the same configs, profiles, etc. Nothing has changed except the upgrade of the FreeBSD box from 5.1 to 5.2. Any thoughts? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[4.9-R] Ip forwarding for internal VNC.
Hi everybody, I have the following setup: FreeBSD Server (4.9-R) 2 NIC's [xl0,Public Range IP, 196.xx.xx.xx] [xl1,Private Range IP, 192.168.0.1] Windows 2k server [Private IP, 192.168.0.2] The Windows 2000 server is running VNC and is serving as an application server for windows software that is not-so-stable on FreeBSD. :P (The windows machine is not connected directly to the Internet for obvious reasons ;) ) What I want: I want to be able to connect to the VNC service running on the Windows machine, via the Internet. Is it possible to set up port forwarding so that if I connect to the FreeBSD machine on port 5800, the request be forwarded to the Windows machine on port 5800? Do I need to set up the FreeBSD machine in any specific way to accomplish this setup? Thank you in advance. Please copy me in any replies, as I am only subscribed to the digest. Thank you. Regards Jaco van Tonder ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: Re: [4.9-R] Ip forwarding for internal VNC.]
Sorry, forgot to Cc list: [xl0,Public Range IP, 196.xx.xx.xx] [xl1,Private Range IP, 192.168.0.1] Windows 2k server [Private IP, 192.168.0.2] The Windows 2000 server is running VNC and is serving as an application server for windows software that is not-so-stable on FreeBSD. :P (The windows machine is not connected directly to the Internet for obvious reasons ;) ) What I want: I want to be able to connect to the VNC service running on the Windows machine, via the Internet. Put the following in your natd.conf file: redirect_port tcp 192.168.0.2:5800 5800 then HUP natd. Steve Is it possible to set up port forwarding so that if I connect to the FreeBSD machine on port 5800, the request be forwarded to the Windows machine on port 5800? Do I need to set up the FreeBSD machine in any specific way to accomplish this setup? Thank you in advance. Please copy me in any replies, as I am only subscribed to the digest. Thank you. Regards Jaco van Tonder ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [4.9-R] Ip forwarding for internal VNC.
On Fri, Dec 19, 2003 at 09:12:22PM +0200, [EMAIL PROTECTED] wrote: Hi everybody, I have the following setup: FreeBSD Server (4.9-R) 2 NIC's [xl0,Public Range IP, 196.xx.xx.xx] [xl1,Private Range IP, 192.168.0.1] Windows 2k server [Private IP, 192.168.0.2] The Windows 2000 server is running VNC and is serving as an application server for windows software that is not-so-stable on FreeBSD. :P (The windows machine is not connected directly to the Internet for obvious reasons ;) ) What I want: I want to be able to connect to the VNC service running on the Windows machine, via the Internet. Is it possible to set up port forwarding so that if I connect to the FreeBSD machine on port 5800, the request be forwarded to the Windows machine on port 5800? Do I need to set up the FreeBSD machine in any specific way to accomplish this setup? Don't do that. Use ssh port forwarding; that way the tunnel only exists when you want it to, and you will be the only person who can use it. Check the ssh manpage for details; see the -L option. Ceri -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Way OT: SSH+VNC as quickndirty VPN
Here's the scenario: I have a Windows machine at work. I have a VNC server on it. It is behind a firewall over which I have no control, so I cannot make a direct connection to this machine from outside. What I'd like to do is to initiate a SSH connection (with compression) to my BSD machine at home (which I can do) and forward the VNC server connection through that SSH tunnel. I'd like to then lock my workstation and office, go home, and use vncviewer to have access to my workstation at work. That way I can do work at odd hours and while watching Buffy the Vampire Slayer. Is this possible? I have tried a few combinations of port forwarding, but for whatever reason, find it unintuitive. Can't quite get it to work. Any suggestions much appreciated. -John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Way OT: SSH+VNC as quickndirty VPN
On 0, Goodleaf, John M [EMAIL PROTECTED] wrote: : :Here's the scenario: :I have a Windows machine at work. I have a VNC server on it. It is behind a :firewall over which I have no control, so I cannot make a direct connection :to this machine from outside. What I'd like to do is to initiate a SSH :connection (with compression) to my BSD machine at home (which I can do) and :forward the VNC server connection through that SSH tunnel. I'd like to then :lock my workstation and office, go home, and use vncviewer to have access to :my workstation at work. That way I can do work at odd hours and while :watching Buffy the Vampire Slayer. : :Is this possible? I have tried a few combinations of port forwarding, but :for whatever reason, find it unintuitive. Can't quite get it to work. Any :suggestions much appreciated. I agree, it is counter-intuitive, but I know it mostly works on a Unix-to- Unix connection, but I have forgotten how to set it up. There may be a problem with doing it with windows as the server, though. vnc can only grant access to a single session in windows, and that session's display is based on reading the video frame buffer. This generally would mean that you can't simultaneously lock your machine and do work on it at the same time from home. In other words, when you login from home, everything you do will be displayed on the windows machine in your office while you are doing it. -- Allan Bowhill [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
VNC ssh tunneling problem: getsockopt TCP_NODELAY error
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
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]
