Hello again, Okay, (@Robert) I can confirm that it is not reliable when I am not manually initiating the dhcp from my desktop. Also (@David) the beagle does not automatically remove the connection when I disconnect the ethernet, and so I have to manually remove the no longer valid default route. This is probably where ifplugd would make life easier.
Cheers. On Tue, Nov 18, 2014 at 12:03 PM, Jason Lange <[email protected]> wrote: > @david > I have tested this. Try it, it works. > > On Tue, Nov 18, 2014 at 11:52 AM, David Goodenough < > [email protected]> wrote: > >> On Tuesday 18 November 2014 11:40:42 Jason Lange wrote: >> > On Fri, Sep 12, 2014 at 9:35 AM, Robert Nelson <[email protected] >> > >> > >> > wrote: >> > > On Fri, Sep 12, 2014 at 11:27 AM, Greg Kelley <[email protected]> >> > > >> > > wrote: >> > > > Robert, >> > > > >> > > > I think part of the reason ntp and dhcpclient aren't getting network >> > > > connections at boot is because they are set at S03 in init and wicd >> is >> > > >> > > set >> > > >> > > > at S06 and is last to get going. It appears that eth0 is not coming >> up >> > > >> > > until >> > > >> > > > wicd loads? >> > > >> > > Correct, wicd set's up eth0, that's how we got the 11-12 second bootup >> > > time. Otherwise if eth0 is handled by /etc/network/interfaces bootup >> > > could last 2 minutes for users who don't connect eth0. I should >> > > atleast really move ntp from S03 to S06.. >> > >> > @Robert >> > >> > There's no need to pull in wicd to solve this; all you need to do is to >> > replace "auto eth0" with "allow-hotplug eth0" (not both) in >> > "/etc/network/interfaces". This gives you eth0 at boot if it's plugged >> in >> > but it doesn't wait if it's not, and if you plug it in later it comes >> right >> > up. Oddly it doesn't even wait very long if it's plugged in at start-up >> > and there is no dhcp being offered. (all of this is assuming "iface >> eth0 >> > inet dhcp" is in there too; I imagine a static route comes up right >> away >> > regardless.) >> > >> > Cheers. >> This is not what allow-hotplug means. It refers to an ethernet interface >> such >> as a USB device being plugged in. In order to get the behaviour you want >> you need ifplugd. To quote from the package description:- >> >> Description-en: configuration daemon for ethernet devices >> ifplugd is a daemon which will automatically configure your ethernet >> device >> when a cable is plugged in and automatically de-configure it if the >> cable is >> pulled out. This is useful on laptops with onboard network adapters, >> since it >> will only configure the interface when a cable is really connected. >> >> David >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
