From owner-freebsd-current@FreeBSD.ORG Fri Mar 26 05:55:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5798516A4CE for ; Fri, 26 Mar 2004 05:55:47 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05C1E43D48 for ; Fri, 26 Mar 2004 05:55:47 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i2QDthvK012104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Mar 2004 08:55:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i2QDtcrR024160; Fri, 26 Mar 2004 08:55:38 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16484.13914.523746.734591@grasshopper.cs.duke.edu> Date: Fri, 26 Mar 2004 08:55:38 -0500 (EST) To: noackjr@alumni.rice.edu In-Reply-To: <40640650.70005@alumni.rice.edu> References: <4063FB53.1040307@supsi.ch> <40640650.70005@alumni.rice.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: Ok, who broke interface autoconfiguration? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2004 13:55:47 -0000 Jon Noack writes: > > I run several machines with em network cards and 5.2.1-p3 with no > issues. I noticed your netmask is 255.255.254.0. I wonder if the issue > only occurs with certain (rare?) netmasks. I'm definitely grasping for > straws here. In any case, it's ~4:30am local time so I will crawl off > to bed and hope this doesn't sound too moronic in the morning... FWIW, my netmask is the same (0xffffff00) on all machines where I've seen this. But I'm using fxp and sk, not em. Drew