From owner-freebsd-questions Tue Jun 20 22:50:19 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from fedde.littleton.co.us (fedde.littleton.co.us [216.17.174.44])
by hub.freebsd.org (Postfix) with ESMTP id B5ADC37B84D
for <freebsd-questions@FreeBSD.ORG>; Tue, 20 Jun 2000 22:50:17 -0700 (PDT)
(envelope-from cfedde@fedde.littleton.co.us)
Received: from fedde.littleton.co.us (localhost [127.0.0.1])
by fedde.littleton.co.us (8.10.0/8.10.0) with ESMTP id e5L5oG102167;
Tue, 20 Jun 2000 23:50:16 -0600 (MDT)
Message-Id: <200006210550.e5L5oG102167@fedde.littleton.co.us>
To: "Daniel Schrock" <d_jab@anonymous-daemon.org>
Cc: "freebsd-questions" <freebsd-questions@FreeBSD.ORG>
Subject: Re: How to open ports for traffic?
In-Reply-To: <00c601bfdb3e$dfcd6b20$0271a8c0@anonymousdaemon.org>
From: Chris Fedde <chris@fedde.littleton.co.us>
Date: Tue, 20 Jun 2000 23:50:16 -0600
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 21 Jun 2000 00:09:27 -0500 "Daniel Schrock" wrote:
+------------------
| The ports in question are not normally even listed in /etc/services (they
| are game ports-one tcp/udp...5 udp...in the 21000 range)
+------------------
It may be that you'll need to set up some "scafolding" to find out what is
going on. You can set up a listener at some remote system on the port in
question then try to reach it by using the three argument form of telnet.
You may also try using a tool like traceroute to locate where the traffic
is being lost.
chris
--
Chris Fedde
303 773 9134
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message