Date: Wed, 18 Apr 2001 00:11:49 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Robert Clark" <res03db2@gte.net> Cc: <michael@tenzo.com>, <freebsd-questions@FreeBSD.ORG> Subject: RE: Naming ethernet NICs Message-ID: <006801c0c7d6$d5ff9700$1401a8c0@tedm.placo.com> In-Reply-To: <20010417215639.A54277@darkstar.gte.net>
next in thread | previous in thread | raw e-mail | index | archive | help
No, that's not what I meant. Note that in that post I never said that I _didn't like_ having to test each port. :-) What I was merely point out is that the original poster was saying that the "eth0, eth1, eth2..." way of doing things is superior, and I was just responding that "no, it has problems too, such as matching up ports to nics" then following it with an example of ed0, ed1, ed2... I figured that the poster would be able to grasp that there's no difference between eth0, eth1, eth2,,, and ed0, ed1, ed2,,, for what he seemed to think was desirable behavior for having everything named the same. As a matter of fact, I actually don't advocate using different NICS in routers, because if they are all the same then you can make a custom compiled kernel a little smaller since you only have to include 1 nic driver in it. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Robert Clark >Sent: Tuesday, April 17, 2001 9:57 PM >To: Ted Mittelstaedt >Cc: michael@tenzo.com; freebsd-questions@FreeBSD.ORG >Subject: Re: Naming ethernet NICs > > > > >So you're advocating using NICs on different drivers, just >so that you can tell them apart? > > > >On Tue, Apr 10, 2001 at 10:45:27PM -0700, Ted Mittelstaedt wrote: >> >-----Original Message----- >> >From: owner-freebsd-questions@FreeBSD.ORG >> >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Michael O'Henly >> > >> >So if NICs are named on the basis of their type/driver, doesn't >> >that mean a >> >lot of reconfiguring is needed if you should happen to replace >a card with >> >something different? >> > >> >> Let me point out that with regular PC hardware, you can't >replace a NIC with >> a different type without taking the server offline. Once you do >that, all >> of the benefits of "transparent reconfiguration" are basically lost. >> >> In any case, even if you do it differently and make everything >"eth0, eth1, >> etc. and so on, then how do you determine what physical card in >the system >> goes with what port? >> >> To give you an example, recently I built a router on a 486 with >5 separate >> nics in them. Every NIC in the router is the same, (SMC8013) and >> thus I had ed0, ed1, ed2, etc. On bootup, I still had to test >each port to >> determine which physical card went to what ed. >> >> >> >> Ted Mittelstaedt tedm@toybox.placo.com >> Author of: The FreeBSD Corporate Networker's Guide >> Book website: http://www.freebsd-corp-net-guide.com >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006801c0c7d6$d5ff9700$1401a8c0>