From owner-freebsd-net Tue Mar 30 5:28:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id 76D4F15AC0 for ; Tue, 30 Mar 1999 05:28:08 -0800 (PST) (envelope-from stefan@promo.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id PAA25775; Tue, 30 Mar 1999 15:26:38 +0200 (CEST) Date: Tue, 30 Mar 1999 15:26:37 +0200 From: Stefan Bethke To: "Alex Sel'kov" Cc: freebsd-net@FreeBSD.ORG Subject: Re: 2 cards in one collision domain Message-ID: <690244.3131796397@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex Sel'kov wrote: > What's wrong? Why I recieve this strange messages? > > Another question: I have two 21143-based NIC's, but only one of them > correctly select 100Mbit transfer rate. >> --- /var/log/messages >> Mar 30 02:18:02 <0.3> turtle /kernel: arp: 00:00:1c:b0:d9:37 is >> using my IP >> address 192.168.10.1! >> Mar 30 02:18:02 <0.3> turtle /kernel: arp: 00:c0:ca:11:78:ed is >> using my IP >> address 192.168.10.1! >> >> --- ifconfig -a >> >> de0: flags=8843 mtu 1500 >> inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255 >> ether 00:00:1c:b0:d9:37 >> media: autoselect (100baseTX) status: active >> supported media: autoselect 100baseTX 100baseTX >> 10baseT/UT >> P 10baseT/UTP >> de1: flags=8843 mtu 1500 >> inet 192.168.20.1 netmask 0xffffff00 broadcast 192.168.20.255 >> ether 00:c0:ca:11:78:ed >> media: autoselect (10baseT/UTP) status: active >> supported media: autoselect 100baseTX 100baseTX >> 10baseT/UT >> P 10baseT/UTP >> lo0: flags=8049 mtu 16384 >> inet 127.0.0.1 netmask 0xff000000 You didn't by chance enable net.link.ether.inet.proxyall? The kernel normally shouldn't, but your's stumbles over it's own ARP replies: an ARP request for 192.168.10.1 is presumably answered correctly on de0, but also on de1. In turn de0 snoops the reply, and moans. The non-working autoselect might be due to different PHY chips used (jugding from the vastly different MAC addresses, I guess the cards are from two diffent vendors). Check what dmesg says about the PHY chips. Your hub/switch does support auto-negotiation, does it? Some PHYs are not very good at auto-sensing, AFAIK. In this case, set the media manually. Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message