Date: Tue, 14 Nov 2000 11:40:03 -0800 (PST) From: Stefan Molnar <stefan@csudsu.com> To: Rich Wales <richw@webcom.com> Cc: Wilko Bulte <wkb@freebie.demon.nl>, freebsd-stable@freebsd.org Subject: Re: Bridging code in 4.2RC1 still not fixed Message-ID: <Pine.BSF.4.21.0011141138470.10599-100000@clockwork.csudsu.com> In-Reply-To: <20001114192111.06912.richw@wyattearp.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hummm, just because the card is useable does not mean the bridging code works or is in the driver. Even tho lnc is supported, the patch might have negated that effect. On Tue, 14 Nov 2000, Rich Wales wrote: > Stefan Molnar wrote: > > > I had bridging plus ipfw working in 4.0-R to 4.1-S for > > some time. I only had it crash when I used a tulip card > > (de0), I used dc0 for the setup. It did go to a slow > > crawl, and figured out it was the cards themself, it > > would goto a crawl with just nat. I do not have it > > running currently. What cards are you using? > > The system in question has three NIC's (all PCI): > > ==> ed1 (RealTek 8029 PCI) > ==> lnc1 (Linksys HomeLink PNA) > ==> xl0 (3Com 3c900-TPO) > > At the time of the test, the 3Com card was installed, but not in use. > I was using PPP (/usr/sbin/ppp) and a dialup ISP connection. I am now > using the 3Com card as an interface to a DSL hookup. > > My LNC driver has been patched to recognize and initialize HomeLink > cards (1Mbps Ethernet over inside phone wiring). The patched code > works just fine when the system is configured as a conventional router > (not as a bridge). > > Rich Wales richw@webcom.com http://www.webcom.com/richw/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0011141138470.10599-100000>