Date: Wed, 11 Apr 2001 13:04:33 -0400 From: "John Straiton" <jks@clickcom.com> To: <freebsd-questions@FreeBSD.ORG> Subject: RE: Naming ethernet NICs Message-ID: <MPEBIEINAKAJNIDNGFBBCEHCCDAA.jks@clickcom.com> In-Reply-To: <01041106563200.03731@pravda.tenzo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yes, this is what I meant. The reason I raised the questions is that I'm > configuring a simple firewall for my home network and so far I've > "hardcoded" > NIC names in three or four different places. Presumably if I ever > replaced a > NIC with a different type/driver, I'd have to rediscover all the > places I'd > used the old name. So is there any reason why in this situation, you couldn't create a quick script (I say script simply because I find if I script something and keep the file, I can faithfully recreate the situation- and we're trying to keep things easy to remember in this situation, right?) to create symbolic links from the real NIC names to something like WAN0 and LAN0 , then use those names in your scripts? Then if you changed NIC's you would just change the link and your other files would indirectly see the change? John Straiton ClickCom, Inc. ne@clickcom.com 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?MPEBIEINAKAJNIDNGFBBCEHCCDAA.jks>