Freebox Server (Ultra V9/ Pop V8/ Delta V7 / Revolution V6 / Mini 4K)

  • État Fermée
  • Pourcentage achevé
    100%
  • Type Anomalie
  • Catégorie Services locaux → Client VPN
  • Assignée à
    mbizon
  • Système d'exploitation Tous
  • Sévérité Critique
  • Priorité Très Basse
  • Basée sur la version 2.1.0
  • Due pour la version Non décidée
  • Échéance Non décidée
  • Votes 1
  • Privée
Concerne le projet: Freebox Server (Ultra V9/ Pop V8/ Delta V7 / Revolution V6 / Mini 4K)
Ouverte par plevi - 15/04/2014
Dernière modification par mbizon - 30/04/2014

FS#14641 - Le mode PPTP ne fonctionne pas

Le client VPN ne fonctionne pas plus en PPTP qu’en OpenVPN (voir autre poste). Les paramètres sont bien acceptés, mais il ne se connecte pas. Bien évidement les même paramètres fonctionnent parfaitement depuis mon client VPN sur PC (supporte OpenVPN et PPTP). Manifestement, cette partie-là du firmware 2.10 n’a pas été testée avant déploiement.

Fermée par  mbizon
30.04.2014 09:26
Raison de la fermeture :  Résolu
plevi a commenté le 16.04.2014 08:46

Edit de cette description: Le mode OpenVPN fonctionne, lui, mais nécessite un ajout de documentation, sans lequel les utilisateurs doivent tâtonner et deviner comment configurer ce mode (Voir tâche n°14648).

Admin
mbizon a commenté le 16.04.2014 11:47

Manifestement vous avez tort puisque je m'en sers.

Fournissez le log de connexion pour permettre le diag.

plevi a commenté le 16.04.2014 15:06

Tout dernier test effectué ce jour, voici mon log (niveau "warning"):

2014-04-16 17:03:09 pptp: protocol error
2014-04-16 17:03:32 ppp: pppd exited with return code 19
2014-04-16 17:03:32 pptp: protocol error
Admin
mbizon a commenté le 16.04.2014 15:10

passez en niveau debug svp

plevi a commenté le 16.04.2014 15:33

Ok, voici mon log en niveau 'debug':

