From owner-freebsd-net Tue Mar 30 9:27:39 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 F345C15B67; Tue, 30 Mar 1999 09:27:02 -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 TAA26966; Tue, 30 Mar 1999 19:25:11 +0200 (CEST) Date: Tue, 30 Mar 1999 19:25:09 +0200 From: Stefan Bethke To: "Alex Sel'kov" Cc: freebsd-net@FreeBSD.ORG Subject: RE: 2 cards in one collision domain Message-ID: <1551469.3131810709@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: >> 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. >> > > Hmm. I'm newbie, so I can't play with such things like sysctl yet :) > > sysctl -a| grep net.link.ether.inet.proxyall > net.link.ether.inet.proxyall: 0 > > As far as I can understand 0 stands for "disabled"? Yes. > But you are definitely right - looks like enabled internal bridge. Where > I can look for parameters which control such behaivor? Did you add "options BRIDGE" to your kernel config file? I'm now somewhat confused. I *think* that you'd normally shouldn't see this message, unless you enabled bridging. However, why would you want to enable bridging between two interfaces connected to the same net? Why have you connected both interfaces to the same net? If you want your host to be on two subnets on the same wire, simply configure both IPs (see /etc/rc.conf for details). >> 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. >> > > Yes, cards from differnt vendors. > > Mar 29 03:19:40 <0.2> turtle /kernel: de0: > rev 0x41 int a irq 16 on pci0.19.0 > Mar 29 03:19:40 <0.2> turtle /kernel: de0: 21143 [10-100Mb/s] pass 4.1 > (invalid EESPROM checksum) > Mar 29 03:19:40 <0.2> turtle /kernel: de0: address 00:00:1c:b0:d9:37 > > Mar 29 03:19:40 <0.2> turtle /kernel: de1: > rev 0x30 int a irq 16 on pci2.4.0 > Mar 29 03:19:40 <0.2> turtle /kernel: de1: 21143 [10-100Mb/s] pass 3.0 > Mar 29 03:19:40 <0.2> turtle /kernel: de1: address 00:c0:ca:11:78:ed Hhm. Can you compile /sys/pci/if_de.c with TULIP_DEBUG enabled? And give us some more information on the make and model of the cards your using? 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