From owner-freebsd-current Sat May 3 02:43:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA21157 for current-outgoing; Sat, 3 May 1997 02:43:19 -0700 (PDT) Received: from gw.itfs.nsk.su (ns.itfs.nsk.su [193.124.36.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA21152 for ; Sat, 3 May 1997 02:43:15 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id QAA02695 for current@freebsd.org; Sat, 3 May 1997 16:30:06 +0700 Received: by itfs.nsk.su; Sat, 3 May 97 16:58:50 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.7.5/8.6.12) id QAA00115; Sat, 3 May 1997 16:31:47 +0700 (NSD) From: "Nickolay N. Dudorov" To: current@freebsd.org Subject: Re: divert still broken? Date: 3 May 1997 09:31:45 GMT Message-ID: <5kf0m1$s96@news.itfs.nsk.su> References: <199705020945.MAA22316@shadows.aeon.net> <336A31B5.6201DD56@whistle.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer wrote: > it is broken.. > garret broke it and we have yet to fix it... May be it is possible not only "unbroke" it but slightly extend it's functionality/usability (not really an IPDIVERT but 'ipfw' functionality) ? It seems to me that IP-traffic monitoring/accounting can be made more convinient with ipfw rules of type add 5000 tee 98 ip from some.net/24 to any out via interf0 wich will differ from add 5000 divert 98 ip from some.net/24 to any out via interf0 in not only diverting (copies of)packets to socket 98 but also in allowing usual processing of this packets (with the next ipfw rules and normal routing). In this case my (yet to be written) monitoring/accounting program will just read packets from (read-only ?) divert socket 98 not bothering itself with returning packets back to kernel. Is such an "idea' feasible ? N.Dudorov