On 24 Jun, 2013,at 04:07 PM, erik quanstrom wrote: > > Looking in /net/ndb, my network looks like this: > > > > ip=127.0.0.1 ipmask=/104 ipgw=:: > > sys=gnot > > sys=gnot > > dom=gnot.localdomain > > dns=192.168.220.2 > > > > I don't know if that's correct. > > i think this is the issue. if the ip network is 127.0.0.1/104, > then the gateway (:: = 0:0:0:0:0:0:0:0) is not on the > same network. so 192.168.220.2 can't be reached. Thank you. That makes sense. It's unclear to me why /net/ndb is like it is. I had the idea that ipconfig would set everything up for me. Perhaps I was wrong? In other words: After installing a new Plan 9 instance (in VMware), what should I do to get it online? > > Debugging further, it turns out I can query my DNS server directly: > > > > term% ndb/dnsdebug @192.168.220.2 www.google.com > > 31846.1: sending to 192.168.220.2/192.168.220.2 www.google.com ip > > 31846: rcvd OK from 192.168.220.2 ( recurse can_recurse) > > [...snip...] > > this looks like a bug. what is the contents of /net/iproute? /net/iproute: term% cat /net/iproute 0.0.0.0 /96 192.168.220.2 4 none - 192.168.220.0 /120 192.168.220.0 4i ifc 1 192.168.220.0 /128 192.168.220.0 4b ifc - 192.168.220.128 /128 192.168.220.128 4u ifc 1 192.168.220.255 /128 192.168.220.255 4b ifc - 127.0.0.0 /104 127.0.0.0 4i ifc - 127.0.0.0 /128 127.0.0.0 4b ifc - 127.0.0.1 /128 127.0.0.1 4u ifc - 127.255.255.255 /128 127.255.255.255 4b ifc - 255.255.255.255 /128 255.255.255.255 4b ifc 1