Date: Thu, 01 Apr 2010 14:56:04 -0400 From: Steve Polyack <korvus@comcast.net> To: Peter Steele <psteele@maxiscale.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Testing ethernet interface status Message-ID: <4BB4EC44.2070804@comcast.net> In-Reply-To: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3B65FC5D@MBX03.exg5.exghost.com> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3B65FC5D@MBX03.exg5.exghost.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/01/10 14:21, Peter Steele wrote: > What's the best what to test the status of an Ethernet interface programmatically? We've been using this code similar to this: > > struct ifmediareq ifmr; > memset(&ifmr, 0, sizeof(ifmr)); > strcpy(ifmr.ifm_name, "nfe0"); > ioctl(sockfd, SIOCGIFMEDIA, (caddr_t)&ifmr) > > and then checking the value of ifmr.ifm_status& IFM_ACTIVE. We've found that every once in a while this code will return a false positive, indicating that the interface has gone offline when in fact it has not. > > So, is there a more reliable call to test if an Ethernet interface has gone offline? > I was going to suggest that you look at the ifconfig(8) source code, but then I did so myself - it looks like you're doing it pretty much exactly how they are. I've never noticed ifconfig(8) returning an incorrect value, not to say it's not possible. Are you sure that nothing is causing interface state resets? i.e. mismatched duplex/speed settings between the FreeBSD machine and the switch? Have you checked dmesg(8) for logs of interface state changes? You can also check the output of 'netstat -i' to check for interface errors.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BB4EC44.2070804>