From owner-freebsd-security  Mon Sep 14 10:29:53 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA08679
          for freebsd-security-outgoing; Mon, 14 Sep 1998 10:29:53 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from echonyc.com (echonyc.com [198.67.15.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08671
          for <security@FreeBSD.ORG>; Mon, 14 Sep 1998 10:29:51 -0700 (PDT)
          (envelope-from benedict@echonyc.com)
Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id NAA21219;
	Mon, 14 Sep 1998 13:29:28 -0400 (EDT)
Date: Mon, 14 Sep 1998 13:29:28 -0400 (EDT)
From: Snob Art Genre <benedict@echonyc.com>
Reply-To: ben@rosengart.com
To: Liam Slusser <liam@tiora.net>
cc: security@FreeBSD.ORG
Subject: Re: smurf and broadcast packets..
In-Reply-To: <Pine.BSF.3.96.980914013859.545A-100000@orbital.tiora.net>
Message-ID: <Pine.GSO.4.02.9809141328230.19838-100000@echonyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Mon, 14 Sep 1998, Liam Slusser wrote:

>  changed it to 0, and from there...i ran into a wierd
> problem.  My server has two network cards in it, ed0 (internet side,
> 24.0.185.89) and ed1 (internal network, 10.0.0.1), and runs natd.  When i
> turned net.inet.icmp.bmcastecho to 0..i could not ping 10.0.0.255 but i
> could ping my internet side 24.0.189.255.

Not so weird.  The broadcast address on your internal network is
probably 10.255.255.255.


 Ben

"You have your mind on computers, it seems." 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message