1. Конфига ppp пакета.
unit 1
defaultroute
#usepeerdns
mtu 1500# Пытаться восстановить соединение при разрыве
persistremotename PPTP
# Вывод сообщений об ошибках (DEBUG MODE)
#debug# Имя пользователя для VPN из файла /etc/ppp/chap-secrets
user iron
noauth
pty "pptp 10.200.145.75 --nolaunchpppd"# Отключение BSD компрессии
nobsdcomprequire-mppe
maxfail 0
nodeflate
-----------------------------------------------------------
2. Автостарт сей впнки предполагается при поднятии физического интерфейса eth1. Реализовано через ip-up.d.
3. После перезагрузки сессия поднимается и висит, но трафик не идет нивкакую. Единственный выход-после загрузки всего руками оборвать ее и снова включить. Тогда все работает и трафик через нее идет.
Вот что пишется в лог:
Mar 16 20:31:02 ironnet pptp[2342]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request'
Mar 16 20:31:02 ironnet pptp[2342]: anon log[ctrlp_disp:pptp_ctrl.c:738]: Received Start Control Connection Reply
Mar 16 20:31:02 ironnet pptp[2342]: anon log[ctrlp_disp:pptp_ctrl.c:772]: Client connection established.
Mar 16 20:31:02 ironnet kernel: eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
Mar 16 20:31:02 ironnet kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Mar 16 20:31:02 ironnet kernel: eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Mar 16 20:31:02 ironnet kernel: CSLIP: code copyright 1989 Regents of the University of California
Mar 16 20:31:02 ironnet kernel: PPP generic driver version 2.4.2
Mar 16 20:31:02 ironnet kernel: NET: Registered protocol family 10
Mar 16 20:31:02 ironnet kernel: lo: Disabled Privacy Extensions
Mar 16 20:31:02 ironnet kernel: IPv6 over IPv4 tunneling driver
Mar 16 20:31:03 ironnet pptp[2342]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request'
Mar 16 20:31:03 ironnet pptp[2342]: anon log[ctrlp_disp:pptp_ctrl.c:857]: Received Outgoing Call Reply.
Mar 16 20:31:03 ironnet pptp[2342]: anon log[ctrlp_disp:pptp_ctrl.c:896]: Outgoing call established (call ID 0, peer's call ID 1408).
Mar 16 20:31:04 ironnet pppd[2103]: CHAP authentication succeeded
Mar 16 20:31:04 ironnet kernel: PPP MPPE Compression module registered
Mar 16 20:31:04 ironnet pppd[2103]: MPPE 128-bit stateless compression enabled
Mar 16 20:31:04 ironnet pppd[2103]: not replacing existing default route via 10.221.24.1
Mar 16 20:31:04 ironnet pppd[2103]: local IP address 192.168.1.201
Mar 16 20:31:04 ironnet pppd[2103]: remote IP address 192.168.1.1
Mar 16 20:31:09 ironnet kernel: eth1: no IPv6 routers present
Mar 16 20:31:09 ironnet kernel: eth2: no IPv6 routers present
Mar 16 20:31:10 ironnet kernel: eth0: no IPv6 routers present
Mar 16 20:32:04 ironnet pptp[2342]: anon log[logecho:pptp_ctrl.c:676]: Echo Request received.
Mar 16 20:32:04 ironnet pptp[2342]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 6 'Echo-Reply'
Mar 16 20:32:31 ironnet kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Mar 16 20:32:31 ironnet kernel: Netfilter messages via NETLINK v0.30.
Mar 16 20:32:31 ironnet kernel: ip_conntrack version 2.4 (4095 buckets, 32760 max) - 224 bytes per conntrack
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x48c3
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x9b
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x8a3e
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xa1
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x17
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xc882
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 'Vendor-Specific Network Protocol' (0x5b)
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xe817
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x3cc3
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x5
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x87
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x2c97
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x77
Mar 16 20:32:33 ironnet kernel: Bridge firewalling registered
Mar 16 20:32:33 ironnet kernel: eth0: Promiscuous mode enabled.
Mar 16 20:32:33 ironnet kernel: device eth0 entered promiscuous mode
Mar 16 20:32:33 ironnet kernel: eth2: Promiscuous mode enabled.
Mar 16 20:32:33 ironnet kernel: device eth2 entered promiscuous mode
Mar 16 20:32:33 ironnet kernel: bridge: port 2(eth2) entering learning state
Mar 16 20:32:33 ironnet kernel: bridge: port 1(eth0) entering learning state
Mar 16 20:32:33 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x38b3
Mar 16 20:32:35 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x1eb1
Mar 16 20:32:35 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xdcd5
Mar 16 20:32:35 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xa848
Mar 16 20:32:35 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x81
Mar 16 20:32:35 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 'Multi-Link' (0x3d)
Mar 16 20:32:37 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x2414
Mar 16 20:32:37 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xaee8
Mar 16 20:32:37 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 'Encryption' (0x53)
Mar 16 20:32:41 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xad
Mar 16 20:32:41 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x7b
Mar 16 20:32:41 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x1f
Mar 16 20:32:42 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xea4
Mar 16 20:32:43 ironnet kernel: bridge: no IPv6 routers present
Mar 16 20:32:47 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x3
Mar 16 20:32:47 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xe3
Mar 16 20:32:47 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x79
Mar 16 20:32:48 ironnet kernel: bridge: topology change detected, propagating
Mar 16 20:32:48 ironnet kernel: bridge: port 2(eth2) entering forwarding state
Mar 16 20:32:48 ironnet kernel: bridge: topology change detected, propagating
Mar 16 20:32:48 ironnet kernel: bridge: port 1(eth0) entering forwarding state
Mar 16 20:32:50 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xca7
Mar 16 20:32:51 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xb
Mar 16 20:32:53 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xb5
Mar 16 20:32:54 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x90aa
Mar 16 20:32:55 ironnet pptp[2342]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:32:55 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xd3
Mar 16 20:32:55 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x3
Mar 16 20:32:59 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x8ee2
Mar 16 20:33:00 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x5f
Mar 16 20:33:05 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x9ed2
Mar 16 20:33:05 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 'Serial Data Transport Protocol (PPP-SDTP)' (0x49)
Mar 16 20:33:05 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x71
Mar 16 20:33:07 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x5676
Mar 16 20:33:12 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 'Encryption' (0x53)
Mar 16 20:33:16 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xc5
Mar 16 20:33:17 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x37
Mar 16 20:33:17 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x19
Mar 16 20:33:17 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x93
Mar 16 20:33:19 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0xf5
Mar 16 20:33:21 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 'RTP IPHC Compressed non-TCP' (0x65)
Mar 16 20:33:22 ironnet pppd[2103]: Protocol-Reject for unsupported protocol 0x8e4d
# здесь ручное убивание соединения
Mar 16 20:33:25 ironnet pppd[2103]: Terminating on signal 15
Mar 16 20:33:25 ironnet pppd[2103]: Connect time 2.4 minutes.
Mar 16 20:33:25 ironnet pppd[2103]: Sent 144352175 bytes, received 0 bytes.
Mar 16 20:33:25 ironnet pptp[2342]: anon log[callmgr_main:pptp_callmgr.c:255]: Closing connection (shutdown)
Mar 16 20:33:25 ironnet pptp[2342]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request'
Mar 16 20:33:25 ironnet pptp[2342]: anon log[call_callback:pptp_callmgr.c:78]: Closing connection (call state)
Mar 16 20:33:25 ironnet pppd[2103]: MPPE disabled
Mar 16 20:33:25 ironnet pppd[2103]: Modem hangup
Mar 16 20:33:25 ironnet pppd[2103]: Connection terminated.
Mar 16 20:33:25 ironnet pppd[2103]: Exit.
# и ручное поднимание
Mar 16 20:33:27 ironnet pppd[3238]: pppd 2.4.4 started by root, uid 0
Mar 16 20:33:27 ironnet pptp[3239]: anon log[main:pptp.c:267]: The synchronous pptp option is NOT activated
Mar 16 20:33:27 ironnet pppd[3238]: Using interface ppp1
Mar 16 20:33:27 ironnet pppd[3238]: Connect: ppp1 <--> /dev/pts/0
Mar 16 20:33:27 ironnet pptp[3243]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request'
Mar 16 20:33:27 ironnet pptp[3243]: anon log[ctrlp_disp:pptp_ctrl.c:738]: Received Start Control Connection Reply
Mar 16 20:33:27 ironnet pptp[3243]: anon log[ctrlp_disp:pptp_ctrl.c:772]: Client connection established.
Mar 16 20:33:28 ironnet pptp[3243]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request'
Mar 16 20:33:28 ironnet pptp[3243]: anon log[ctrlp_disp:pptp_ctrl.c:857]: Received Outgoing Call Reply.
Mar 16 20:33:28 ironnet pptp[3243]: anon log[ctrlp_disp:pptp_ctrl.c:896]: Outgoing call established (call ID 0, peer's call ID 1536).
Mar 16 20:33:28 ironnet pppd[3238]: CHAP authentication succeeded
Mar 16 20:33:28 ironnet pppd[3238]: MPPE 128-bit stateless compression enabled
Mar 16 20:33:28 ironnet pppd[3238]: local IP address 192.168.1.201
Mar 16 20:33:28 ironnet pppd[3238]: remote IP address 192.168.1.1
Mar 16 20:34:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:35:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:36:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:37:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:38:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:39:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:40:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:41:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:42:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:43:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
Mar 16 20:43:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:678]: no more Echo Reply/Request packets will be reported.
И все работает как часы.
4. Есть возможность изменить конфиг впн-сервера. Я так понимаю, трабла в шифровании или в чем-то подобном. По крайней мере, раньше другая впнка с точь-в-точь такими же параметрами кроме параметра require-mppe работала сразу и счастливо.Вопрос: что сделать для корректного поднятия впн туннеля?
>[оверквотинг удален]
>Mar 16 20:43:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received.
>Mar 16 20:43:28 ironnet pptp[3243]: anon log[logecho:pptp_ctrl.c:678]: no more Echo Reply/Request packets
>will be reported.
>И все работает как часы.
>4. Есть возможность изменить конфиг впн-сервера. Я так понимаю, трабла в шифровании
>или в чем-то подобном. По крайней мере, раньше другая впнка с
>точь-в-точь такими же параметрами кроме параметра require-mppe работала сразу и счастливо.
>
>
>Вопрос: что сделать для корректного поднятия впн туннеля?все очень просто - вы скорее всего подымаете vpn до того как загрузяться модули ядра для его поддержки - или вкомпелите все нужно в ядро или стратуйте vpn только после того как загрузяться модули.
Оченно извиняюсь, в первом посте описка... не ip-up.d, а post-up.
>стратуйте vpn только после того как загрузяться модули.Как например, есть варианты? sleep в post-up?
Решено.
mtu 1372
mru 1372