2014-04-16 17:23:09 l3 state change 'l3_wait_down' => 'l3_cleanup_start'
2014-04-16 17:23:09 calling helper script at '/etc/fbxconnman/conn.post-down'
2014-04-16 17:23:09 l3 state change 'l3_cleanup_start' => 'l3_wait_postdown_helper'
2014-04-16 17:23:09 l3 state change 'l3_wait_postdown_helper' => 'l3_cleanup_finish'
2014-04-16 17:23:09 l3 state change 'l3_cleanup_finish' => 'l3_finished'
2014-04-16 17:23:09 state change 'wait_l3_up' => 'wait_l3_down'
2014-04-16 17:23:09 l3 state change 'l3_finished' => 'l3_down'
2014-04-16 17:23:09 state is now DOWN
2014-04-16 17:23:09 state change 'wait_l3_down' => 'l3_finished'
2014-04-16 17:23:09 state change 'l3_finished' => 'wait_l2_down'
2014-04-16 17:23:09 l2 state change 'l2_up' => 'l2_cleanup'
2014-04-16 17:23:09 l2 state change 'l2_cleanup' => 'l2_down'
2014-04-16 17:23:09 state change 'wait_l2_down' => 'down'
2014-04-16 17:23:38 disabling connection
2014-04-16 17:23:38 l2 state change 'l2_down' => 'l2_down'
2014-04-16 17:23:38 l3 state change 'l3_down' => 'l3_down'
2014-04-16 17:23:38 state change 'down' => 'down'
2014-04-16 17:23:42 l2 state change 'l2_down' => 'l2_down'
2014-04-16 17:23:42 l3 state change 'l3_down' => 'l3_down'
2014-04-16 17:23:42 state change 'down' => 'down'
2014-04-16 17:23:42 enabling connection
2014-04-16 17:23:42 state change 'down' => 'wait_l2_up'
2014-04-16 17:23:42 l2 state change 'l2_down' => 'l2_up'
2014-04-16 17:23:42 state change 'wait_l2_up' => 'l2_up'
2014-04-16 17:23:42 state change 'l2_up' => 'wait_l3_up'
2014-04-16 17:23:42 l3 state change 'l3_down' => 'l3_start'
2014-04-16 17:23:42 starting
2014-04-16 17:23:42 calling helper script at '/etc/fbxconnman/conn.pre-up'
2014-04-16 17:23:42 l3 state change 'l3_start' => 'l3_wait_preup_helper'
2014-04-16 17:23:42 l3 state change 'l3_wait_preup_helper' => 'l3_wait_stable'
2014-04-16 17:23:42 pptp: fsm state change: INIT -> RESOLV
2014-04-16 17:23:42 pptp: resolving 'france.privateinternetaccess.com'...
2014-04-16 17:23:42 pptp: fsm state change: RESOLV -> WAIT_RESOLV
2014-04-16 17:23:42 pptp: fsm state change: WAIT_RESOLV -> CONNECT
2014-04-16 17:23:42 pptp: connecting to '62.210.167.201:1723'
2014-04-16 17:23:42 pptp: fsm state change: CONNECT -> WAIT_CONNECT
2014-04-16 17:23:42 pptp: fsm state change: WAIT_CONNECT -> PPTP_CREATE_CTRL
2014-04-16 17:23:42 pptp: snd <Start-Control-Connection-Request>
2014-04-16 17:23:42 pptp: fsm state change: PPTP_CREATE_CTRL -> PPTP_WAIT_CTRL
2014-04-16 17:23:42 pptp: got <Start-Control-Connection-Reply>
2014-04-16 17:23:42 pptp: control connection established
2014-04-16 17:23:42 pptp: fsm state change: PPTP_WAIT_CTRL -> PPTP_DO_CALL
2014-04-16 17:23:42 pptp: snd <Outgoing-Call-Request>
2014-04-16 17:23:42 pptp: fsm state change: PPTP_DO_CALL -> PPTP_WAIT_CALL
2014-04-16 17:23:42 pptp: got <Outgoing-Call-Reply>
2014-04-16 17:23:42 pptp: fsm state change: PPTP_WAIT_CALL -> PPTP_DO_CALL
2014-04-16 17:23:42 pptp: call established
2014-04-16 17:23:42 pptp: local call id:19 - peer call id:57216
2014-04-16 17:23:42 pptp: fsm state change: PPTP_DO_CALL -> ACTIVE
2014-04-16 17:23:42 ppp: started pppd (pid 19952)
2014-04-16 17:23:42 ppp: fsm state change: FORK -> WAIT_PPPD_HELLO
2014-04-16 17:23:42 ppp: pppd: Plugin pppstatus.so loaded.
2014-04-16 17:23:42 ppp: pppd: PPP status plugin
2014-04-16 17:23:42 ppp: got hello message from pppd
2014-04-16 17:23:42 ppp: fsm state change: WAIT_PPPD_HELLO -> ACTIVE
2014-04-16 17:23:42 ppp: pppd: pppstatus: connected to status manager
2014-04-16 17:23:42 ppp: phase change to SERIALCONN
2014-04-16 17:23:42 ppp: asked for connect fd
2014-04-16 17:23:42 ppp: pppd: using channel 19
2014-04-16 17:23:42 ppp: pppd: Using interface ppp0
2014-04-16 17:23:42 ppp: pppd: Connect: ppp0 <--> 
2014-04-16 17:23:42 ppp: pppd: sent [LCP ConfReq id=0x1 <mru 1460> <magic 0x22e2dbb1>]
2014-04-16 17:23:42 ppp: phase change to ESTABLISH
2014-04-16 17:23:42 ppp: pppd: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <auth chap MS-v2> <magic 0x69417e26> <pcomp> <accomp>]
2014-04-16 17:23:42 ppp: remote peer detected
2014-04-16 17:23:42 ppp: pppd: sent [LCP ConfRej id=0x1 <asyncmap 0x0> <accomp>]
2014-04-16 17:23:42 ppp: pppd: rcvd [LCP ConfAck id=0x1 <mru 1460> <magic 0x22e2dbb1>]
2014-04-16 17:23:42 ppp: pppd: rcvd [LCP ConfReq id=0x2 <auth chap MS-v2> <magic 0x69417e26> <pcomp>]
2014-04-16 17:23:42 ppp: pppd: sent [LCP ConfAck id=0x2 <auth chap MS-v2> <magic 0x69417e26> <pcomp>]
2014-04-16 17:23:42 ppp: pppd: sent [LCP EchoReq id=0x0 magic=0x22e2dbb1]
2014-04-16 17:23:42 ppp: phase change to AUTHENTICATE
2014-04-16 17:23:42 ppp: pppd: rcvd [LCP EchoReq id=0x0 magic=0x69417e26]
2014-04-16 17:23:42 ppp: pppd: sent [LCP EchoRep id=0x0 magic=0x22e2dbb1]
2014-04-16 17:23:42 ppp: pppd: rcvd [CHAP Challenge id=0x30 <1e4ebe9d4b72a0ade619845a146d513c>, name = "pptpd"]
2014-04-16 17:23:42 ppp: pppd: added response cache entry 0
2014-04-16 17:23:42 ppp: pppd: sent [CHAP Response id=0x30 <f85e5fa4aea668a0a6e733062552783800000000000000003d7682c6c5140efe386977e737f86484bd88e5546928180700>, name = "[Mon Identifiant]"]
2014-04-16 17:23:42 ppp: pppd: rcvd [LCP EchoRep id=0x0 magic=0x69417e26]
2014-04-16 17:23:43 ppp: pppd: rcvd [CHAP Failure id=0x30 ""]
2014-04-16 17:23:43 ppp: pppd: MS-CHAP authentication failed: 
2014-04-16 17:23:43 ppp: pppd: CHAP authentication failed
2014-04-16 17:23:43 ppp: pppd: sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
2014-04-16 17:23:43 ppp: authentication failed
2014-04-16 17:23:43 ppp: phase change to TERMINATE
2014-04-16 17:23:43 ppp: phase change to ESTABLISH
2014-04-16 17:23:43 ppp: pppd: rcvd [LCP TermReq id=0x3 "Authentication failed"]
2014-04-16 17:23:43 ppp: pppd: sent [LCP TermAck id=0x3]
2014-04-16 17:23:43 ppp: pppd: rcvd [LCP TermAck id=0x2]
2014-04-16 17:23:43 ppp: pppd: Connection terminated.
2014-04-16 17:23:43 ppp: phase change to DISCONNECT
2014-04-16 17:23:43 ppp: pppd exited with return code 19
2014-04-16 17:23:43 ppp: fsm state change: ACTIVE -> DEAD
2014-04-16 17:23:43 pptp: fsm state change: ACTIVE -> PPTP_SEND_CALL_CLEAR
2014-04-16 17:23:43 pptp: snd <Call-Clear-Request>
2014-04-16 17:23:43 pptp: fsm state change: PPTP_SEND_CALL_CLEAR -> PPTP_WAIT_DISCONNECT
2014-04-16 17:23:43 pptp: remote close connection
2014-04-16 17:23:43 pptp: protocol error
2014-04-16 17:23:43 pptp: fsm state change: PPTP_WAIT_DISCONNECT -> DOWN
2014-04-16 17:23:43 l3 is now stable
2014-04-16 17:23:43 l3 does not fulfil config requirement
2014-04-16 17:23:43 l3 state change 'l3_wait_stable' => 'l3_bring_down'
2014-04-16 17:23:43 waiting for l3 providers to go down
2014-04-16 17:23:43 l3 state change 'l3_bring_down' => 'l3_wait_down'
2014-04-16 17:23:43 l3 state change 'l3_wait_down' => 'l3_cleanup_start'
2014-04-16 17:23:43 calling helper script at '/etc/fbxconnman/conn.post-down'
2014-04-16 17:23:43 l3 state change 'l3_cleanup_start' => 'l3_wait_postdown_helper'
2014-04-16 17:23:43 l3 state change 'l3_wait_postdown_helper' => 'l3_cleanup_finish'
2014-04-16 17:23:43 l3 state change 'l3_cleanup_finish' => 'l3_finished'
2014-04-16 17:23:43 state change 'wait_l3_up' => 'wait_l3_down'
2014-04-16 17:23:43 l3 state change 'l3_finished' => 'l3_down'
2014-04-16 17:23:43 state is now DOWN
2014-04-16 17:23:43 state change 'wait_l3_down' => 'l3_finished'
2014-04-16 17:23:43 state change 'l3_finished' => 'wait_l2_down'
2014-04-16 17:23:43 l2 state change 'l2_up' => 'l2_cleanup'
2014-04-16 17:23:43 l2 state change 'l2_cleanup' => 'l2_down'
2014-04-16 17:23:43 state change 'wait_l2_down' => 'down'

