From: Kyohei Kadota <lufia@lufia.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: IP routing problems on GCP
Date: Sun, 23 Aug 2020 22:33:55 +0900 [thread overview]
Message-ID: <CAFMepcn7ajD0py7foPnx-U4WUAFgtAnXNy_+5TxcNiCWA_GVGA@mail.gmail.com> (raw)
Hi.
I'm migrating my 9legacy machines to GCP but my auth/cpu servers can't
get root from the fileserver.
Is there someone that is using full system Plan 9 on GCP?
Notes:
- DHCP of VPC network on GCP sends ipmask=/32 options to that client.
- If ipmask is /32 then ip/ipconfig ignores it.
- Therefore each instance can't reach other instances in the same region.
In my experience, the communications works only if /net/ipifc is
configured from /lib/ndb/local by ip/ipconfig -N, its ipmask is /20,
and it is added to /net/iproute manually that the routes to other
instances, but in this case, the cpu/auth servers couldn't reach to
the fs because nothing to add the routes before getting root.
--
kadota
next reply other threads:[~2020-08-23 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 13:33 Kyohei Kadota [this message]
2020-08-23 17:40 ` [9fans] " David du Colombier
2020-09-01 10:08 ` Kyohei Kadota
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=CAFMepcn7ajD0py7foPnx-U4WUAFgtAnXNy_+5TxcNiCWA_GVGA@mail.gmail.com \
--to=lufia@lufia.org \
--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).