Перейти к содержимому

проблемы с pptpd


lamo

Рекомендованные сообщения

До недавнего времени все работало номально,потом вдруг перестало....Куда копать не знаю....

Вот лог:

Nov 10 17:02:04 observer pptpd[11732]: MGR: Launching /usr/local/sbin/pptpctrl to handle client
Nov 10 17:02:04 observer pptpd[11732]: CTRL: local address = 172.27.200.200
Nov 10 17:02:04 observer pptpd[11732]: CTRL: remote address = 172.27.200.1
Nov 10 17:02:04 observer pptpd[11732]: CTRL: pppd options file = /etc/ppp/options.pptpd
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Client 172.27.15.2 control connection started
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Received PPTP Control Message (type: 1)
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Made a START CTRL CONN RPLY packet
Nov 10 17:02:04 observer pptpd[11732]: CTRL: I wrote 156 bytes to the client.
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Sent packet to client
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Received PPTP Control Message (type: 7)
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Set parameters to 100000000 maxbps, 64 window size
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Made a OUT CALL RPLY packet
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Starting call (launching pppd, opening GRE)
Nov 10 17:02:04 observer pptpd[11732]: CTRL: pty_fd = 6
Nov 10 17:02:04 observer pptpd[11732]: CTRL: tty_fd = 7
Nov 10 17:02:04 observer pptpd[11733]: CTRL (PPPD Launcher): program binary = /usr/local/sbin/pppd
Nov 10 17:02:04 observer pptpd[11733]: CTRL (PPPD Launcher): local address = 172.27.200.200
Nov 10 17:02:04 observer pptpd[11733]: CTRL (PPPD Launcher): remote address = 172.27.200.1
Nov 10 17:02:04 observer pppd[11733]: Plugin /usr/local/lib/pppd/2.4.3/radius.so loaded.
Nov 10 17:02:04 observer pppd[11733]: RADIUS plugin initialized.
Nov 10 17:02:04 observer pptpd[11732]: CTRL: I wrote 32 bytes to the client.
Nov 10 17:02:04 observer pptpd[11732]: CTRL: Sent packet to client
Nov 10 17:02:05 observer pptpd[11732]: CTRL: Received PPTP Control Message (type: 15)
Nov 10 17:02:05 observer pptpd[11732]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Nov 10 17:02:05 observer pppd[11733]: pppd 2.4.3 started by root, uid 0
Nov 10 17:02:05 observer pppd[11733]: using channel 47
Nov 10 17:02:05 observer pppd[11733]: Using interface ppp0
Nov 10 17:02:05 observer pppd[11733]: Connect: ppp0 <--> /dev/pts/2
Nov 10 17:02:05 observer pppd[11733]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <auth chap MD5> <magic 0xc425ba02> <pcomp> <accomp>]
Nov 10 17:02:05 observer pptpd[11732]: GRE: Bad checksum from pppd.
Nov 10 17:02:08 observer pppd[11733]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <auth chap MD5> <magic 0xc425ba02> <pcomp> <accomp>]
Nov 10 17:02:35 observer pppd[11733]: LCP: timeout sending Config-Requests
Nov 10 17:02:35 observer pppd[11733]: Connection terminated.
Nov 10 17:02:35 observer pppd[11733]: using channel 48
Nov 10 17:02:36 observer pppd[11733]: Using interface ppp0
Nov 10 17:02:36 observer pppd[11733]: Connect: ppp0 <--> /dev/pts/2
Nov 10 17:02:36 observer pppd[11733]: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <auth chap MD5> <magic 0xe6fc1b02> <pcomp> <accomp>]
Nov 10 17:02:36 observer pppd[11733]: tcflush failed: Bad file descriptor
Nov 10 17:02:36 observer pppd[11733]: tcsetattr: Invalid argument (line 1001)
Nov 10 17:02:36 observer pppd[11733]: Exit.
Nov 10 17:02:36 observer pptpd[11732]: GRE: read(fd=6,buffer=804eda0,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
Nov 10 17:02:36 observer pptpd[11732]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7)
Nov 10 17:02:36 observer pptpd[11732]: CTRL: Reaping child PPP[11733]
Nov 10 17:02:36 observer pptpd[11732]: CTRL: Client 172.27.15.2 control connection finished
Nov 10 17:02:36 observer pptpd[11732]: CTRL: Exiting now
Nov 10 17:02:36 observer pptpd[11444]: MGR: Reaped child 11732

 

