Ipv OVH: service networking Error

jrd10 · February 27, 2021, 2:56pm

Bonjour et bravo pour YNH qui a bien évolué depuis 2 ans,
particulièrement dans la partie auto-diagnostic

Suite à une manip sur l’ip v6, j’ai cette erreur dans le service networking status

dhclient[7579]: suspect value in domain_search option - discarded
dhclient[7579]: suspect value in domain_search option - discarded
dhclient[7579]: Error printing text.
(que je n’avais pas avant )

Sur un VPS SSD1 OVH, YNH à jour, dns v6 ok,
je retournais une “remarque” dans l’autodiagnostic sur l’ip v6.

J’ai suivi ce tuto (parmi d’autres)
https://forum.yunohost.org/t/resolu-probleme-avec-i pv6/11556/15
maintenant c’est OK

Mais en vérifiant le status du service…

    admin@jreservices:/etc/network$ sudo service networking status                                      
    ● networking.service - Raise network interfaces
       Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)         
       Active: active (exited) since Sat 2021-02-27 15:37:59 CET; 5s ago
         Docs: man:interfaces(5)                                                                        
      Process: 7569 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)          
     Main PID: 7569 (code=exited, status=0/SUCCESS)                                                     
        Tasks: 1 (limit: 2320)                                                                          
       Memory: 1.9M                                                                                     
       CGroup: /system.slice/networking.service                                                         
               └─7579 /sbin/dhclient -4 -v -i -pf /run/dhclient.ens3.pid -lf /var/lib/dhcp/dhclient.ens3
                                                                                                        
    Feb 27 15:37:56 jreservices.fr dhclient[7579]: suspect value in domain_search option - discarded
    Feb 27 15:37:56 jreservices.fr dhclient[7579]: suspect value in domain_search option - discarded
    Feb 27 15:37:57 jreservices.fr dhclient[7579]: Error printing text.
    Feb 27 15:37:57 jreservices.fr ifup[7569]: Error printing text.                                     
    Feb 27 15:37:57 jreservices.fr dhclient[7579]: bound to 51.77.158.179 -- renewal in 32817 seconds.  
    Feb 27 15:37:57 jreservices.fr ifup[7569]: bound to 51.77.158.179 -- renewal in 32817 seconds.      
    Feb 27 15:37:57 jreservices.fr ifup[7569]: Sending network state change signal to nslcd...done.     
    Feb 27 15:37:59 jreservices.fr ifup[7569]: Waiting for DAD... Done                                  
    Feb 27 15:37:59 jreservices.fr ifup[7569]: Sending network state change signal to nslcd...done.     
    Feb 27 15:37:59 jreservices.fr systemd[1]: Started Raise network interfaces.

Voir les 3 erreurs en tête de liste.

Et pourtant, elle tourne !

admin@jreservices:/etc/network$ ping -v6 jreservices.fr                                             
PING jreservices.fr(jreservices.fr (2001:41d0:305:2100::6f4c)) 56 data bytes                        
64 bytes from jreservices.fr (2001:41d0:305:2100::6f4c): icmp_seq=1 ttl=64 time=0.059 ms

Merci d’un retour, encore bravo.
jrd10

jrd10 · February 27, 2021, 3:06pm

rebonjour,

A tout hasard, j’ajoute une copie de mon fichier interfaces

Le deux lignes iface m’étonne. Une en loopback, l’autres en dhcp. Mais je ne suis pas expert :).

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*                                                                  
                                                                                                    
# The loopback network interface
auto lo                                                                                             
iface lo inet loopback                                                                              
                                                                                                    
# The primary network interface
allow-hotplug ens4                                                                                  
iface ens4 inet dhcp                                                                                
                                                                                                    
# Add for ipv6 YUNOHOST. 20210227, bu jrd10 
                                                                                                    
iface ens3 inet6 static                                                                             
address 2001:41d0:305:2100:0:0:0:6f4c                                                               
netmask 128                                                                                         
post-up /sbin/ip -6 route add 2001:41d0:0305:2100:0000:0000:0000:0001 dev ens3                      
post-up /sbin/ip -6 route add default via 2001:41d0:0305:2100:0000:0000:0000:0001 dev ens3          
pre-down /sbin/ip -6 route del default via 2001:41d0:0305:2100:0000:0000:0000:0001 dev ens3         
pre-down /sbin/ip -6 route del 2001:41d0:0305:2100:0000:0000:0000:0001 dev ens3

et mon ip a, ens3 OK

admin@jreservices:/etc/network$ ip a                                                                
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 100
0
    link/ether fa:16:3e:2b:49:4b brd ff:ff:ff:ff:ff:ff
    inet 51.77.158.179/32 brd 51.77.158.179 scope global dynamic ens3
       valid_lft 85128sec preferred_lft 85128sec
    inet6 2001:41d0:305:2100::6f4c/128 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe2b:494b/64 scope link 
       valid_lft forever preferred_lft forever

Merci de tout retour.

Aleks · February 27, 2021, 4:25pm

J’ai ptete une idée d’où ça peut venir

Tu peux faire un grep -nr domain_search /etc/dhcp ?

jrd10 · February 27, 2021, 5:33pm

Merci du retour rapide.

admin@jreservices:~$ grep -nr domain_search /etc/dhcp                                                                                                                                         
/etc/dhcp/dhclient-enter-hooks.d/resolvconf:32:                 if [ "$new_domain_name_servers" ] && [ "$new_domain_search" ] ; then                                                          
/etc/dhcp/dhclient-enter-hooks.d/resolvconf:33:                         R="${R}search $new_domain_search                                                                                      
/etc/dhcp/dhclient-enter-hooks.d/resolvconf:52:                 if [ "$new_dhcp6_name_servers" ] && [ "$new_dhcp6_domain_search" ] ; then                                                     
/etc/dhcp/dhclient-enter-hooks.d/resolvconf:53:                         R="${R}search $new_dhcp6_domain_search                                                                                
/etc/dhcp/debug:22:                            domain_name domain_search domain_name_servers \                                                                                                
/etc/dhcp/debug:26:                            dhcp6_domain_search dhcp6_name_servers ; do

José

system · March 14, 2021, 5:33pm

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.