From owner-freebsd-current@FreeBSD.ORG Sat May 10 11:13:20 2003 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 D5CA537B401 for ; Sat, 10 May 2003 11:13:20 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 387B843FCB for ; Sat, 10 May 2003 11:13:18 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0084.cvx40-bradley.dialup.earthlink.net ([216.244.42.84] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19EYqS-0003TT-00; Sat, 10 May 2003 11:13:16 -0700 Message-ID: <3EBD40F2.A91F080E@mindspring.com> Date: Sat, 10 May 2003 11:12:02 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Glenn Johnson References: <20030510035315.GA1812@node1.cluster.srrc.usda.gov> <20030510053529.GA42125@pit.databus.com> <20030510063236.GA36282@gforce.johnson.home> <20030510160338.GA1837@gforce.johnson.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a449a18077e964a8c4bc8527d0a647863ea7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org Subject: Re: strange network interface problem 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: Sat, 10 May 2003 18:13:21 -0000 Glenn Johnson wrote: > On Sat, May 10, 2003 at 10:05:55AM -0400, Chris BeHanna wrote: > > Is it possible that someone at corporate mucked with DNS so that > > the software that needs the license from FlexLM is resolving to the > > wrong address? > > No, I maintain my own DNS for my machines. The most likely cause is probe-order changes as a result of an ACPI code update (first interface <-> second interface), and/or routing code changes. Without bsearching a source code delta that caused the problem (basically, you need to try log2(number_of_days)+1 kernels), and then doing a CVS diff, it's going to be impossible for anyone other than Glenn to isolate the change that's causing his problem. An it'd be a lot of work, because it could also have been rc changes. -- Terry