From owner-freebsd-questions Tue Nov 21 8:48:20 2000 Delivered-To: freebsd-questions@freebsd.org Received: from alpha.ces.cwru.edu (alpha.CES.CWRU.Edu [129.22.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 023ED37B4C5 for ; Tue, 21 Nov 2000 08:48:17 -0800 (PST) Received: from akasha (akasha [129.22.16.70]) by alpha.ces.cwru.edu (8.9.3+Sun/8.9.1) with ESMTP id LAA27672 for ; Tue, 21 Nov 2000 11:48:13 -0500 (EST) Date: Tue, 21 Nov 2000 11:48:12 -0500 (EST) From: David Carlin X-Sender: djc6@akasha.CES.CWRU.Edu To: freebsd-questions@FreeBSD.ORG Subject: Bridging Loop Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm in the testing phases of setting up a bridge/firewall for a lab at the university I work for. The lab has about 60 computers and is currently uplinked to a network of over 13,000 hosts (with usually about 9,000 online at any given time). The campus network is one giant bridged network; every host is on the same subnet. Right now I have the internal interface hooked up to a single computer via a crossover cable. The external interface is hooked up to a 5 port hub with some other machines. The machines on the 5 side can access the machine behind the firewall without any problems. When I replace the 5 port hub with a connection to the campus network however, I get looping errors and about 90% packet loss to the machine hooked up via the crossover cable. I don't know where the loop errors are coming from; the machine with the crossover cable only has one interface, so I don't see how there are multiple paths to it. Is the bridge table getting full or something? I don't even know how large it is (8192?) Thanks for the info! -- David Carlin -- djc6@scl.cwru.edu | Case Western Reserve University Manager, Smith Computer Lab | 10900 Euclid Ave. Phone: (216) 368-5066 | A.W. Smith Building Room #103 Fax: (216) 368-5461 | Cleveland, OH 44106-7071 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message