From owner-freebsd-hackers Fri Aug 17 4: 9:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 5F82537B409 for ; Fri, 17 Aug 2001 04:09:12 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from vel@localhost) by bugz.infotecs.ru (8.11.5/8.11.4) id f7HB98k29893 for freebsd-hackers@freebsd.org; Fri, 17 Aug 2001 15:09:08 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108171109.f7HB98k29893@bugz.infotecs.ru> Subject: IP address on bridge To: freebsd-hackers@freebsd.org Date: Fri, 17 Aug 2001 15:09:08 +0400 (MSD) X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I'm observing some strange problem when I have an IP address on one card on a bridge machine and want to telnet in. I have 4.2-RELEASE box with two network cards: Realtek 8139 (rl0) and 3Com 3C905B (xl0). rl0 is connected to the world, and xl0 to the intranet switch. FreeBSD handbook says that I'm allowed to assign an IP address to one of the two interfaces. Okay, so I assign the address to xl0. But I'm unable to access it from a machine on xl0 side. arp is found properly, and packets are sent, but somehow bridge machine just ignores those packets (tcpdump shows nothing). If I assign IP address to rl0 rather than xl0, it works for short time, then machine I telnet from says that arp of the bridge is moved to xl0 arp again, and packets get lost. ifconfig rl0 down/up and ping'ing the machine I telnet from (so it gets proper arp) heals, but for the short time again. When I swap network cables on those cards, so that xl0 looks to the world and rl0 to the intranet, then assigning IP address to rl0 works fine, I'm always able to telnet in from intranet side. Is it some bug in the xl0 driver ? Was it already fixed, and would upgrading to -current solve this problem ? Or is it me who misses something ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message