J'ai juste changé mon identifiant, sans intérêt ici.

Admin
mbizon a commenté le 16.04.2014 15:37

Regardez ces lignes:

2014-04-16 17:23:43 ppp: pppd: MS-CHAP authentication failed:
2014-04-16 17:23:43 ppp: pppd: CHAP authentication failed
2014-04-16 17:23:43 ppp: pppd: sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
2014-04-16 17:23:43 ppp: authentication failed
2014-04-16 17:23:43 ppp: phase change to TERMINATE
2014-04-16 17:23:43 ppp: phase change to ESTABLISH
2014-04-16 17:23:43 ppp: pppd: rcvd [LCP TermReq id=0x3 "Authentication failed"]

le mot de passe serait incorrect ?

plevi a commenté le 16.04.2014 15:45

C'est pourtant MÊME mot de passe que j'utilise chez ce même fournisseur VPN en mode OpenVPN et, là, ça marche. Ceci dit, c'est un mot de passe un peu long et légèrement chiadé: en voici une version modifiée (les chiffres et lettres min/majuscules ont été changées mais leur emplacement dans la chaine est strictement celui-là et les autres symboles sont inchangés: Bel7501!Joe_

Admin
mbizon a commenté le 16.04.2014 15:59

Essayez avec le cryptage désactivé en mode PAP (ne copiez pas les logs).

