Uncomment ip/ifconfig in termrc as Erik suggested or stick the four lines that I showed in termrc.local. I think there is some sequencing issue if you run them manually.
Before switching the VB version try changing its network setting to NAT. With a different VB version you'll likely chase a different set if problems! > On Feb 12, 2014, at 12:17 AM, Peter Hull <peterhul...@gmail.com> wrote: > >> On Tue, Feb 11, 2014 at 9:29 PM, erik quanstrom <quans...@quanstro.net> >> wrote: >> i certainly would do some debugging to see if ndb/cs is really >> running, and if dns is running, too. iirc, the default termrc >> has ipconfig commented out, so dns will not start. > I'm typing ip/ipconfig and ndb/dns -r on every reboot at the moment. I > tried ndb/csquery and it looked reasonable. For a query of > 'localhost!cs' I got '/net/localhost/clone cs' and for > 'localhost!dns' I got '/net/localhost/clone dns' > For ndb/dnsquery it looked less good, for 'localhost ip' I got > '!dns:resource does not exist; negrcode 0' and for 'www.google.com ip' > I got '!dns: dns failure' > I have only just started on plan 9 so apologies if this is the wrong > way to test the servers. > > For those already running on virtual box, what version are you > running? I could try that and see if it's a VB problem (I believe they > overhauled the network code in v4.3) > > Thanks. > pete >
