From b.gohla@gmx.de Sun Jan 20 23:03:37 2002 Return-Path: X-Sender: b.gohla@gmx.de X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_0_1_3); 21 Jan 2002 07:03:36 -0000 Received: (qmail 73190 invoked from network); 21 Jan 2002 07:03:36 -0000 Received: from unknown (216.115.97.172) by m9.grp.snv.yahoo.com with QMQP; 21 Jan 2002 07:03:36 -0000 Received: from unknown (HELO mail.gmx.net) (213.165.64.20) by mta2.grp.snv.yahoo.com with SMTP; 21 Jan 2002 07:03:35 -0000 Received: (qmail 21383 invoked by uid 0); 21 Jan 2002 07:03:34 -0000 Received: from b7a22.pppool.de (HELO linux) (213.7.122.34) by mail.gmx.net (mp012-rz3) with SMTP; 21 Jan 2002 07:03:34 -0000 Content-Type: text/plain; charset="utf-8" To: lojban@yahoogroups.com Subject: Re: [lojban] SpeakFreely results Date: Mon, 21 Jan 2002 08:01:50 +0100 X-Mailer: KMail [version 1.2] References: In-Reply-To: MIME-Version: 1.0 Message-Id: <02012108015000.01014@linux> Content-Transfer-Encoding: quoted-printable From: =?utf-8?q?Bj=C3=B6rn=20Gohla?= Reply-To: b.gohla@gmx.de X-Yahoo-Group-Post: member; u=36703491 X-Yahoo-Profile: badbirdde -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 21 January 2002 07:01, Jim Carter wrote: > The server does IP masquerade (NAT), but it matches up laptop packets wit= h > their replies for DNS and NTP, so most likely it will do the same for any > port including 2074. Here's an excerpt from the server rules. sfmike sends from port 2075 as far as i can see, so matching up ports=20 properly on demand would require a special kernel module, like the ones for= =20 passive ftp or quake. - --=20 - -------------------- Something being fool-proof means it takes an engineer to break it. pub 1024D/834F4976 2001-01-07 Bj=C3=B6rn Gohla (Wissenschaftler, Weltb=C3= =BCrger)=20 Key fingerprint =3D 9FF4 FEDA CCDF DA0E 14D5 8129 6C14 3C39 834F 4976 sub 1024g/29571FE2 2001-01-07 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8S7zibBQ8OYNPSXYRAvybAJoCCy0GbHQ5+7ujdDNrb/sTRLiSTQCgknI2 lV9SUFaHL2J1gPsgsIdbvtU=3D =3DE3VB -----END PGP SIGNATURE-----