9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Patryk Laurent <plaurent@me.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Help with networking on Virtual Box
Date: Tue, 11 Feb 2014 07:33:43 -0800	[thread overview]
Message-ID: <6E5DB994-69A7-4395-8E7F-A2801DF92364@me.com> (raw)
In-Reply-To: <CAK9Gx1euSVy+MuL1_y4dkeRGg2kuM7h9zcDmb-EVetZ3s-983w@mail.gmail.com>

Hi Peter,

I had the same DNS issue under VirtualBox. Here is my procedure after every reboot (I am new to plan9 so there may be a better way):

1. Run ip/ipconfig
2. cat /net/ipselftab to find your VM's internal ip (10.0.x.x?)
3. Set your IP in /lib/ndb/local  ip = …
4. Run ndb/dns -r

I don't know enough about plan9 to know why this is necessary.  I pieced this procedure together using the docs and help from the IRC channel. 

Plan9 is really cool though -- enjoy!

Best,
Patryk



> On Feb 11, 2014, at 3:32, Peter Hull <peterhull90@gmail.com> wrote:
> 
> Dear All,
> I am just trying to set up Plan 9 so I can have a play with it. I'm
> running it in VirtualBox 4.3.6 and I'm running into the DNS problem
> that has been reported earlier [1]
> 
> ip/ipconfig seems to run fine but it assigns an address of 127.0.0.1
> and DNS doesn't work.
> 
> Unfortunately (as far as I can see) the previous reports didn't come
> up with a solution or the reporter found a different way to run Plan
> 9.
> 
> I used the -D option on ip/ipconfig and got this:
> term% ip/ipconfig -D
> ipconfig: parsebootp: new packet
> ipconfig: parseoptions: type(53) len 1, bytes left 58
> ipconfig: parseoptions: serverid(54) len 4, bytes left 55
> ipconfig: parseoptions: lease(51) len 4, bytes left 49
> ipconfig: parseoptions: ipmask(1) len 4, bytes left 43
> ipconfig: parseoptions: ipgw(3) len 4, bytes left 37
> ipconfig: parseoptions: dns(6) len 4, bytes left 31
> ipconfig: got offer from 0.0.0.0
> ipconfig: lease=86400
> ipconfig: server=192.168.1.1 sname=
> ipconfig: parsebootp: new packet
> ipconfig: parseoptions: type(53) len 1, bytes left 58
> ipconfig: parseoptions: serverid(54) len 4, bytes left 55
> ipconfig: parseoptions: lease(51) len 4, bytes left 49
> ipconfig: parseoptions: ipmask(1) len 4, bytes left 43
> ipconfig: parseoptions: ipgw(3) len 4, bytes left 37
> ipconfig: parseoptions: dns(6) len 4, bytes left 31
> ipconfig: got ack from 0.0.0.0
> ipconfig: lease=86400
> ipconfig: ipaddr=192.168.1.25 ipmask=255.255.255.0
> ipconfig: ipgw=192.168.1.1
> ipconfig: dns=192.168.1.1
> ipconfig: server=192.168.1.1 sname=
> term% cat /net/ndb
> ip=127.0.0.1 ipmask=/104 ipgw=::
> sys=gnot
> sys=gnot
> dns=192.168.1.1
> 
> Does anyone know how I might go about solving the problem?
> 
> Thanks,
> Peter
> 
> [1]: http://9fans.net/archive/2013/08/31
> 



  parent reply	other threads:[~2014-02-11 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 11:32 Peter Hull
2014-02-11 13:30 ` erik quanstrom
2014-02-11 15:33 ` Patryk Laurent [this message]
2014-02-11 17:58 ` Bakul Shah
2014-02-11 20:09   ` Peter Hull
2014-02-11 20:40     ` Bakul Shah
2014-02-11 21:27       ` erik quanstrom
2014-02-11 21:29     ` erik quanstrom
2014-02-12  8:17       ` Peter Hull
2014-02-12  8:52         ` Bakul Shah
2014-02-12  9:35           ` Peter Hull

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6E5DB994-69A7-4395-8E7F-A2801DF92364@me.com \
    --to=plaurent@me.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).