PDA

View Full Version : gre protocol don't working


eightn
09-28-2005, 12:41 PM
I am using pptp server at unixshell. It work fine 2 month, but today I can't connect to server.

The problem is - gre packets from my computer can't reach unixshell machine.


from server pptp log:

pptpd[4025]: CTRL: Client 195.16.60.162 control connection started
pptpd[4025]: CTRL: Starting call (launching pppd, opening GRE)
pppd[4026]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
pppd[4026]: pptpd-logwtmp: $Version$
pppd[4026]: pppd 2.4.2 started by root, uid 0
pppd[4026]: using channel 112
pppd[4026]: Using interface ppp0
pppd[4026]: Connect: ppp0 <--> /dev/pts/2
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: sent [LCP ConfReq id=0x1 <mru 1490> <asyncmap 0x0> <auth chap MS-v2> <magic 0xb50e8527> <pcomp> <accomp>]
pppd[4026]: LCP: timeout sending Config-Requests
pppd[4026]: Connection terminated.
pppd[4026]: Exit.
pptpd[4025]: GRE: read(fd=6,buffer=804e620,len=8196) from PTY failed: status= -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
pptpd[4025]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7)
pptpd[4025]: CTRL: Reaping child PPP[4026]
pptpd[4025]: CTRL: Client 195.16.60.162 control connection finished



I am use tcpdump to localize problem.

tcpdump from unixshell:

IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: S 2989827217:2989827217(0) win 65535 <mss 1460,nop,nop,sackOK>
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: S 2085881353:2085881353(0) ack 2989827218 win 5840 <mss 1460,nop,nop,sackOK>
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: P 1:157(156) ack 1 win 65535: pptp CTRL_MSGTYPE=SCCRQ PROTO_VER(1.0) [|pptp]
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: . ack 157 win 5840
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: P 1:157(156) ack 157 win 5840: pptp CTRL_MSGTYPE=SCCRP PROTO_VER(1.0) [|pptp]
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: P 157:325(168) ack 157 win 65379: pptp CTRL_MSGTYPE=OCRQCALL_ID(49153) [|pptp]
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: P 157:189(32) ack 325 win 5840: pptp CTRL_MSGTYPE=OCRP CALL_ID(2432) [|pptp]
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 0 ack 4294967295 gre-ppp-payload
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: P 325:349(24) ack 189 win 65347: pptp CTRL_MSGTYPE=SLI PEER_CALL_ID(2432) [|pptp]
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: . ack 349 win 5840
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 1 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 2 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 3 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 4 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 5 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 6 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 7 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 8 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 9 gre-ppp-payload
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: F 189:189(0) ack 349 win 5840
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: F 349:349(0) ack 190 win 65347
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: . ack 350 win 5840




tcpdump from my computer:


IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: S 2989827217:2989827217(0) win 65535 <mss 1460,nop,nop,sackOK>
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: S 2085881353:2085881353(0) ack 2989827218 win 5840 <mss 1460,nop,nop,sackOK>
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: P 1:157(156) ack 1 win 65535: pptp CTRL_MSGTYPE=SCCRQ PROTO_VER(1.0) [|pptp]
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: . ack 157 win 5840IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: P 1:157(156) ack 157 win 5840: pptp CTRL_MSGTYPE=SCCRP PROTO_VER(1.0) [|pptp]
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: P 157:325(168) ack 157 win 65379: pptp CTRL_MSGTYPE=OCRQCALL_ID(49153) [|pptp]
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: P 157:189(32) ack 325 win 5840: pptp CTRL_MSGTYPE=OCRP CAIP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: S 2989827217:2989827217(0) win 65535 <mss 1460,nop,nop,sa
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 0 ack 4294967295 gre-ppp-payload
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: P 325:349(24) ack 189 win 65347: pptp CTRL_MSGTYPE=SLI PEER_CALL_ID(2432) [|pptp]
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 0 gre-ppp-payload
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: . ack 349 win 5840
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 1 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 1 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 2 ack 1 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 3 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 2 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 4 ack 2 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 5 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 3 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 6 ack 3 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 4 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 7 ack 4 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 8 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 5 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 9 ack 5 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 10 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 6 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 11 ack 6 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 12 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 7 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 13 ack 7 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 8 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 14 ack 8 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 15 gre-ppp-payload
IP 63.247.78.87 > 195.16.xxx.xxx: call 49153 seq 9 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 16 ack 9 gre-ppp-payload
IP 195.16.xxx.xxx > 63.247.78.87: call 2432 seq 17 gre-ppp-payload
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: F 189:189(0) ack 349 win 5840
IP 195.16.xxx.xxx.2845 > 63.247.78.87.1723: F 349:349(0) ack 190 win 65347
IP 63.247.78.87.1723 > 195.16.xxx.xxx.2845: . ack 350 win 5840


