9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kyohei Kadota <lufia@lufia.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] IP routing problems on GCP
Date: Tue, 1 Sep 2020 19:08:36 +0900	[thread overview]
Message-ID: <CAFMepcnrbdQxJ1Fufa=HYQFKQLd8hwNJ8i44G2MKANu-4uRcdg@mail.gmail.com> (raw)
In-Reply-To: <cbb19eb0-9f69-475e-ba42-5f52f101bdd1@www.fastmail.com>

> ip-ipconfig-mask.diff

What intentions were these changes added?

Though I'm not sure why that was added, I've noticed that DHCP of the
VPC sends two Classless Static Route options. (DHCP option number:
121)

1. ip=0.0.0.0   mask=/0  remote=17.xx.0.1
2. ip=17.xx.0.1 mask=/32 remote=0.0.0.0

In my opinion, maybe remote=0.0.0.0 means the ipnet will be attached
directly to the interface.
If it is true, currently, my instance on GCP has been able to get the
correct network configuration
from DHCP with *hacked* kernel and ip/ipconfig.

2020年8月24日(月) 2:41 David du Colombier <0intro@gmail.com>:
>
> > 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?
>
> Yes, but only using a local file server.
> I've never tried to boot Plan 9 from a remote file server so far.
>
> > 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.
>
> 9legacy includes a patch that considers 32 mask as 0.
>
> http://9legacy.org/9legacy/patch/ip-ipconfig-mask.diff
>
> --
> David du Colombier
>
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Tc21c3dd261e604cf-M926904f4ad643a6a16f23051
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

      reply	other threads:[~2020-09-01 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 13:33 Kyohei Kadota
2020-08-23 17:40 ` [9fans] " David du Colombier
2020-09-01 10:08   ` Kyohei Kadota [this message]

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='CAFMepcnrbdQxJ1Fufa=HYQFKQLd8hwNJ8i44G2MKANu-4uRcdg@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).