[pptp-server] PopTop Problem
George R. Kasica
georgek at netwrx1.com
Wed Sep 29 15:34:47 CDT 1999
Sorry to bug you with this but I need to get it working soon and have
had no success....
George
Well, I've got pptpd 1.0 working well here, with a small problem.....I
still seem to send all data down the "normal" channel be it dialup or
ethernet connect rather than everything over the VPN....this causes
the problem that I still appear to come to the ISPs news server from
"outside" their network....how to I accomplish the following (the
Client is WIN98 Server with pptpd on it Linux 2.2.5) IP Addresses are
REAL there is no firewall between:
Client Server ISP
205.254.202.120 ----- VPN ------------ 205.254.202.114 - 156.46.10.23
10.36.9.242 --------- INTERNET--------->
I'm getting the VPN Adapter assigned the IP address above yet the
traffic when trace routed seems to go through the 'Net rather than
routing through the Server hence the problem with appearing from
"outside" the net.
Any suggestions, and please keep it simple and as clear as possible.
>your route table may be sending the packets in a direction you may not have
>expected. print our yout route table and i'll have a look
>
>-matt
>
Matt:
Here it is in "steps"
1) Just ethernet connected, no dialup or VPN (cannot get out to
Internet from here) Ethernet info 3.231.4.237 255.255.252.0
C:\WINDOWS\Desktop>route print
Active Routes:
Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 3.231.4.254 3.231.4.237
1
3.231.4.0 255.255.252.0 3.231.4.237 3.231.4.237
1
3.231.4.237 255.255.255.255 127.0.0.1 127.0.0.1
1
3.255.255.255 255.255.255.255 3.231.4.237 3.231.4.237
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
224.0.0.0 224.0.0.0 3.231.4.237 3.231.4.237
1
255.255.255.255 255.255.255.255 3.231.4.237 0.0.0.0
1
2) Dialup Connection with Ethernet
Info Ethernet 3.231.4.237 255.255.252.0
Dialup: 208.254.238.104 255.255.255.255 Internet goes through here.
Active Routes:
Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 3.231.4.254 3.231.4.237
2
0.0.0.0 0.0.0.0 208.254.238.104 208.254.238.104
1
3.231.4.0 255.255.252.0 3.231.4.237 3.231.4.237
2
3.231.4.237 255.255.255.255 127.0.0.1 127.0.0.1
1
3.255.255.255 255.255.255.255 3.231.4.237 3.231.4.237
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
208.254.238.0 255.255.255.0 208.254.238.104 208.254.238.104
1
208.254.238.104 255.255.255.255 127.0.0.1 127.0.0.1
1
224.0.0.0 224.0.0.0 3.231.4.237 3.231.4.237
1
224.0.0.0 224.0.0.0 208.254.238.104 208.254.238.104
1
255.255.255.255 255.255.255.255 208.254.238.104 208.254.238.104
1
3) Ethernet with dialup and VPN Active:
Info Ethernet 3.231.4.237 255.255.252.0
Dialup: 208.254.238.104 255.255.255.255 Internet goes through here.
VPN: 205.254.202.120 255.255.255.0
Active Routes:
Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 3.231.4.254 3.231.4.237
2
0.0.0.0 0.0.0.0 208.254.238.104 208.254.238.104
1
3.231.4.0 255.255.252.0 3.231.4.237 3.231.4.237
2
3.231.4.237 255.255.255.255 127.0.0.1 127.0.0.1
1
3.255.255.255 255.255.255.255 3.231.4.237 3.231.4.237
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
205.254.202.0 255.255.255.0 205.254.202.120 205.254.202.120
1
205.254.202.114 255.255.255.255 208.254.238.104 208.254.238.104
1
205.254.202.120 255.255.255.255 127.0.0.1 127.0.0.1
1
208.254.238.0 255.255.255.0 208.254.238.104 208.254.238.104
1
208.254.238.104 255.255.255.255 127.0.0.1 127.0.0.1
1
224.0.0.0 224.0.0.0 3.231.4.237 3.231.4.237
1
224.0.0.0 224.0.0.0 208.254.238.104 208.254.238.104
1
224.0.0.0 224.0.0.0 205.254.202.120 205.254.202.120
1
255.255.255.255 255.255.255.255 208.254.238.104 208.254.238.104
1
A trace route to news.alpha.net (156.46.10.23) shows:
Trace news.alpha.net; Start time 09/24/99 09:23:42
Tracing route to 156.46.10.23
50 bytes from 156.46.10.23: time=175 ms
Hop Avg Diff Address
1 104 104 206.115.150.210
tnt18.chi5.da.uu.net
2 102 -5 207.76.46.206
3 99 -5 152.63.64.22
132.ATM11-0-0.HR2.CHI1.ALTER.NET
4 103 2 146.188.208.46
103.ATM3-0.XR2.CHI4.ALTER.NET
5 102 1 146.188.208.13
194.ATM9-0-0.BR1.CHI1.ALTER.NET
6 123 21 137.39.250.6
gw14-chi-8-0.sprintlink.net
7 103 -11 144.232.10.157
sl-bb11-chi-2-1.sprintlink.net
8 104 1 144.232.0.202
sl-gw16-chi-8-0-0.sprintlink.net
9 762 660 144.228.207.18
sl-alphadot-2-1-0.sprintlink.net
10 145 -299 206.190.31.9
core51-h-1-0.mke.alpha.net
11 198 50 156.46.10.23
news.alpha.net
End time 09/24/99 09:24:10
host reached
But it does NOT go through the PPTP Server eagle.netwrx1.net
(205.254.202.114) (thats a one not an L)
If you'd like to try testing you can use the login of georgek and
password of tibbs1 (thats a one not an L)
Here is the netstat -nr from the PPTP Server:
[root at eagle /root]# netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
205.254.202.120 0.0.0.0 255.255.255.255 UH 0 0
0 ppp0
192.168.1.0 0.0.0.0 255.255.255.240 U 0 0
0 eth0
205.254.202.112 0.0.0.0 255.255.255.240 U 0 0
0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo
0.0.0.0 205.254.202.113 0.0.0.0 UG 0 0
0 eth0
More information about the pptp-server
mailing list