Date: Sat, 8 Apr 2006 19:16:38 -0400 From: Mike Meyer <mwm-keyword-freebsdhackers.102a7e@mired.org> To: David Taylor <davidt@yadt.co.uk> Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever Message-ID: <17464.17494.251794.271711@bhuda.mired.org> In-Reply-To: <20060408224140.GA15366@outcold.yadt.co.uk> References: <C05CAC06.C0BD%ceri@submonkey.net> <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <20060408224140.GA15366@outcold.yadt.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
In <20060408224140.GA15366@outcold.yadt.co.uk>, David Taylor <davidt@yadt.co.uk> typed: > That doesn't quite work, though. Unless you require everyone wanting > to distinguish between LAN and WAN interfaces uses different types > of hardware for each card, they'll still end up with xl0 and xl1 > (or whatever), which is in no way better than eth0 and eth1, You're right - but at least you have the option of using different types of cards to get different names. I agree that this sucks, but it's better than nothing. I tried to find out how to tell the difference between ethernet interfaces on Linux. Seems that the 2.6 kernel can assign different names to the ethernet devices at each reboot. Um, yeah. Solutions for this problem all seem to involve assigning an arbitrary name based on the MAC address. This has two problems: 1) you have to have a mapping somewhere of mac addresses to cards so you know where to plug in the wan port vs. the lan port. 2) if you replace a dead card with an identical card, your configuration breaks. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17464.17494.251794.271711>