Mon serveur YunoHost
Matériel: Raspberry Pi à la maison / avec VPN /
Version de YunoHost: 4.1.7.1
J’ai accès à mon serveur : En SSH | Par la webadmin
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : non
adresse IPv6 du vpn arn doublée ?
Bonjour,
on a configuré une adresse vpn avec un .cube il y a près d’un mois sur un raspberry Pi. Apès une mise à jour, l’adresse IPv6 semble avoir subitement changée…
Je ne comprends pas bien pourquoi on en trouve 2 d’ailleurs maintenant ?
Voici quelques détails:
$ sudo ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.X.XX netmask 255.255.255.0 broadcast 192.168.X.255
inet6 fe80::XXXX:XXXX:XXXX:XXXX prefixlen 64 scopeid 0x20<link>
inet6 2a01:XXX:XXX:XXXX:XXXX:XXXX:XXXX:XXXX prefixlen 64 scopeid 0x0<global>
ether b8:27:eb:9d:42:c9 txqueuelen 1000 (Ethernet)
RX packets 3445 bytes 1255929 (1.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3228 bytes 978934 (955.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3011 bytes 298295 (291.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3011 bytes 298295 (291.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 89.234.141.34 netmask 255.255.255.192 destination 89.234.141.34
inet6 fe80::XXXX:XXXX:XXXX:XXXX prefixlen 64 scopeid 0x20<link>
inet6 2a00:XXXX:XXXX:XXXX::XX prefixlen 128 scopeid 0x0<global>
inet6 2a00:XXXX:XXXX:XXX::XX prefixlen 64 scopeid 0x0<global>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100
Diagnostic
sudo yunohost diagnosis show --issues
reports:
0:
description: DNS records
id: dnsrecords
items:
0:
details:
- Please check the documentation at https://yunohost.org/dns_config if you need help about configuring DNS records.
- The following DNS record does not seem to follow the recommended configuration:
Type: AAAA
Name: @
Current value: 2a00:XXXX:XXXX:XXX::XX
Expected value: 2a00:XXXX:XXXX:XXXX::XX
status: ERROR
summary: Some DNS records are missing or incorrect for domain lucchareyron.com (category basic)
1:
details:
- Please check the documentation at https://yunohost.org/dns_config if you need help about configuring DNS records.
- The following DNS record does not seem to follow the recommended configuration:
Type: AAAA
Name: *
Current value: 2a00:XXXX:XXXX:XXX::XX
Expected value: 2a00:XXXX:XXXX:XXXX::XX
status: WARNING
summary: Some DNS records are missing or incorrect for domain nom_domaine.tld (category extra)
2:
details:
- Please check the documentation at https://yunohost.org/dns_config if you need help about configuring DNS records.
- The following DNS record does not seem to follow the recommended configuration:
Type: AAAA
Name: @
Current value: 2a00:XXXX:XXXX:XXX::XX
Expected value: 2a00:XXXX:XXXX:XXXX::XX
status: ERROR
summary: Some DNS records are missing or incorrect for domain www.nom_domaine.tld (category basic)
1:
description: Email
id: mail
items:
details:
- You should first try to configure the reverse DNS with lucchareyron.com in your internet router interface or your hosting provider interface. (Some hosting provider may require you to send them a support ticket for this).
- Some providers won't let you configure your reverse DNS (or their feature might be broken...). If your reverse DNS is correctly configured for IPv4, you can try disabling the use of IPv6 when sending emails by running 'yunohost settings set smtp.allow_ipv6 -v off'. Note: this last solution means that you won't be able to send or receive emails from the few IPv6-only servers out there.
status: ERROR
summary: No reverse DNS is defined in IPv6. Some emails may fail to get delivered or may get flagged as spam.
C’est embêtant car le reverse dns est configuré pour l’adresse 2a00:XXXX:XXXX:XXXX::XX et non l’adresse 2a00:XXXX:XXXX:XXX::XX
autre commande:
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.X.XX/24 brd 192.168.0.255 scope global dynamic noprefixroute eth0
valid_lft 40771sec preferred_lft 35371sec
inet6 2a01:XXX:XXX:XXXX:XXXX:XXXX:XXXX:XXXX/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86231sec preferred_lft 86231sec
inet6 fe80::XXXX:XXXX:XXXX:XXXX/64 scope link
valid_lft forever preferred_lft forever
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
link/none
inet XX.XXX.XXX.XX/26 brd XX.XXX.XXX.XX scope global tun0
valid_lft forever preferred_lft forever
inet6 2a00:XXXX:XXXX:XXXX::XX/128 scope global
valid_lft forever preferred_lft forever
inet6 2a00:XXXX:XXXX:XXX::XX/64 scope global
valid_lft forever preferred_lft forever
inet6 feXX::XXXX:XXXX:XXXX:XXXX/64 scope link stable-privacy
valid_lft forever preferred_lft forever
Que dois-je faire ??