[rÉsolu] vpn pptp avec mppe

Support Debian
#35

A nouveau:

  • as tu suivi les traces de tentative dans les logs sur ton serveur ?
  • as tu essayé de te connecter depuis un client linux (une knoppix, par exemple) depuis le 192.168.0 ?
  • pourrais tu ENFIN donner la config (depuis le temps qu’on avance pas à t’aider) que ton administrateur juge bonne (en masquant les éléments critiques bien sûr) afin que NOUS puissions juger si ce que ton administrateur dit est vrai ?
#36

Salut, voici quelques logs:

[quote]kern.log:
Jul 11 10:05:21 debian kernel: IPv4 over IPv4 tunneling driver
Jul 11 10:05:21 debian kernel: GRE over IPv4 tunneling driver

Jul 11 10:05:21 debian kernel: IPv6 over IPv4 tunneling driver
Jul 11 10:05:21 debian kernel: Bridge firewalling registered

APRES UN MODPROBE PPP_MPPE:
Jul 11 10:10:17 debian kernel: PPP MPPE Compression module registered

debug:
Jul 11 10:05:47 debian pptpd[1953]: CTRL: Reaping child PPP[1954]
Jul 11 10:09:25 debian pptpd[1988]: CTRL: Reaping child PPP[1989]
Jul 11 10:09:26 debian pptpd[1990]: CTRL: Reaping child PPP[1991]
Jul 11 10:09:27 debian pptpd[1992]: CTRL: Reaping child PPP[1993]
Jul 11 10:09:27 debian pptpd[1994]: CTRL: Reaping child PPP[1995]
Jul 11 10:09:27 debian pptpd[1996]: CTRL: Reaping child PPP[1997]
Jul 11 10:11:20 debian pptpd[2028]: CTRL: Reaping child PPP[2029]
Jul 11 10:11:37 debian pptpd[2031]: CTRL: Reaping child PPP[2032]

daemon.log:
Jul 11 10:14:14 debian pptpd[2047]: CTRL: Client 192.168.3.5 control connection started
Jul 11 10:14:14 debian pptpd[2047]: CTRL: Starting call (launching pppd, opening GRE)
Jul 11 10:14:14 debian pptpd[2047]: GRE: read(fd=6,buffer=80505a0,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
Jul 11 10:14:14 debian pptpd[2047]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7)
Jul 11 10:14:14 debian pptpd[2047]: CTRL: Reaping child PPP[2048]
Jul 11 10:14:14 debian pptpd[2047]: CTRL: Client 192.168.3.5 control connection finished[/quote]

La config de chap-secrets:

[quote]# Secrets for authentication using CHAP

client server secret IP addresses

vpn pptpd vpn *
vpn debi vpn “*”[/quote]

La config de pptpd.conf:

[quote]

TAG: ppp

Path to the pppd program, default ‘/usr/sbin/pppd’ on Linux

#ppp /usr/sbin/pppd

TAG: option

Specifies the location of the PPP options file.

By default PPP looks in ‘/etc/ppp/options’

option /etc/ppp/pptpd-options

TAG: debug

Turns on (more) debugging to syslog

#debug

TAG: stimeout

Specifies timeout (in seconds) on starting ctrl connection

stimeout 10

TAG: noipparam

Suppress the passing of the client’s IP address to PPP, which is

done by default otherwise.

#noipparam

TAG: logwtmp

Use wtmp(5) to record client connections and disconnections.

logwtmp

TAG: bcrelay

Turns on broadcast relay to clients from interface

#bcrelay eth1

TAG: localip

TAG: remoteip

Specifies the local and remote IP address ranges.

Any addresses work as long as the local machine takes care of the

routing. But if you want to use MS-Windows networking, you should

use IP addresses out of the LAN address space and use the proxyarp

option in the pppd options file, or run bcrelay.

You can specify single IP addresses seperated by commas or you can

specify ranges, or both. For example:

192.168.0.234,192.168.0.245-249,192.168.0.254

IMPORTANT RESTRICTIONS:

1. No spaces are permitted between commas or within addresses.

2. If you give more IP addresses than MAX_CONNECTIONS, it will

start at the beginning of the list and go until it gets

MAX_CONNECTIONS IPs. Others will be ignored.

3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,

you must type 234-238 if you mean this.

4. If you give a single localIP, that’s ok - all local IPs will

be set to the given one. You MUST still give at least one remote

IP for each simultaneous client.

(Recommended)

#localip 192.168.0.1
#remoteip 192.168.0.234-238,192.168.0.245

or

#localip 192.168.0.234-238,192.168.0.245
#remoteip 192.168.1.234-238,192.168.1.245

localip 192.168.3.210
remoteip 192.168.3.234-238,192.168.3.245[/quote]

voila voila

Je voulais savoir si c’était normale que mon module mppe ne se charge pas automatiquement? en effet je dois faire une modprobe pour le charger:

[quote]debian:~# lsmod
Module Size Used by
autofs4 14476 -
deflate 2600 -
zlib_deflate 19960 -
zlib_inflate 15976 -
des 14824 -
sha1 2120 -
af_key 26776 -
af_packet 12048 -

debian:~# modprobe ppp_mppe

debian:~# lsmod
Module Size Used by
arc4 1512 -
ppp_mppe 5900 -
autofs4 14476 -
deflate 2600 -
zlib_deflate 19960 -
zlib_inflate 15976 -
des 14824 -
sha1 2120 -
af_key 26776 -
af_packet 12048 -
debian:~#[/quote]

#37

Enfin, j’ai réussi à établir la connexion VPN entre mon serveur vpn (linux) et un client vpn (windows XP) !

J’ai utilisé ce tuto :

http://www.supinfo-projects.com/en/2004/serveurvpnlinux/1/

Par contre je narrive pas à établir une connexion VPN lorsque sous le client XP je coche la case « Exiger le cryptage des données(déconnexion sinon) », il me reste à résoudre ce petit problème

si quelqu’un aurait une idée :question: il s’agit peut etre d’une erreur au niveau du « Use 40-bit MPPE encryption? » ou du « Use 128-bit MPPE encryption? » :question:

#38

Je pense que tu devrais poster ton:
option /etc/ppp/pptpd-options

#39

Voila mon pptpd-option:

[code]#### /etc/ppp/pptpd-options ####

nom du VPN (indispensable pour gérer les mots de passe ensuite)

name vpnDebi

Il faut chapms-v2 pour l’authentification

require-chapms-v2

Activation des chaps

+chap
+chapms
+chapms-v2

Cryptage MPPE

mppe-40
mppe-128
mppe-stateless

Si possible, adresses des serveurs DNS et WINS à attribuer au client VPN

ms-dns 172.22.0.10
ms-wins 172.22.0.20

Autres options

nodefaultroute
proxyarp
lock
nobsdcomp
nodeflate
auth
####[/code]

#40

Je croyais que c’etait soit
require
ou
refuse
??

Tu t’es inspiré de l’exemple /usr/share/doc/pptpd/examples/options.pptpd ???

Et je te conseille fortement de rajouter une option de debug car vu la nature de ppp, les deux hotes echangent leur options jusqu’a converger vers une configuration compatibles pour les deux. Donc il se peut tres bien que certaines protocoles ou certains cryptages soient activés alors que tu ne les veux pas. Ex PAP qui fait transiter les mots de passe en clair…

wiki.gadz.org/Linux/TunnelVPNAvecPptp

#41