pptpd.conf

ppp /usr/local/sbin/pppd

# TAG: option
#       Specifies the location of the PPP options file.
#       By default PPP looks in '/etc/ppp/options'
#
option /etc/ppp/options.pptpd

# 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 <if>
#       Turns on broadcast relay to clients from interface <if>
#
#bcrelay eth1

# TAG: delegate
#       Delegates the allocation of client IP addresses to pppd.
#
#       Without this option, which is the default, pptpd manages the list of
#       IP addresses for clients and passes the next free address to pppd.
#       With this option, pptpd does not pass an address, and so pppd may use
#       radius or chap-secrets to allocate an address.
#
#delegate

# TAG: connections
#       Limits the number of client connections that may be accepted.
#
#       If pptpd is allocating IP addresses (e.g. delegate is not
#       used) then the number of connections is also limited by the
#       remoteip option.  The default is 100.
#connections 100

# TAG: localip
# TAG: remoteip
#       Specifies the local and remote IP address ranges.
#
#       These options are ignored if delegate option is set.
#
#       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 the value of connections,
#          it will start at the beginning of the list and go until it
#          gets 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 172.27.200.200
remoteip 172.27.200.1
#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

 

options.pptpd

# Authentication

# Name of the local system for authentication purposes
# (must match the second field in /etc/ppp/chap-secrets entries)
name pptpd
auth
lcp-echo-failure 60
lcp-echo-interval 6

# Strip the domain prefix from the username before authentication.
# (applies if you use pppd with chapms-strip-domain patch)
#chapms-strip-domain

# Encryption
# (There have been multiple versions of PPP with encryption support,
# choose with of the following sections you will use.)


# BSD licensed ppp-2.4.2 upstream with MPPE only, kernel module ppp_mppe.o
# {{{
refuse-pap
#refuse-chap
require-chap
#refuse-mschap
require-mschap
# Require the peer to authenticate itself using MS-CHAPv2 [Microsoft
# Challenge Handshake Authentication Protocol, Version 2] authentication.
#require-mschap-v2
# Require MPPE 128-bit encryption
# (note that MPPE requires the use of MSCHAP-V2 during authentication)
#require-mppe-128
# }}}

# Network and Routing

# If pppd is acting as a server for Microsoft Windows clients, this
# option allows pppd to supply one or two DNS (Domain Name Server)
# addresses to the clients.  The first instance of this option
# specifies the primary DNS address; the second instance (if given)
# specifies the secondary DNS address.
#ms-dns 10.0.0.1
#ms-dns 10.0.0.2

# If pppd is acting as a server for Microsoft Windows or "Samba"
# clients, this option allows pppd to supply one or two WINS (Windows
# Internet Name Services) server addresses to the clients.  The first
# instance of this option specifies the primary WINS address; the
# second instance (if given) specifies the secondary WINS address.
#ms-wins 10.0.0.3
#ms-wins 10.0.0.4

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.  This will have the effect of making the peer appear to other
# systems to be on the local ethernet.
# (you do not need this if your PPTP server is responsible for routing
# packets to the clients -- James Cameron)
#proxyarp





debug

# Print out all the option values which have been set.
# (often requested by mailing list to verify options)
#dump


# Miscellaneous

# Create a UUCP-style lock file for the pseudo-tty to ensure exclusive
# access.
lock

# Disable BSD-Compress compression
nobsdcomp

# Disable Van Jacobson compression
# (needed on some networks with Windows 9x/ME/XP clients, see posting to
# poptop-server on 14th April 2005 by Pawel Pokrywka and followups,
# [url="http://marc.theaimsgroup.com/?t=111343175400006&r=1&w=2"]http://marc.theaimsgroup.com/?t=111343175400006&r=1&w=2[/url] )
novj
novjccomp

# turn off logging to stderr, since this may be redirected to pptpd,
# which may trigger a loopback
#nologfd

# put plugins here
# (putting them higher up may cause them to sent messages to the pty)
plugin /usr/local/lib/pppd/2.4.3/radius.so

система: Mandrake 10.0

Может кто сталкивался...Подскажите плз..

