From owner-freebsd-hackers Fri May 17 16:09:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA27755 for hackers-outgoing; Fri, 17 May 1996 16:09:51 -0700 (PDT) Received: from independence.ecn.uoknor.edu (independence.ecn.uoknor.edu [129.15.112.69]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA27745 for ; Fri, 17 May 1996 16:09:44 -0700 (PDT) Received: from servalan.UUCP by independence.ecn.uoknor.edu with UUCP (Smail3.1.29.1 #29) id m0uKYZ1-00088zC; Fri, 17 May 96 18:04 CDT Received: by servalan.servalan.com via sendmail with stdio id for freebsd-hackers@freebsd.org; Fri, 17 May 96 17:47:19 -0500 (CDT) (Smail-3.1.91 1996-Mar-5 #1 built 1996-Mar-6) Message-Id: Date: Fri, 17 May 96 17:47:19 -0500 (CDT) From: rmtodd@servalan.servalan.com (Richard Todd) To: freebsd-hackers@freebsd.org Subject: Re: hrmm Newsgroups: servalan.mailinglist.fbsd-hackers References: <13423.832320033@time.cdrom.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In servalan.mailinglist.fbsd-hackers you write: >> I've been sitting here watching ICMPs for kicks and I had an idea though I >> can't say as how useful it might be... I was thinking of a kernel level ICMP >> logging utility that would be set using sysctl with appx 3 different levels >> of logging. >Or how about this idea: >Have a general purpose packet-filter device (call it, say, bpfilter) >and a program to read from it in whatever detail you wish. We could >call that program `tcpdump' :-) Or even have a program that listens on a raw socket for ICMP packets and syslog what it finds, and call it 'icmpinfo'. :-) (Yes there is such a program, and no, you don't need bpf to look at ICMP packets that are sent to your own system, opening a raw socket suffices. Shouldn't be too difficult to make icmpinfo work on FreeBSD...)