From: Armando Camarero <arcepi@arcepi.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: booting a terminal in qemu
Date: Wed, 28 Feb 2007 20:34:30 +0100 [thread overview]
Message-ID: <45E5D946.7080902@arcepi.net> (raw)
In-Reply-To: <ee9e417a0702271524x69e35c16ndfe765323452fad8@mail.gmail.com>
Russ Cox escribió:
> This should work as far as Plan 9 is concerned.
> It's qemu that is troublesome. One possible approach
> to debugging is to boot the live (install) CD and then
> run ip/ipconfig -g 10.0.2.2 ether /net/ether0 10.0.2.15 255.255.255.0
> and see if that's enough to get a working network (i.e.,
> can you ping or telnet to port 567 or 9fs the remote machine).
>
> I have this script as my /etc/qemu-ifup, though I can't
> remember exactly why it is needed:
>
> #!/bin/sh
> sudo -p "Password for $0:" /sbin/ifconfig $1 172.20.0.1
>
> Russ
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.
next prev parent reply other threads:[~2007-02-28 19:34 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 [this message]
2007-02-28 19:51 ` Gabriel Diaz
2007-03-01 3:11 ` erik quanstrom
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=45E5D946.7080902@arcepi.net \
--to=arcepi@arcepi.net \
--cc=9fans@cse.psu.edu \
/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).