From owner-freebsd-isp  Tue Jan 11 20:50:23 2000
Delivered-To: freebsd-isp@freebsd.org
Received: from misery.sdf.com (misery.sdf.com [204.244.213.49])
	by hub.freebsd.org (Postfix) with ESMTP id 5E00E154D4
	for <isp@freebsd.org>; Tue, 11 Jan 2000 20:50:15 -0800 (PST)
	(envelope-from tom@sdf.com)
Received: from tom (helo=localhost)
	by misery.sdf.com with local-esmtp (Exim 2.12 #1)
	id 128Fij-0002Zy-00; Tue, 11 Jan 2000 20:49:21 -0800
Date: Tue, 11 Jan 2000 20:49:18 -0800 (PST)
From: Tom <tom@sdf.com>
To: Shino <shino@hakkenden.com>
Cc: FreeBSD-ISP <isp@FreeBSD.ORG>
Subject: Re: FW: routed netbeui tcpdump
In-Reply-To: <NCEFJNEGOFKAEADCKNLPIEKHDDAA.shino@hakkenden.com>
Message-ID: <Pine.BSF.4.05.10001112047390.14799-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


> I have several router boxes running freebsd RouteD.  I thought routed only
> passed tcp packets but I am seeing netbeui and ipx packets as well... stuff
> I
> would only expect to see in a bridge situation.  Any thoughts on why routed
> might be passing netbeui packets?
> 
> Secondarily would tcpdump catch netbeui packets or just tcp packets?
> 
> Thanks!
> 
> Shino

  First of all, routed does not route packets.  Read the manpage on
what it is for.  You probably you don't even need it.

  tcpdump just shows what is on the wire, not what may be routed.

Tom



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message