From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux
Date: Sat, 7 Jul 2018 17:33:14 +0300 [thread overview]
Message-ID: <CAJ1xhMXHbosW1-CrP-rF9g-48KOkDz4QbRkk9EFAnLLEqCq38w@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmKPyHikuv_xo=j1Z2pknjZCJMm2U3umhYO-a7SZWeX8pg@mail.gmail.com>
Thanks. I'll give that a try.
On Fri, Jul 6, 2018 at 10:37 PM Skip Tavakkolian
<skip.tavakkolian@gmail.com> wrote:
>
> You could use private network addresses (10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16). Your /lib/ndb/local file can then be setup around a subnet like 192.168.9.0/24. According to the following, qemu uses 10.0.2.0/24 when using "user mode networking" and provides a virtual dhcp (10.0.2.2), dns (10.0.2.3) and cifs (10.0.2.4). Using "tap" mode, you get to pick the subnet in qemu-ifup script.
>
> https://en.wikibooks.org/wiki/QEMU/Networking
>
>
> On Fri, Jul 6, 2018 at 9:43 AM Alexander Kapshuk <alexander.kapshuk@gmail.com> wrote:
>>
>> I've installed Plan 9 in qemu on Linux as instructed here:
>> https://9p.io/wiki/plan9/Installing_Plan_9_on_Qemu/index.html
>>
>> Now I'm in the process of converting it into a standalone cpu server.
>> I'm following the instructions given here:
>> https://9p.io/wiki/plan9/Configuring_a_Standalone_CPU_Server/index.html
>>
>> I would like to configure a static IP address for the cpu server, so I
>> can drawterm into it from other machines on my home network.
>> My knowledge of networking is limited. I understand that I need to put this:
>> ip/ipconfig -g <gateway-addr> ether /net/ether0 <ip-addr> <ip-mask>
>>
>> into my /cfg/$sysname/cpurc.
>>
>> What I don't understand, and am asking for assistance with, is where
>> those three ip addresses in the example above have to come from. Do I
>> add them to the ethernet interface on the host system, or is there a
>> way to do this from within the Plan 9 system?
>>
>> Thanks.
>> Alexander Kapshuk.
>>
next prev parent reply other threads:[~2018-07-07 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 16:42 Alexander Kapshuk
2018-07-06 19:25 ` Skip Tavakkolian
2018-07-07 14:33 ` Alexander Kapshuk [this message]
2018-08-25 11:20 ` Alexander Kapshuk
2018-08-25 17:53 ` hiro
2018-08-25 18:27 ` Bakul Shah
2018-08-25 19:17 ` Alexander Kapshuk
2018-08-25 19:28 ` hiro
2018-08-25 20:05 ` Alexander Kapshuk
2018-08-25 20:59 ` hiro
2018-08-26 4:56 ` Alexander Kapshuk
2018-08-26 13:45 ` Alexander Kapshuk
2018-08-25 19:42 ` 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=CAJ1xhMXHbosW1-CrP-rF9g-48KOkDz4QbRkk9EFAnLLEqCq38w@mail.gmail.com \
--to=alexander.kapshuk@gmail.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).