Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 May 2009 12:29:33 +0200
From:      Milan Obuch <freebsd-net@dino.sk>
To:        freebsd-net@freebsd.org
Cc:        "Li, Qing" <qing.li@bluecoat.com>
Subject:   Re: Weird dhclient behavior after today's rebuild
Message-ID:  <200905141229.34731.freebsd-net@dino.sk>
In-Reply-To: <B583FBF374231F4A89607B4D08578A431443BD@bcs-mail03.internal.cacheflow.com>
References:  <200905140703.10473.freebsd-net@dino.sk> <B583FBF374231F4A89607B4D08578A431443BD@bcs-mail03.internal.cacheflow.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 14 May 2009 07:32:22 Li, Qing wrote:
> I have committed the patch, please update your source and
> give it a try.
>
> Thanks,
>
> -- Qing
>

After fresh csup and rebuild it works again. I suppose your fix wents into 
sys/netinet/in.c, as I did not see anything else network related in csup's 
output...

Thanks for quick fix.

Milan

> -----Original Message-----
> From: owner-freebsd-net@freebsd.org on behalf of Milan Obuch
> Sent: Wed 5/13/2009 10:03 PM
> To: freebsd-net@freebsd.org
> Subject: Weird dhclient behavior after today's rebuild
>
> Hi,
>
> I did full system rebuild from freshly csup'ped sources. Everything went
> smooth as usual, but after reboot network card did not get configured via
> DHCP. There were four lines logged on console/in syslog:
>
> dhclient[822]: re0: not found
> dhclient[822]: exiting
> dhclient[823]: connection closed
> dhclient[823]: exiting
>
> I did some tests, disabled automatic dhclient invocation in rc.conf.
>
> Then, after connecting cable, ifconfig re0 show status active, netstat -rnf
> inet shows only loopback route (128.0.0.1 on lo0). Manually starting
> dhclient re0:
>
> ifconfig: ioctl (SIOCAIFADDR): File exists
> re0: not found
> exiting
>

[ snip ]



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905141229.34731.freebsd-net>