9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Armando Camarero <arcepi@arcepi.net>
Subject: Re: [9fans] Re: booting a terminal in qemu
Date: Wed, 28 Feb 2007 22:11:18 -0500	[thread overview]
Message-ID: <20070301031118.60F131F35FD@medicine-bow.quanstro.net> (raw)
In-Reply-To: <45E5D946.7080902@arcepi.net>

you learn something new every day.  i didn't know about the -p option to ip/ipconfig.

the function that does the work for dhcp and ip/ipconfig is parseipmask(2).
parseipmask does not differentiate between "255.255.255.0" and "/120",
so it is not likely to be the problem.

the other difference in your ndb entries is the missing dns entry in
the second.  how did you check that the network doesn't work?  have you tried to
ping the gateway?
	ip/ping 10.0.2.2
if that works, it's a dns problem.

- erik

Armando Camarero <arcepi@arcepi.net> writes

| I'm trying to manually configure the NIC in a normal Plan 9 install on
| QEMU. If I run ip/ipconfig (so it gets configured using DHCP) /net/ndb
| looks:
| 
| ip=10.0.2.15 ipmask=255.255.255.0 ipgw=10.0.2.2
|     dns=10.0.2.3
| 
| and network works fine.
| 
| But if I run ip/ipconfig -g 10.0.2.2 ether /net/ether0 10.0.2.15
| 255.255.255.0 it looks:
| 
| ip=10.0.2.15 ipmask=/120 ipgw=10.0.2.2
| 
| and I can't use network. Is "ipmask=/120" correct?
| 
| Is this what makes Plan 9 not boot using network in QEMU?
| 
| Armando.


  parent reply	other threads:[~2007-03-01  3:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 19:30 [9fans] " John Floren
2007-02-27 21:12 ` Steve Simon
2007-02-27 21:09   ` William Josephson
2007-02-27 22:40 ` [9fans] " John Floren
2007-02-27 23:24   ` Russ Cox
2007-02-28 19:10     ` ron minnich
2007-02-28 19:34     ` Armando Camarero
2007-02-28 19:51       ` Gabriel Diaz
2007-03-01  3:11       ` erik quanstrom [this message]
2007-03-01 13:15         ` Armando Camarero
2007-02-28 20:13     ` Bakul Shah

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=20070301031118.60F131F35FD@medicine-bow.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=arcepi@arcepi.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).