Jump to content

Recommended Posts

Имею следующую связку:

Клиент1--хаб--Координатор1-ISP-Координатор2--хаб--PPTPсервер

| |

Клиент2---| |--Клиент3

Клиент1(ViPNet клиент есть): w2k

Клиент2(ViPNet клиент нет): Linux

Клиент3ViPNet клиент есть): XP

Координатор1: Versions: ViPNet 2.8-259, daemon 2.11-550, driver 2.11-380

Координатор2: Versions: ViPNet 2.8-231, daemon 2.11-537, driver 2.11-368

PPTPсервер: Linux 2.6.17 pppd 2.4.2

При тестировании PPTPсервера в подсети Клиента1 и Клиента2, регистрация на PPTPсервере проходила без проблем. После того, как PPTPсервер был поставлен ЗА Координатор2 (относительно Клиента1 и Клиента2) регистрация на PPTPсервере не проходит :( на Клиент2 вижу следующее сообщение:

w1800 ppp # pon vpn.0

pppd options in effect:

debug # (from /etc/ppp/peers/vpn.0)

updetach # (from /etc/ppp/peers/vpn.0)

dump # (from /etc/ppp/peers/vpn.0)

noauth # (from /etc/ppp/peers/vpn.0)

name test1 # (from /etc/ppp/peers/vpn.0)

remotename test1 # (from /etc/ppp/peers/vpn.0)

# (from /etc/ppp/options.pptp)

pty /usr/sbin/pptp 10.69.1.12 --nolaunchpppd # (from /etc/ppp/peers/vpn.0)

passive # (from /etc/ppp/options.pptp)

nobsdcomp # (from /etc/ppp/options.pptp)

nodeflate # (from /etc/ppp/options.pptp)

nomppe # (from /etc/ppp/options.pptp)

using channel 14

Using interface ppp0

Connect: ppp0 <--> /dev/pts/5

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9643948> <pcomp> <accomp>]

LCP: timeout sending Config-Requests

Modem hangup

Connection terminated.

Waiting for 1 child processes...

script /usr/sbin/pptp 10.69.1.12 --nolaunchpppd, pid 14419

Script /usr/sbin/pptp 10.69.1.12 --nolaunchpppd finished (pid 14419), status = 0x0

В логах PPTPсервера следующее:

Jul 28 12:24:48 [pptpd] CTRL: Client 10.69.101.251 control connection started

Jul 28 12:24:49 [pptpd] CTRL: Starting call (launching pppd, opening GRE)

Jul 28 12:24:49 [pppd] Plugin radius.so loaded.

Jul 28 12:24:49 [pppd] RADIUS plugin initialized.

Jul 28 12:24:49 [pppd] Plugin radattr.so loaded.

Jul 28 12:24:49 [pppd] RADATTR plugin initialized.

Jul 28 12:24:49 [pppd] pppd options in effect:

Jul 28 12:24:49 [pppd] debug debug__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] dump__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] plugin radius.so__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] plugin radattr.so__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] require-mschap-v2__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] refuse-pap__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] refuse-chap__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] refuse-mschap__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] 115200__# (from command line)

Jul 28 12:24:49 [pppd] lock__# (from /etc/ppp/options)

Jul 28 12:24:49 [pppd] local__# (from command line)

Jul 28 12:24:49 [pppd] mtu 1354__# (from /etc/ppp/options)

Jul 28 12:24:49 [pppd] ms-dns *** # [don't know how to print value]__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] proxyarp__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] 12.0.0.1:192.168.1.1__# (from command line)

Jul 28 12:24:49 [pppd] nobsdcomp__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] nodeflate__# (from /etc/ppp/options.pptpd)

Jul 28 12:24:49 [pppd] pppd 2.4.4 started by root, uid 0

Jul 28 12:24:49 [pppd] Using interface ppp0

Jul 28 12:24:49 [pppd] Connect: ppp0 <--> /dev/pts/0

Jul 28 12:24:49 [pptpd] GRE: Bad checksum from pppd.

Jul 28 12:25:01 [cron] (root) CMD (/usr/abills/libexec/billd -all )

Jul 28 12:25:19 [pppd] LCP: timeout sending Config-Requests_

Jul 28 12:25:19 [pppd] Connection terminated.

Jul 28 12:25:19 [pppd] Modem hangup