plevi a commenté le 16.04.2014 16:15

C'est fait. Le résultat est le même: "protocol error", "pppd exited with return code 19", etc.

Admin
mbizon a commenté le 16.04.2014 16:17

pouvez vous me copier-coller juste les lignes de log après "phase change to AUTHENTICATE" (attention de ne pas inclure vos identifiants/mdp)

plevi a commenté le 16.04.2014 16:24
2014-04-16 18:21:19 ppp: phase change to AUTHENTICATE
2014-04-16 18:21:19 ppp: pppd: rcvd [LCP EchoReq id=0x0 magic=0x69980f7f]
2014-04-16 18:21:19 ppp: pppd: sent [LCP EchoRep id=0x0 magic=0x3d4ca444]
2014-04-16 18:21:19 ppp: pppd: rcvd [CHAP Challenge id=0x47 <b8353e9ba970b87237f12ea449d25056>, name = "pptpd"]
2014-04-16 18:21:19 ppp: pppd: added response cache entry 0
2014-04-16 18:21:19 ppp: pppd: sent [CHAP Response id=0x47 <a3e866741c203007a9ef970f3f07d2c30000000000000000e3a4c8855c1c788bdcee374060afd7223c6c30dd5c6e01db00>, name = "IDENTIFIANT"]
2014-04-16 18:21:19 ppp: pppd: rcvd [LCP EchoRep id=0x0 magic=0x69980f7f]
2014-04-16 18:21:20 ppp: pppd: rcvd [CHAP Failure id=0x47 ""]
2014-04-16 18:21:20 ppp: pppd: MS-CHAP authentication failed: 
2014-04-16 18:21:20 ppp: pppd: CHAP authentication failed
2014-04-16 18:21:20 ppp: pppd: sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
2014-04-16 18:21:20 ppp: pppd: rcvd [LCP TermReq id=0x3 "Authentication failed"]
2014-04-16 18:21:20 ppp: pppd: sent [LCP TermAck id=0x3]
2014-04-16 18:21:20 ppp: authentication failed
2014-04-16 18:21:20 ppp: phase change to TERMINATE
2014-04-16 18:21:20 ppp: phase change to ESTABLISH
2014-04-16 18:21:20 ppp: pppd: rcvd [LCP TermAck id=0x2]
2014-04-16 18:21:20 ppp: pppd: Connection terminated.
2014-04-16 18:21:20 ppp: phase change to DISCONNECT
2014-04-16 18:21:20 ppp: pppd exited with return code 19
2014-04-16 18:21:20 ppp: fsm state change: ACTIVE -> DEAD
2014-04-16 18:21:20 pptp: fsm state change: ACTIVE -> PPTP_SEND_CALL_CLEAR
2014-04-16 18:21:20 pptp: snd <Call-Clear-Request>
2014-04-16 18:21:20 pptp: fsm state change: PPTP_SEND_CALL_CLEAR -> PPTP_WAIT_DISCONNECT
2014-04-16 18:21:20 pptp: remote close connection
2014-04-16 18:21:20 pptp: protocol error
2014-04-16 18:21:20 pptp: fsm state change: PPTP_WAIT_DISCONNECT -> DOWN
2014-04-16 18:21:20 l3 is now stable
2014-04-16 18:21:20 l3 does not fulfil config requirement
2014-04-16 18:21:20 l3 state change 'l3_wait_stable' => 'l3_bring_down'
2014-04-16 18:21:20 waiting for l3 providers to go down
2014-04-16 18:21:20 l3 state change 'l3_bring_down' => 'l3_wait_down'
2014-04-16 18:21:20 l3 state change 'l3_wait_down' => 'l3_cleanup_start'
2014-04-16 18:21:20 calling helper script at '/etc/fbxconnman/conn.post-down'
2014-04-16 18:21:20 l3 state change 'l3_cleanup_start' => 'l3_wait_postdown_helper'
2014-04-16 18:21:20 l3 state change 'l3_wait_postdown_helper' => 'l3_cleanup_finish'
2014-04-16 18:21:20 l3 state change 'l3_cleanup_finish' => 'l3_finished'
2014-04-16 18:21:20 state change 'wait_l3_up' => 'wait_l3_down'
2014-04-16 18:21:20 l3 state change 'l3_finished' => 'l3_down'
2014-04-16 18:21:20 state is now DOWN
2014-04-16 18:21:20 state change 'wait_l3_down' => 'l3_finished'
2014-04-16 18:21:20 state change 'l3_finished' => 'wait_l2_down'
2014-04-16 18:21:20 l2 state change 'l2_up' => 'l2_cleanup'
2014-04-16 18:21:20 l2 state change 'l2_cleanup' => 'l2_down'
2014-04-16 18:21:20 state change 'wait_l2_down' => 'down'
Admin
mbizon a commenté le 16.04.2014 16:39

