VPN: Poptop - bekomme keine Verbindung aufgebaut

Alle weiteren Dienste, die nicht in die drei oberen Foren gehören.
Antworten
osaldi2oao
Beiträge: 6
Registriert: 08.03.2009 11:24:48

VPN: Poptop - bekomme keine Verbindung aufgebaut

Beitrag von osaldi2oao » 02.05.2010 15:25:32

Hi,

ich wollte auf meinem Vserver einen VPN-Server einrichten, so dass ich an öffentlichen WLANs eine gesicherte Verbindung aufbauen kann.

Server:

Code: Alles auswählen

debian:/etc/ppp# uname -a
Linux debian 2.6.26-2-openvz-amd64 #1 SMP Fri Aug 14 08:15:13 UTC 2009 i686 GNU/Linux
Installiert habe ich poptop und wie folgt konfiguriert:

Code: Alles auswählen


debian:/etc/ppp# cat pptpd-options 
###############################################################################
# $Id: pptpd-options 4643 2006-11-06 18:42:43Z rene $
#
# Sample Poptop PPP options file /etc/ppp/pptpd-options
# Options used by PPP when a connection arrives from a client.
# This file is pointed to by /etc/pptpd.conf option keyword.
# Changes are effective on the next connection.  See "man pppd".
#
# You are expected to change this file to suit your system.  As
# packaged, it requires PPP 2.4.2 and the kernel MPPE module.
###############################################################################


# Authentication

# Name of the local system for authentication purposes 
# (must match the second field in /etc/ppp/chap-secrets entries)
name pptpd

# Optional: domain name to use for authentication
# domain mydomain.net

# Strip the domain prefix from the username before authentication.
# (applies if you use pppd with chapms-strip-domain patch)
#chapms-strip-domain


# Encryption
# Debian: on systems with a kernel built with the package
# kernel-patch-mppe >= 2.4.2 and using ppp >= 2.4.2, ...
# {{{
refuse-pap
refuse-chap
refuse-mschap
# Require the peer to authenticate itself using MS-CHAPv2 [Microsoft
# Challenge Handshake Authentication Protocol, Version 2] authentication.
require-mschap-v2
# Require MPPE 128-bit encryption
# (note that MPPE requires the use of MSCHAP-V2 during authentication)
#require-mppe-128
mppe required
mppe stateless
nodeflate
# }}}




# Network and Routing

# If pppd is acting as a server for Microsoft Windows clients, this
# option allows pppd to supply one or two DNS (Domain Name Server)
# addresses to the clients.  The first instance of this option
# specifies the primary DNS address; the second instance (if given)
# specifies the secondary DNS address.
# Attention! This information may not be taken into account by a Windows
# client. See KB311218 in Microsoft's knowledge base for more information.
ms-dns 8.8.8.8
#ms-dns 10.0.0.2

# If pppd is acting as a server for Microsoft Windows or "Samba"
# clients, this option allows pppd to supply one or two WINS (Windows
# Internet Name Services) server addresses to the clients.  The first
# instance of this option specifies the primary WINS address; the
# second instance (if given) specifies the secondary WINS address.
#ms-wins 10.0.0.3
#ms-wins 10.0.0.4

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.  This will have the effect of making the peer appear to other
# systems to be on the local ethernet.
# (you do not need this if your PPTP server is responsible for routing
# packets to the clients -- James Cameron)
proxyarp

# Debian: do not replace the default route
nodefaultroute


# Logging

# Enable connection debugging facilities.
# (see your syslog configuration for where pppd sends to)
debug

# Print out all the option values which have been set.
# (often requested by mailing list to verify options)
dump


# Miscellaneous

# Create a UUCP-style lock file for the pseudo-tty to ensure exclusive
# access.
lock

# Disable BSD-Compress compression
nobsdcomp 

Code: Alles auswählen

debian:/etc/ppp# cat ../pptpd.conf 
###############################################################################
# $Id: pptpd.conf 4255 2004-10-03 18:44:00Z rene $
#
# Sample Poptop configuration file /etc/pptpd.conf
#
# Changes are effective when pptpd is restarted.
###############################################################################

# TAG: ppp
#	Path to the pppd program, default '/usr/sbin/pppd' on Linux
#
#ppp /usr/sbin/pppd

# TAG: option
#	Specifies the location of the PPP options file.
#	By default PPP looks in '/etc/ppp/options'
#
option /etc/ppp/pptpd-options

# TAG: debug
#	Turns on (more) debugging to syslog
#
debug
logfile /tmp/pppd.log

# TAG: stimeout
#	Specifies timeout (in seconds) on starting ctrl connection
#
# stimeout 10

# TAG: noipparam
#       Suppress the passing of the client's IP address to PPP, which is
#       done by default otherwise.
#
#noipparam

# TAG: logwtmp
#	Use wtmp(5) to record client connections and disconnections.
#
logwtmp

# TAG: bcrelay <if>
#	Turns on broadcast relay to clients from interface <if>
#
#bcrelay eth1

