Date: Mon, 24 Dec 2012 15:03:11 -0500 From: George Mitchell <george@m5p.com> To: Ian Lepore <freebsd@damnhippie.dyndns.org> Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi EABI test image Message-ID: <50D8B4FF.3020201@m5p.com> In-Reply-To: <1356371614.1129.114.camel@revolution.hippie.lan> References: <20121224103825.086cd584@fubar.geek.nz> <50D79C5C.1000704@m5p.com> <20121224135512.30c84b7c@fubar.geek.nz> <50D87B88.6080504@m5p.com> <1356371614.1129.114.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/24/12 12:53, Ian Lepore wrote: > On Mon, 2012-12-24 at 10:58 -0500, George Mitchell wrote: >> On 12/23/12 19:55, Andrew Turner wrote: >>> On Sun, 23 Dec 2012 19:05:48 -0500 >>> George Mitchell <george+freebsd@m5p.com> wrote: >>> [...] >>>> Although rc.conf says ue0_config="DHCP"', dhclient doesn't run. I can >>>> run it manually, and then everything network-related works. >>> I've seen this before with other RPi images. >>> >> Changing DHCP to SYNCDHCP "fixes" the issue. I'll try to see if I can >> figure out why DHCP doesn't work. >> > > To look into why =DHCP doesn't work, look at devd and the devd rules to > figure out why usb-based interfaces (apparently) aren't being handled. > The way the rc system works these days, DHCP means "do 'ifconfig up' on > the interface and let devd launch dhclient in response to that", and > SYNCDHCP means "the rc system directly invokes dhclient immediately". > > -- Ian > That sure explains it! rc.conf says devd_enable="NO". Removing this line causes DHCP to run as expected with ue0_config="DHCP". -- George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D8B4FF.3020201>