D’après ton lien (http://wiki.gadz.org/Linux/TunnelVPNAvecPptp) le kernel 2.6.15 doit supporter le mppe:

Je tourne sur la 2.6.15 et le mppe ne marche pas.

J’ai regardé le /usr/share/doc/pptpd/examples/options.pptpd et il y parle de 2 version de ppp: ppp-2.4.2 et ppp-2.4.1. Dans mon cas il s’agit du ppp-2.4.1, le fait que le mppe ne fonctionne pas viendrait-il du fait que j’ai une mauvaise version du ppp?

De plus avant quand je tapait un “#modprobe ppp_mppe” je le trouvait et la il me dit:

debian:~# modprobe ppp_mppe FATAL: Module ppp_mppe not found. debian:~#

alor que le module est présent dans mon noyau…
:question:

#42

2.4.1 :open_mouth:

packages.debian.org/changelogs/p … /changelog

Ton truc il a 4 ans !?

C’est une faille locale mais qd meme!

plus loin… :

[quote] * New upstream release. Fixes:
+ pass-filter configuration option. (Closes: #309214)
+ LCP FSM bugs causing reconnection problems.
(Closes: #298657, #312118, #313205)
+ pty fd leaks. (Closes: #276550, #310292, #310293, #325705, #330444)

  • Removed the following patches which have been merged upstream:
    060_mppe-negotiation-fix, fix_winbind_base64, man_clarify_call,
    multicast_pado, pcap, pcap_fixactive, proc_net_ipx.[/quote]

T’es pas en woody qd meme?

Le mppe c’est un module noyau et un appli coté utilisateur. Donc a priori tu ne sais pas lequel des deux pose probleme.

#43

Salut, en fait je n’ai trouvé que le ppp2.4.1 et le 2.4.2, c’est pour ca je ne pensais pas qu’il y avait des versions supérieurs…

Je suis en 2.6.15 Sarge, je viens d’installer « ppp-2.4.4b1.tar.gz » (./configure && make && make install), mais quand je coche la case « Exiger le cryptage des données(déconnexion sinon) », il me dit toujours que la connexion est impossible:

Si cette erreur c’est reproduite, cela ve donc dire qu’il doit manquer un patche ou un module dans mon démon ppp?

une idée pour résoudre ce problème :question:

#44

bob786, tu as donné trop d’info. Je n’ai pas le temps de tester, mais je pense que suis en mesure de me connecter en pptp chez toi avec ce que tu as donné.
C’est une TRES mauvaise idée de dévoiler ton “chap-secrets”, donc je te conseilles tout de suite de changer le nom de ton serveur, et de remodifier ensuite ton chap secrets pour ajuster aussi le password.
Enfin je dis ça parceque l’*’ est un mot de passe que j’utilise parfois, donc je me dis que ca n’est pas un faux password, mais peut être que je me trompe.
Pour le reste, tes logs disent bien que ton mppe est actif, et le problême ne vient pas du module (le mppe du 2.6.15 est rôdé).
Maintenant, ça peut venir de l’install depuis un tar.gz.
Pourquoi ne prends tu pas le pkt debian ?

console@MAT64LIN:~$ apt-cache policy ppp ppp: Installed: 2.4.4b1-1 Candidate: 2.4.4b1-1 Version table: *** 2.4.4b1-1 0 997 http://ftp.fr.debian.org etch/main Packages 987 http://ftp.fr.debian.org sid/main Packages 100 /var/lib/dpkg/status 2.4.3-20050321+2sarge1 0 990 http://security.debian.org sarge/updates/main Packages 2.4.3-20050321+2 0 988 http://ftp.fr.debian.org sarge/main Packages
finalement, voici mon /etc/ppp/pptpd-options qui marche (plus utilisé, je passe en ce moment en openvpn):

name ####
refuse-pap
refuse-chap
refuse-mschap
require-mschap-v2
require-mppe-128

ms-dns 192.168.#.#
ms-wins 192.168.#.#

proxyarp
nodefaultroute
lock
nobsdcomp
ipcp-accept-remote
#45

Salut, oui matt les changements sont fait pour le chap-secrets :smiley: :blush:

Sinon j’ai comme toi:

debian:~# apt-cache policy ppp ppp: Installé : 2.4.4b1-1 Candidat : 2.4.4b1-1 Table de version : *** 2.4.4b1-1 0 500 http://ftp.fr.debian.org testing/main Packages 500 http://mir2.ovh.net testing/main Packages 500 http://ftp.u-picardie.fr testing/main Packages 100 /var/lib/dpkg/status debian:~#

J’ai aussi remplacer mon “/etc/ppp/pptpd-options” par le tiens et idem ca ne marche toujours pas quand je coche la case “Exiger le cryptage des données(déconnexion sinon)”.

La version de ppp est ok en plus de ca:

[code]debian:~# apt-cache show ppp
Package: ppp
Priority: optional
Section: admin
Installed-Size: 1000
Maintainer: Marco d’Itri md@linux.it
Architecture: i386
Version: 2.4.4b1-1
Replaces: ppp-pam, ppp-udeb
Depends: libc6 (>= 2.3.5-1), libpam0g (>= 0.76), libpcap0.8 (>= 0.9.3-1), zlib1g (>= 1:1.2.1), libpam-modules, libpam-runtime (>= 0.76-13.1), netbase, procps, makedev (>= 2.3.1-56)
Suggests: libatm1
Conflicts: ppp-pam, ppp-udeb, pppdcapiplugin (<= 1:3.7.2005-07-09-2)
Filename: pool/main/p/ppp/ppp_2.4.4b1-1_i386.deb
Size: 326324
MD5sum: 75ed41fea69db2b6ec2808b556737322
SHA1: 5c6428e5f62f91f9186f39df333d4e5c9cca18e0
SHA256: 207ba03c60314fc8340c495ed189c5f46c4c4d0910eef4a8dad6e71c0142f8fc
Description: Point-to-Point Protocol (PPP) daemon
The Point-to-Point Protocol (PPP) provides a standard way to transmit
datagrams over a serial link, as well as a standard way for the machines
at either end of the link (the “peers”) to negotiate various optional
characteristics of the link. Using PPP, a serial link can be used to
transmit Internet Protocol (IP) datagrams, allowing TCP/IP connections
between the peers.
Tag: hardware::modem, interface::daemon, protocol::ipv6, role::sw:server, use::dialing

debian:~#[/code]

Si l’erreur vient d’un install depuis un tar.gz alor faudrait-il que je recommence l’installation? ni a t-il pas un autre moyen d’y remédier :question:

#46

Finalement j’ai ajouter la ligne suivante dans mon « pptpd.conf » duquel nous n’avons jamais parlé:

Car sinon lors de ma connexion, il prenait le « /etc/ppp/options » par défaut.

En utilisant mon « pptpd-options », la connexion vpn met un peu plus de temps à se connecter et quand j’essai de me connecter toujours en cochant la fameuse case « Exiger le cryptage des données(déconnexion sinon) », j’ai un autre message d’erreur qui à l’air moin grave que le précédent mais bon la connexion ne marche toujours pas :confused: :

:question:

#47

re: lecture des logs sur le serveur…

#48

Voila les logs

messages:

[quote]Jul 12 13:54:14 debian kernel: CSLIP: code copyright 1989 Regents of the University of California
Jul 12 13:54:14 debian kernel: PPP generic driver version 2.4.2
Jul 12 13:54:17 debian kernel: PPP MPPE Compression module registered[/quote]

l’erreur 628 apparaît juste après les log ci-dessus

debug:

[quote]
Jul 12 13:54:20 debian pptpd[1857]: MGR: Reaped child 1956
Jul 12 13:55:19 debian pptpd[2088]: MGR: Launching /usr/sbin/pptpctrl to handle client
Jul 12 13:55:19 debian pptpd[2088]: CTRL: local address = 192.168.3.210
Jul 12 13:55:19 debian pptpd[2088]: CTRL: remote address = 192.168.3.20
Jul 12 13:55:19 debian pptpd[2088]: CTRL: pppd options file = /etc/ppp/pptpd-options
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Received PPTP Control Message (type: 1)
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Made a START CTRL CONN RPLY packet
Jul 12 13:55:19 debian pptpd[2088]: CTRL: I wrote 156 bytes to the client.
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Sent packet to client
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Received PPTP Control Message (type: 7)
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Set parameters to 100000000 maxbps, 64 window size
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Made a OUT CALL RPLY packet
Jul 12 13:55:19 debian pptpd[2088]: CTRL: pty_fd = 6
Jul 12 13:55:19 debian pptpd[2088]: CTRL: tty_fd = 7
Jul 12 13:55:19 debian pptpd[2089]: CTRL (PPPD Launcher): program binary = /usr/sbin/pppd
Jul 12 13:55:19 debian pptpd[2089]: CTRL (PPPD Launcher): local address = 192.168.3.210
Jul 12 13:55:19 debian pptpd[2089]: CTRL (PPPD Launcher): remote address = 192.168.3.20
Jul 12 13:55:19 debian pptpd[2088]: CTRL: I wrote 32 bytes to the client.
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Sent packet to client
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Received PPTP Control Message (type: 15)
Jul 12 13:55:19 debian pptpd[2088]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Jul 12 13:55:19 debian pptpd[2088]: GRE: accepting packet #0
Jul 12 13:55:19 debian pptpd[2088]: GRE: accepting packet #1
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #2
Jul 12 13:55:22 debian pptpd[2088]: CTRL: Received PPTP Control Message (type: 15)
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #3
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #4
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #5
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #6
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #7
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #8
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #9
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #10
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #11
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #12
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #13
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #14
Jul 12 13:55:22 debian pptpd[2088]: GRE: accepting packet #15
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #16
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #17
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #18
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #19
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #20
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #21
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #22
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #23
Jul 12 13:55:23 debian pptpd[2088]: CTRL: Received PPTP Control Message (type: 15)
Jul 12 13:55:23 debian pptpd[2088]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Jul 12 13:55:23 debian pptpd[2088]: GRE: accepting packet #24
Jul 12 13:55:23 debian pptpd[2088]: CTRL: Received PPTP Control Message (type: 12)
Jul 12 13:55:23 debian pptpd[2088]: CTRL: Made a CALL DISCONNECT RPLY packet
Jul 12 13:55:23 debian pptpd[2088]: CTRL: Received CALL CLR request (closing call)
Jul 12 13:55:23 debian pptpd[2088]: CTRL: Reaping child PPP[2089]
Jul 12 13:55:24 debian pptpd[2088]: CTRL: Exiting now
Jul 12 13:55:24 debian pptpd[1857]: MGR: Reaped child 2088[/quote]

#49

[quote]Jul 12 13:55:23 debian pptpd[2088]: CTRL: Received PPTP Control Message (type: 12)
Jul 12 13:55:23 debian pptpd[2088]: CTRL: Made a CALL DISCONNECT RPLY packet [/quote]

Je suis plus habitué au log de ppp mais le problèem ce situe la.

Le serveur a recu une demande d’une option de type 12.
Mais le serveur est configuré de telle sorte qu’il n’accepte pas cette option ( refuse,…)
Donc il DISCONNECT REPLY.

Soit sur de mettre à fond le debug hein!! et ensuite lire /var/log/ppp-debug.log

#50

groups.google.fr/group/comp.os.l … type%3A+12&rnum=9&hl=fr#16ddd97d2b1bd067

#51

Oui j’ai deja ajouter la ligne suivante dans mon pptpd.conf:

Je vais carrément vous balancer mon pptpd.conf:

[quote]option /etc/ppp/pptpd-options

debug

localip 172.#.#.#
remoteip 172.#.#.#-#[/quote]

Mais je n’est pas tro bien saisie ta réponse Boris?

#52

Je sais je suis rarement clair.
Désolé :slightly_smiling:

#53

Voici finalement mes log lorsque jessai de me connecter en VPN mais sa échoue (on voit bien dans les 2 logs que des paquets ont été aceptés… :confused: ):

debug:

Jul 12 14:51:29 debian pptpd[2986]: MGR: Launching /usr/sbin/pptpctrl to handle client Jul 12 14:51:29 debian pptpd[2986]: CTRL: local address = 192.168.3.210 Jul 12 14:51:29 debian pptpd[2986]: CTRL: remote address = 192.168.3.20 Jul 12 14:51:29 debian pptpd[2986]: CTRL: pppd options file = /etc/ppp/pptpd-options Jul 12 14:51:29 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 1) Jul 12 14:51:29 debian pptpd[2986]: CTRL: Made a START CTRL CONN RPLY packet Jul 12 14:51:29 debian pptpd[2986]: CTRL: I wrote 156 bytes to the client. Jul 12 14:51:29 debian pptpd[2986]: CTRL: Sent packet to client Jul 12 14:51:29 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 7) Jul 12 14:51:29 debian pptpd[2986]: CTRL: Set parameters to 100000000 maxbps, 64 window size Jul 12 14:51:29 debian pptpd[2986]: CTRL: Made a OUT CALL RPLY packet Jul 12 14:51:29 debian pptpd[2986]: CTRL: pty_fd = 6 Jul 12 14:51:29 debian pptpd[2986]: CTRL: tty_fd = 7 Jul 12 14:51:29 debian pptpd[2987]: CTRL (PPPD Launcher): program binary = /usr/sbin/pppd Jul 12 14:51:29 debian pptpd[2987]: CTRL (PPPD Launcher): local address = 192.168.3.210 Jul 12 14:51:29 debian pptpd[2987]: CTRL (PPPD Launcher): remote address = 192.168.3.20 Jul 12 14:51:29 debian pptpd[2986]: CTRL: I wrote 32 bytes to the client. Jul 12 14:51:29 debian pptpd[2986]: CTRL: Sent packet to client Jul 12 14:51:29 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 15) Jul 12 14:51:29 debian pptpd[2986]: CTRL: Got a SET LINK INFO packet with standard ACCMs Jul 12 14:51:29 debian pptpd[2986]: GRE: accepting packet #0 Jul 12 14:51:29 debian pptpd[2986]: GRE: accepting packet #1 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #2 Jul 12 14:51:32 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 15) Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #3 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #4 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #5 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #6 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #7 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #8 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #9 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #10 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #11 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #12 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #13 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #14 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #15 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #16 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #17 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #18 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #19 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #20 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #21 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #22 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #23 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #24 Jul 12 14:51:32 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 15) Jul 12 14:51:32 debian pptpd[2986]: CTRL: Got a SET LINK INFO packet with standard ACCMs Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #25 Jul 12 14:51:35 debian pptpd[2986]: CTRL: Reaping child PPP[2987] Jul 12 14:51:35 debian pptpd[2986]: CTRL: Exiting now Jul 12 14:51:35 debian pptpd[2848]: MGR: Reaped child 2986

daemon.log:

Jul 12 14:51:29 debian pptpd[2986]: MGR: Launching /usr/sbin/pptpctrl to handle client Jul 12 14:51:29 debian pptpd[2986]: CTRL: local address = 192.168.3.210 Jul 12 14:51:29 debian pptpd[2986]: CTRL: remote address = 192.168.3.20 Jul 12 14:51:29 debian pptpd[2986]: CTRL: pppd options file = /etc/ppp/pptpd-options Jul 12 14:51:29 debian pptpd[2986]: CTRL: Client 192.168.3.5 control connection started Jul 12 14:51:29 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 1) Jul 12 14:51:29 debian pptpd[2986]: CTRL: Made a START CTRL CONN RPLY packet Jul 12 14:51:29 debian pptpd[2986]: CTRL: I wrote 156 bytes to the client. Jul 12 14:51:29 debian pptpd[2986]: CTRL: Sent packet to client Jul 12 14:51:29 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 7) Jul 12 14:51:29 debian pptpd[2986]: CTRL: Set parameters to 100000000 maxbps, 64 window size Jul 12 14:51:29 debian pptpd[2986]: CTRL: Made a OUT CALL RPLY packet Jul 12 14:51:29 debian pptpd[2986]: CTRL: Starting call (launching pppd, opening GRE) Jul 12 14:51:29 debian pptpd[2986]: CTRL: pty_fd = 6 Jul 12 14:51:29 debian pptpd[2986]: CTRL: tty_fd = 7 Jul 12 14:51:29 debian pptpd[2987]: CTRL (PPPD Launcher): program binary = /usr/sbin/pppd Jul 12 14:51:29 debian pptpd[2987]: CTRL (PPPD Launcher): local address = 192.168.3.210 Jul 12 14:51:29 debian pptpd[2987]: CTRL (PPPD Launcher): remote address = 192.168.3.20 Jul 12 14:51:29 debian pppd[2987]: pppd 2.4.1 started by root, uid 0 Jul 12 14:51:29 debian pppd[2987]: Using interface ppp0 Jul 12 14:51:29 debian pppd[2987]: Connect: ppp0 <--> /dev/pts/1 Jul 12 14:51:29 debian pptpd[2986]: CTRL: I wrote 32 bytes to the client. Jul 12 14:51:29 debian pptpd[2986]: CTRL: Sent packet to client Jul 12 14:51:29 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 15) Jul 12 14:51:29 debian pptpd[2986]: CTRL: Got a SET LINK INFO packet with standard ACCMs Jul 12 14:51:29 debian pptpd[2986]: GRE: accepting packet #0 Jul 12 14:51:29 debian pptpd[2986]: GRE: accepting packet #1 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #2 Jul 12 14:51:32 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 15) Jul 12 14:51:32 debian pptpd[2986]: CTRL: Ignored a SET LINK INFO packet with real ACCMs! Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #3 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #4 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #5 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #6 Jul 12 14:51:32 debian pppd[2987]: MSCHAP-v2 peer authentication succeeded for yougas Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #7 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #8 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #9 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #10 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #11 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #12 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #13 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #14 Jul 12 14:51:32 debian pppd[2987]: found interface eth0 for proxy arp Jul 12 14:51:32 debian pppd[2987]: local IP address 192.168.3.210 Jul 12 14:51:32 debian pppd[2987]: remote IP address 192.168.3.20 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #15 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #16 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #17 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #18 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #19 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #20 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #21 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #22 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #23 Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #24 Jul 12 14:51:32 debian pptpd[2986]: CTRL: Received PPTP Control Message (type: 15) Jul 12 14:51:32 debian pptpd[2986]: CTRL: Got a SET LINK INFO packet with standard ACCMs Jul 12 14:51:32 debian pptpd[2986]: GRE: accepting packet #25 Jul 12 14:51:32 debian pppd[2987]: LCP terminated by peer (g^NdY^@<M-Mt^@^@^BM-f) Jul 12 14:51:35 debian pppd[2987]: Connection terminated. Jul 12 14:51:35 debian pppd[2987]: Connect time 0.1 minutes. Jul 12 14:51:35 debian pppd[2987]: Sent 128 bytes, received 385 bytes. Jul 12 14:51:35 debian pppd[2987]: Exit. Jul 12 14:51:35 debian pptpd[2986]: GRE: read(fd=6,buffer=80505a0,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs Jul 12 14:51:35 debian pptpd[2986]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7) Jul 12 14:51:35 debian pptpd[2986]: CTRL: Reaping child PPP[2987] Jul 12 14:51:35 debian pptpd[2986]: CTRL: Client 192.168.3.5 control connection finished Jul 12 14:51:35 debian pptpd[2986]: CTRL: Exiting now Jul 12 14:51:35 debian pptpd[2848]: MGR: Reaped child 2986

#54

Personne n’a une ou des solutions :unamused: :question: