From: igor@9lab.org
To: 9front@9front.org
Cc: igor@9lab.org
Subject: [9front] ipv6 configuration
Date: Sat, 03 Feb 2024 19:21:26 +0100 [thread overview]
Message-ID: <5C4DC27D67F57D53A645D16E277BBA25@9lab.org> (raw)
I am trying to expose my 9front server via ipv6 in addition to ipv4.
The main reason for doing this is because mail servers that are backed
by IPv6 have a higher score and I would like to move my mail server
from obsd to 9front eventually.
Unfortunately my knowledge about ipv6 is very limited and I hope one
of you has a working setup/snippet from /lib/ndb/local that could be
shared.
Here is what I have in /lib/ndb/local with the IPv6 entry
at the bottom:
<snip>
# -- system: localhost
sys=localhost dom=localhost ip=127.0.0.1
# -- authentication server to be used
auth=mux authdom=9lab
# -- network (uniquely identified by 'ip' and 'ipmask')
ipnet=9lab ip=45.132.244.0 ipmask=255.255.252.0 ipgw=45.132.244.1
dom=9lab.org
dns=46.38.225.230
auth=mux
# -- 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=mux6 dom=mux6.9lab.org ipv6=2a03:4000:48:2e::1 ether=6a822e1fa13e
</snap>
The domain name is setup correctly. Reverse DNS works as well
so that can't be an issue.
Here is the output of netaudit:
cpu% netaudit
env var $sysname=mux looks ok
checking this host's tuple:
sys=mux looks ok
ip=45.132.244.17 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
dns=46.38.225.230 does not reply to ping
auth=mux looks ok
no fs= entry (needed for tls boot)
I can't ping the host via ipv6; surely I am forgeting something obvious.
Thanks in advance for any hints.
Cheers,
Igor
next reply other threads:[~2024-02-03 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 18:21 igor [this message]
2024-02-03 18:35 ` Arne Meyer
2024-02-03 20:12 ` igor
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=5C4DC27D67F57D53A645D16E277BBA25@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).