Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN client with Fedora core 3

Status
Not open for further replies.

jundalabee

IS-IT--Management
Nov 19, 2003
35
Hi I Am using Fedora core 3 to try to connect to my work. I can get around linux ok, but my underlying knowledge is limited. I am using pptp-config to try to connect but I am coming to a dead end once I try to connect. Below are my debug messages and replaced my works ip-addy with a dummy class C. Could someone give me some tips or give me advice on a better way to do it?

I am running an adsl router with nat, eth0 is 192.168.1.9. adsl router gateway is 192.168.1.1. I have add a route in pptpconfig which is replaced in this text with 199.199.199.0/24

pptpconfig: debug information dump begins
WARNING: security sensitive information follows
pptpconfig 1.2 2004/06/19 08:57:15
# pppd --version
pppd version 2.4.2
# uname -a
Linux Patton 2.6.9-1.667 #1 Tue Nov 2 14:41:25 EST 2004 i686 athlon i386 GNU/Linux
# grep mppe /proc/modules
# modinfo ppp_mppe
filename: /lib/modules/2.6.9-1.667/kernel/drivers/net/ppp_mppe.ko
license: Dual BSD/GPL
vermagic: 2.6.9-1.667 686 REGPARM 4KSTACKS gcc-3.4
depends: ppp_generic
Array
(
[name] => work
[server] => 199.199.199.22
[domain] =>
[username] => *hidden*
[password] => (hidden by pptpconfig)
[pppd-options] =>
[pptp-options] =>
[resolv] =>
[dns-options] =>
[routing] => routing_client_to_lan
[usepeerdns] => 1
[require-mppe] => 1
[nomppe-40] => 1
[nomppe-128] => 1
[refuse-eap] => 1
[mppe-stateful] => 1
[autostart] =>
[iconify] =>
[persist] =>
[debug] => 1
[client-to-lan] => a:1:{s:14:"199.199.199.0/24";s:0:"";}
)
# route -n (before pppd)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
pptpconfig: debug information dump ends, starting pppd
pppd options in effect:
debug # (from /etc/ppp/peers/work)
updetach # (from command line)
logfd 1 # (from command line)
linkname work # (from /etc/ppp/peers/work)
dump # (from /etc/ppp/peers/work)
noauth # (from /etc/ppp/peers/work)
refuse-eap # (from /etc/ppp/peers/work)
name *hidden* # (from /etc/ppp/peers/work)
remotename work # (from /etc/ppp/peers/work)
# (from /etc/ppp/options.pptp)
pty pptp 199.199.199.22 --nolaunchpppd # (from /etc/ppp/peers/work)
ipparam work # (from /etc/ppp/peers/work)
usepeerdns # (from /etc/ppp/peers/work)
nobsdcomp # (from /etc/ppp/options.pptp)
nodeflate # (from /etc/ppp/options.pptp)
# (from /etc/ppp/peers/work)
# (from /etc/ppp/peers/work)
nomppe-128 # (from /etc/ppp/peers/work)
mppe-stateful # (from /etc/ppp/peers/work)
using channel 6
Using interface ppp0
pptpconfig: monitoring interface ppp0
Connect: ppp0 <--> /dev/pts/2
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x1 <mru 1200> <magic 0xe5ddf90f> <quality lqr 00 00 0b b8> <auth chap MS-v2>]
sent [LCP ConfRej id=0x1 <quality lqr 00 00 0b b8>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x73da7eb9> <pcomp> <accomp>]
LCP: timeout sending Config-Requests
Connection terminated.
Waiting for 1 child processes...
script pptp 199.199.199.22 --nolaunchpppd , pid 4581
Script pptp 199.199.199.22 --nolaunchpppd finished (pid 4581), status = 0x0
# route -n (after pppd exit)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
pptpconfig: pppd process terminated by signal 10 (failed)
pptpconfig: SIGUSR1
# route -n (after completion)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
 
I've seen failures like this with the MS side not configured properly. But, there are multiple ways for the VPN to fail. No matter which end is at fault, you need to enable logging or "dump" to get the details of the failure.

Have you tried these directions when you installed and configured the PPTP client?

Are you using the GUI or the command line interface to configure PPTP? I found that there were some differences between the GUI and the CLI. I would make changes in the GUI and the changes would not be reflected in the CLI. So I would stick with one or the other.

THis link for troubleshooting the PPTP is great and its current as of Jan 05 :)

This line is is what you need to do regardless:
"Add the options debug dump to the pppd command line or options file, then retry the connection."
"click on the tunnel, click on Miscellaneous, click on Enable connection debugging facilities, click on Update, click on Start, examine the output."

If you do a DUMP then post the results here if you still need some help.

MikeS

Find me at
&quot;Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots.&quot;
Sun Tzu
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top