Date: Wed, 26 Nov 2008 18:39:50 +0000 From: "Joao Barros" <joao.barros@gmail.com> To: "Ivan Voras" <ivoras@freebsd.org>, "Jia-Shiun Li" <jiashiun@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: if_le unit number change? Message-ID: <70e8236f0811261039i2e8d24eakbc88d3c526bb580@mail.gmail.com> In-Reply-To: <ggjphj$10s$1@ger.gmane.org> References: <1d6d20bc0811260656t101ddb0eu35296ac973c6ba10@mail.gmail.com> <ggjphj$10s$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 26, 2008 at 3:21 PM, Ivan Voras <ivoras@freebsd.org> wrote: > Jia-Shiun Li wrote: >> I use vmware to run freebsd. >> >> recent update of 8-current changed the unit number of the virtual >> network interface, an emulated if_le. usually the unit number should >> start from 0 ,namely le0. But after updating the source, le0 becomes >> le1. This makes interface name mismatching that in rc.conf. I checked >> the commit log but there seems nothing related in sys/dev/le. So >> should this be caused by something else? > > I have the same thing, but I thought it was just my bad luck sice I'm > working on the kernel. If it's the same thing you should notice in your > dmesg that both "le0" and "le1" are actually "detected" (I presume > wrongly, or at least that one of them is wrong) but ifconfig recognizes > only "le1" and errors out at any operation with le0. I'm guessing you both have only 1 virtual interface configured for that VM? Can you check? You can also try changing the interface to the enhanced type if your VMWare version allows you to.You'll get an "em" instead of an "le" -- Joao Barros
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70e8236f0811261039i2e8d24eakbc88d3c526bb580>