From: igor@9lab.org
To: 9front@9front.org
Cc: igor@9lab.org
Subject: Re: [9front] ipv6 configuration
Date: Sat, 03 Feb 2024 21:12:16 +0100 [thread overview]
Message-ID: <481F2C16B857B87AF909FC825EA1D75A@9lab.org> (raw)
In-Reply-To: <1230131450.4958643.1706985353338@comcenter.netcologne.de>
Quoth Arne Meyer <meyer.arne83@netcologne.de>:
[…]
> i think you can use an ip=<addr> tuple for ipv6.
[…]
Eureka, thanks for the hint!
So I do not need to use ipv6=<addr> but can use
ip=<addr> instead.
This is what a working configuration looks like:
# -- system: mux IPv4 (IP:45.132.244.17/22 GW:45.132.244.1)
sys=mux dom=mux.9lab.org ip=45.132.244.17 ether=6a822e1fa13e
# -- system: mux6 IPv6 (IP:2a03:4000:48:2e::/64 GW:fe80::1)
sys=mux dom=mux.9lab.org ip=2a03:4000:48:2e::1 ipmask=64 ipgw=fe80::1 ether=6a822e1fa13e
cpu% netaudit
env var $sysname=mux looks ok
checking this host's tuple:
sys=mux looks ok
ip=45.132.244.17 looks ok
ip=2a03:4000:48:2e::1 looks ok
dom=mux.9lab.org looks ok
ether=6a822e1fa13e looks ok
checking the network tuple:
we are in ipnet=9lab
ipgw=45.132.244.1 looks ok
ipgw=fe80::1 looks ok
dns=46.38.225.230 does not reply to ping
auth=mux looks ok
no fs= entry (needed for tls boot)
Cheers,
Igor
prev parent reply other threads:[~2024-02-03 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 18:21 igor
2024-02-03 18:35 ` Arne Meyer
2024-02-03 20:12 ` igor [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=481F2C16B857B87AF909FC825EA1D75A@9lab.org \
--to=igor@9lab.org \
--cc=9front@9front.org \
/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).