From owner-freebsd-current@FreeBSD.ORG Sat May 10 07:05:46 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 E906A37B401 for ; Sat, 10 May 2003 07:05:45 -0700 (PDT) Received: from topperwein.pennasoft.com (acs-24-154-51-127.zoominternet.net [24.154.51.127]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7B3B43FD7 for ; Sat, 10 May 2003 07:05:44 -0700 (PDT) (envelope-from behanna@topperwein.pennasoft.com) Received: from topperwein.pennasoft.com (localhost [127.0.0.1]) h4AE61T5081043 for ; Sat, 10 May 2003 10:06:01 -0400 (EDT) (envelope-from behanna@topperwein.pennasoft.com) Received: from localhost (localhost [[UNIX: localhost]]) by topperwein.pennasoft.com (8.12.9/8.12.9/Submit) id h4AE5tQM081042 for current@freebsd.org; Sat, 10 May 2003 10:05:55 -0400 (EDT) From: Chris BeHanna To: current@freebsd.org Date: Sat, 10 May 2003 10:05:55 -0400 User-Agent: KMail/1.5.1 References: <20030510035315.GA1812@node1.cluster.srrc.usda.gov> <20030510053529.GA42125@pit.databus.com> <20030510063236.GA36282@gforce.johnson.home> In-Reply-To: <20030510063236.GA36282@gforce.johnson.home> Organization: PennaSoft Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305101005.55721.chris@pennasoft.com> Subject: Re: strange network interface problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: chris@pennasoft.com 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 14:05:46 -0000 On Saturday 10 May 2003 02:32, Glenn Johnson wrote: > On Sat, May 10, 2003 at 01:35:29AM -0400, Barney Wolff wrote: > > On Fri, May 09, 2003 at 10:53:15PM -0500, Glenn Johnson wrote: > > > This is a weird one but hopefully someone can help. I have two > > > software programs that I frequently use and they each use licensing > > > software that depends on the Ethernet interface. One uses FlexLM > > > and the other a node locked scheme. They are both Linux programs, > > > which may be important. The machine in question is a dual homed > > > machine with one xl interface and one fxp interface. The xl > > > interface is on a 192.168.1.0 network and the fxp is on the > > > corporate LAN. The hostname points to the 192.168.1.1 address. > > > The license keys were generated from the MAC address of the xl > > > interface. This worked fine as of a couple of days ago but because > > > of the ffs bug I am not about to back my sources back in time. > > > > > > After updating to a recent -CURRENT, > > > > > > FreeBSD 5.1-BETA #0: Thu May 8 12:42:08 CDT 2003 > > > root@node1.cluster.srrc.usda.gov:/usr/obj/usr/src/sys/CLUSTER-FW > > > > > > the programs in question are getting the interfaces mixed up. For > > > the program that uses the node locked scheme I was able to get > > > another license generated and so am okay for that one. However, > > > the program that uses FlexLM is locked to the 192.168.1.0 network. > > > The problem is the software is seeing the dual homed machine on the > > > wrong interface and so thinks it is not on the network. 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? > > In what order does ifconfig print the interfaces? /var/run/dmesg.boot? > > xl0 is first. > > [...attempts to reorder ifconfig if listing via juggling in rc.conf > didn't work...] > > It does not seem like that would help as they are in the desired order. > FlexLM is in fact using the correct interface for the ether address > but the software that needs the license from FlexLM is getting the IP > address from the other interface. As I said, the software license > checking worked just a few days ago. Something has changed with > -CURRENT, or something weird is happening with the system. Is the software that needs the license running on your box, or on some other box in the corporate LAN? > > If all else fails, switch the nics around in their slots. Hard to do > > if either is on the motherboard, I know. > > The fxp interface is on the motherboard. That is probably part of your answer as to why the software finds it first. -- Chris BeHanna http://www.pennasoft.com Principal Consultant PennaSoft Corporation chris@pennasoft.com