Date: Thu, 12 Jul 2012 14:01:51 -0700 From: Freddie Cash <fjwcash@gmail.com> To: Chris Benesch <chris.benesch@gmail.com> Cc: Yuri <yuri@rawbw.com>, freebsd-net@freebsd.org Subject: Re: System doesn't detect unplugged network cable and doesn't set interface up properly with DHCP Message-ID: <CAOjFWZ6dCDSkdxGNGzmo%2Bu871sOF8r05b6psukoP9pDLQHHk6A@mail.gmail.com> In-Reply-To: <CAPKwmM1MLm5nYX6LT480iX2R9gKAQBskUghwVj6Q8KF8oMyL=w@mail.gmail.com> References: <4FFF3683.7020107@rawbw.com> <CAPKwmM1MLm5nYX6LT480iX2R9gKAQBskUghwVj6Q8KF8oMyL=w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 12, 2012 at 1:52 PM, Chris Benesch <chris.benesch@gmail.com> wrote: > Thats pretty standard for BSD and most Unixes. DHCP hands out leases for a > specified period of time, so unless there is a reason to reset it, it > wont. Windows does that, but it is designed more as a client / user facing > OS whereas BSD is designed to run in the background silently serving you > content and directing traffic. > > I can save you some steps though, > > ps -ax | grep dhclient > > You will get a list, on the one that is dhclient or /sbin/dhclient, take > the number at the far left, thats the process ID > > kill <process id> > dhclient re0 pkill dhclient dhclient re0 Saves a few more steps. :) There's also: service netif restart re0 -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ6dCDSkdxGNGzmo%2Bu871sOF8r05b6psukoP9pDLQHHk6A>