On Tue, Sep 27, 2011 at 8:08 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > On Tue, 27 Sep 2011 07:56:55 -0700 > Mark Knecht <markkne...@gmail.com> wrote: > >> Hi Alan, >> OK, so wicd really does seem to do the job. It was only about 10 >> minutes to get it working. Thanks to you and others for suggesting I >> look at it. >> >> Basically, I've removed net.eth0 and net.wlan0 from rc-update and >> added them with '!' to hotplug in rc.conf. Additionally I commented >> out everything in /etc/conf.d/net just to ensure no one is using it. I >> configured the settings for both networks in wicd to different ip >> addresses and they seem to be what the machine is using. Switching >> between the two networks is completely painless. All good so far. >> >> The only thing I've noticed is that ntp-client doesn't run when >> booting. ntpd does run immediately after ntp-client fails. I'm not >> sure if that's caused by some delay in the wired network coming up >> using wicd or something else but it was working in my previous setup. >> Any ideas about that one? > > Yes, I had that too. IIRC the fix is to tweak the ntp init scripts to > only run after the wicd daemon is running. The init script for ntp > assumes you'll be using the net.* stuff. > > This might warrant a properly bug report actually. > >> Anyway, I suspect I could drop in at the library and get it to >> connect there. I'll give that a try later this week. > Thanks. I'll explore that and if I find the same thing I'll submit a bug report if there isn't one already.
Cheers, Mark
