Nie jesteś zalogowany. Proszę się zalogować lub zarejestrować.
eko.one.pl → Oprogramowanie / Software → Problem z vpn pptp
Strony 1
Zaloguj się lub zarejestruj by napisać odpowiedź
Witam.
Mam problem z pptp. Dodałem plugin do gargoyle by obsy (najnowsza wersja) skonfigurowałem serwer, login i hasło - zatwierdziłem zmiany i klient się połączył, dostałem adres.
Ale dostęp do internetu (i bramy vpn) jest tylko kilka(naście) sekund po połączeniu, następnie zanika - a połączenie w panelu widoczne jest jako aktywne i faktycznie interfejs jest podniesiony.
Miał ktoś może podobny przypadek ?
Logi patrz.
A jak moge zobaczyc logi pptp?
Musze wlaczac jakies bardziej szczegółowe?
Jeśli tak to jak?
logread. Wszystkie są razem.
Jan 9 21:37:54 HomeNet daemon.info dhcpd: DHCPREQUEST for 192.168.0.2 from bc:ee:7b:48:58:8d via eth1: unknown lease 192.168.0.2.
Jan 9 21:38:06 HomeNet daemon.info dhcpd: DHCPINFORM from 192.168.0.10 via eth1
Jan 9 21:38:06 HomeNet daemon.info dhcpd: DHCPACK to 192.168.0.10 (84:2b:2b:a3:ae:29) via eth1
Jan 9 21:40:03 HomeNet cron.info crond[5861]: crond: crond (busybox 1.19.4) started, log level 7
Jan 9 21:40:03 HomeNet local5.notice qosmon[5069]: terminated sigterm=15, sel_err=-1
Jan 9 21:40:04 HomeNet daemon.info dnsmasq[1827]: exiting on receipt of SIGTERM
Jan 9 21:40:04 HomeNet kern.info kernel: [ 435.540000] device wlan0 left promiscuous mode
Jan 9 21:40:04 HomeNet kern.info kernel: [ 435.540000] br-lan: port 2(wlan0) entered disabled state
Jan 9 21:40:07 HomeNet kern.info kernel: [ 438.470000] eth1: link down
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.920000] br-lan: port 1(eth0) entered disabled state
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.930000] device eth0 left promiscuous mode
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.930000] br-lan: port 1(eth0) entered disabled state
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.950000] eth0: link down
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.950000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.960000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.970000] device eth0 entered promiscuous mode
Jan 9 21:40:08 HomeNet kern.info kernel: [ 438.970000] ADDRCONF(NETDEV_UP): br-lan: link is not ready
Jan 9 21:40:08 HomeNet daemon.notice netifd: Interface 'lan' is now up
Jan 9 21:40:08 HomeNet daemon.notice netifd: Interface 'loopback' is now up
Jan 9 21:40:08 HomeNet daemon.notice netifd: Interface 'wan' is now up
Jan 9 21:40:08 HomeNet kern.info kernel: [ 439.000000] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jan 9 21:40:08 HomeNet user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Jan 9 21:40:08 HomeNet kern.debug kernel: [ 439.470000] ar71xx: pll_reg 0xb8050018: 0x13000a44
Jan 9 21:40:08 HomeNet kern.info kernel: [ 439.470000] eth1: link up (100Mbps/Full duplex)
Jan 9 21:40:08 HomeNet kern.info kernel: [ 439.470000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jan 9 21:40:09 HomeNet kern.debug kernel: [ 440.470000] ar71xx: pll_reg 0xb8050014: 0x13000a44
Jan 9 21:40:09 HomeNet kern.info kernel: [ 440.470000] eth0: link up (100Mbps/Full duplex)
Jan 9 21:40:09 HomeNet kern.info kernel: [ 440.470000] br-lan: port 1(eth0) entered forwarding state
Jan 9 21:40:09 HomeNet kern.info kernel: [ 440.480000] br-lan: port 1(eth0) entered forwarding state
Jan 9 21:40:09 HomeNet kern.info kernel: [ 440.480000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan 9 21:40:09 HomeNet kern.info kernel: [ 440.490000] ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Jan 9 21:40:11 HomeNet kern.info kernel: [ 442.480000] br-lan: port 1(eth0) entered forwarding state
Jan 9 21:40:12 HomeNet kern.info kernel: [ 443.490000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 9 21:40:12 HomeNet kern.info kernel: [ 443.510000] device wlan0 entered promiscuous mode
Jan 9 21:40:12 HomeNet kern.info kernel: [ 443.530000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 9 21:40:13 HomeNet kern.info kernel: [ 443.850000] br-lan: port 2(wlan0) entered forwarding state
Jan 9 21:40:13 HomeNet kern.info kernel: [ 443.850000] br-lan: port 2(wlan0) entered forwarding state
Jan 9 21:40:13 HomeNet kern.info kernel: [ 443.860000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 9 21:40:13 HomeNet daemon.notice netifd: vpnpptp (5986): Could not resolve server address
Jan 9 21:40:15 HomeNet kern.info kernel: [ 445.850000] br-lan: port 2(wlan0) entered forwarding state
Jan 9 21:40:16 HomeNet daemon.info hostapd: wlan0: STA 5c:ac:4c:56:6b:da IEEE 802.11: authenticated
Jan 9 21:40:16 HomeNet daemon.info hostapd: wlan0: STA 5c:ac:4c:56:6b:da IEEE 802.11: associated (aid 1)
Jan 9 21:40:16 HomeNet daemon.info hostapd: wlan0: STA 5c:ac:4c:56:6b:da WPA: pairwise key handshake completed (RSN)
Jan 9 21:40:17 HomeNet user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Jan 9 21:40:17 HomeNet user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: started, version 2.66 cachesize 150
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: using local addresses only for domain lan
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: reading /tmp/resolv.conf.auto
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.159.1#53
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.152.34#53
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.159.1#53
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.152.34#53
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: using local addresses only for domain lan
Jan 9 21:40:17 HomeNet daemon.info dnsmasq[6367]: read /etc/hosts - 66 addresses
Jan 9 21:40:18 HomeNet daemon.notice netifd: Interface 'vpnpptp' is now down
Jan 9 21:40:19 HomeNet daemon.info pppd[6427]: Plugin pptp.so loaded.
Jan 9 21:40:19 HomeNet daemon.info pppd[6427]: PPTP plugin version 1.00
Jan 9 21:40:19 HomeNet daemon.notice pppd[6427]: pppd 2.4.5 started by root, uid 0
Jan 9 21:40:20 HomeNet daemon.info pppd[6427]: Using interface pptp-vpnpptp
Jan 9 21:40:20 HomeNet daemon.notice pppd[6427]: Connect: pptp-vpnpptp <--> pptp (pl05.vpnonline.eu)
Jan 9 21:40:20 HomeNet daemon.notice pppd[6427]: CHAP authentication succeeded
Jan 9 21:40:20 HomeNet daemon.notice pppd[6427]: MPPE 128-bit stateless compression enabled
Jan 9 21:40:21 HomeNet daemon.notice pppd[6427]: local IP address 10.100.200.19
Jan 9 21:40:21 HomeNet daemon.notice pppd[6427]: remote IP address 10.100.200.254
Jan 9 21:40:21 HomeNet daemon.notice pppd[6427]: primary DNS address 208.67.220.220
Jan 9 21:40:21 HomeNet daemon.notice pppd[6427]: secondary DNS address 208.67.222.222
Jan 9 21:40:21 HomeNet daemon.notice netifd: Interface 'vpnpptp' is now up
Jan 9 21:40:23 HomeNet cron.info crond[6481]: crond: crond (busybox 1.19.4) started, log level 7
Jan 9 21:40:28 HomeNet daemon.info hostapd: wlan0: STA 10:bf:48:f5:de:e7 IEEE 802.11: authenticated
Jan 9 21:40:28 HomeNet daemon.info hostapd: wlan0: STA 10:bf:48:f5:de:e7 IEEE 802.11: associated (aid 2)
Jan 9 21:40:28 HomeNet daemon.info hostapd: wlan0: STA 10:bf:48:f5:de:e7 WPA: pairwise key handshake completed (RSN)
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: reading /tmp/resolv.conf.auto
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.159.1#53
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.152.34#53
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: using nameserver 208.67.222.222#53
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: using nameserver 208.67.220.220#53
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.159.1#53
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: using nameserver 194.204.152.34#53
Jan 9 21:40:28 HomeNet daemon.info dnsmasq[6367]: using local addresses only for domain lan
Jan 9 21:40:39 HomeNet daemon.info ddns_gargoyle[1972]: Successfully retrieved local ip from url: http://checkip.dyndns.org
Jan 9 21:40:40 HomeNet user.notice firewall: Reloading firewall due to ifup of vpnpptp (pptp-vpnpptp)
Jan 9 21:40:42 HomeNet user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Jan 9 21:40:44 HomeNet daemon.info ddns_gargoyle[1972]: Update successful
Jan 9 21:41:01 HomeNet cron.info crond[6481]: crond: USER root pid 7071 cmd /usr/bin/set_kernel_timezone >/dev/null 2>&1
Jan 9 21:41:40 HomeNet cron.info crond[7228]: crond: crond (busybox 1.19.4) started, log level 7
Jan 9 21:41:52 HomeNet cron.info crond[8280]: crond: crond (busybox 1.19.4) started, log level 7
Jan 9 21:41:54 HomeNet kern.info kernel: [ 544.740000] IMQ driver unloaded successfully.
Jan 9 21:41:54 HomeNet kern.info kernel: [ 544.900000] Hooked IMQ after mangle on INPUT
Jan 9 21:41:54 HomeNet kern.info kernel: [ 544.900000] Hooked IMQ after mangle on FORWARD
Jan 9 21:41:54 HomeNet kern.info kernel: [ 544.900000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1)
Jan 9 21:41:59 HomeNet local5.info qosmon[8907]: starting socketfd = 5, statusfd = 4
Jan 9 21:42:20 HomeNet daemon.info ddns_gargoyle[1972]: Could not determine local ip from url: http://checkip.org
Akurat to nic jeszcze nie ma. Nawiązał połączenie i tyle.
A mogę jakieś bardziej szczegółowe "włączyć" ?
Może to problem z GRE ? mój router jest za natem.
Trasy
default pptp-vpnpptp 10.100.200.254 0
10.100.200.254 pptp-vpnpptp * 0
46.29.17.202 eth1 (WAN) 192.168.0.252 0
192.168.0.0/255.255.255.0 eth1 (WAN) * 0
192.168.5.0/255.255.255.0 br-lan (LAN) * 0
Nie masz już jak. Możesz w debugu uruchamiać i sprawdzić jak coś Ci to powie: http://wiki.openwrt.org/doc/howto/vpn.client.pptp
Strony 1
Zaloguj się lub zarejestruj by napisać odpowiedź
eko.one.pl → Oprogramowanie / Software → Problem z vpn pptp
Forum oparte o PunBB, wspierane przez Informer Technologies, Inc