Ссылка на сообщение
Поделиться на других сайтах

Когда-то была аналогичная проблема под RedHat 9.0 - долго мучился и сношал гугл. В итоге где-то откопал несколько замечаний о том, что все из-за кривости в редхете ядра. В итоге решилось все установкой слакваря.

Так что как вариант попробуй обновить ядро...

Ссылка на сообщение
Поделиться на других сайтах

А если iptables выключить на время, тоже не работает ? Похоже просто gre не проходит... От дистрибутива это не зависит :o. Опции и патчи ядра играют роль. В ядре должно быть CONFIG_NET_IPGRE=y

Ссылка на сообщение
Поделиться на других сайтах
  • 1 month later...

Похожий трабл

 

Лог:

Dec 21 12:33:58 localhost pppd[6412]: pppd 2.4.4 started by kolia, uid 1000
Dec 21 12:33:58 localhost pppd[6412]: using channel 1
Dec 21 12:33:58 localhost pppd[6412]: Using interface ppp0
Dec 21 12:33:58 localhost pppd[6412]: Connect: ppp0 <--> /dev/pts/1
Dec 21 12:34:07 localhost pptpd[6411]: CTRL: timeout waiting for first packet from our pppd
Dec 21 12:34:07 localhost pptpd[6411]: GRE: socket() failed
Dec 21 12:34:07 localhost pptpd[6411]: CTRL: I wrote 32 bytes to the client.
Dec 21 12:34:07 localhost pptpd[6411]: CTRL: Sent packet to client
Dec 21 12:34:07 localhost pptpd[6411]: CTRL: Received PPTP Control Message (type: 15)
Dec 21 12:34:07 localhost pptpd[6411]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Dec 21 12:34:44 localhost pptpd[6411]: CTRL: Received PPTP Control Message (type: 12)
Dec 21 12:34:44 localhost pptpd[6411]: CTRL: Made a CALL DISCONNECT RPLY packet
Dec 21 12:34:44 localhost pptpd[6411]: CTRL: Received CALL CLR request (closing call)
Dec 21 12:34:44 localhost pptpd[6411]: CTRL: Request to close call but call not open
Dec 21 12:34:44 localhost pppd[6412]: Modem hangup
Dec 21 12:34:44 localhost pppd[6412]: Connection terminated.
Dec 21 12:34:44 localhost pptpd[6411]: CTRL: Reaping child PPP[6412]
Dec 21 12:34:44 localhost pppd[6412]: Exit.
Dec 21 12:34:44 localhost pptpd[6411]: CTRL: Client 10.0.0.1 control connection finished
Dec 21 12:34:44 localhost pptpd[6411]: CTRL: Exiting now
Dec 21 12:34:44 localhost pptpd[6410]: MGR: Reaped child 6411

 

Подключение подвисает на проверке логина пароля.

 

cat /etc/pptpd.conf

ppp /usr/sbin/pppd
option /etc/ppp/pptpd-options
debug
localip 192.168.0.1
remoteip 192.168.0.2-254

cat /etc/ppp/pptpd-options

require-chap
require-mschap
ms-dns 10.0.0.99
ms-dns 10.0.0.99
ms-wins 10.0.0.99
ms-wins 10.0.0.99
proxyarp
nodefaultroute
debug
dump
lock
nobsdcomp
ipcp-accept-local
ipcp-accept-remote
auth
+chap
+mschap
-pap
nomppe
silent
idle 1800

Ссылка на сообщение
Поделиться на других сайтах

Этап проверки логина пароля прошел. Трабл был в протоколах шифрования. правда где не понял.

 

Теперь на этапе Регистрация компьютера в сети. Вешается сетевой интерфейс сервака и на внешние раздражители не отвечает.

 

Грешу на скрипт ip-up

Ссылка на сообщение
Поделиться на других сайтах

Создайте аккаунт или войдите в него для комментирования

Вы должны быть пользователем, чтобы оставить комментарий

Создать аккаунт

Зарегистрируйтесь для получения аккаунта. Это просто!

Зарегистрировать аккаунт

Войти

Уже зарегистрированы? Войдите здесь.

Войти сейчас
  • Сейчас на странице   0 пользователей

    Нет пользователей, просматривающих эту страницу.

×
×
  • Создать...