# TAG: localip
# TAG: remoteip
#	Specifies the local and remote IP address ranges.
#
#       Any addresses work as long as the local machine takes care of the
#       routing.  But if you want to use MS-Windows networking, you should
#       use IP addresses out of the LAN address space and use the proxyarp
#       option in the pppd options file, or run bcrelay.
#
#	You can specify single IP addresses seperated by commas or you can
#	specify ranges, or both. For example:
#
#		192.168.0.234,192.168.0.245-249,192.168.0.254
#
#	IMPORTANT RESTRICTIONS:
#
#	1. No spaces are permitted between commas or within addresses.
#
#	2. If you give more IP addresses than MAX_CONNECTIONS, it will
#	   start at the beginning of the list and go until it gets 
#	   MAX_CONNECTIONS IPs. Others will be ignored.
#
#	3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,
#	   you must type 234-238 if you mean this.
#
#	4. If you give a single localIP, that's ok - all local IPs will
#	   be set to the given one. You MUST still give at least one remote
#	   IP for each simultaneous client.
#
# (Recommended)
localip 192.168.0.1
remoteip 192.168.0.234-238,192.168.0.245
# or
#localip 192.168.0.234-238,192.168.0.245
#remoteip 192.168.1.234-238,192.168.1.245


Code: Alles auswählen

debian:/etc/ppp# cat chap-secrets  
# Secrets for authentication using CHAP
# client	server	secret			IP addresses


joern1 pptpd meinpw *
Logfile sagt folgendes beim Verbindungsaufbau:

Code: Alles auswählen

May  2 15:18:40 debian pptpd[32354]: MGR: Launching /usr/sbin/pptpctrl to handle client
May  2 15:18:40 debian pptpd[32354]: CTRL: local address = 192.168.0.1
May  2 15:18:40 debian pptpd[32354]: CTRL: remote address = 192.168.0.234
May  2 15:18:40 debian pptpd[32354]: CTRL: pppd options file = /etc/ppp/pptpd-options
May  2 15:18:40 debian pptpd[32354]: CTRL: Received PPTP Control Message (type: 1)
May  2 15:18:40 debian pptpd[32354]: CTRL: Made a START CTRL CONN RPLY packet
May  2 15:18:40 debian pptpd[32354]: CTRL: I wrote 156 bytes to the client.
May  2 15:18:40 debian pptpd[32354]: CTRL: Sent packet to client
May  2 15:18:40 debian pptpd[32354]: CTRL: Received PPTP Control Message (type: 7)
May  2 15:18:40 debian pptpd[32354]: CTRL: Set parameters to 100000000 maxbps, 64 window size
May  2 15:18:40 debian pptpd[32354]: CTRL: Made a OUT CALL RPLY packet
May  2 15:18:40 debian pptpd[32354]: CTRL: pty_fd = 6
May  2 15:18:40 debian pptpd[32354]: CTRL: tty_fd = 7
May  2 15:18:40 debian pptpd[32355]: CTRL (PPPD Launcher): program binary = /usr/sbin/pppd
May  2 15:18:40 debian pptpd[32355]: CTRL (PPPD Launcher): local address = 192.168.0.1
May  2 15:18:40 debian pptpd[32355]: CTRL (PPPD Launcher): remote address = 192.168.0.234
May  2 15:18:40 debian pptpd[32354]: CTRL: I wrote 32 bytes to the client.
May  2 15:18:40 debian pptpd[32354]: CTRL: Sent packet to client
May  2 15:18:40 debian pptpd[32354]: CTRL: Reaping child PPP[32355]
May  2 15:18:40 debian pptpd[32354]: CTRL: Exiting now
May  2 15:18:40 debian pptpd[32211]: MGR: Reaped child 32354
Gestestet habe ich es mit dem XP-VPN-Client, unter Netzwerk PPTP-VPN ausgewählt, als User: "joern1" und als Passwort: "meinpw".
Fehlermeldung vom Client ist: "Fehler 619. Es konnte keine Verbindung vom Remoteconputer hergestellt werden..."

Ich habe es vom Handy auch noch mal getestet und dort bekommt ich sinngemäß die selbe Fehlermeldung und exakt die selben Logeinträge.


Jemand ne Idee woran es liegen könnte?

Benutzeravatar
chroiss
Beiträge: 332
Registriert: 29.10.2004 09:29:43
Lizenz eigener Beiträge: MIT Lizenz
Wohnort: BREMEN (in Wellington,NZ a.D) (in OLDENBURG a.D.) (in BREMEN a.D.) (in COLOGNE a.D.)

Re: VPN: Poptop - bekomme keine Verbindung aufgebaut

Beitrag von chroiss » 06.05.2010 11:32:10

hast du mal versucht

Code: Alles auswählen

#require-mppe-128
mppe required
mppe stateless
durch

Code: Alles auswählen

require-mppe-128
#mppe required
#mppe stateless
zu ersetzen?
"The only secure computer is one that's unplugged, locked in a safe, and buried 20 feet under the ground in a secret location... and I'm not even too sure about that one"--Dennis Huges, FBI.

osaldi2oao
Beiträge: 6
Registriert: 08.03.2009 11:24:48

Re: VPN: Poptop - bekomme keine Verbindung aufgebaut

Beitrag von osaldi2oao » 29.06.2010 20:12:55

Habe ich mal probiert, hatte aber nicht geklappt.

Mir ist nun folgendes aufgefallen:
debian:~# /usr/sbin/pppd
/usr/sbin/pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
debian:~# uname -a
Linux debian 2.6.26-2-openvz-amd64 #1 SMP Fri Aug 14 08:15:13 UTC 2009 i686 GNU/Linux
Ist wie gesagt ein VServer, da habe ich wohl keine Chance das zum Laufen zu bekommen, sehe ich das richtig?

Antworten