一、简介
前段时间笔者写了一篇《Fedora core 2下建立Poptop服务器以及常见问题》的文章,收到许多朋友的欢迎,但是那篇文章只支持MPPE数据加密,不支持MPPC数据压缩,未免有些遗憾,所以笔者再接再厉阅读了一些文档,终于使PPTP ×××实现了MPPC数据压缩功能。首先我们先来介绍一下MPPE/MPPC的概念。
MPPE:Microsoft Point-to-Point Encryption,微软的点对点加密协议,可以对在点对点链路上传输的数据包进行加密,详细介绍请见RFC3078和RFC3079。
MPPC:Microsoft Point-to-Point Compression,微软的点对点压缩协议,可以对在点对点链路上传输的数据包进行压缩,详细介绍请见RFC21189。
那么要想在Linux环境下使PPTP ×××支持这两种协议,需要做两件事情:第一、给Linux内核打补丁,然后重新编译内核,让内核支持MPPE/MPPC。第二、给ppp套件打补丁,让ppp也支持MPPE/MPPC。好啦,知道了原理就好办了,下面就让我们一起来实现这些功能吧。
首先先来看看我们试验的环境,一台安装了Fedora core 2的服务器充当了连接内网与外网的NAT主机以及×××服务器的作用。外网网卡IP:211.137.115.5,内网网卡IP:10.100.0.200。网络拓扑图如下:
图1:网络拓扑图
二、下载
先来看看我们需要下载的套件吧。2.6.5-1.358
1、Linux Kernel 2.6.6
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.6.tar.gz
2、linux-2.6.6-mppe-mppc-1.0.patch.gz
http://www.polbox.com/h/hs001/linux-2.6.6-mppe-mppc-1.0.patch.gz
3、ppp-2.4.3
ftp://ftp.samba.org/pub/ppp/ppp-2.4.3.tar.gz
4、ppp-2.4.3-mppe-mppc-1.1.patch.gz
http://www.polbox.com/h/hs001/ppp-2.4.3-mppe-mppc-1.1.patch.gz
5、pptp-1.1.4
http://internap.dl.sourceforge.net/sourceforge/poptop/pptpd-1.1.4-b4.tar.gz
把这些都下载到/usr/src目录下面,然后准备进行安装与配置。
三、安装
1、重新编译Linux内核,以支持MPPE/MPPC
Fedora core 2默认的内核版本为kernel 2.6.5-1.358,是不支持MPPE/MPPC的,所以我们要重新下载内核文件并且重新编译才行,这里选用了Kernel 2.6.6。
//解压缩内核文件
#tar zxvf linux-2.6.6.tar.gz
//给内核文件打补丁
#patch –p0 –i linux-2.6.6-mppe-mppc-1.0.patch.gz
#cd linux-2.6.6
//进入Linux内核文本配置界面
#make menuconfig
选择进入Device Drivers ->; Networking support ->;
<>; PPP BSD-Compress compression
<>; Microsoft PPP compression/encryption (MPPC/MPPE)
找到上面两项,分别按下空格键,最前面的<>;就会变成<M>;,如下
<M>; PPP BSD-Compress compression
<M>; Microsoft PPP compression/encryption (MPPC/MPPE)
表示将这两项以模块形式编译到内核里面。然后保存退出。
//建立相依的属性关系
#make dep
//将旧的资料删除
#make clean
//开始编译内核
#make bzImage
//开始编译模块
#make modules
//将资料安装在/lib/modules/2.6.6里面
#make modules_install
//将刚刚make bzImage建立完成的内核安装到系统里面
#make install
好啦,经过上面7个步骤就完成了内核编译的工作,是不是很简单呀,所以大家不要认为编译Linux内核很复杂,其实是非常简单的。
因为我们是以模块方式来安装补丁的,所以每次系统启动时都需要加载模块才行,因此我们要在/etc/rc.d/rc.local里面写入一行:
/sbin/modprobe ppp_mppe_mppc
2、安装PPP套件
因为Fedora core 2默认情况下已经安装了ppp-2.4.2-2,但是并不支持MPPE/MPPC,因此我们要先把它卸载掉,然后手工编译安装PPP。
#rpm -e --nodeps ppp
//解压缩ppp-2.4.3
#tar zxvf ppp-2.4.3.tar.gz
//给ppp打补丁
#patch –p0 –i ppp-2.4.3-mppe-mppc-1.1.patch.gz
#cd ppp-2.4.3
//进行编译安装
#./configure
#make
#make install
3、安装pptp套件
#tar zxvf pptpd-1.1.4-b4.tar.gz
#cd pptpd-1.1.4-b4
#./configure
#make
#make install
好啦,到这里我们已经完成了全部的安装工作,下面将要进行最后的配置工作了。
四、配置
这里需要修改如下3个配置文件。
/etc/pptpd.conf // Poptop配置文件
/etc/ppp/options.pptpd // Poptop选项文件
/etc/ppp/chap-secrets //账号、密码存放文件
/etc/pptpd.conf
option /etc/ppp/options.pptpd
debug
Logwtmp
localip 10.100.0.201
remoteip 10.100.0.202-210
/etc/ppp/options.pptpd
name pptp
lock
mtu 1450
mru 1450
proxyarp
auth
ipcp-accept-local
ipcp-accept-remote
lcp-echo-failure 3
lcp-echo-interval 5
deflate 0
# Handshake Auth Method
+chap
+mschap-v2
# Data Encryption Methods
mppe required
/etc/ppp/chap-secrets
#×××客户账号和密码。
# Secrets for authentication using CHAP
# client server secret IP addresses
“username1” pptpd “password1” *
“username2” pptpd “password2” 10.100.0.203
注意:后面的IP地址栏可以知道次用户登陆后讲分配的IP地址,如果不具体指定,请用*号代替。
启动NAT转发
echo "1" >; /proc/sys/net/ipv4/ip_forward
/sbin/depmod -a
/sbin/modprobe ip_tables
/sbin/modprobe iptable_nat
/sbin/modprobe ip_nat_ftp
/sbin/modprobe ipt_LOG
五、启动pptpd
# /usr/local/sbin/pptpd
好啊,到这里为止一个支持MPPE/MMPC的PPTP ×××服务器就架设完毕了,另外关于客户端的设置以及常见问题就不在这里讲了,大家可以参考我写的另一篇文章《Fedora core 2下建立Poptop服务器以及常见问题》进行设置。
另,做这个试验时笔者遇到了许多问题和困难,多亏了网友水若寒、Monster等朋友的关心和帮助,才能使得试验继续进行!笔者在这里要感谢大家的支持,以后会继续努力,以回报大家的支持!
前段时间笔者写了一篇《Fedora core 2下建立Poptop服务器以及常见问题》的文章,收到许多朋友的欢迎,但是那篇文章只支持MPPE数据加密,不支持MPPC数据压缩,未免有些遗憾,所以笔者再接再厉阅读了一些文档,终于使PPTP ×××实现了MPPC数据压缩功能。首先我们先来介绍一下MPPE/MPPC的概念。
MPPE:Microsoft Point-to-Point Encryption,微软的点对点加密协议,可以对在点对点链路上传输的数据包进行加密,详细介绍请见RFC3078和RFC3079。
MPPC:Microsoft Point-to-Point Compression,微软的点对点压缩协议,可以对在点对点链路上传输的数据包进行压缩,详细介绍请见RFC21189。
那么要想在Linux环境下使PPTP ×××支持这两种协议,需要做两件事情:第一、给Linux内核打补丁,然后重新编译内核,让内核支持MPPE/MPPC。第二、给ppp套件打补丁,让ppp也支持MPPE/MPPC。好啦,知道了原理就好办了,下面就让我们一起来实现这些功能吧。
首先先来看看我们试验的环境,一台安装了Fedora core 2的服务器充当了连接内网与外网的NAT主机以及×××服务器的作用。外网网卡IP:211.137.115.5,内网网卡IP:10.100.0.200。网络拓扑图如下:
图1:网络拓扑图
二、下载
先来看看我们需要下载的套件吧。2.6.5-1.358
1、Linux Kernel 2.6.6
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.6.tar.gz
2、linux-2.6.6-mppe-mppc-1.0.patch.gz
http://www.polbox.com/h/hs001/linux-2.6.6-mppe-mppc-1.0.patch.gz
3、ppp-2.4.3
ftp://ftp.samba.org/pub/ppp/ppp-2.4.3.tar.gz
4、ppp-2.4.3-mppe-mppc-1.1.patch.gz
http://www.polbox.com/h/hs001/ppp-2.4.3-mppe-mppc-1.1.patch.gz
5、pptp-1.1.4
http://internap.dl.sourceforge.net/sourceforge/poptop/pptpd-1.1.4-b4.tar.gz
把这些都下载到/usr/src目录下面,然后准备进行安装与配置。
三、安装
1、重新编译Linux内核,以支持MPPE/MPPC
Fedora core 2默认的内核版本为kernel 2.6.5-1.358,是不支持MPPE/MPPC的,所以我们要重新下载内核文件并且重新编译才行,这里选用了Kernel 2.6.6。
//解压缩内核文件
#tar zxvf linux-2.6.6.tar.gz
//给内核文件打补丁
#patch –p0 –i linux-2.6.6-mppe-mppc-1.0.patch.gz
#cd linux-2.6.6
//进入Linux内核文本配置界面
#make menuconfig
选择进入Device Drivers ->; Networking support ->;
<>; PPP BSD-Compress compression
<>; Microsoft PPP compression/encryption (MPPC/MPPE)
找到上面两项,分别按下空格键,最前面的<>;就会变成<M>;,如下
<M>; PPP BSD-Compress compression
<M>; Microsoft PPP compression/encryption (MPPC/MPPE)
表示将这两项以模块形式编译到内核里面。然后保存退出。
//建立相依的属性关系
#make dep
//将旧的资料删除
#make clean
//开始编译内核
#make bzImage
//开始编译模块
#make modules
//将资料安装在/lib/modules/2.6.6里面
#make modules_install
//将刚刚make bzImage建立完成的内核安装到系统里面
#make install
好啦,经过上面7个步骤就完成了内核编译的工作,是不是很简单呀,所以大家不要认为编译Linux内核很复杂,其实是非常简单的。
因为我们是以模块方式来安装补丁的,所以每次系统启动时都需要加载模块才行,因此我们要在/etc/rc.d/rc.local里面写入一行:
/sbin/modprobe ppp_mppe_mppc
2、安装PPP套件
因为Fedora core 2默认情况下已经安装了ppp-2.4.2-2,但是并不支持MPPE/MPPC,因此我们要先把它卸载掉,然后手工编译安装PPP。
#rpm -e --nodeps ppp
//解压缩ppp-2.4.3
#tar zxvf ppp-2.4.3.tar.gz
//给ppp打补丁
#patch –p0 –i ppp-2.4.3-mppe-mppc-1.1.patch.gz
#cd ppp-2.4.3
//进行编译安装
#./configure
#make
#make install
3、安装pptp套件
#tar zxvf pptpd-1.1.4-b4.tar.gz
#cd pptpd-1.1.4-b4
#./configure
#make
#make install
好啦,到这里我们已经完成了全部的安装工作,下面将要进行最后的配置工作了。
四、配置
这里需要修改如下3个配置文件。
/etc/pptpd.conf // Poptop配置文件
/etc/ppp/options.pptpd // Poptop选项文件
/etc/ppp/chap-secrets //账号、密码存放文件
/etc/pptpd.conf
option /etc/ppp/options.pptpd
debug
Logwtmp
localip 10.100.0.201
remoteip 10.100.0.202-210
/etc/ppp/options.pptpd
name pptp
lock
mtu 1450
mru 1450
proxyarp
auth
ipcp-accept-local
ipcp-accept-remote
lcp-echo-failure 3
lcp-echo-interval 5
deflate 0
# Handshake Auth Method
+chap
+mschap-v2
# Data Encryption Methods
mppe required
/etc/ppp/chap-secrets
#×××客户账号和密码。
# Secrets for authentication using CHAP
# client server secret IP addresses
“username1” pptpd “password1” *
“username2” pptpd “password2” 10.100.0.203
注意:后面的IP地址栏可以知道次用户登陆后讲分配的IP地址,如果不具体指定,请用*号代替。
启动NAT转发
echo "1" >; /proc/sys/net/ipv4/ip_forward
/sbin/depmod -a
/sbin/modprobe ip_tables
/sbin/modprobe iptable_nat
/sbin/modprobe ip_nat_ftp
/sbin/modprobe ipt_LOG
五、启动pptpd
# /usr/local/sbin/pptpd
好啊,到这里为止一个支持MPPE/MMPC的PPTP ×××服务器就架设完毕了,另外关于客户端的设置以及常见问题就不在这里讲了,大家可以参考我写的另一篇文章《Fedora core 2下建立Poptop服务器以及常见问题》进行设置。
另,做这个试验时笔者遇到了许多问题和困难,多亏了网友水若寒、Monster等朋友的关心和帮助,才能使得试验继续进行!笔者在这里要感谢大家的支持,以后会继续努力,以回报大家的支持!
![]() | |
| |
水若寒 回复于:2004-12-21 00:11:03
支持!!
支持!!
prowoo 回复于:2005-01-04 20:10:34
:o 有待一试
:o 有待一试
jackieyuan 回复于:2005-01-05 23:14:30
您的文章很通俗易懂,非常敬佩您写作的敬业精神! :D
您的文章很通俗易懂,非常敬佩您写作的敬业精神! :D
lxy1220 回复于:2005-01-07 10:41:38
在下佩服 十分感谢
在下佩服 十分感谢
aicoa 回复于:2005-01-07 16:32:43
做***,选择poptop
我用相同的配置做了两个服务器,其中一个正常使用,
而另一个无论如何也不能正常工作
已经配置了十几遍了,更换机器也不行
两个机器的配置cpu跟网卡不同
但是感觉应该跟硬件关系不大
使用的软件包:
dkms-2.0.2-1.noarch.rpm
kernel_ppp_mppe-0.0.4-3dkms.noarch.rpm
ppp-2.4.3-0.cvs_20040527.1.i386.rpm
pptpd-1.2.1-1.i386.rpm
配置如下:
/etc/ppptpd.conf:
做***,选择poptop
我用相同的配置做了两个服务器,其中一个正常使用,
而另一个无论如何也不能正常工作
已经配置了十几遍了,更换机器也不行
两个机器的配置cpu跟网卡不同
但是感觉应该跟硬件关系不大
使用的软件包:
dkms-2.0.2-1.noarch.rpm
kernel_ppp_mppe-0.0.4-3dkms.noarch.rpm
ppp-2.4.3-0.cvs_20040527.1.i386.rpm
pptpd-1.2.1-1.i386.rpm
配置如下:
/etc/ppptpd.conf:
option /etc/ppp/options.pptpd
debug
logwtmp
localip 192.168.3.230
remoteip 192.168.3.231-239
/etc/ppp/options.pptpd
name ***srv2
refuse-pap
refuse-chap
refuse-mschap
require-mppe-128
proxyarp
lock
nobsdcomp
/etc/ppp/chap-secrets
testuser ***srv2 "password-testuser" *
使用同一台笔记本,相同的客户端配置拨号
连接成功的服务器日志记录如下:
***srv1 pptpd[10013]: CTRL: Client 61.135.24.2 control connection started
***srv1 pptpd[10013]: CTRL: Starting call (launching pppd, opening GRE)
***srv1 pppd[10014]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
***srv1 pppd[10014]: pppd 2.4.3 started by root, uid 0
***srv1 pppd[10014]: Using interface ppp0
***srv1 pppd[10014]: Connect: ppp0 <-->; /dev/pts/2
***srv1 pptpd[10013]: GRE: Bad checksum from pppd.
***srv1 /etc/hotplug/net.agent: assuming ppp0 is already up
***srv1 pptpd[10013]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
***srv1 pptpd[10013]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
***srv1 pppd[10014]: MPPE 128-bit stateless compression enabled
***srv1 pppd[10014]: found interface eth1 for proxy arp
***srv1 pppd[10014]: local IP address 192.168.4.150
***srv1 pppd[10014]: remote IP address 192.168.4.152
***srv1 pppd[10014]: LCP terminated by peer (A2#^Y^@<M-Mt^@^@^@^@)
***srv1 kernel: application bug: pptpctrl(10013) has SIGCHLD set to SIG_IGN but calls
wait().
***srv1 kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
***srv1 pppd[10014]: Modem hangup
***srv1 pppd[10014]: Connection terminated.
***srv1 pppd[10014]: Connect time 15.6 minutes.
***srv1 pppd[10014]: Sent 213361 bytes, received 48842 bytes.
***srv1 pppd[10014]: Exit.
***srv1 pptpd[10013]: CTRL: Client 61.135.24.2 control connection finished
***srv1 /etc/hotplug/net.agent: NET unregister event not supported
连接失败的服务器日志记录如下:
***srv2 pptpd[2087]: CTRL: Client 61.135.30.130 control connection started
***srv2 pptpd[2087]: CTRL: Starting call (launching pppd, opening GRE)
***srv2 pppd[2088]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
***srv2 pppd[2088]: pppd 2.4.3 started by root, uid 0
***srv2 pppd[2088]: Using interface ppp0
***srv2 pppd[2088]: Connect: ppp0 <-->; /dev/pts/2
***srv2 pptpd[2087]: GRE: Bad checksum from pppd.
***srv2 /etc/hotplug/net.agent: assuming ppp0 is already up
***srv2 pppd[2088]: LCP: timeout sending Config-Requests
***srv2 pppd[2088]: Connection terminated.
***srv2 pppd[2088]: Exit.
***srv2 pptpd[2087]: GRE: read(fd=4,buffer=804e6e0,len=8196) from PTY
failed: status = -1 error = Input/output error, usually caused by unexpected
termination of pppd, check option syntax and pppd logs
***srv2 pptpd[2087]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
***srv2 pptpd[2087]: CTRL: Client 61.135.30.130 control connection finished
***srv2 kernel: application bug: pptpctrl(2087) has SIGCHLD set to SIG_IGN but calls
wait().
***srv2 kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
***srv2 /etc/hotplug/net.agent: NET unregister event not supported
谁愿意跟我讨论讨论这个问题吗?
[ 本帖最后由 aicoa 于 2006-1-24 09:09 编辑 ]
水若寒 回复于:2005-01-18 17:12:21
我的环境:
我的环境:
kernel: linux-2.6.10.tar.gz
kernel_patch: linux-2.6.10-mppe-mppc-1.2.patch.gz
pppd: ppp-2.4.3.tar.gz
pppd_patch: ppp-2.4.3-mppe-mppc-1.1.patch.gz
pptpd: pptpd-1.2.1.tar.gz
检验内核和PPP是否支持MPPE/MPPE
[root@yf165 etc]# strings `which pppd`|grep -i mppe|wc --lines
30
[root@yf165 etc]# strings `which pppd`|grep -i mppc|wc --lines
7
[root@yf165 etc]# dmesg | grep MPPE
MPPE/MPPC encryption/compression module registered
相关配置:
[color=blue]1、/etc/pptpd.conf[/color]
# TAG: ppp
# Path to the pppd program, default '/usr/sbin/pppd' on Linux
#
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: 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
[color=blue]2、/etc/ppp/options.pptpd[/color]
# Authentication
# Name of the local system for authentication purposes
# (must match the second field in /etc/ppp/chap-secrets entries)
name pptpd
# 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
refuse-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
# }}}
# OpenSSL licensed ppp-2.4.1 fork with MPPE only, kernel module mppe.o
# {{{
#-chap
#-chapms
# Require the peer to authenticate itself using MS-CHAPv2 [Microsoft
# Challenge Handshake Authentication Protocol, Version 2] authentication.
#+chapms-v2
# Require MPPE encryption
# (note that MPPE requires the use of MSCHAP-V2 during authentication)
#mppe-40 # enable either 40-bit or 128-bit, not both
#mppe-128
#mppe-stateless
# }}}
# 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 211.95.193.97
#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
# Logging
# Enable connection debugging facilities.
# (see your syslog configuration for where pppd sends to)
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
[color=blue]3、/etc/ppp/chap-secrets[/color]
# Secrets for authentication using CHAP
# client server secret IP addresse
test pptpd test *
[color=green]问题:[/color]
当我打开require-mppe-128这个选项时,连接不成功,
查看/var/log/messages有以下信息
Jan 17 22:31:01 yf165 pptpd[6607]: CTRL: Client 218.15.194.251 control connection started
Jan 17 22:31:02 yf165 pptpd[6607]: CTRL: Starting call (launching pppd, opening GRE)
Jan 17 22:31:02 yf165 pppd[6608]: In file /etc/ppp/options.pptpd: unrecognized option 'require-mppe-128'
Jan 17 22:31:02 yf165 pptpd[6607]: GRE: read(fd=4,buffer=804db80,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
Jan 17 22:31:02 yf165 pptpd[6607]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
Jan 17 22:31:02 yf165 pptpd[6607]: CTRL: Client 218.15.194.251 control connection finished
[color=red]In file /etc/ppp/options.pptpd: unrecognized option 'require-mppe-128'
GRE: read(fd=4,buffer=804db80,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
CTRL: PTY read or GRE write failed (pty,gre)=(4,5)[/color]
当我注释掉,可以连接,客户端信息栏里显示已经支持MPPE/MPPC,
但还是有些问题:
Jan 18 00:08:40 yf165 pptpd[4387]: CTRL: Client 218.15.194.251 control connection started
Jan 18 00:08:40 yf165 pptpd[4387]: CTRL: Starting call (launching pppd, opening GRE)
Jan 18 00:08:40 yf165 pppd[4388]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
Jan 18 00:08:40 yf165 pppd[4388]: pptpd-logwtmp: $Version$
Jan 18 00:08:40 yf165 pppd[4388]: pppd 2.4.3 started by root, uid 0
Jan 18 00:08:40 yf165 pppd[4388]: Using interface ppp0
Jan 18 00:08:40 yf165 pppd[4388]: Connect: ppp0 <-->; /dev/pts/1
Jan 18 00:08:40 yf165 pptpd[4387]: GRE: Bad checksum from pppd.
Jan 18 00:08:42 yf165 pptpd[4387]: CTRL: Ignored a SET LINK INFO packet with real ACCMs
Jan 18 00:08:44 yf165 pppd[4388]: Cannot determine ethernet address for proxy ARP
Jan 18 00:08:44 yf165 pppd[4388]: local IP address 192.168.0.1
Jan 18 00:08:44 yf165 pppd[4388]: remote IP address 192.168.0.235
Jan 18 00:08:44 yf165 pppd[4388]: pptpd-logwtmp.so ip-up ppp0 test 218.15.194.251
Jan 18 00:08:44 yf165 pppd[4388]: MPPC/MPPE 128-bit stateful compression enabled
Jan 18 00:09:24 yf165 pppd[4388]: LCP terminated by peer (^P^AWm^@<M-Mt^@^@^@^@)
Jan 18 00:09:24 yf165 pppd[4388]: pptpd-logwtmp.so ip-down ppp0
Jan 18 00:09:24 yf165 pppd[4388]: Connect time 0.7 minutes.
Jan 18 00:09:24 yf165 pppd[4388]: Sent 1020 bytes, received 5382 bytes.
Jan 18 00:09:24 yf165 pppd[4388]: Modem hangup
Jan 18 00:09:24 yf165 pppd[4388]: Connection terminated.
Jan 18 00:09:25 yf165 pppd[4388]: Exit.
Jan 18 00:09:25 yf165 pptpd[4387]: CTRL: Client 218.15.194.251 control connection finished
[color=red]GRE: Bad checksum from pppd.
CTRL: Ignored a SET LINK INFO packet with real ACCMs
Cannot determine ethernet address for proxy ARP[/color]
到底出了什么问题呢?请各位不吝赐教!!谢谢![color=red][/color]
yanyp 回复于:2005-02-15 16:19:58
gre协议号是47,你把他打开试试
gre协议号是47,你把他打开试试
wheel 回复于:2005-02-20 12:17:41
可否使用CA认证?
可否使用CA认证?
qhzz 回复于:2005-03-11 17:46:12
我的不能连接,请问是怎么回事,提示如下:
ar 12 17:56:46 xining pptpd[2732]: MGR: Manager process started
Mar 12 17:56:46 xining pptpd[2732]: MGR: Maximum of 22 connections available
Mar 12 17:57:10 xining pptpd[2733]: CTRL: Client 192.168.0.5 control connection started
Mar 12 17:57:10 xining pptpd[2733]: CTRL: Starting call (launching pppd, opening GRE)
Mar 12 17:57:10 xining pptpd[2734]: CTRL (PPPD Launcher): Failed to launch PPP daemon.
Mar 12 17:57:10 xining pptpd[2734]: CTRL: PPPD launch failed!
Mar 12 17:57:10 xining pptpd[2733]: GRE: read(fd=5,buffer=804d760,len=8196) from PTY failed: status = -1 error = Input/output error
Mar 12 17:57:10 xining pptpd[2733]: CTRL: PTY read or GRE write failed (pty,gre)=(5,6)
Mar 12 17:57:10 xining pptpd[2733]: CTRL: Client 192.168.0.5 control connection finished
我的不能连接,请问是怎么回事,提示如下:
ar 12 17:56:46 xining pptpd[2732]: MGR: Manager process started
Mar 12 17:56:46 xining pptpd[2732]: MGR: Maximum of 22 connections available
Mar 12 17:57:10 xining pptpd[2733]: CTRL: Client 192.168.0.5 control connection started
Mar 12 17:57:10 xining pptpd[2733]: CTRL: Starting call (launching pppd, opening GRE)
Mar 12 17:57:10 xining pptpd[2734]: CTRL (PPPD Launcher): Failed to launch PPP daemon.
Mar 12 17:57:10 xining pptpd[2734]: CTRL: PPPD launch failed!
Mar 12 17:57:10 xining pptpd[2733]: GRE: read(fd=5,buffer=804d760,len=8196) from PTY failed: status = -1 error = Input/output error
Mar 12 17:57:10 xining pptpd[2733]: CTRL: PTY read or GRE write failed (pty,gre)=(5,6)
Mar 12 17:57:10 xining pptpd[2733]: CTRL: Client 192.168.0.5 control connection finished
platinum 回复于:2005-03-29 23:05:17
引用:原帖由 "tjyihui" 发表:
启动NAT转发
echo "1" >; /proc/sys/net/ipv4/ip_forward
/sbin/depmod -a
/sbin/modprobe ip_tables
/sbin/modprobe iptable_nat
/sbin/modprobe ip_nat_ftp
/sbin/modprobe ipt_LOG
我提出一些异议,大家讨论一下
1、这个脚本仅仅是允许访问LAN或者相同×××地址池内的IP,而没有允许NAT,也就是×××默认路由不要使用远程的,否则不能再上网
2、depmod命令在patch后执行一次即可,不用每次执行
3、ip_tables、iptable_nat、ipt_LOG模块会随iptables相关语句自动加载
4、ip_nat_ftp的用途是用于PASSIVE模式的FTP传输的,如果×××池或LAN里面没有FTP服务器,这句话根本没必要
引用:原帖由 "tjyihui" 发表:
启动NAT转发
echo "1" >; /proc/sys/net/ipv4/ip_forward
/sbin/depmod -a
/sbin/modprobe ip_tables
/sbin/modprobe iptable_nat
/sbin/modprobe ip_nat_ftp
/sbin/modprobe ipt_LOG
我提出一些异议,大家讨论一下
1、这个脚本仅仅是允许访问LAN或者相同×××地址池内的IP,而没有允许NAT,也就是×××默认路由不要使用远程的,否则不能再上网
2、depmod命令在patch后执行一次即可,不用每次执行
3、ip_tables、iptable_nat、ipt_LOG模块会随iptables相关语句自动加载
4、ip_nat_ftp的用途是用于PASSIVE模式的FTP传输的,如果×××池或LAN里面没有FTP服务器,这句话根本没必要
lihn 回复于:2005-04-01 13:27:56
我在客户端测试。可以成功连接,但无法ping通*** server 和其他的IP。怎么解决?
我在客户端测试。可以成功连接,但无法ping通*** server 和其他的IP。怎么解决?
ljily000 回复于:2005-05-04 01:05:58
非得重新编译内核?我的机器太慢了,编译一次内核得很长时间,不编译内核可以实现MPPC压缩和MPPE吗?
非得重新编译内核?我的机器太慢了,编译一次内核得很长时间,不编译内核可以实现MPPC压缩和MPPE吗?
ljily000 回复于:2005-05-05 12:08:47
顶!
非得编译内核吗?不编译内核可以实现MPPC压缩和MPPE加密吗?
顶!
非得编译内核吗?不编译内核可以实现MPPC压缩和MPPE加密吗?
ljily000 回复于:2005-05-08 22:36:00
tjyihui我按你的步骤做了,出现如下错误:(/var/log/message)
May 6 17:16:36 server xinetd: xinetd startup succeeded
May 6 17:16:36 server crond: crond startup succeeded
May 6 17:16:38 server cups: cupsd startup succeeded
May 6 17:16:38 server anacron: anacron startup succeeded
May 6 17:16:38 server atd: atd startup succeeded
May 6 17:16:38 server kernel: CSLIP: code copyright 1989 Regents of the University of California
May 6 17:16:38 server kernel: PPP generic driver version 2.4.2
May 6 17:16:38 server kernel: MPPE/MPPC encryption/compression module registered
May 6 17:16:48 server sshd(pam_unix)[1536]: session opened for user root by (uid=0)
May 6 17:17:15 server pptpd[1852]: MGR: Manager process started
May 6 17:17:15 server pptpd[1852]: MGR: Maximum of 51 connections available
May 6 17:17:32 server pptpd[1872]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:32 server pptpd[1872]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:32 server pppd[1873]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:32 server pptpd[1872]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:32 server pptpd[1872]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:32 server pptpd[1872]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:47 server pptpd[1891]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:47 server pptpd[1891]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:47 server pppd[1892]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:47 server pptpd[1891]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:47 server pptpd[1891]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:47 server pptpd[1891]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:48 server pptpd[1893]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:48 server pptpd[1893]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:48 server pppd[1894]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:48 server pptpd[1893]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:48 server pptpd[1893]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:48 server pptpd[1893]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:49 server pptpd[1895]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:49 server pptpd[1895]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:49 server pppd[1896]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:49 server pptpd[1895]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:49 server pptpd[1895]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:49 server pptpd[1895]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:50 server pptpd[1897]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:50 server pptpd[1897]: CTRL: Starting call (launching pppd, opening GRE)
何故?
tjyihui我按你的步骤做了,出现如下错误:(/var/log/message)
May 6 17:16:36 server xinetd: xinetd startup succeeded
May 6 17:16:36 server crond: crond startup succeeded
May 6 17:16:38 server cups: cupsd startup succeeded
May 6 17:16:38 server anacron: anacron startup succeeded
May 6 17:16:38 server atd: atd startup succeeded
May 6 17:16:38 server kernel: CSLIP: code copyright 1989 Regents of the University of California
May 6 17:16:38 server kernel: PPP generic driver version 2.4.2
May 6 17:16:38 server kernel: MPPE/MPPC encryption/compression module registered
May 6 17:16:48 server sshd(pam_unix)[1536]: session opened for user root by (uid=0)
May 6 17:17:15 server pptpd[1852]: MGR: Manager process started
May 6 17:17:15 server pptpd[1852]: MGR: Maximum of 51 connections available
May 6 17:17:32 server pptpd[1872]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:32 server pptpd[1872]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:32 server pppd[1873]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:32 server pptpd[1872]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:32 server pptpd[1872]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:32 server pptpd[1872]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:47 server pptpd[1891]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:47 server pptpd[1891]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:47 server pppd[1892]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:47 server pptpd[1891]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:47 server pptpd[1891]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:47 server pptpd[1891]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:48 server pptpd[1893]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:48 server pptpd[1893]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:48 server pppd[1894]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:48 server pptpd[1893]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:48 server pptpd[1893]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:48 server pptpd[1893]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:49 server pptpd[1895]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:49 server pptpd[1895]: CTRL: Starting call (launching pppd, opening GRE)
May 6 17:17:49 server pppd[1896]: In file /etc/ppp/options.pptpd: unrecognized option 'refuse-mschap'
May 6 17:17:49 server pptpd[1895]: GRE: read(fd=4,buffer=804d560,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
May 6 17:17:49 server pptpd[1895]: CTRL: PTY read or GRE write failed (pty,gre)=(4,5)
May 6 17:17:49 server pptpd[1895]: CTRL: Client 10.0.0.205 control connection finished
May 6 17:17:50 server pptpd[1897]: CTRL: Client 10.0.0.205 control connection started
May 6 17:17:50 server pptpd[1897]: CTRL: Starting call (launching pppd, opening GRE)
何故?
jondj 回复于:2005-05-12 21:46:59
在给ppp打补丁时出现下列错误:
不知道何解。
[root@RHEL4 ~]# ls
anaconda-ks.cfg Desktop install.log install.log.syslog ppp-2.4.3 ppp-2.4.3-mppe-mppc-1.1.patch.gz ppp-2.4.3.tar.gz
[root@RHEL4 ~]# patch -p0 -i ppp-2.4.3-mppe-mppc-1.1.patch.gz
patch unexpectedly ends in middle of line
patch: **** Only garbage was found in the patch input.
[root@RHEL4 ~]#
在给ppp打补丁时出现下列错误:
不知道何解。
[root@RHEL4 ~]# ls
anaconda-ks.cfg Desktop install.log install.log.syslog ppp-2.4.3 ppp-2.4.3-mppe-mppc-1.1.patch.gz ppp-2.4.3.tar.gz
[root@RHEL4 ~]# patch -p0 -i ppp-2.4.3-mppe-mppc-1.1.patch.gz
patch unexpectedly ends in middle of line
patch: **** Only garbage was found in the patch input.
[root@RHEL4 ~]#
platinum 回复于:2005-05-12 22:36:48
晕,先gunzip ppp-2.4.3-mppe-mppc-1.1.patch.gz
晕,先gunzip ppp-2.4.3-mppe-mppc-1.1.patch.gz
jondj 回复于:2005-05-12 23:06:38
我的系统是RHEL4 (2。6。9)要不要打内核补丁?
如果要,补丁文件在哪儿下载。
我的系统是RHEL4 (2。6。9)要不要打内核补丁?
如果要,补丁文件在哪儿下载。
platinum 回复于:2005-05-13 00:15:51
引用:原帖由 "jondj" 发表:
我的系统是RHEL4 (2。6。9)要不要打内核补丁?
如果要,补丁文件在哪儿下载。
你没好好看这篇文章吧?
引用:原帖由 "jondj" 发表:
我的系统是RHEL4 (2。6。9)要不要打内核补丁?
如果要,补丁文件在哪儿下载。
你没好好看这篇文章吧?
studentstep 回复于:2005-12-14 09:30:14
mark
mark
QUSHIQIANG 回复于:2006-01-05 08:46:22
http://pptpclient.sourceforge.net/
News: MPPE in Linux 2.6.15
Linux kernel 2.6.15 has been released and includes the PPP MPPE encryption module, which implements the Microsoft Point-to-Point Encryption method as a PPP compressor/decompressor.
This is necessary for Linux clients and servers to interoperate with Microsoft Point-to-Point Tunneling Protocol (PPTP) servers (either Microsoft PPTP servers or the poptop project) which use MPPE to encrypt data when creating a ×××.
Now that Linux includes the module, the PPTP projects recommend upgrading to 2.6.15.
-- James Cameron
2006-01-03
http://pptpclient.sourceforge.net/
News: MPPE in Linux 2.6.15
Linux kernel 2.6.15 has been released and includes the PPP MPPE encryption module, which implements the Microsoft Point-to-Point Encryption method as a PPP compressor/decompressor.
This is necessary for Linux clients and servers to interoperate with Microsoft Point-to-Point Tunneling Protocol (PPTP) servers (either Microsoft PPTP servers or the poptop project) which use MPPE to encrypt data when creating a ×××.
Now that Linux includes the module, the PPTP projects recommend upgrading to 2.6.15.
-- James Cameron
2006-01-03
lisim 回复于:2006-01-11 14:56:13
Linux 2.6.15 内核是否也支持mppc ?
Linux 2.6.15 内核是否也支持mppc ?
wybearss 回复于:2006-01-15 19:10:44
想问下各位大虾,这个pptp服务软件,什么地方影响它的性能呢?
多CPU 高级网卡 还是内存?或者是其它呢?
在我的测试下,一个pptp连接消耗不到1% 的CPU资源,内存也是不到1M
请教下各位!谢谢
想问下各位大虾,这个pptp服务软件,什么地方影响它的性能呢?
多CPU 高级网卡 还是内存?或者是其它呢?
在我的测试下,一个pptp连接消耗不到1% 的CPU资源,内存也是不到1M
请教下各位!谢谢
转载于:https://blog.51cto.com/enchen/156534

1085

被折叠的 条评论
为什么被折叠?



