It's official--I'm an idiot. That was the problem, a simple ip=10.1.18.190 added to the gozer entry fixed it.
John On Tue, Jul 12, 2011 at 11:36 AM, John Floren <j...@jfloren.net> wrote: > I'm at lunch right now, but if "no ip in ndb" turns out to be the problem I > will have to buy myself a big dunce cap. > > On Jul 12, 2011 11:16 AM, "erik quanstrom" <quans...@quanstro.net> wrote: >>> My /lib/ndb/local contains these lines (gozer gets its IP from a >>> different DHCP server): >>> >>> auth=gozer authdom=mydom >>> >>> sys=gozer dom=gozer.mydom >>> >>> sys=zuul dom=zuul.mydom >>> bootf=/386/9pxeload >>> ip=10.1.18.192 ether=<whatever> >>> >>> Here are some commands I've tried, and the results I've seen: >>> >>> term% cpu -h gozer >>> cpu: can't dial: gozer: port unreachable >> >> so where would your term lookup the ip address of gozer? >> >> - erik >> >
