* [9front] ipv6 configuration
@ 2024-02-03 18:21 igor
2024-02-03 18:35 ` Arne Meyer
0 siblings, 1 reply; 3+ messages in thread
From: igor @ 2024-02-03 18:21 UTC (permalink / raw)
To: 9front; +Cc: igor
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [9front] ipv6 configuration
2024-02-03 18:21 [9front] ipv6 configuration igor
@ 2024-02-03 18:35 ` Arne Meyer
2024-02-03 20:12 ` igor
0 siblings, 1 reply; 3+ messages in thread
From: Arne Meyer @ 2024-02-03 18:35 UTC (permalink / raw)
To: 9front
Hey Igor,
i think you can use an ip=<addr> tuple for ipv6.
> igor@9lab.org hat am 03.02.2024 19:21 CET geschrieben:
>
>
> 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:2a03:4000:48:2e::1 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [9front] ipv6 configuration
2024-02-03 18:35 ` Arne Meyer
@ 2024-02-03 20:12 ` igor
0 siblings, 0 replies; 3+ messages in thread
From: igor @ 2024-02-03 20:12 UTC (permalink / raw)
To: 9front; +Cc: igor
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-02-03 20:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-03 18:21 [9front] ipv6 configuration igor
2024-02-03 18:35 ` Arne Meyer
2024-02-03 20:12 ` igor
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).