Date: Mon, 8 Mar 1999 08:05:30 -0600 (CST) From: James Wyatt <jwyatt@RWSystems.net> To: =?X-UNKNOWN?Q?Ronald_Wiplinger_=28=C3Q=A4=AF=AF=C7=29?= <ronald@trace.net.tw> Cc: "freebsd-isp@FreeBSD.ORG" <freebsd-isp@FreeBSD.ORG> Subject: Re: Ethernet card problem Message-ID: <Pine.BSF.4.05.9903080752350.21155-100000@kasie.rwsystems.net> In-Reply-To: <36E37494.14798FFC@trace.net.tw>
index | next in thread | previous in thread | raw e-mail
On Mon, 8 Mar 1999, Ronald Wiplinger (ÃQ¤¯¯Ç) wrote:
[ ... ]
> This error comes up, since I have installed the bandwidth filter of
> ETINC. The system crashs frequently after 2 hours of operation. I
> believe it is related to the above message.
Now *that* is a "hard" bandwidth limiter! 8{( Has some polite (since I
don't think he's getting paid for this) mail to Dennis helped?
> Suppose I have to change this Ethernet card (D-link) to a Intel Ethernet
> Express 100. How can I have two fxp* cards in one machine and still know
> which one is for which gateway ????
You will save future headaches if you label the back of the cards. (fwiw:
I usually label one 'O' for "Outside the 'wall" and interface '0'. I
usually label the other 'I' for "Inside" and interface '1')
On ISA cards, I use the setup utility to set the card to match kernel
entries; slot order is independent. For PCI cards, I usually see it assign
the lower numbered (PCI-slot wise) card to interface '0' and successive
slots to successive cards.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9903080752350.21155-100000>