Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was

2005-10-17 Thread Erik Hofman

John Wojnaroski wrote:

you might try

http://sourceforge.net/projects/openatc

It died a quiet death when no one showed up for the network field test


Hmm, it looks like it started when the time wasn't right. I think we 
have enough momentum right now for a restart.


Erik

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was README.multiplayer update

2005-10-17 Thread Oliver Schroeder
Am Saturday 15 October 2005 23:45 schrieb Arnt Karlsen:
 ..we're not re-inventing pcproxy, are we?

No, at least I surely won't. 

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was README.multiplayer update

2005-10-16 Thread Vassilii Khachaturov
 network connection to a flight simulation network, such as VATSIM or
 IVAO, which is based on the fsd (Flight Simulator Daemon) protocol. This
 is particulary useful for players who wish to have multiple network
 clients active at the same time. In tech-terms, PCProxy is a
 multi-connect masquerading proxy for fsd traffic over TCP/IP.
  .
  PCProxy currently only supports networks which operate using the fsd
  protocol, like VATSIM and IVAO.

I think we're not --- the flightgear server/client comm is UDP based.
Reading into the upstream pages of pcproxy
http://www.leune.org/pcproxy/
I wonder if the flightgear server though
should support the fsd protocol at some future point of time
to be a gateway between our and VATSIM/IVAO flying...

V.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was

2005-10-16 Thread Martin Spott
Vassilii Khachaturov wrote:

 I wonder if the flightgear server though
 should support the fsd protocol at some future point of time
 to be a gateway between our and VATSIM/IVAO flying...

It's not a matter if it _should_ or not. The relevant details of the
protocol, at least as used by VASTIM, are 'closed',

Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was

2005-10-16 Thread Vassilii Khachaturov
  I wonder if the flightgear server though
  should support the fsd protocol at some future point of time
  to be a gateway between our and VATSIM/IVAO flying...

 It's not a matter if it _should_ or not. The relevant details of the
 protocol, at least as used by VASTIM, are 'closed',

Security by obscurity, as far as I am reading the forums... stupid.
Apparently the pcproxy is in Debian (which made me believe we can
interface the protocol, too) because it just forwards the packets
w/o examining their contents too much.

Hopefully one day we'll provide an open source alternative to that.

V.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was

2005-10-16 Thread Arnt Karlsen
On Sun, 16 Oct 2005 19:11:51 +0200 (IST), Vassilii wrote in message 
[EMAIL PROTECTED]:

   I wonder if the flightgear server though
   should support the fsd protocol at some future point of time
   to be a gateway between our and VATSIM/IVAO flying...
 
  It's not a matter if it _should_ or not. The relevant details of the
  protocol, at least as used by VASTIM, are 'closed',
 
 Security by obscurity, as far as I am reading the forums... stupid.
 Apparently the pcproxy is in Debian (which made me believe we can
 interface the protocol, too) because it just forwards the packets
 w/o examining their contents too much.
 
 Hopefully one day we'll provide an open source alternative to that.

..one way is simply set up a pcproxy box to interface between 
our stuff and the VATSIM/IVAO guys.  Or, between our stuff 
and http://www.wbfree.net/index.php  ;o)

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was

2005-10-16 Thread John Wojnaroski

you might try

http://sourceforge.net/projects/openatc

It died a quiet death when no one showed up for the network field test

JW

Vassilii Khachaturov wrote


I wonder if the flightgear server though
should support the fsd protocol at some future point of time
to be a gateway between our and VATSIM/IVAO flying...
 


It's not a matter if it _should_ or not. The relevant details of the
protocol, at least as used by VASTIM, are 'closed',
   



Security by obscurity, as far as I am reading the forums... stupid.
Apparently the pcproxy is in Debian (which made me believe we can
interface the protocol, too) because it just forwards the packets
w/o examining their contents too much.

Hopefully one day we'll provide an open source alternative to that.

V.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


 




___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was

2005-10-16 Thread Martin Spott
Vassilii Khachaturov wrote:
  I wonder if the flightgear server though
  should support the fsd protocol at some future point of time
  to be a gateway between our and VATSIM/IVAO flying...

 It's not a matter if it _should_ or not. The relevant details of the
 protocol, at least as used by VASTIM, are 'closed',
 
 Security by obscurity, as far as I am reading the forums... stupid.

