Титла: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Aug 30, 2011, 23:04
Здравейте, Проблема с който се мъча е следният. Смениха ми един тунел от openvpn на pptp. Под виндофсът се свързвам без проблеми (тоест GRE не е блокирано, нямам и защитна стена). Под Линукс немога да вдигна тунела. Ситуацията е следната: dzver ~ #pon bahur debug dump logfd 1 nodetach pppd options in effect: debug # (from command line) nodetach # (from command line) logfd 1 # (from command line) dump # (from command line) noauth # (from /etc/ppp/options.pptp) name mursha # (from /etc/ppp/peers/bahur) remotename mursha # (from /etc/ppp/peers/bahur) # (from /etc/ppp/options.pptp) pty pptp xxx.xxx.xxx.xxx --nolaunchpppd # (from /etc/ppp/peers/bahur) mru 1450 # (from /etc/ppp/options.pptp) mtu 1450 # (from /etc/ppp/options.pptp) lcp-echo-failure 3 # (from /etc/ppp/peers/bahur) lcp-echo-interval 5 # (from /etc/ppp/peers/bahur) nobsdcomp # (from /etc/ppp/options.pptp) nodeflate # (from /etc/ppp/options.pptp) require-mppe-128 # (from /etc/ppp/peers/bahur) using channel 8 Using interface ppp0 Connect: ppp0 <--> /dev/pts/11 sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] sent [LCP ConfReq id=0x1 <mru 1450> <asyncmap 0x0> <magic 0x21d21781> <pcomp> <accomp>] LCP: timeout sending Config-Requests Connection terminated. Modem hangup Waiting for 1 child processes... script pptp xxx.xxx.xxx.xxx --nolaunchpppd, pid 6372 Script pptp xxx.xxx.xxx.xxx --nolaunchpppd finished (pid 6372), status = 0x0
Съдържание на файла /etc/ppp/options.pptp lock mtu 1450 mru 1450 noauth nodeflate nobsdcomp lcp-echo-failure 3 lcp-echo-interval 5
Съдържание на файла /etc/ppp/peers/bahur # written by pptpsetup pty "pptp XXX.XXX.XXX.XXX --nolaunchpppd" lock noauth nobsdcomp nodeflate name mursha remotename mursha require-mppe-128 file /etc/ppp/options.pptp lcp-echo-failure 3 lcp-echo-interval 5
Потребителското име, паролата и името на тунела в chap са ОК Някой да има идея къде бъркам в конфигурацията? Защо сървера не отговаря на LCP съобщенията а всичко друго до този момент е ОК? От същият компютър под ХП вдига тунела без проблем. ЕДИТ: Модулите са: dzver ~ # lsmod Module Size Used by ppp_mppe 5338 0 ppp_async 6379 0 crc_ccitt 1241 1 ppp_async ppp_generic 21409 2 ppp_mppe,ppp_async slhc 5079 1 ppp_generic
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: tolostoi в Aug 30, 2011, 23:17
Какво има в /var/logmasages от това което виждам (но не съм гледал подобен дебъг) изобщо не се стига до опит за хендшейк, да не бъркаш адреса на сервера или да нямаш маршрут до него (пинг имаш ли до сервера)?
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Aug 30, 2011, 23:34
Да имам пинг както и телнет до порт 1723. Под вин работи. Във лога се намира същото което е и на терминала. С tcpdump наблюдавам и ситуацията е следната: започва трансвера вдига ppp връзката споразумява се нещо със сървера, и започва да изпраща LCP съобщенията, обаче сървера не отговаря с нищо. След няколкото проби изпраща терминиращо съобщение, сървера отговаря с ACK пакет и се разпада връзката. Ситуацията е много странна така че грешката е нещо дребно, или пропуск някъкъв. Аз неможах да го открия.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: tolostoi в Aug 31, 2011, 09:41
Взема ли си адрес? Пробвай да промениш или махнеш криптирането, това понеже имам някакъв смътен спомен, че под виндовс криптирането е по-подразбиране на автоматично разпознаване. Другото което се сещам е, ако не си взема адрес, да му кажеш да пробва другите видове, chap, mschap, mschapv2 ...
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: gat3way в Aug 31, 2011, 10:23
Без да е минал LCP и IPCP, няма да си вземе IP адрес :)
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Aug 31, 2011, 19:42
Махнах всички допълнителни настройки, и положението е същото. Защо сървера не отговаря на LCP немога да разбера. Поне да каже нещо че парола или криптиране не му изнася а то мълчание. А адрес естествено няма - не са се споразумели
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: tolostoi в Sep 01, 2011, 10:14
??? Бих пробвал с друга мрежова карта и/или с network-manager-а на гнома, напоследък не съм пускал пптп от конзола.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: 10101 в Sep 01, 2011, 10:57
В syslog-a какво е положението? pppd[7094]: CHAP authentication succeeded Sep 1 10:54:48 kernel: [64119.002443] PPP BSD Compression module registered Sep 1 10:54:48 kernel: [64119.039588] PPP Deflate Compression module registered Sep 1 10:54:48 pppd[7094]: LCP terminated by peer (MPPE required but peer negotiation failed)
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Sep 01, 2011, 20:15
С networkmanager положението е същото. Ще пробвам да изтрия настройките за пиър и чап и ще пробвам пак. В syslog е същото което го дава на екрана, аз не деатачвам процеса. И една "добра" новина е че като стартирам 2 пъти пптп-то вторият път се закачва и имам за 1 минута рутинг до VPN мрежата. След 1 минута го разкачва със следният лог:
Script pptp ххх.ххх.ххх.ххх --nolaunchpppd finished (pid 4109), status = 0x0 Sep 1 03:50:33 dzver pppd[4108]: Modem hangup Sep 1 03:50:33 dzver pppd[4108]: Connect time 1.4 minutes. Sep 1 03:50:33 dzver pppd[4108]: Sent 0 bytes, received 0 bytes. Sep 1 03:50:33 dzver pppd[4108]: Script /etc/ppp/ip-down started (pid 4166) Sep 1 03:50:33 dzver pppd[4108]: MPPE disabled Sep 1 03:50:33 dzver pppd[4108]: sent [LCP TermReq id=0x2 "MPPE disabled"] Sep 1 03:50:33 dzver pppd[4108]: Connection terminated.
Тоест опитва се да дигне ppp0 интерфейс паралелно и ppp1 интерфейса, ppp0 не успява, но ppp1 го вдига успешно със следните съобщения:
Sep 1 03:49:06 dzver pppd[4108]: using channel 8 Sep 1 03:49:06 dzver pppd[4108]: Using interface ppp1 Sep 1 03:49:06 dzver pppd[4108]: Connect: ppp1 <--> /dev/pts/12 Sep 1 03:49:06 dzver modem-manager: (net/ppp1): could not get port's parent device Sep 1 03:49:06 dzver pppd[4108]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <auth chap MS-v2> <magic 0x6786ce0a> <pcomp> <accomp>] Sep 1 03:49:06 dzver pppd[4108]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xb9949ebe> <pcomp>] Sep 1 03:49:06 dzver pppd[4108]: sent [LCP ConfRej id=0x1 <accomp>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xb9949ebe> <pcomp>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [LCP ConfReq id=0x2 <asyncmap 0x0> <auth chap MS-v2> <magic 0x6786ce0a> <pcomp>] Sep 1 03:49:06 dzver pppd[4108]: sent [LCP ConfAck id=0x2 <asyncmap 0x0> <auth chap MS-v2> <magic 0x6786ce0a> <pcomp>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [CHAP Challenge id=0x1 <a91a09d620fef9fb6af014f5d4b5866e>, name = "vpnххх"] Sep 1 03:49:06 dzver pppd[4108]: Warning - secret file /etc/ppp/chap-secrets has world and/or group access Sep 1 03:49:06 dzver pppd[4108]: sent [CHAP Response id=0x1 <ed683c2e6d99b8b97009a4ceb353242100000000000000004b68014d521d2577f69db91b85c4306c38403a6718ff40b200>, name = "xxxxx"] Sep 1 03:49:06 dzver pppd[4108]: rcvd [CHAP Success id=0x1 "S=F2909D930EE721BB69E063D023A429E7AD794DFB"] Sep 1 03:49:06 dzver pppd[4108]: CHAP authentication succeeded Sep 1 03:49:06 dzver pppd[4108]: sent [CCP ConfReq id=0x1 <mppe +H -M +S -L -D -C>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [IPCP ConfReq id=0x1 <addr 10.35.35.1> <compress VJ 0f 01>] Sep 1 03:49:06 dzver pppd[4108]: sent [IPCP TermAck id=0x1] Sep 1 03:49:06 dzver pppd[4108]: rcvd [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <mppe +H -M +S +L -D -C> <bsd v1 15>] Sep 1 03:49:06 dzver pppd[4108]: sent [CCP ConfRej id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [CCP ConfAck id=0x1 <mppe +H -M +S -L -D -C>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [CCP ConfReq id=0x2 <mppe +H -M +S +L -D -C>] Sep 1 03:49:06 dzver pppd[4108]: sent [CCP ConfNak id=0x2 <mppe +H -M +S -L -D -C>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [CCP ConfReq id=0x3 <mppe +H -M +S -L -D -C>] Sep 1 03:49:06 dzver pppd[4108]: sent [CCP ConfAck id=0x3 <mppe +H -M +S -L -D -C>] Sep 1 03:49:06 dzver pppd[4108]: MPPE 128-bit stateless compression enabled Sep 1 03:49:06 dzver pppd[4108]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [IPCP ConfNak id=0x1 <addr 10.35.35.166>] Sep 1 03:49:06 dzver pppd[4108]: sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 10.35.35.166>] Sep 1 03:49:06 dzver pppd[4108]: rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 10.35.35.166>] Sep 1 03:49:09 dzver pppd[4100]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6910bab9> <pcomp>] Sep 1 03:49:09 dzver pppd[4108]: rcvd [IPCP ConfReq id=0x1 <addr 10.35.35.1> <compress VJ 0f 01>] Sep 1 03:49:09 dzver pppd[4108]: sent [IPCP ConfAck id=0x1 <addr 10.35.35.1> <compress VJ 0f 01>] Sep 1 03:49:09 dzver pppd[4108]: local IP address 10.35.35.166 Sep 1 03:49:09 dzver pppd[4108]: remote IP address 10.35.35.1 Sep 1 03:49:09 dzver pppd[4108]: Script /etc/ppp/ip-up started (pid 4110) Sep 1 03:49:09 dzver pppd[4108]: Script /etc/ppp/ip-up finished (pid 4110), status = 0x0
В този случай има връзка до вътрешната мрежа но както описах се разкапва след малко със горните съобщения. Въобще си нямам на идея какво не се споразумяват със сървера та да го дигне от първият път.
ЕДИТ: Опитах и с networkmanager през 2-те IP-та на рутера резултата е същият:
Sep 1 23:25:01 dzver NetworkManager[2374]: <info> Starting VPN service 'pptp'... Sep 1 23:25:01 dzver NetworkManager[2374]: <info> VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 5213 Sep 1 23:25:01 dzver NetworkManager[2374]: <info> VPN service 'pptp' appeared; activating connections Sep 1 23:25:01 dzver NetworkManager[2374]: <info> VPN plugin state changed: 1 Sep 1 23:25:01 dzver NetworkManager[2374]: <info> VPN plugin state changed: 3 Sep 1 23:25:01 dzver NetworkManager[2374]: <info> VPN connection 'IP VPN BTK' (Connect) reply received. Sep 1 23:25:01 dzver pppd[5215]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Sep 1 23:25:01 dzver kernel: [41346.240266] PPP generic driver version 2.4.2 Sep 1 23:25:01 dzver pppd[5215]: pppd 2.4.5 started by root, uid 0 Sep 1 23:25:01 dzver modem-manager: (net/ppp0): could not get port's parent device Sep 1 23:25:01 dzver pppd[5215]: Using interface ppp0 Sep 1 23:25:01 dzver pppd[5215]: Connect: ppp0 <--> /dev/pts/7 Sep 1 23:25:01 dzver pptp[5220]: nm-pptp-service-5213 log[main:pptp.c:310]: The synchronous pptp option is NOT activated Sep 1 23:25:01 dzver pptp[5226]: nm-pptp-service-5213 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Sep 1 23:25:01 dzver pptp[5226]: nm-pptp-service-5213 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Sep 1 23:25:01 dzver pptp[5226]: nm-pptp-service-5213 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Sep 1 23:25:02 dzver pptp[5226]: nm-pptp-service-5213 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Sep 1 23:25:02 dzver pptp[5226]: nm-pptp-service-5213 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Sep 1 23:25:02 dzver pptp[5226]: nm-pptp-service-5213 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 0). Sep 1 23:25:32 dzver pppd[5215]: LCP: timeout sending Config-Requests Sep 1 23:25:32 dzver pppd[5215]: Connection terminated. Sep 1 23:25:32 dzver NetworkManager[2374]: <warn> VPN plugin failed: 1 Sep 1 23:25:32 dzver pppd[5215]: Modem hangup Sep 1 23:25:32 dzver pptp[5220]: nm-pptp-service-5213 warn[decaps_hdlc:pptp_gre.c:204]: short read (-1): Input/output error Sep 1 23:25:32 dzver pptp[5220]: nm-pptp-service-5213 warn[decaps_hdlc:pptp_gre.c:216]: pppd may have shutdown, see pppd log Sep 1 23:25:32 dzver pptp[5226]: nm-pptp-service-5213 log[callmgr_main:pptp_callmgr.c:234]: Closing connection (unhandled) Sep 1 23:25:32 dzver pptp[5226]: nm-pptp-service-5213 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request' Sep 1 23:25:32 dzver pptp[5226]: nm-pptp-service-5213 log[call_callback:pptp_callmgr.c:79]: Closing connection (call state) Sep 1 23:25:32 dzver NetworkManager[2374]: <warn> VPN plugin failed: 1 Sep 1 23:25:32 dzver pppd[5215]: Exit. Sep 1 23:25:32 dzver NetworkManager[2374]: <warn> VPN plugin failed: 1 Sep 1 23:25:32 dzver NetworkManager[2374]: <info> VPN plugin state changed: 6 Sep 1 23:25:32 dzver NetworkManager[2374]: <info> VPN plugin state change reason: 0 Sep 1 23:25:32 dzver NetworkManager[2374]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Sep 1 23:25:32 dzver NetworkManager[2374]: <info> Policy set 'VIVACOM' (eth1) as default for IPv4 routing and DNS. Sep 1 23:25:37 dzver NetworkManager[2374]: <info> VPN service 'pptp' disappeared
Sep 1 23:25:59 dzver NetworkManager[2374]: <info> Starting VPN service 'pptp'... Sep 1 23:25:59 dzver NetworkManager[2374]: <info> VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 5251 Sep 1 23:25:59 dzver NetworkManager[2374]: <info> VPN service 'pptp' appeared; activating connections Sep 1 23:25:59 dzver NetworkManager[2374]: <info> VPN plugin state changed: 3 Sep 1 23:25:59 dzver NetworkManager[2374]: <info> VPN connection 'IP Atlantis' (Connect) reply received. Sep 1 23:25:59 dzver pppd[5252]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Sep 1 23:25:59 dzver pppd[5252]: pppd 2.4.5 started by root, uid 0 Sep 1 23:25:59 dzver pppd[5252]: Using interface ppp0 Sep 1 23:25:59 dzver pppd[5252]: Connect: ppp0 <--> /dev/pts/7 Sep 1 23:25:59 dzver modem-manager: (net/ppp0): could not get port's parent device Sep 1 23:25:59 dzver pptp[5254]: nm-pptp-service-5251 log[main:pptp.c:310]: The synchronous pptp option is NOT activated Sep 1 23:25:59 dzver pptp[5258]: nm-pptp-service-5251 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Sep 1 23:25:59 dzver pptp[5258]: nm-pptp-service-5251 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Sep 1 23:25:59 dzver pptp[5258]: nm-pptp-service-5251 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Sep 1 23:26:00 dzver pptp[5258]: nm-pptp-service-5251 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Sep 1 23:26:00 dzver pptp[5258]: nm-pptp-service-5251 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Sep 1 23:26:00 dzver pptp[5258]: nm-pptp-service-5251 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 0). Sep 1 23:26:30 dzver pppd[5252]: LCP: timeout sending Config-Requests Sep 1 23:26:30 dzver pppd[5252]: Connection terminated. Sep 1 23:26:30 dzver NetworkManager[2374]: <warn> VPN plugin failed: 1 Sep 1 23:26:30 dzver pppd[5252]: Modem hangup Sep 1 23:26:30 dzver pptp[5254]: nm-pptp-service-5251 warn[decaps_hdlc:pptp_gre.c:204]: short read (-1): Input/output error Sep 1 23:26:30 dzver pptp[5254]: nm-pptp-service-5251 warn[decaps_hdlc:pptp_gre.c:216]: pppd may have shutdown, see pppd log Sep 1 23:26:30 dzver pptp[5258]: nm-pptp-service-5251 log[callmgr_main:pptp_callmgr.c:234]: Closing connection (unhandled) Sep 1 23:26:30 dzver pptp[5258]: nm-pptp-service-5251 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request' Sep 1 23:26:30 dzver pptp[5258]: nm-pptp-service-5251 log[call_callback:pptp_callmgr.c:79]: Closing connection (call state) Sep 1 23:26:30 dzver NetworkManager[2374]: <warn> VPN plugin failed: 1 Sep 1 23:26:30 dzver pppd[5252]: Exit. Sep 1 23:26:30 dzver NetworkManager[2374]: <warn> VPN plugin failed: 1 Sep 1 23:26:30 dzver NetworkManager[2374]: <info> VPN plugin state changed: 6 Sep 1 23:26:30 dzver NetworkManager[2374]: <info> VPN plugin state change reason: 0 Sep 1 23:26:30 dzver NetworkManager[2374]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Sep 1 23:26:30 dzver NetworkManager[2374]: <info> Policy set 'VIVACOM' (eth1) as default for IPv4 routing and DNS. Sep 1 23:26:35 dzver NetworkManager[2374]: <info> VPN service 'pptp' disappeared
С другата мрежа която е на микротик на съседни IP адреси на същите доставчици няма проблем и с конзола и с networkmanager-a на КДЕ. Проблема е че не ми дава достъп до необходимата ми вътрешна мрежа през микротика.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: tolostoi в Sep 01, 2011, 22:52
Стрелям в тъмното, но в момента не съм в състояние да мисля :) Да не би ... сервера да прави проверка по мак адрес, а пък под windows да ти е друг мак-а (случва се)?
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Sep 02, 2011, 00:05
Компютъра е един и същи лан картата също, минавам през 10-ина рутера. wireshark също не подсказва нищо. Като стартирам 2 пъти конекцията един след друг (без да изчакам да свърши първата) връзката се вдига, само че като свърши първата понеже не е осъществена гаси pppd и по този начин гаси и втората връзка която е осъществена. Имаше един начин да извикам pppd и в последствие pptp от конзола, но немога да намеря как се прави. Така не става мисля че нещо бъркам в синтаксиса
pppd noauth nobsdcomp nodeflate mppe-40mppe-128 mppe-stateless name domain\\\\username remotename PPTP require-chapms-v2 pty "pptp 10.0.0.5 --nolaunchpppd"
А ми се иска да ги стартирам по отделно първо pppd после pptp и ако трябва да го повторя
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: 10101 в Sep 02, 2011, 08:44
"С другата мрежа която е на микротик на съседни IP адреси на същите доставчици няма проблем и с конзола и с networkmanager-a на КДЕ. Проблема е че не ми дава достъп до необходимата ми вътрешна мрежа през микротика."
NAT? gre през нат е сложничко.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Sep 02, 2011, 10:53
Ната през който минава е един и същи. Под виндовс работи под линукс само като изключения, което ме навежда на единственната възможна мисъл че аз съм оцапал нещо по конфигурациите. Освен да пускам една виндовс машина да ме рутира в къщи (доста неестествено звучи) ??? >:(
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: Ipolit в Sep 02, 2011, 11:30
в options.pptp сложи едно nodefaultroute може би затова се разпада, щото почва да се мъчи да ти прекара целия интернет през VPN-а Освен това моите наблюдения са, че автоматично не се получават маршрутите. Затова ако мрежата, към която се свързваш е различна от 10.35.35.0/24 трябва да си я добавиш в /etc/ppp/ip-up ip ro add xxx.xxx.xxx.xxx/xx via 10.35.35.1 Също така, ако се използва някакъв ДНС сървър от тунела, линуксите не искат да го вземат - до сега съм виждал да работи с ХП и МАК ОС, но не и с линукс и Уин 7, тъй че трябва да си добавиш и ДНС-а - може пак в /etc/ppp/ip-up
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Sep 02, 2011, 13:44
За nodefaultroute ще го пробвам, въпреки че не стигам по нормалният път до вдигане на ppp интерфейса. DNS не ползвам от VPN-а. По принцип рутинга не го вземам от сървера вдигам си го сам. Бих заложил обаче на NAT по между дома и този рутер се оказват 2 натвания mtr използвах да проверя за загуби и ги видях. На работа със същата конфигурация но на директна връзка със сървера се вдига от раз ppp интерфейса.
Някакви идеи за настройките за NAT (нещо което да го има при Вин но при Линукс да се указва допълнително)
Вариянт 2 - до рутера са 10 хопа има загуба от 1-2% на пакетите. Дали това не влияе.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: tolostoi в Sep 02, 2011, 14:46
Когато има проблем с мту-то (поне в случаите които съм виждал) се проявява след конекцията, слага се едно правило iptables и се решава проблема, но ти изобщо не се закачаш, според мен, нещо от сървъра те рита, за това ти казах и да провериш хв адреса (виждал съм една и съща мрежова карта с различен мак адрес под линукс и виндовс) Ако искаш пробвай с това правило преди да вдигнеш тунела, но едва ли: iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu btw По-правилно е да се изпълни в mangle веригата.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Sep 02, 2011, 21:51
Не става с правилата в таблицата. Ето малко сниф с wireshark Под линукс - не вървящата връзка: No. Time Source Destination Protocol Info 1 0.000000 192.168.1.10 REMOTE_IP TCP 34553 > pptp [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1 TSV=13430644 TSER=0 WS=6
Frame 1: 74 bytes on wire (592 bits), 74 bytes captured (592 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: 34553 (34553), Dst Port: pptp (1723), Seq: 0, Len: 0 Source port: 34553 (34553) Destination port: pptp (1723) [Stream index: 0] Sequence number: 0 (relative sequence number) Header length: 40 bytes Flags: 0x02 (SYN) Window size: 14600 Checksum: 0xc543 [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (20 bytes)
No. Time Source Destination Protocol Info 2 0.029074 REMOTE_IP 192.168.1.10 TCP pptp > 34553 [SYN, ACK] Seq=0 Ack=1 Win=31944 Len=0 MSS=1452 SACK_PERM=1 TSV=235056215 TSER=13430644 WS=0
Frame 2: 74 bytes on wire (592 bits), 74 bytes captured (592 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: 34553 (34553), Seq: 0, Ack: 1, Len: 0 Source port: pptp (1723) Destination port: 34553 (34553) [Stream index: 0] Sequence number: 0 (relative sequence number) Acknowledgement number: 1 (relative ack number) Header length: 40 bytes Flags: 0x12 (SYN, ACK) Window size: 31944 Checksum: 0xd965 [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (20 bytes) [SEQ/ACK analysis]
No. Time Source Destination Protocol Info 3 0.029118 192.168.1.10 REMOTE_IP TCP 34553 > pptp [ACK] Seq=1 Ack=1 Win=14656 Len=0 TSV=13430674 TSER=235056215
Frame 3: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: 34553 (34553), Dst Port: pptp (1723), Seq: 1, Ack: 1, Len: 0 Source port: 34553 (34553) Destination port: pptp (1723) [Stream index: 0] Sequence number: 1 (relative sequence number) Acknowledgement number: 1 (relative ack number) Header length: 32 bytes Flags: 0x10 (ACK) Window size: 14656 (scaled) Checksum: 0xc53b [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis]
No. Time Source Destination Protocol Info 4 0.029547 192.168.1.10 REMOTE_IP PPTP Start-Control-Connection-Request
Frame 4: 222 bytes on wire (1776 bits), 222 bytes captured (1776 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: 34553 (34553), Dst Port: pptp (1723), Seq: 1, Ack: 1, Len: 156 Source port: 34553 (34553) Destination port: pptp (1723) [Stream index: 0] Sequence number: 1 (relative sequence number) [Next sequence number: 157 (relative sequence number)] Acknowledgement number: 1 (relative ack number) Header length: 32 bytes Flags: 0x18 (PSH, ACK) Window size: 14656 (scaled) Checksum: 0xc5d7 [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis] Point-to-Point Tunnelling Protocol Length: 156 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Start-Control-Connection-Request (1) Reserved: 0 Protocol version: 1.0 Reserved: 0 Framing capabilities: Either Framing supported (3) Bearer capabilities: Either access supported (3) Maximum channels: 65535 Firmware revision: 1 Hostname: local Vendor: cananian
No. Time Source Destination Protocol Info 5 0.080712 REMOTE_IP 192.168.1.10 TCP pptp > 34553 [ACK] Seq=1 Ack=157 Win=31944 Len=0 TSV=235056220 TSER=13430674
Frame 5: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: 34553 (34553), Seq: 1, Ack: 157, Len: 0 Source port: pptp (1723) Destination port: 34553 (34553) [Stream index: 0] Sequence number: 1 (relative sequence number) Acknowledgement number: 157 (relative ack number) Header length: 32 bytes Flags: 0x10 (ACK) Window size: 31944 Checksum: 0x0764 [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis]
No. Time Source Destination Protocol Info 6 0.084226 REMOTE_IP 192.168.1.10 PPTP Start-Control-Connection-Reply
Frame 6: 222 bytes on wire (1776 bits), 222 bytes captured (1776 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: 34553 (34553), Seq: 1, Ack: 157, Len: 156 Source port: pptp (1723) Destination port: 34553 (34553) [Stream index: 0] Sequence number: 1 (relative sequence number) [Next sequence number: 157 (relative sequence number)] Acknowledgement number: 157 (relative ack number) Header length: 32 bytes Flags: 0x18 (PSH, ACK) Window size: 31944 Checksum: 0x6dd5 [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis] Point-to-Point Tunnelling Protocol Length: 156 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Start-Control-Connection-Reply (2) Reserved: 0 Protocol version: 1.0 Result: Successful channel establishment (1) Error: None (0) Framing capabilities: Unknown framing type (0) Bearer capabilities: Unknown bearer type (0) Maximum channels: 1 Firmware revision: 1 Hostname: local Vendor: MoretonBay
No. Time Source Destination Protocol Info 7 0.084252 192.168.1.10 REMOTE_IP TCP 34553 > pptp [ACK] Seq=157 Ack=157 Win=15680 Len=0 TSV=13430729 TSER=235056220
Frame 7: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: 34553 (34553), Dst Port: pptp (1723), Seq: 157, Ack: 157, Len: 0 Source port: 34553 (34553) Destination port: pptp (1723) [Stream index: 0] Sequence number: 157 (relative sequence number) Acknowledgement number: 157 (relative ack number) Header length: 32 bytes Flags: 0x10 (ACK) Window size: 15680 (scaled) Checksum: 0xc53b [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis]
No. Time Source Destination Protocol Info 8 1.029829 192.168.1.10 REMOTE_IP PPTP Outgoing-Call-Request
Frame 8: 234 bytes on wire (1872 bits), 234 bytes captured (1872 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: 34553 (34553), Dst Port: pptp (1723), Seq: 157, Ack: 157, Len: 168 Source port: 34553 (34553) Destination port: pptp (1723) [Stream index: 0] Sequence number: 157 (relative sequence number) [Next sequence number: 325 (relative sequence number)] Acknowledgement number: 157 (relative ack number) Header length: 32 bytes Flags: 0x18 (PSH, ACK) Window size: 15680 (scaled) Checksum: 0xc5e3 [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis] Point-to-Point Tunnelling Protocol Length: 168 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Outgoing-Call-Request (7) Reserved: 0 Call ID: 0 Call Serial Number: 0 Minimum BPS: 2400 Maximum BPS: 10000000 Bearer capabilities: Either access supported (3) Framing capabilities: Either Framing supported (3) Receive window size: 3 Processing delay: 0 Phone number length: 0 Reserved: 0 Phone number: Subaddress:
No. Time Source Destination Protocol Info 9 1.063898 REMOTE_IP 192.168.1.10 PPTP Outgoing-Call-Reply
Frame 9: 98 bytes on wire (784 bits), 98 bytes captured (784 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: 34553 (34553), Seq: 157, Ack: 325, Len: 32 Source port: pptp (1723) Destination port: 34553 (34553) [Stream index: 0] Sequence number: 157 (relative sequence number) [Next sequence number: 189 (relative sequence number)] Acknowledgement number: 325 (relative ack number) Header length: 32 bytes Flags: 0x18 (PSH, ACK) Window size: 31944 Checksum: 0x12d4 [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis] Point-to-Point Tunnelling Protocol Length: 32 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Outgoing-Call-Reply (8) Reserved: 0 Call ID: 0 Peer's call ID: 0 Result: Connected (1) Error: None (0) Cause code: 0 Connect speed: 10000000 Receive window size: 32 Processing delay: 0 Physical channel ID: 0
No. Time Source Destination Protocol Info 10 1.063922 192.168.1.10 REMOTE_IP TCP 34553 > pptp [ACK] Seq=325 Ack=189 Win=15680 Len=0 TSV=13431708 TSER=235056318
Frame 10: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: 34553 (34553), Dst Port: pptp (1723), Seq: 325, Ack: 189, Len: 0 Source port: 34553 (34553) Destination port: pptp (1723) [Stream index: 0] Sequence number: 325 (relative sequence number) Acknowledgement number: 189 (relative ack number) Header length: 32 bytes Flags: 0x10 (ACK) Window size: 15680 (scaled) Checksum: 0xc53b [validation disabled] [Good Checksum: False] [Bad Checksum: False] Options: (12 bytes) [SEQ/ACK analysis]
No. Time Source Destination Protocol Info 11 1.064100 192.168.1.10 REMOTE_IP PPP LCP Configuration Request
Frame 11: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Generic Routing Encapsulation (PPP) Point-to-Point Protocol PPP Link Control Protocol
No. Time Source Destination Protocol Info 12 3.997712 192.168.1.10 REMOTE_IP PPP LCP Configuration Request
Frame 12: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Generic Routing Encapsulation (PPP) Point-to-Point Protocol PPP Link Control Protocol
И така до края на връзката без отговор от сървера
Под Windows вървящата връзка: No. Time Source Destination Protocol Info 1 0.000000 192.168.1.10 REMOTE_IP TCP rkb-oscs > pptp [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1
Frame 1: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: rkb-oscs (1817), Dst Port: pptp (1723), Seq: 0, Len: 0
No. Time Source Destination Protocol Info 2 0.047890 REMOTE_IP 192.168.1.10 TCP pptp > rkb-oscs [SYN, ACK] Seq=0 Ack=1 Win=31944 Len=0 MSS=1452 SACK_PERM=1
Frame 2: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: rkb-oscs (1817), Seq: 0, Ack: 1, Len: 0
No. Time Source Destination Protocol Info 3 0.047999 192.168.1.10 REMOTE_IP PPTP Start-Control-Connection-Request
Frame 3: 210 bytes on wire (1680 bits), 210 bytes captured (1680 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: rkb-oscs (1817), Dst Port: pptp (1723), Seq: 1, Ack: 1, Len: 156 Point-to-Point Tunnelling Protocol Length: 156 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Start-Control-Connection-Request (1) Reserved: 0 Protocol version: 1.0 Reserved: 0 Framing capabilities: Asynchronous Framing supported (1) Bearer capabilities: Analog access supported (1) Maximum channels: 0 Firmware revision: 2600 Hostname: Vendor: Microsoft Windows NT
No. Time Source Destination Protocol Info 4 0.074975 REMOTE_IP 192.168.1.10 TCP pptp > rkb-oscs [ACK] Seq=1 Ack=157 Win=31944 Len=0
Frame 4: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: rkb-oscs (1817), Seq: 1, Ack: 157, Len: 0
No. Time Source Destination Protocol Info 5 0.080788 REMOTE_IP 192.168.1.10 PPTP Start-Control-Connection-Reply
Frame 5: 210 bytes on wire (1680 bits), 210 bytes captured (1680 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: rkb-oscs (1817), Seq: 1, Ack: 157, Len: 156 Point-to-Point Tunnelling Protocol Length: 156 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Start-Control-Connection-Reply (2) Reserved: 0 Protocol version: 1.0 Result: Successful channel establishment (1) Error: None (0) Framing capabilities: Unknown framing type (0) Bearer capabilities: Unknown bearer type (0) Maximum channels: 1 Firmware revision: 1 Hostname: local Vendor: MoretonBay
No. Time Source Destination Protocol Info 6 0.080852 192.168.1.10 REMOTE_IP PPTP Outgoing-Call-Request
Frame 6: 222 bytes on wire (1776 bits), 222 bytes captured (1776 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: rkb-oscs (1817), Dst Port: pptp (1723), Seq: 157, Ack: 157, Len: 168 Point-to-Point Tunnelling Protocol Length: 168 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Outgoing-Call-Request (7) Reserved: 0 Call ID: 32768 Call Serial Number: 26637 Minimum BPS: 300 Maximum BPS: 100000000 Bearer capabilities: Either access supported (3) Framing capabilities: Either Framing supported (3) Receive window size: 64 Processing delay: 0 Phone number length: 0 Reserved: 0 Phone number: Subaddress:
No. Time Source Destination Protocol Info 7 0.114447 REMOTE_IP 192.168.1.10 PPTP Outgoing-Call-Reply
Frame 7: 86 bytes on wire (688 bits), 86 bytes captured (688 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Transmission Control Protocol, Src Port: pptp (1723), Dst Port: rkb-oscs (1817), Seq: 157, Ack: 325, Len: 32 Point-to-Point Tunnelling Protocol Length: 32 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Outgoing-Call-Reply (8) Reserved: 0 Call ID: 0 Peer's call ID: 32768 Result: Connected (1) Error: None (0) Cause code: 0 Connect speed: 100000000 Receive window size: 32 Processing delay: 0 Physical channel ID: 0
No. Time Source Destination Protocol Info 8 0.120118 192.168.1.10 REMOTE_IP PPTP Set-Link-Info
Frame 8: 78 bytes on wire (624 bits), 78 bytes captured (624 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Transmission Control Protocol, Src Port: rkb-oscs (1817), Dst Port: pptp (1723), Seq: 325, Ack: 189, Len: 24 Point-to-Point Tunnelling Protocol Length: 24 Message type: Control Message (1) Cookie: 0x1a2b3c4d (correct) Control type: Set-Link-Info (15) Reserved: 0 Peer's call ID: 0 Reserved: 0 Send ACCM: 0xffffffff Recv ACCM: 0xffffffff
No. Time Source Destination Protocol Info 9 0.122705 192.168.1.10 REMOTE_IP PPP LCP Configuration Request
Frame 9: 71 bytes on wire (568 bits), 71 bytes captured (568 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Generic Routing Encapsulation (PPP) Point-to-Point Protocol PPP Link Control Protocol
No. Time Source Destination Protocol Info 10 0.128734 REMOTE_IP 192.168.1.10 PPP LCP Configuration Request
Frame 10: 79 bytes on wire (632 bits), 79 bytes captured (632 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Generic Routing Encapsulation (PPP) Point-to-Point Protocol PPP Link Control Protocol
No. Time Source Destination Protocol Info 11 0.129017 192.168.1.10 REMOTE_IP PPP LCP Configuration Ack
Frame 11: 79 bytes on wire (632 bits), 79 bytes captured (632 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Generic Routing Encapsulation (PPP) Point-to-Point Protocol PPP Link Control Protocol
No. Time Source Destination Protocol Info 12 0.148428 REMOTE_IP 192.168.1.10 GRE Encapsulated PPP
Frame 12: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Generic Routing Encapsulation (PPP)
No. Time Source Destination Protocol Info 13 0.149707 REMOTE_IP 192.168.1.10 PPP LCP Configuration Reject
Frame 13: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Generic Routing Encapsulation (PPP) Point-to-Point Protocol PPP Link Control Protocol
No. Time Source Destination Protocol Info 14 0.150069 192.168.1.10 REMOTE_IP PPP LCP Configuration Request
Frame 14: 72 bytes on wire (576 bits), 72 bytes captured (576 bits) Ethernet II, Src: Wiltron_00:62:c4 (00:e0:a0:00:62:c4), Dst: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0) Internet Protocol, Src: 192.168.1.10 (192.168.1.10), Dst: REMOTE_IP (REMOTE_IP) Generic Routing Encapsulation (PPP) Point-to-Point Protocol PPP Link Control Protocol
No. Time Source Destination Protocol Info 15 0.157391 REMOTE_IP 192.168.1.10 GRE Encapsulated PPP
Frame 15: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) Ethernet II, Src: PirelliB_b0:17:f0 (38:22:9d:b0:17:f0), Dst: Wiltron_00:62:c4 (00:e0:a0:00:62:c4) Internet Protocol, Src: REMOTE_IP (REMOTE_IP), Dst: 192.168.1.10 (192.168.1.10) Generic Routing Encapsulation (PPP)
И така нататъка връзката се осъществява
Някой ако му разбира на тази боза да свирка какво съм омазал в настройките едит: Да неби сървера да не иска да работи с толкова високи портове на които ми излиза трафика.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: 10101 в Sep 03, 2011, 08:55
Не се заблуждавайте, MAC - адресите нямат нищо общо. Според мен е NAT, дано не се окажа прав.
Титла: Re: PPTP клиент не се свързва под линукс
Публикувано от: victim70 в Sep 03, 2011, 20:47
Вероятно е нат но и под вин е същият нат. Проблема е че нямам контрол на връзката за да видя какво не му харесва. Сисадмина е хипер претоварен наистина. Няма време да обърне внимание а и не искам да го тормозя с 'дреболии'.
ЕДИТ: Писах в поста на пптп - да видим.
|