From owner-freebsd-security Fri Jul 2 3:29:30 1999 Delivered-To: freebsd-security@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 137B3150BA for ; Fri, 2 Jul 1999 03:29:27 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id MAA13794; Fri, 2 Jul 1999 12:29:22 +0200 (CEST) (envelope-from des) To: Josef Karthauser Cc: Dag-Erling Smorgrav , Snob Art Genre , Bill Fink , freebsd-security@FreeBSD.ORG Subject: Re: your mail References: <19990702095858.V69050@pavilion.net> <19990702104239.X69050@pavilion.net> From: Dag-Erling Smorgrav Date: 02 Jul 1999 12:29:22 +0200 In-Reply-To: Josef Karthauser's message of "Fri, 2 Jul 1999 10:42:40 +0100" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Josef Karthauser writes: > On Fri, Jul 02, 1999 at 11:24:04AM +0200, Dag-Erling Smorgrav wrote: > > Josef Karthauser writes: > > > As an associated thing can anyone think of an easy way of ignoring traffic > > > coming from a particular MAC address on the network? I've got a user who > > > keeps changing their IP address to get arround the fact that I've restricted > > > traffic to that address. > > So terminate him. > [...] (I could disconnect him from the network > but that's harder to police.) So disconnect him from the network. It's your network. You set the rules. He breaks the rules, he loses access. Anything short of that is an invitation for him to try and circumvent your measures. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message