From owner-freebsd-stable Wed May 16 10:36:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by hub.freebsd.org (Postfix) with ESMTP id 7541437B423 for ; Wed, 16 May 2001 10:36:32 -0700 (PDT) (envelope-from khera@kcilink.com) Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106]) by yertle.kciLink.com (Postfix) with ESMTP id CC4E12E460 for ; Wed, 16 May 2001 13:36:31 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.3/8.11.3) id f4GHaVw90212; Wed, 16 May 2001 13:36:31 -0400 (EDT) (envelope-from khera@kcilink.com) X-Authentication-Warning: onceler.kciLink.com: khera set sender to khera@kcilink.com using -f To: stable@freebsd.org Subject: Re: dual fxp ethernet, one doesn't "work" References: <15105.44534.131385.573668@onceler.kciLink.com> From: Vivek Khera Date: 16 May 2001 13:36:31 -0400 In-Reply-To: <15105.44534.131385.573668@onceler.kciLink.com> Message-ID: Lines: 35 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "VK" == Vivek Khera writes: VK> Box name "m02": VK> [m02]% ifconfig -a VK> fxp0: flags=8843 mtu 1500 VK> inet 192.168.200.65 netmask 0xffffff00 broadcast 192.168.200.255 VK> ether 00:b0:d0:e1:34:de VK> media: autoselect (100baseTX) status: active VK> supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX VK> fxp1: flags=8943 mtu 1500 VK> inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 VK> ether 00:b0:d0:e1:34:df VK> media: autoselect (10baseT/UTP) status: active VK> supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX VK> lo0: flags=8049 mtu 16384 VK> inet 127.0.0.1 netmask 0xff000000 Ok... more data. It is definitely a FreeBSD problem with dual fxp NICs. Evidence: I swapped the cables and IP numbers for fxp1 and fxp0. Now, fxp1 works and fxp0 doesn't. That is, the interface I assign to 192.168.100.2 doesn't work, but the one assinged 192.168.200.64 works fine. The order in which they are assigned doesn't matter. Is there some magic to the 192.168.100.2 address? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message