Date: Mon, 8 Dec 2003 10:33:46 -0600 From: Craig Boston <craig@xfoil.gank.org> To: Current <freebsd-current@freebsd.org> Subject: Re: dev/em: Link is not up until 2 seconds after "ifconfig up" Message-ID: <200312081033.46104.craig@xfoil.gank.org> In-Reply-To: <7my8to5bqk.wl@black.imgsrc.co.jp> References: <7m8ylp6pn0.wl@black.imgsrc.co.jp> <20031207150250.L35454@sbk-gw.sibnet.ru> <7my8to5bqk.wl@black.imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 07 December 2003 07:39 pm, Jun Kuriyama wrote: > At Sun, 7 Dec 2003 15:04:51 +0600 (NOVT), > > Hmm, no luck. I've fixed the speed and mediaopt both of em(4) and > switch, but it shows autoselect state and no carrier... Hmm, just kind of a 'me too', but I've noticed some unusual behaviour with the link state of em as well. It seems that if the interface is in the "down" state, it always shows as "no carrier" even if something is plugged in. It isn't until something tries to configure it or I manually issue an ifconfig up that it actually autonegotiates the link speed, etc. Most (all that support link state?) other network drivers in FreeBSD seem to report the link state even if the interface is down. I know for sure that fxp and xl do. IMHO this is a useful feature because it allows sufficiently smart scripts to change their behavior -- i.e. only run dhclient on interfaces that actually have something plugged in. Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312081033.46104.craig>