Received: by oss.sgi.com id ; Wed, 21 Jun 2000 09:55:06 -0700 Received: from dialup341.canberra.net.au ([203.33.188.213]:62982 "HELO halfway") by oss.sgi.com with SMTP id ; Wed, 21 Jun 2000 09:54:56 -0700 Received: from linuxcare.com.au (localhost [127.0.0.1]) by halfway (Postfix) with ESMTP id 83F988193 for ; Wed, 21 Jun 2000 17:59:59 +1000 (EST) From: Rusty Russell To: netdev@oss.sgi.com Subject: RFC: Reporting dropped packets Date: Wed, 21 Jun 2000 17:59:59 +1000 Message-Id: <20000621075959.83F988193@halfway> Sender: owner-netdev@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;netdev-outgoing There are a number of places in the network code where we drop packets which people might be interested in knowing about (eg. my nat code, CONFIG_IP_ROUTE_VERBOSE). Be very nice if these were more flexible, and centralized. Options are: 1) Leave it alone. 2) Add nf_dropping(int pf, unsigned int hook, const struct sk_buff *skb, const struct net_device *indev, const struct net_device *outdev, const char *reason); nf_register_drop() and nf_unregister_drop() for recipients of dropped packets. 3) Add a bogus NF_IP_DROPPING hook IPv4 netfilter; make the skb->nfmark field hold an enum indicating why the packet was dropped. The third is most trivial, and is what I'm leaning towards at this stage. Anyone feel strongly that the current stuff is nicer? Will prepare patch if noone objects... Rusty. -- Hacking time.