Indeed, and I find it very annoying. Instead of developing our own ATC
network strategies if would be terribly nice if we could simply jump on
that train - without violating copyrights, NDA's or whatever 

 Hopefully one day we'll provide an open source alternative to that.

Yes, but we should take into account that it takes a while until we
have such a network infrastructure that offers ATC service at almost
every medium large airport areound the clock  ;-)

Cheers,
Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] ..we're not re-inventing pcproxy?, was

2005-10-16 Thread John Wojnaroski



Martin Spott wrote:


Vassilii Khachaturov wrote:
 


I wonder if the flightgear server though
should support the fsd protocol at some future point of time
to be a gateway between our and VATSIM/IVAO flying...
   


It's not a matter if it _should_ or not. The relevant details of the
protocol, at least as used by VASTIM, are 'closed',
 


Security by obscurity, as far as I am reading the forums... stupid.
   



Indeed, and I find it very annoying. Instead of developing our own ATC
network strategies if would be terribly nice if we could simply jump on
that train - without violating copyrights, NDA's or whatever 

 


Hopefully one day we'll provide an open source alternative to that.
   



Yes, but we should take into account that it takes a while until we
have such a network infrastructure that offers ATC service at almost
every medium large airport areound the clock  ;-)

Cheers,
Martin.

But if it could be combined with Dave Culp's AI controller then you 
might have, at least,
a 'silicon-based' based controller available on demand and plug-in when 
the 'carbon-based'

controller was not available. Throw in some tts and speech recognition...

Not a trivial task or something you build over a weekend.  Probably a 
job bigger and more

complex that eclipses all of effort put forth on Flightgear to date.

Any volunteers???:-)

Regards
John W.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


[Flightgear-devel] ..we're not re-inventing pcproxy?, was README.multiplayer update

2005-10-15 Thread Arnt Karlsen
On Sat, 15 Oct 2005 11:36:22 +0200, Oliver wrote in message 
[EMAIL PROTECTED]:

 Am Freitag 14 Oktober 2005 19:28 schrieb Andy Ross:
 The NAT router will create a temporary IP/port combination for the
 client, and  this combination is what the server will see when
 receiving data. The server  assumes that this combination will not
 change. But this assumption is wrong,  especially with UDP as there is
 no connection. So the server has to reread  the port from the UDP
 header everytime it reseives new data from the client  and recreate a
 socket for it (and clse the existing one of course). That will result
 in multiple create/close socket operations per second for  every
 client. And that will simply result in multiple already in use
 errors  per second.
 You can argue that you've never noticed such NAT behavior, and you are
  possibly right. But it will really only work with a so called cone
  NAT 
 router, which will make IP/port combination persistent.
 
 Interesting reading, although not directly connected to this
 discussion, is: http://gnunet.org/papers/nat.pdf

..we're not re-inventing pcproxy, are we?
[EMAIL PROTECTED]:/var/www/01-gas/fmb.no/gas $ apt-cache --full show pcproxy
Package: pcproxy
Priority: optional
Section: games
Installed-Size: 196
Maintainer: Kees Leune [EMAIL PROTECTED]
Architecture: all
Version: 1.1.1-2
Depends: tk8.0 | tk8.2 | tk8.3 | tk8.4
Filename: pool/main/p/pcproxy/pcproxy_1.1.1-2_all.deb
Size: 38294
MD5sum: 8d02f7c3a9d11db4938697f32e3c0239
Description: A masquerading proxy for flight simulation networks
 PCProxy allows multiple flight simulation clients to share a single
network connection to a flight simulation network, such as VATSIM or
IVAO, which is based on the fsd (Flight Simulator Daemon) protocol. This
is particulary useful for players who wish to have multiple network
clients active at the same time. In tech-terms, PCProxy is a
multi-connect masquerading proxy for fsd traffic over TCP/IP.
 .
 PCProxy currently only supports networks which operate using the fsd
 protocol, like VATSIM and IVAO.
Tag: use::proxying



-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d