From owner-freebsd-current@FreeBSD.ORG Sat May 10 15:30:50 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 270AA37B404 for ; Sat, 10 May 2003 15:30:50 -0700 (PDT) Received: from remt26.cluster1.charter.net (remt26.cluster1.charter.net [209.225.8.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id E783843F85 for ; Sat, 10 May 2003 15:30:48 -0700 (PDT) (envelope-from glennpj@charter.net) Received: from [24.158.214.251] (HELO gforce.johnson.home) by remt26.cluster1.charter.net (CommuniGate Pro SMTP 4.0.6) with ESMTP id 20483744 for current@freebsd.org; Sat, 10 May 2003 18:30:47 -0400 Received: from gforce.johnson.home (localhost [127.0.0.1]) by gforce.johnson.home (8.12.9/8.12.9) with ESMTP id h4AMUjEi025164 for ; Sat, 10 May 2003 17:30:46 -0500 (CDT) (envelope-from glenn@gforce.johnson.home) Received: (from glenn@localhost) by gforce.johnson.home (8.12.9/8.12.9/Submit) id h4AMUj5K025150 for current@freebsd.org; Sat, 10 May 2003 17:30:45 -0500 (CDT) Date: Sat, 10 May 2003 17:30:45 -0500 From: Glenn Johnson To: current@freebsd.org Message-ID: <20030510223045.GA49085@gforce.johnson.home> Mail-Followup-To: current@freebsd.org References: <20030510035315.GA1812@node1.cluster.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030510035315.GA1812@node1.cluster.srrc.usda.gov> User-Agent: Mutt/1.4.1i 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 22:30:50 -0000 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. I worked on this remotely and got the problem solved but I am still wondering if there is a problem. It turns out there was an entry for the IP address and its corresponding hostname of the corporate LAN interface in the /etc/hosts file. This is the one on the fxp interface, not the xl interface fir the 192.168.1.0 network. This was put there by the FreeBSD installer. I use DNS for host name resolution and so did not think about it. I also run NIS on this machine and so there was a hosts map provided by NIS. The program that was having a problem is a Linux program and it uses NIS before DNS, via its default nsswitch.conf file, and so was picking up the IP address from the NIS hosts map. What I do not understand is how the hostname, that was _not_ in the hosts file, got associated with a different IP address, the one that was in the hosts file. I deleted the entry from the /etc/hosts file and remade the NIS maps and the problem program now gets the correct IP address. I could also have edited the Linux nsswitch.conf file. After I did this I remembered that I had updated the NIS maps about three days ago. No doubt that is when the crossover occurred. I am going to put this down as just some strangeness with NIS, DNS, and /etc/hosts going between the FreeBSD and the Linux layer on the same machine. It could have just been a "glitch" because I had not had this happen before. I tried to reproduce the problem by putting the entry back in the hosts file and regenerating the NIS maps but it behaves correctly now. Thanks. -- Glenn Johnson glennpj@charter.net