traceroute from my computer to unixshell

traceroute to 63.247.78.87 (63.247.78.87), 30 hops max, 38 byte packets
1 195.16.xxx.xxx 0.194 ms 0.147 ms 0.168 ms
2 194.85.128.246 3.761 ms 3.721 ms 3.702 ms
3 194.85.156.65 15.719 ms 7.384 ms 5.273 ms
4 194.85.156.2 5.551 ms 6.068 ms 5.929 ms
5 194.85.156.37 5.903 ms 5.818 ms 5.016 ms
6 166.63.220.69 29.835 ms 24.304 ms 26.181 ms
7 166.63.220.129 28.541 ms 166.63.220.145 30.730 ms 166.63.220.129 25.670 ms
8 208.173.216.25 38.139 ms 38.876 ms 34.291 ms
9 195.2.10.181 48.927 ms 60.219 ms 53.502 ms
10 195.2.10.146 57.920 ms 52.740 ms 53.580 ms
11 195.2.10.125 56.697 ms 62.749 ms 55.466 ms
12 195.66.226.48 55.266 ms 65.955 ms 61.449 ms
13 213.248.74.5 61.369 ms 54.850 ms 54.762 ms
14 213.248.65.90 123.967 ms 122.450 ms 126.998 ms
15 213.248.80.69 127.745 ms 127.535 ms 134.172 ms
16 213.248.80.142 140.212 ms 142.732 ms 142.890 ms
17 213.248.90.54 156.539 ms 151.181 ms 150.072 ms
18 209.51.149.105 224.033 ms 150.601 ms 148.950 ms
19 209.51.131.6 150.813 ms 150.922 ms 150.067 ms
20 * * *
21 72.9.242.103 149.859 ms 150.610 ms 149.170 ms
22 63.247.78.87 152.148 ms 152.927 ms 154.587 ms



I am try to use vpn connection from another machine, but result is not changed.


traceroute to 63.247.78.87 (63.247.78.87), 30 hops max, 40 byte packets
1 195.28.xxx.xxx 2.053 ms 1.940 ms 1.766 ms
2 195.28.34.129 4.778 ms 4.935 ms 5.064 ms
3 195.28.32.7 5.271 ms 6.291 ms 5.969 ms
4 213.248.99.77 6.426 ms 6.786 ms 9.261 ms
5 213.248.65.45 29.652 ms 29.876 ms 28.604 ms
6 213.248.65.29 37.584 ms 37.728 ms 39.185 ms
7 213.248.82.101 119.823 ms 118.637 ms 122.401 ms
8 213.248.80.138 129.761 ms 128.889 ms 131.461 ms
9 213.248.80.142 135.702 ms 137.030 ms 138.643 ms
10 213.248.90.54 163.708 ms 163.670 ms 163.711 ms
11 209.51.149.105 163.832 ms 163.519 ms 162.398 ms
12 209.51.131.6 162.850 ms 166.175 ms 163.276 ms
13 * * *
14 72.9.242.103 164.660 ms 164.263 ms 163.931 ms
15 63.247.78.87 162.702 ms 163.613 ms 165.628 ms



Where is problem?
Who are drop gre packets? :(

eightn
12-28-2005, 09:20 AM
Last problem was resolved after 2-3 days after I wrote this message.


But today gre protocol don't working again :(