Une fois la ligne de cmd lancée :

Reading package lists... Done
Building dependency tree
Reading state information... Done
omr-glorytun is already the newest version (0.3.4-4).
0 upgraded, 0 newly installed, 0 to remove and 96 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up omr-glorytun (0.3.4-4) ...
Failed to enable unit: Unit file glorytun-udp@tun0.service does not exist.
dpkg: error processing package omr-glorytun (--configure):
 installed omr-glorytun package post-installation script subprocess returned error exit status                         1
Errors were encountered while processing:
 omr-glorytun
E: Sub-process /usr/bin/dpkg returned an error code (1)

puis un "journalctl -xe" :

-- Subject: A new session 3 has been created for user debian
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 3 has been created for the user debian.
--
-- The leading process of the session is 1878.
Jun 15 14:43:54 vps-30998b9f systemd[1]: Started Session 3 of user debian.
-- Subject: A start job for unit session-3.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-3.scope has finished successfully.
--
-- The job identifier is 254.
Jun 15 14:43:57 vps-30998b9f sudo[1914]:   debian : TTY=pts/0 ; PWD=/home/debian
Jun 15 14:43:57 vps-30998b9f sudo[1914]: pam_unix(sudo:session): session opened
Jun 15 14:44:27 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is
Jun 15 14:44:34 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is
Jun 15 14:44:58 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is
Jun 15 14:45:41 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is
Jun 15 14:45:43 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is
lines 1995-2017/2017 (END)
-- Subject: A new session 3 has been created for user debian
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 3 has been created for the user debian.
--
-- The leading process of the session is 1878.
Jun 15 14:43:54 vps-30998b9f systemd[1]: Started Session 3 of user debian.
-- Subject: A start job for unit session-3.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-3.scope has finished successfully.
--
-- The job identifier is 254.
Jun 15 14:43:57 vps-30998b9f sudo[1914]:   debian : TTY=pts/0 ; PWD=/home/debian ; USER=root ; COMMAND=/bin/
Jun 15 14:43:57 vps-30998b9f sudo[1914]: pam_unix(sudo:session): session opened for user root by debian(uid=
Jun 15 14:44:27 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:44:34 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:44:58 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:45:41 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:45:43 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
lines 1995-2017/2017 (END)
-- Subject: A new session 3 has been created for user debian
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 3 has been created for the user debian.
--
-- The leading process of the session is 1878.
Jun 15 14:43:54 vps-30998b9f systemd[1]: Started Session 3 of user debian.
-- Subject: A start job for unit session-3.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-3.scope has finished successfully.
--
-- The job identifier is 254.
Jun 15 14:43:57 vps-30998b9f sudo[1914]:   debian : TTY=pts/0 ; PWD=/home/debian ; USER=root ; COMMAND=/bin/bash
Jun 15 14:43:57 vps-30998b9f sudo[1914]: pam_unix(sudo:session): session opened for user root by debian(uid=0)
Jun 15 14:44:27 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:44:34 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:44:58 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:45:41 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected
Jun 15 14:45:43 vps-30998b9f ss-server[546]: getpeername: Transport endpoint is not connected


 

En ajoutant un --reinstall ça doit être mieux, "apt-get -y install --reinstall omr-glorytun"

Non tjs pas 

Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 96 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for omr-glorytun:amd64

Non tjs pas 

Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 96 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for omr-glorytun:amd64

"apt-get remove omr-glorytun" ?
Sinon oui réinstallation du VPS, je n'ai aucune idée de comment tu as pu avoir ce mélange étrange.

Si le VPS est dédié à cet usage c'est effectivement le plus simple/rapide de le réinstaller que de chercher 107 ans ^^.

Si le VPS est dédié à cet usage c'est effectivement le plus simple/rapide de le réinstaller que de chercher 107 ans ^^.

Oui oui tout à fait d'accord, des fois on se prend la tête pour pas grand chose ! 

Bonjour ycarus

J ai fait l update avec l ipv6 mais depuis je pouvais plus acceder au 192.168.100.1 pendant un moment de mon pc  connecte en ethernet sur l omr ,les sites ne s ouvraient plus et je n arrive meme plus a rentrer dans les differents modems à partir de celui-ci alors qu il n y avait aucun souci avec la version precedente.

Explications possibles? et remedes possibles?

Si on veut desactiver l ipv6 sur omr ,comment doit on proceder?

Merci de ta reponse

Il faudrait plus de détails car la c'est pas très clair : ça fonctionne maintenant ou pas ?
Pour désactiver l'IPv6 c'est l'inverse que ce qui a été fait pour l'activer: en décochant la case qui se trouve dans les paramètres avancées du wizard.