le mode indique toujours que le MS-CHAP est utilisé

il faut bien décocher les cases et faire start/stop sur le VPN.

plevi a commenté le 16.04.2014 16:47

C'est peut-être là le problème: j'ai suivi strictement ce que vous m'avez conseillé et j'avais tout décoché, sauf PAP. En outre, à chaque nouvelle tentative je fais un start/stop afin d'avoir un log - et des conditions de test - clean.

plevi a commenté le 16.04.2014 16:50

Tiens tiens tiens ... encore plus intéressant: pris de doute, je revérifie la config de mon PPTP et là, je vois que tout est décoché, sauf ... MS-CHAPv2 !! Je ré-édite en enlevant ce dernier et en re-cochant PAP puis je sauve et je ferme. Ensuite, je rouvre la fenêtre dédition et là ... c'est encore MS-CHAPv2 qui est activé !!

Admin
mbizon a commenté le 16.04.2014 17:16

En effet, ça n'a peut être rien à voir avec votre problème mais effectivement ça ne fonctionne pas.

Impossible de tester en PAP pour l'instant donc, il faudra attendre le prochain firmwarE.

plevi a commenté le 17.04.2014 08:26

Ah ... et une résolution est planifiée ?

Même problème que toi je dois resté en mode PAP mais il ne sauvegarde pas correctement le config PPTP :-( vivement le correction ....

Chargement...

Activer les raccourcis clavier

Liste des tâches

Détails de la tâche

Édition de la tâche