From owner-freebsd-stable Tue May 15 15:30:19 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 D2DD137B424 for ; Tue, 15 May 2001 15:30:14 -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 59D002E460 for ; Tue, 15 May 2001 18:30:14 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.3/8.11.3) id f4FMUE627327; Tue, 15 May 2001 18:30:14 -0400 (EDT) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15105.44534.131385.573668@onceler.kciLink.com> Date: Tue, 15 May 2001 18:30:14 -0400 To: stable@freebsd.org Subject: dual fxp ethernet, one doesn't "work" X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have three machines with dual fxp NICs on them. They are all Dell PowerEdge 1550 boxes, running 4.3-STABLE from yesterday (I updated the kernel from today to see if the latest patches to if_fxp.c fixes the problem, but it didn't). Here's what I see. Box name "m02": [m02]% ifconfig -a fxp0: flags=8843 mtu 1500 inet 192.168.200.65 netmask 0xffffff00 broadcast 192.168.200.255 ether 00:b0:d0:e1:34:de media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX fxp1: flags=8943 mtu 1500 inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 ether 00:b0:d0:e1:34:df media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 [m02]% netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.200.2 UGSc 1 0 fxp0 127.0.0.1 127.0.0.1 UH 1 2 lo0 192.168.100 link#2 UC 1 0 fxp1 => 192.168.100.128 link#2 UHLW 0 1 fxp1 => 192.168.200 link#1 UC 2 0 fxp0 => 192.168.200.2 0:2:e3:4:14:6 UHLW 3 499 fxp0 1130 from this box, I can ping 192.168.200.200 fine. Trying to ping 192.168.100.200 (which are both addresses on the same remote box, different NICs) fails. From tcpdump, I see that m02 is issuing the arp "who-has" requests, but gets no replies even though they are published. This is the same for any 192.168.100.* address. However, if I ping 192.168.100.200 from another box, then m02 sees that traffic via tcpdump on fxp1. If I ping m02 from another host, tcpdump on fxp1 says: 18:15:23.245232 arp who-has m02-prv tell d01-prv 18:15:23.245240 arp reply m02-prv is-at 0:b0:d0:e1:34:df The arp reply doesn't show up on any other host in the 192.168.100 network (m01-prv is the host name of the fxp1 IP address). If I ping another host on the 192.168.100 network, the who-has and the reply both get seen by fxp1 on the host m01. I have one box on these same two subnets (which are on physically separate hubs) with one de and one sis network card, and it speaks properly to both nets. It is only my machines with two fxp devices where the 192.168.100 network appears mute when sending out data. Any idea? I had same behavior with 4.3-RELEASE on these boxes, so I'm a bit stumped. The cabling seems ok since I see data coming in, but never see data going out to other hosts. Searching mailing lists, google, and man pages for fxp and ifconfig did not yield any info. I know the routing/configs are otherwise correct, since it works fine with a de0/sis0 combo but not fxp0/fxp1 combo. Thanks for any pointers. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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