From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 21:57:07 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98D7716A41F for ; Fri, 9 Sep 2005 21:57:07 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3952043D46 for ; Fri, 9 Sep 2005 21:57:07 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j89Lv50u022427; Fri, 9 Sep 2005 17:57:05 -0400 (EDT) Date: Fri, 9 Sep 2005 17:57:05 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Peter Jeremy In-Reply-To: <20050909204453.GA89302@server.vk2pj.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: "Ryan P. Sommers" , hackers@freebsd.org Subject: Re: "Smart" Hubs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2005 21:57:07 -0000 On Sat, 10 Sep 2005, Peter Jeremy wrote: > On Fri, Sep 09, 2005 at 02:44:56PM -0400, Daniel Eischen wrote: > >On Fri, 9 Sep 2005, Brooks Davis wrote: > >> > On Fri, Sep 09, 2005 at 08:39:30AM -0600, Ryan P. Sommers wrote: > >> > > Hub in question is a linksys NH1005 v2. > >> > > > >> > > PS If anyone knows of a hub that's "easy" to find and still is an actuall > >> > > good 'ol hub, let me know. > ... > >> Alternativly, if you can get your hands on a second ethernet port for > >> your sniffer box, make a passive tap: > > > >I came in kinda late to this thread, but if you're trying to find > >a hub/switch in order to sniff network traffic, then you can always > >go for a switch that let's you monitor traffic on other ports. > >I know the Cisco's will let you do this, but I'd be suprised if > >you couldn't find it on some other cheaper switches. > > I think most managed switches let you do this. The keyword being > "managed" and a managed switch is always going to be far more > expensive than a hub. This is mostly useful if you already have > the infrastructure in place and just want to look at one of the > systems attached to the switch. Like I pointed out, though, it isn't as expensive as you think ($175 US for the Netgear). That's equivalent to about 2 hours of labor time at the rate my company charges. -- DE