From owner-freebsd-current@FreeBSD.ORG Fri May 9 20:53:23 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 14EB837B401 for ; Fri, 9 May 2003 20:53:23 -0700 (PDT) Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CE2A43FD7 for ; Fri, 9 May 2003 20:53:19 -0700 (PDT) (envelope-from gjohnson@srrc.ars.usda.gov) Received: from node1.cluster.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.12.9/8.12.9) with ESMTP id h4A3rHZG001844 for ; Fri, 9 May 2003 22:53:17 -0500 (CDT) (envelope-from glenn@node1.cluster.srrc.usda.gov) Received: (from glenn@localhost)h4A3rFM1001843 for current@freebsd.org; Fri, 9 May 2003 22:53:15 -0500 (CDT) Date: Fri, 9 May 2003 22:53:15 -0500 From: Glenn Johnson To: current@freebsd.org Message-ID: <20030510035315.GA1812@node1.cluster.srrc.usda.gov> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: 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 03:53:23 -0000 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. Here is some data to illustrate the problem. The ifconfig utility shows the xl interface to be: xl0: flags=8843 mtu 1500 options=3 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::201:2ff:fec9:21d5%xl0 prefixlen 64 scopeid 0x1 ether 00:01:02:c9:21:d5 media: Ethernet autoselect (100baseTX ) status: active The FlexLM daemon is seeing this as the primary interface, as it should. Here is the output of 'lmutil lmhostid': lmutil - Copyright (C) 1989-2000 Globetrotter Software, Inc. The FLEXlm host ID of this machine is "000102c921d5" Note that the host ID is correctly derived from the ether address of 00:01:02:c9:21:d5 for xl0. However, the software that uses the license "sees" the fxp interface and gets that IP address, the one on the corporate LAN instead of the one on the 192.168.1.0 network. Of course, I then get a message about the host not being on the correct network. This just started happening and since the other license software did a similar thing, I am inclined to think that something is up with FreeBSD -CURRENT. Like I said, this all _did_ work just a few days ago. I hope I have made sense here and thanks in advance for any input. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: gjohnson@srrc.ars.usda.gov