bruno a écritPas étonnant que cela ne fonctionne pas…
Il faut modifier ton fichier /etc/netplan/50-cloud-init.yaml comme suit :
network:
ethernets:
enp2s0:
addresses: [192.168.0.250/24]
gateway4: 192.168.0.254
nameservers:
addresses: [80.67.169.12, 80.67.169.40]
dhcp4: false
dhcp6: false
version: 2
Puis
sudo netplan apply
et enfin
sudo systemctl restart systemd-networkd
Voir la doc [doc]netplan[/doc]
Bruno bonne nouvelle grace à toi les cartes ethernet fonctionne le fait qui na pas ping google mais l'ip c'est à cause du /etc/resolv.conf
il y avez marquer nameserver 192.168.0.254
alors que le système met par défaut ceci
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS
# servers currently in use.
#
# Third party programs must not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5)
# in a different way, replace this symlink by a static file or a
# different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported
# modes of operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
mais le problème quand je ping ça affiche ceci c'est normale
neko-world@neko-world:~$ ping google.fr
PING google.fr(par10s28-in-x03.1e100.net (2a00:1450:4007:80a::2003)) 56 data bytes
64 bytes from par10s28-in-x03.1e100.net (2a00:1450:4007:80a::2003): icmp_seq=1 ttl=57 time=23.8 ms
64 bytes from par10s28-in-x03.1e100.net (2a00:1450:4007:80a::2003): icmp_seq=2 ttl=57 time=23.6 ms
^C
--- google.fr ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 23.642/23.740/23.838/0.098 ms
neko-world@neko-world:~$