Jul 28 12:25:19 [pppd] Exit.

Jul 28 12:25:19 [pptpd] GRE: read(fd=8,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

Jul 28 12:25:19 [pptpd] CTRL: PTY read or GRE write failed (pty,gre)=(8,9)

Jul 28 12:25:19 [pptpd] CTRL: Client 10.69.101.251 control connection finished

ОДНАКО, Клиент3 (находящийся в той же подсети, что и PPTPсервер) регистрируется БЕЗ проблем...

В туннелях, естетственно Клиент2 прописан..

Может ли ViPNetP[Координатор] влиять на установление соединение с PPTPсервером?

Share this post


Link to post
Share on other sites
Имею следующую связку:

Клиент1--хаб--Координатор1-ISP-Координатор2--хаб--PPTPсервер

| |

Клиент2---| |--Клиент3

Картинка запортилась, вот, перерисовал:

Клиент1--хаб1--Координатор1-ISP-Координатор2--хаб2--PPTPсервер

Клиент2--/***********************************---Клиент3

Пояснение:

Клиент1 и Клиент2 поключены к хаб1

Клиент3 и PPTPсервер поключены к хаб2

на звездочки не смотреть (пробелы видимо удаляются)

Share this post


Link to post
Share on other sites

Уточните, пожалуста схему:

Клиент2 прописан в туннелях на Координаторе1?

ppptp сервер прописан в туннеле на Координаторе2?

Какие сетевые карты установлены на обоих Коориднаторах?

Share this post


Link to post
Share on other sites
Уточните, пожалуста схему:

Клиент2 прописан в туннелях на Координаторе1?

ppptp сервер прописан в туннеле на Координаторе2?

Да, конечно, все в тунелях прописано, соединения по другим службам проходит без проблем.

Какие сетевые карты установлены на обоих Координаторах?

Координатор1:

# lspci

00:04.0 Ethernet controller: Silicon Integrated Systems [siS] SiS900 PCI Fast Ethernet (rev 90)

00:08.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)

00:0a.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)

Координатор2:

# lspci

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

01:02.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)

01:08.0 Ethernet controller: Intel Corp.: Unknown device 1050 (rev 02)

Есть мнение, что в случае использование NAT, между клиентом и сервером, нужно задействовать модули ip_nat_proto_gre и ip_conntrack_proto_gre на шлюзах, выполняющими NAT. Наобум проверить не могу, т.к. координаторы все живые, Координатор1 на ядре 2.4.31 (там похоже нет поддержки ip_nat_proto_gre и ip_conntrack_proto_gre) Являются ли Координатор1 и Координатор2 устройствами с NAT?

вот что говорит tcpdump, запущеный на PPTPСервере, в момент попытки соединения Клиента1:

#tcpdump -n -i eth0 -s 0 tcp port 1723 or proto 4777

listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

09:46:50.629943 IP 10.69.101.251.51376 > 10.69.1.12.1723: S 2339366141:2339366141(0) win 5840 <mss 1460,sackOK,timestamp 58587951 0,nop,wscale 2>

09:46:50.630002 IP 10.69.1.12.1723 > 10.69.101.251.51376: S 3307726684:3307726684(0) ack 2339366142 win 5792 <mss 1460,sackOK,timestamp 32689947 58587951,nop,wscale 2>

09:46:50.654490 IP 10.69.101.251.51376 > 10.69.1.12.1723: . ack 1 win 1460 <nop,nop,timestamp 58587958 32689947>

09:46:50.656226 IP 10.69.101.251.51376 > 10.69.1.12.1723: P 1:157(156) ack 1 win 1460 <nop,nop,timestamp 58587962 32689947>: pptp CTRL_MSGTYPE=SCCRQ PROTO_VER(1.0) FRAME_CAP(AS) BEARER_CAP(DA) MAX_CHAN(65535) FIRM_REV(1) HOSTNAME(local) VENDOR(cananian)

09:46:50.656240 IP 10.69.1.12.1723 > 10.69.101.251.51376: . ack 157 win 1716 <nop,nop,timestamp 32689950 58587962>

09:46:50.657733 IP 10.69.1.12.1723 > 10.69.101.251.51376: P 1:157(156) ack 157 win 1716 <nop,nop,timestamp 32689950 58587962>: pptp CTRL_MSGTYPE=SCCRP PROTO_VER(1.0) RESULT_CODE(1) ERR_CODE(0) FRAME_CAP() BEARER_CAP() MAX_CHAN(1) FIRM_REV(1) HOSTNAME(local) VENDOR(linux)

09:46:50.698139 IP 10.69.101.251.51376 > 10.69.1.12.1723: . ack 157 win 1728 <nop,nop,timestamp 58587969 32689950>

09:46:51.665574 IP 10.69.101.251.51376 > 10.69.1.12.1723: P 157:325(168) ack 157 win 1728 <nop,nop,timestamp 58588213 32689950>: pptp CTRL_MSGTYPE=OCRQ CALL_ID(0) CALL_SER_NUM(0) MIN_BPS(2400) MAX_BPS(10000000) BEARER_TYPE(Any) FRAME_TYPE(E) RECV_WIN(3) PROC_DELAY(0) PHONE_NO_LEN(0) PHONE_NO() SUB_ADDR()

09:46:51.668289 IP 10.69.1.12.1723 > 10.69.101.251.51376: P 157:189(32) ack 325 win 1984 <nop,nop,timestamp 32690051 58588213>: pptp CTRL_MSGTYPE=OCRP CALL_ID(1152) PEER_CALL_ID(0) RESULT_CODE(1) ERR_CODE(0) CAUSE_CODE(0) CONN_SPEED(10000000) RECV_WIN(3) PROC_DELAY(0) PHY_CHAN_ID(0)

09:46:51.671183 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 0, ack 4294967295, length 45: LCP, Conf-Request (0x01), id 1, length 27

09:46:51.694425 IP 10.69.101.251.51376 > 10.69.1.12.1723: . ack 189 win 1728 <nop,nop,timestamp 58588218 32690051>

09:46:54.673069 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 1, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:46:57.683051 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 2, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:00.693046 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 3, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:03.703040 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 4, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:06.713030 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 5, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:09.723042 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 6, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:12.733055 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 7, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:15.743043 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 8, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:18.753042 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 9, length 41: LCP, Conf-Request (0x01), id 1, length 27

09:47:21.823878 IP 10.69.1.12.1723 > 10.69.101.251.51376: F 189:189(0) ack 325 win 1984 <nop,nop,timestamp 32693067 58588218>

09:47:21.830669 IP 10.69.101.251.51376 > 10.69.1.12.1723: P 325:341(16) ack 190 win 1728 <nop,nop,timestamp 58595757 32693067>: pptp CTRL_MSGTYPE=CCRQ CALL_ID(0)

09:47:21.830730 IP 10.69.1.12.1723 > 10.69.101.251.51376: R 3307726874:3307726874(0) win 0

09:47:21.831224 IP 10.69.101.251.51376 > 10.69.1.12.1723: F 341:341(0) ack 190 win 1728 <nop,nop,timestamp 58595757 32693067>

09:47:21.831238 IP 10.69.1.12.1723 > 10.69.101.251.51376: R 3307726874:3307726874(0) win 0

Share this post


Link to post
Share on other sites
01:08.0 Ethernet controller: Intel Corp.: Unknown device 1050 (rev 02)

эта сетевая карта задействована в работе? какой чип использует?

покажите, пожалуйста, вывод tcpdump... с сервера ppptp, когда к нему подключается Клиент2 и секции [misc] из фала iplir.conf на обоих Координаторах.

Share this post


Link to post
Share on other sites
01:08.0 Ethernet controller: Intel Corp.: Unknown device 1050 (rev 02)

эта сетевая карта задействована в работе? какой чип использует?

да, задействована

# cat modules.conf

alias eth1 e100

alias eth0 8139too

alias eth2 rhinefet

покажите, пожалуйста, вывод tcpdump... с сервера ppptp, когда к нему подключается Клиент2

# tcpdump -n -i eth0 -s 0 tcp port 1723 or proto 47

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

13:41:03.994579 IP 10.69.101.251.39977 > 10.69.1.12.1723: S 3089362:3089362(0) win 5840 <mss 1460,sackOK,timestamp 62101234 0,nop,wscale 2>

13:41:03.994638 IP 10.69.1.12.1723 > 10.69.101.251.39977: S 976582882:976582882(0) ack 3089363 win 5792 <mss 1460,sackOK,timestamp 34095284 62101234,nop,wscale 2>

13:41:04.000870 IP 10.69.101.251.39977 > 10.69.1.12.1723: . ack 1 win 1460 <nop,nop,timestamp 62101236 34095284>

13:41:04.016886 IP 10.69.101.251.39977 > 10.69.1.12.1723: P 1:157(156) ack 1 win 1460 <nop,nop,timestamp 62101240 34095284>: pptp CTRL_MSGTYPE=SCCRQ PROTO_VER(1.0) FRAME_CAP(AS) BEARER_CAP(DA) MAX_CHAN(65535) FIRM_REV(1) HOSTNAME(local) VENDOR(cananian)

13:41:04.016898 IP 10.69.1.12.1723 > 10.69.101.251.39977: . ack 157 win 1716 <nop,nop,timestamp 34095286 62101240>

13:41:04.018391 IP 10.69.1.12.1723 > 10.69.101.251.39977: P 1:157(156) ack 157 win 1716 <nop,nop,timestamp 34095286 62101240>: pptp CTRL_MSGTYPE=SCCRP PROTO_VER(1.0) RESULT_CODE(1) ERR_CODE(0) FRAME_CAP() BEARER_CAP() MAX_CHAN(1) FIRM_REV(1) HOSTNAME(local) VENDOR(linux)

13:41:04.026263 IP 10.69.101.251.39977 > 10.69.1.12.1723: . ack 157 win 1728 <nop,nop,timestamp 62101242 34095286>

13:41:05.027142 IP 10.69.101.251.39977 > 10.69.1.12.1723: P 157:325(168) ack 157 win 1728 <nop,nop,timestamp 62101492 34095286>: pptp CTRL_MSGTYPE=OCRQ CALL_ID(0) CALL_SER_NUM(0) MIN_BPS(2400) MAX_BPS(10000000) BEARER_TYPE(Any) FRAME_TYPE(E) RECV_WIN(3) PROC_DELAY(0) PHONE_NO_LEN(0) PHONE_NO() SUB_ADDR()

13:41:05.031454 IP 10.69.1.12.1723 > 10.69.101.251.39977: P 157:189(32) ack 325 win 1984 <nop,nop,timestamp 34095387 62101492>: pptp CTRL_MSGTYPE=OCRP CALL_ID(1792) PEER_CALL_ID(0) RESULT_CODE(1) ERR_CODE(0) CAUSE_CODE(0) CONN_SPEED(10000000) RECV_WIN(3) PROC_DELAY(0) PHY_CHAN_ID(0)

13:41:05.032761 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 0, ack 4294967295, length 45: LCP, Conf-Request (0x01), id 1, length 27

13:41:05.038294 IP 10.69.101.251.39977 > 10.69.1.12.1723: . ack 189 win 1728 <nop,nop,timestamp 62101495 34095387>

13:41:08.043065 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 1, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:11.053037 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 2, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:14.063035 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 3, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:17.073029 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 4, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:20.083050 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 5, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:23.093030 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 6, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:26.103033 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 7, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:29.113039 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 8, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:32.123033 IP 10.69.1.12 > 10.69.101.251: GREv1, call 0, seq 9, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:41:35.193884 IP 10.69.1.12.1723 > 10.69.101.251.39977: F 189:189(0) ack 325 win 1984 <nop,nop,timestamp 34098404 62101495>

13:41:35.200811 IP 10.69.101.251.39977 > 10.69.1.12.1723: P 325:341(16) ack 190 win 1728 <nop,nop,timestamp 62109036 34098404>: pptp CTRL_MSGTYPE=CCRQ CALL_ID(0)

13:41:35.200872 IP 10.69.1.12.1723 > 10.69.101.251.39977: R 976583072:976583072(0) win 0

13:41:35.201543 IP 10.69.101.251.39977 > 10.69.1.12.1723: F 341:341(0) ack 190 win 1728 <nop,nop,timestamp 62109036 34098404>

13:41:35.201556 IP 10.69.1.12.1723 > 10.69.101.251.39977: R 976583072:976583072(0) win 0

Вот еще вывод tcpdump, при подключении Клиент3 (соединение устанавливается)

# tcpdump -n -i eth0 -s 0 tcp port 1723 or proto 47

listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

13:32:27.435133 IP 10.69.1.21.4742 > 10.69.1.12.1723: S 2284639422:2284639422(0) win 65535 <mss 1351,nop,nop,sackOK>

13:32:27.435177 IP 10.69.1.12.1723 > 10.69.1.21.4742: S 426807480:426807480(0) ack 2284639423 win 5840 <mss 1460,nop,nop,sackOK>

13:32:27.435433 IP 10.69.1.21.4742 > 10.69.1.12.1723: P 1:157(156) ack 1 win 65535: pptp CTRL_MSGTYPE=SCCRQ PROTO_VER(1.0) FRAME_CAP(A) BEARER_CAP(A) MAX_CHAN(0) FIRM_REV(2600) HOSTNAME() VENDOR(Microsoft Windows NT)

13:32:27.435465 IP 10.69.1.12.1723 > 10.69.1.21.4742: . ack 157 win 6432

13:32:27.437094 IP 10.69.1.12.1723 > 10.69.1.21.4742: P 1:157(156) ack 157 win 6432: pptp CTRL_MSGTYPE=SCCRP PROTO_VER(1.0) RESULT_CODE(1) ERR_CODE(0) FRAME_CAP() BEARER_CAP() MAX_CHAN(1) FIRM_REV(1) HOSTNAME(local) VENDOR(linux)

13:32:27.437415 IP 10.69.1.21.4742 > 10.69.1.12.1723: P 157:325(168) ack 157 win 65379: pptp CTRL_MSGTYPE=OCRQ CALL_ID(16384) CALL_SER_NUM(45585) MIN_BPS(300) MAX_BPS(100000000) BEARER_TYPE(Any) FRAME_TYPE(E) RECV_WIN(64) PROC_DELAY(0) PHONE_NO_LEN(0) PHONE_NO() SUB_ADDR()

13:32:27.441716 IP 10.69.1.12.1723 > 10.69.1.21.4742: P 157:189(32) ack 325 win 7504: pptp CTRL_MSGTYPE=OCRP CALL_ID(1664) PEER_CALL_ID(16384) RESULT_CODE(1) ERR_CODE(0) CAUSE_CODE(0) CONN_SPEED(100000000) RECV_WIN(64) PROC_DELAY(0) PHY_CHAN_ID(0)

13:32:27.445396 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 0, ack 4294967295, length 45: LCP, Conf-Request (0x01), id 1, length 27

13:32:27.506479 IP 10.69.1.21.4742 > 10.69.1.12.1723: P 325:349(24) ack 189 win 65347: pptp CTRL_MSGTYPE=SLI PEER_CALL_ID(1664) SEND_ACCM(0xffffffff) RECV_ACCM(0xffffffff)

13:32:27.542890 IP 10.69.1.12.1723 > 10.69.1.21.4742: . ack 349 win 7504

13:32:27.608403 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 0, length 37: LCP, Conf-Request (0x01), id 0, length 23

13:32:27.608655 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 1, ack 0, length 27: LCP, Conf-Reject (0x04), id 0, length 9

13:32:27.609009 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 1, ack 1, length 38: LCP, Conf-Request (0x01), id 1, length 20

13:32:27.609234 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 2, ack 1, length 38: LCP, Conf-Ack (0x02), id 1, length 20

13:32:27.707038 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, ack 2, no-payload, length 12

13:32:30.453050 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 3, length 41: LCP, Conf-Request (0x01), id 1, length 27

13:32:30.453504 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 2, ack 3, length 45: LCP, Conf-Ack (0x02), id 1, length 27

13:32:30.453619 IP 10.69.1.21.4742 > 10.69.1.12.1723: P 349:373(24) ack 189 win 65347: pptp CTRL_MSGTYPE=SLI PEER_CALL_ID(1664) SEND_ACCM(0x00000000) RECV_ACCM(0xffffffff)

13:32:30.453646 IP 10.69.1.12.1723 > 10.69.1.21.4742: . ack 373 win 7504

13:32:30.453769 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 3, length 32: LCP, Ident (0x0c), id 2, length 20

13:32:30.453916 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 4, length 35: LCP, Ident (0x0c), id 3, length 23

13:32:30.454201 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 4, ack 4, length 47: CHAP, Challenge (0x01), id 127, Value 1e0154a4d51dfc6e7500238bebb4e70d, Name i-router

13:32:30.454977 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 5, ack 4, length 77: CHAP, Response (0x02), id 127, Value ef94ab6caf577c0ed2bf864e5635c4d60000000000000000b071630077f0681923bd2a5644e84890aff152e2ee05e25700, Name test1

13:32:30.502977 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 5, no-payload, length 12

13:32:30.744750 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 5, length 60: CHAP, Success (0x03), id 127, Msg S=8EA1A729C7542CEC12838244A91D7A7BB2C40EF6

13:32:30.744764 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 6, length 30: IPCP, Conf-Request (0x01), id 1, length 18

13:32:30.758916 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 6, ack 6, length 28: unknown ctrl-proto (0x80fd), Conf-Request (0x01), id 4, length 12

13:32:30.759067 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 7, length 48: IPCP, Conf-Request (0x01), id 5, length 36

13:32:30.759216 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 8, length 24: IPCP, Conf-Reject (0x04), id 1, length 12

13:32:30.759228 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 7, ack 6, length 22: unknown ctrl-proto (0x80fd), Conf-Request (0x01), id 1, length 6

13:32:30.759244 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 8, length 24: unknown ctrl-proto (0x80fd), Conf-Reject (0x04), id 4, length 12

13:32:30.759627 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 9, ack 8, length 22: unknown ctrl-proto (0x80fd), Conf-Ack (0x02), id 1, length 6

13:32:30.759696 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 9, ack 8, length 34: IPCP, Conf-Reject (0x04), id 5, length 18

13:32:30.759705 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 10, length 24: IPCP, Conf-Request (0x01), id 2, length 12

13:32:30.759761 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 10, length 30: unknown ctrl-proto (0x80fd), Term-Request (0x05), id 6, length 18

13:32:30.760056 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 11, ack 10, length 22: unknown ctrl-proto (0x80fd), Term-Ack (0x06), id 6, length 6

13:32:30.760084 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 11, ack 10, length 40: IPCP, Conf-Request (0x01), id 7, length 24

13:32:30.760305 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 12, ack 11, length 40: IPCP, Conf-Nack (0x03), id 7, length 24

13:32:30.760327 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 12, ack 11, length 28: IPCP, Conf-Ack (0x02), id 2, length 12

13:32:30.760647 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 13, ack 12, length 40: IPCP, Conf-Request (0x01), id 8, length 24

13:32:30.761475 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 13, ack 13, length 40: IPCP, Conf-Ack (0x02), id 8, length 24

13:32:30.848280 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, ack 13, no-payload, length 12

13:32:31.024726 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 14, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:31.072904 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 14, no-payload, length 12

13:32:31.418458 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 15, length 53: IP 12.0.0.69 > 224.0.0.22: igmp v3 report, 1 group record(s)

13:32:31.462902 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 15, no-payload, length 12

13:32:31.490754 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 16, length 174: IP 12.0.0.69.4746 > 239.255.255.250.1900: UDP, length 133

13:32:31.532895 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 16, no-payload, length 12

13:32:31.722638 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 17, length 287: IP 12.0.0.69.2046 > 255.255.255.255.2046: UDP, length 246

13:32:31.762897 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 17, no-payload, length 12

13:32:31.767394 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 18, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:31.812897 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 18, no-payload, length 12

13:32:31.927641 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 19, length 298: IP 0.0.0.0 > 192.168.1.1: ip-proto-241 265

13:32:31.929663 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 20, length 298: IP 0.0.0.0 > 212.120.184.82: ip-proto-241 265

13:32:31.972897 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 20, no-payload, length 12

13:32:32.533206 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 21, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:32.582896 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 21, no-payload, length 12

13:32:32.812856 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 22, length 421: IP 12.0.0.69.2045 > 12.0.0.1.2045: UDP, length 380

13:32:32.862899 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 22, no-payload, length 12

13:32:33.267498 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 23, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:33.312896 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 23, no-payload, length 12

13:32:33.763020 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 14, length 18: unknown ctrl-proto (0x80fd), Conf-Request (0x01), id 1, length 6

13:32:33.763487 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 24, ack 14, length 22: unknown ctrl-proto (0x80fd), Term-Ack (0x06), id 1, length 6

13:32:33.763731 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, seq 15, ack 24, length 47: unknown ctrl-proto (0x80fd), Term-Request (0x05), id 2, length 31

13:32:33.764087 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 25, ack 15, length 47: unknown ctrl-proto (0x80fd), Term-Ack (0x06), id 2, length 31

13:32:33.812898 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 25, no-payload, length 12

13:32:34.029711 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 26, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:34.072895 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 26, no-payload, length 12

13:32:34.486503 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 27, length 174: IP 12.0.0.69.4746 > 239.255.255.250.1900: UDP, length 133

13:32:34.532895 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 27, no-payload, length 12

13:32:34.767651 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 28, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:34.812896 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 28, no-payload, length 12

13:32:35.517564 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 29, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:35.562900 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 29, no-payload, length 12

13:32:35.801416 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 30, length 421: IP 12.0.0.69.2045 > 12.0.0.1.2045: UDP, length 380

13:32:35.842895 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 30, no-payload, length 12

13:32:36.267598 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 31, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:36.312896 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 31, no-payload, length 12

13:32:37.066900 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 32, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:37.112897 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 32, no-payload, length 12

13:32:37.486564 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 33, length 174: IP 12.0.0.69.4746 > 239.255.255.250.1900: UDP, length 133

13:32:37.532898 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 33, no-payload, length 12

13:32:37.814470 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 34, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:37.862897 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 34, no-payload, length 12

13:32:38.564617 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 35, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:38.612898 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 35, no-payload, length 12

13:32:38.816011 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 36, length 421: IP 12.0.0.69.2045 > 12.0.0.1.2045: UDP, length 380

13:32:38.862896 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 36, no-payload, length 12

13:32:39.314917 IP 10.69.1.21 > 10.69.1.12: GREv1, call 1664, seq 37, length 109: IP 12.0.0.69.137 > 255.255.255.255.137: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST

13:32:39.362896 IP 10.69.1.12 > 10.69.1.21: GREv1, call 16384, ack 37, no-payload, length 12

и секции [misc] из фала iplir.conf на обоих Координаторах.

Координатор1:

[misc]

packettype= 4.1

timediff= 21600

warnoldautosave=on

client_pollinterval= 300

server_pollinterval= 900

iparponly= off

ifcheck_timeout= 30

Координатор2:

[misc]

packettype= 4.1

timediff= 21600

client_pollinterval= 1440

server_pollinterval= 1440

iparponly= off

ifcheck_timeout= 30

Напомню, что на Клиент1 и Клиент3 установлен ViPNet[Клиент], если это имеет значение

Клиент1 имеет адрес 10.69.101.118

Клиент2 имеет адрес 10.69.101.251

Клиент3 имеет адрес 10.69.1.21

PPTPсервер имеет адрес 10.69.1.12

Share this post


Link to post
Share on other sites

На PPTPсервере,при удачной авторизации, поднимается виртуальный интерфейс 12.0.0.1 может его добавить в туннели на Координаторы 1 и 2 ? Хотя на обоих Координаторах, на локальных интерфейсах установлен 4 режим...

Share this post


Link to post
Share on other sites

Проделал следующий эксперемент:

на обоих координаторах выгрузил (остановил?) драйвер ViPNet командами

watchdog stop

iplir stop

mftp stop

iplir unload

После этого Клиент1 (в 5 режиме) и Клиент2 успешно зарегестрировались на PPTPСервере!

Жду Ваших коментариев

Share this post


Link to post
Share on other sites

В момент, когда Клиент2 подключается к pptp-серверу, нет ли блокированных пакетов на внутреннем интерфейсе Координатора2?

посмотрите журнал ip-пакетов в этот момент.

Share this post


Link to post
Share on other sites

скорее всего, проблема, возникшая у Вас, нам известна. для того, чтобы ее решить, Вам необходимо обратитьсяк Юрию Авраменко и спросить, где можно получить новую версию ПО. Его тел.: 8 (495) 737-61-92

Share this post


Link to post
Share on other sites
скорее всего, проблема, возникшая у Вас, нам известна. для того, чтобы ее решить, Вам необходимо обратитьсяк Юрию Авраменко и спросить, где можно получить новую версию ПО. Его тел.: 8 (495) 737-61-92

Если не секрет, в какой версии (сборки) устранен данный баг?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.