RE: Kaboodle 0.99d and VNC
Heyaz. I released version 0.99d of Kaboodle today. As some might recall...when you use Kaboodle to connect two networks together using KaboodleProxy, you can VNC and file-transfer across a firewall/router without either side having to do any port-forwarding adjustments. No really. :) Through two *completely* closed firewalls, i.e. with no ports enabled/forwarded? Doesn't that imply that the firewalls really aren't doing a very good job? ;) Wez @ RealVNC Ltd. ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Kaboodle 0.99d and VNC
Wez: Heya. Yes: with no ports enabled/forwarded, two Kaboodle users can VNC and file-transfer with each other. As for what it implies about the firewalls...that's a very big it depends. Kaboodle uses the open-source echoWare.DLL to establish a long-term TCP connection with an echoServer called KaboodleProxy that acts as a relay between Kaboodle clients. So if the firewall is smart enough to block an echoWare to echoServer connection, then of course it won't work. But consumer-grade firewall/routers like LinkSys and Netgear products aren't that smart: by default, they will allow out any outbound connections. And since the echoServer owner can run that server on any port they want (443, for example), the connection will be passed on most commercial-grade firewalls -- with their out of the box configuration -- as well. With the echoWare/echoServer approach, all of the traffic looks like it's outgoing, from the perspective of the firewall. Which is, of course, the same approach that VNC's add client and SSH's reverse tunnels have been utilizing for years. cheers, Scott On Mon, 8 Nov 2004, James Weatherall wrote: Heyaz. I released version 0.99d of Kaboodle today. As some might recall...when you use Kaboodle to connect two networks together using KaboodleProxy, you can VNC and file-transfer across a firewall/router without either side having to do any port-forwarding adjustments. No really. :) Through two *completely* closed firewalls, i.e. with no ports enabled/forwarded? Doesn't that imply that the firewalls really aren't doing a very good job? ;) Wez @ RealVNC Ltd. ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Kaboodle 0.99d and VNC
Hi Scott, Understood. The system you describe will work provided that the required ports are enabled for outgoing access through the firewalls at both ends, and that someone somewhere is running the echoWare server, which I assume you provide yourself? Cheers, Wez @ RealVNC Ltd. -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: 08 November 2004 18:13 To: James Weatherall Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Kaboodle 0.99d and VNC Wez: Heya. Yes: with no ports enabled/forwarded, two Kaboodle users can VNC and file-transfer with each other. As for what it implies about the firewalls...that's a very big it depends. Kaboodle uses the open-source echoWare.DLL to establish a long-term TCP connection with an echoServer called KaboodleProxy that acts as a relay between Kaboodle clients. So if the firewall is smart enough to block an echoWare to echoServer connection, then of course it won't work. But consumer-grade firewall/routers like LinkSys and Netgear products aren't that smart: by default, they will allow out any outbound connections. And since the echoServer owner can run that server on any port they want (443, for example), the connection will be passed on most commercial-grade firewalls -- with their out of the box configuration -- as well. With the echoWare/echoServer approach, all of the traffic looks like it's outgoing, from the perspective of the firewall. Which is, of course, the same approach that VNC's add client and SSH's reverse tunnels have been utilizing for years. cheers, Scott On Mon, 8 Nov 2004, James Weatherall wrote: Heyaz. I released version 0.99d of Kaboodle today. As some might recall...when you use Kaboodle to connect two networks together using KaboodleProxy, you can VNC and file-transfer across a firewall/router without either side having to do any port-forwarding adjustments. No really. :) Through two *completely* closed firewalls, i.e. with no ports enabled/forwarded? Doesn't that imply that the firewalls really aren't doing a very good job? ;) Wez @ RealVNC Ltd. ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Kaboodle 0.99d and VNC
Wez: My company provides the echoServer application for anyone to run (it's Linux-only right now; a Windows one is being worked on). The idea is that a community of users will have one tech-savvy person who can run a server so the rest of the community doesn't have to sweat the details of firewalls or IP-addresses (or even dynamic DNS) anymore. Lots of value for $25, IMO. :) We're running a demo version of it for proof-of-concept with Kaboodle, but unlike GoToMyPC, we're interested in selling the server more than we are subscriptions to the service. cheers, Scott On Mon, 8 Nov 2004, James Weatherall wrote: Hi Scott, Understood. The system you describe will work provided that the required ports are enabled for outgoing access through the firewalls at both ends, and that someone somewhere is running the echoWare server, which I assume you provide yourself? Cheers, Wez @ RealVNC Ltd. -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: 08 November 2004 18:13 To: James Weatherall Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Kaboodle 0.99d and VNC Wez: Heya. Yes: with no ports enabled/forwarded, two Kaboodle users can VNC and file-transfer with each other. snip ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Kaboodle 0.99d and VNC
Scott, Fair enough. The only comment I'd make is that the claim that you can exchange files using Kaboodle without modifying any firewall settings is not correct - you need the echoServer machine's firewall to be properly configured to let connections in, and you need to be sure that both ends allow outgoing connections, at least to the echoServer port. Cheers, Wez @ RealVNC Ltd. -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: 08 November 2004 18:45 To: James Weatherall Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Kaboodle 0.99d and VNC Wez: My company provides the echoServer application for anyone to run (it's Linux-only right now; a Windows one is being worked on). The idea is that a community of users will have one tech-savvy person who can run a server so the rest of the community doesn't have to sweat the details of firewalls or IP-addresses (or even dynamic DNS) anymore. Lots of value for $25, IMO. :) We're running a demo version of it for proof-of-concept with Kaboodle, but unlike GoToMyPC, we're interested in selling the server more than we are subscriptions to the service. cheers, Scott On Mon, 8 Nov 2004, James Weatherall wrote: Hi Scott, Understood. The system you describe will work provided that the required ports are enabled for outgoing access through the firewalls at both ends, and that someone somewhere is running the echoWare server, which I assume you provide yourself? Cheers, Wez @ RealVNC Ltd. -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: 08 November 2004 18:13 To: James Weatherall Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Kaboodle 0.99d and VNC Wez: Heya. Yes: with no ports enabled/forwarded, two Kaboodle users can VNC and file-transfer with each other. snip ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Kaboodle 0.99d and VNC
Wez: A fair point: I should more accurately say that with the echoServer approach, *most* end users will not have to make any firewall adjustments. The person running the echoServer may have to, although they are not necessarily an end user of the client software which uses their server. Thanks for letting me clarify; I didn't mean to come across as misleading. cheers, Scott On Mon, 8 Nov 2004, James Weatherall wrote: Scott, Fair enough. The only comment I'd make is that the claim that you can exchange files using Kaboodle without modifying any firewall settings is not correct - you need the echoServer machine's firewall to be properly configured to let connections in, and you need to be sure that both ends allow outgoing connections, at least to the echoServer port. Cheers, Wez @ RealVNC Ltd. -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: 08 November 2004 18:45 To: James Weatherall Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Kaboodle 0.99d and VNC Wez: My company provides the echoServer application for anyone to run (it's Linux-only right now; a Windows one is being worked on). The idea is that a community of users will have one tech-savvy person who can run a server so the rest of the community doesn't have to sweat the details of firewalls or IP-addresses (or even dynamic DNS) anymore. Lots of value for $25, IMO. :) We're running a demo version of it for proof-of-concept with Kaboodle, but unlike GoToMyPC, we're interested in selling the server more than we are subscriptions to the service. cheers, Scott On Mon, 8 Nov 2004, James Weatherall wrote: Hi Scott, Understood. The system you describe will work provided that the required ports are enabled for outgoing access through the firewalls at both ends, and that someone somewhere is running the echoWare server, which I assume you provide yourself? Cheers, Wez @ RealVNC Ltd. -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: 08 November 2004 18:13 To: James Weatherall Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Kaboodle 0.99d and VNC Wez: Heya. Yes: with no ports enabled/forwarded, two Kaboodle users can VNC and file-transfer with each other. snip ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
