Top-Themen

AppleEntwicklungHardwareInternetLinuxMicrosoftMultimediaNetzwerkeOff TopicSicherheitSonstige SystemeVirtualisierungWeiterbildungZusammenarbeit

Aktuelle Themen

Administrator.de FeedbackApache ServerAppleAssemblerAudioAusbildungAuslandBackupBasicBatch & ShellBenchmarksBibliotheken & ToolkitsBlogsCloud-DiensteClusterCMSCPU, RAM, MainboardsCSSC und C++DatenbankenDatenschutzDebianDigitiales FernsehenDNSDrucker und ScannerDSL, VDSLE-BooksE-BusinessE-MailEntwicklungErkennung und -AbwehrExchange ServerFestplatten, SSD, RaidFirewallFlatratesGoogle AndroidGrafikGrafikkarten & MonitoreGroupwareHardwareHosting & HousingHTMLHumor (lol)Hyper-VIconsIDE & EditorenInformationsdiensteInstallationInstant MessagingInternetInternet DomäneniOSISDN & AnaloganschlüsseiTunesJavaJavaScriptKiXtartKVMLAN, WAN, WirelessLinuxLinux DesktopLinux NetzwerkLinux ToolsLinux UserverwaltungLizenzierungMac OS XMicrosoftMicrosoft OfficeMikroTik RouterOSMonitoringMultimediaMultimedia & ZubehörNetzwerkeNetzwerkgrundlagenNetzwerkmanagementNetzwerkprotokolleNotebook & ZubehörNovell NetwareOff TopicOpenOffice, LibreOfficeOutlook & MailPapierkorbPascal und DelphiPeripheriegerätePerlPHPPythonRechtliche FragenRedHat, CentOS, FedoraRouter & RoutingSambaSAN, NAS, DASSchriftartenSchulung & TrainingSEOServerServer-HardwareSicherheitSicherheits-ToolsSicherheitsgrundlagenSolarisSonstige SystemeSoziale NetzwerkeSpeicherkartenStudentenjobs & PraktikumSuche ProjektpartnerSuseSwitche und HubsTipps & TricksTK-Netze & GeräteUbuntuUMTS, EDGE & GPRSUtilitiesVB for ApplicationsVerschlüsselung & ZertifikateVideo & StreamingViren und TrojanerVirtualisierungVisual StudioVmwareVoice over IPWebbrowserWebentwicklungWeiterbildungWindows 7Windows 8Windows 10Windows InstallationWindows MobileWindows NetzwerkWindows ServerWindows SystemdateienWindows ToolsWindows UpdateWindows UserverwaltungWindows VistaWindows XPXenserverXMLZusammenarbeit
GELÖST

Verbindungsproblem mit OpenVPN

Frage Linux

Mitglied: Zoom78

Zoom78 (Level 1) - Jetzt verbinden

17.10.2010, aktualisiert 18.10.2012, 5209 Aufrufe, 5 Kommentare

Tunnel wird geschlossen

Hallo Leute, ich habe ein sehr dringendes anliegen.

Habe vor durch einen eigenen Suse 11.3 Server zu surfen, damit stets die gleich IP vorhanden ist. Ich habe jetzt OpenVPN installiert und konfiguriert. Die VPN Verbindung zum Server wird problemlos aufgebaut. Ich will, daß der sämtliche Traffic über das VPN durchgeht, dies wiederum weiß ich nicht wie ich das umleiten soll.

Auf dem Client (Windows XP Pro SP3) habe ich "LAN-Verbindung 1" und den "TAP-32 WIN Adapter" von Openvpn. Die Netzwerkeinstellungen daheim:
Netz 192.168.10.0/24
Router 192.168.10.1

Mein PC
NIC#1 192.168.10.5
TAP-32 WIN Adapter - keine IP manuell zugewiesen.



Hier meine config Dateien:

SERVER - Suse 11.3
01.
;local a.b.c.d 
02.
port 443 
03.
 
04.
# TCP or UDP server? 
05.
proto tcp 
06.
;proto udp 
07.
dev tap 
08.
;dev tun 
09.
;dev-node MyTap 
10.
ca /etc/openvpn/easy-rsa/2.0/keys/ca.crt 
11.
cert /etc/openvpn/easy-rsa/2.0/keys/server.crt 
12.
key /etc/openvpn/easy-rsa/2.0/keys/server.key  # This file should be kept secret 
13.
dh /etc/openvpn/easy-rsa/2.0/keys/dh1024.pem 
14.
;server 10.8.0.0 255.255.255.0 
15.
;ifconfig-pool-persist ipp.txt 
16.
server-bridge 10.8.0.4 255.255.255.0 10.8.0.6 10.8.0.30 
17.
;server-bridge 
18.
;push "route 192.168.10.0 255.255.255.0" 
19.
;push "route 192.168.20.0 255.255.255.0" 
20.
push "route 0.0.0.0 0.0.0.0 10.8.0.4" 
21.
;push "route 0.0.0.0 0.0.0.0" 
22.
;client-config-dir ccd 
23.
;route 192.168.40.128 255.255.255.248 
24.
;client-config-dir ccd 
25.
;route 10.9.0.0 255.255.255.252 
26.
;learn-address ./script 
27.
push "redirect-gateway def1 bypass-dhcp" 
28.
;push "dhcp-option DNS 208.67.222.222" 
29.
;push "dhcp-option DNS 208.67.220.220" 
30.
push "dhcp-option DNS 192.168.10.1" 
31.
;client-to-client 
32.
;duplicate-cn 
33.
keepalive 10 120 
34.
;tls-auth ta.key 0 # This file is secret 
35.
;cipher BF-CBC        # Blowfish (default) 
36.
;cipher AES-128-CBC   # AES 
37.
cipher DES-EDE3-CBC  # Triple-DES 
38.
comp-lzo 
39.
;max-clients 100 
40.
;user nobody 
41.
;group nobody 
42.
persist-key 
43.
persist-tun 
44.
status openvpn-status.log 
45.
;log         openvpn.log 
46.
;log-append  openvpn.log 
47.
verb 3 
48.
;mute 20
CLIENT - Windows XP Pro SP3
01.
client 
02.
dev tap 
03.
;dev tun 
04.
;dev-node MyTap 
05.
proto tcp 
06.
;proto udp 
07.
remote XX.XX.XX.XXX 443 
08.
;remote-random 
09.
resolv-retry infinite 
10.
nobind 
11.
;user nobody 
12.
;group nobody 
13.
persist-key 
14.
persist-tun 
15.
;http-proxy-retry # retry on connection failures 
16.
;http-proxy [proxy server] [proxy port #] 
17.
;mute-replay-warnings 
18.
ca c:\\VPN\\ca.crt 
19.
ca c:\\VPN\\vpnhost1.crt 
20.
ca c:\\VPN\\vpnhost1.key 
21.
;ns-cert-type server 
22.
;tls-auth ta.key 1 
23.
cipher DES-EDE3-CBC 
24.
comp-lzo 
25.
verb 3 
26.
;mute 20 
27.
route-up myroute.cmd
Zunächst wird die Verbindung - der Tunnel - aufgebaut, ich kann sehen wie der Icon von OpenVPN-GUI seine Farbe in Grün wechselt und es wird gemeldet, daß die Verbindung aufgebaut wurde. Doch nach ca. 15-20 Sekunden wird der Icon wieder gelb. Folgendes konnte ich aus dem Log von Openvpn ziehen:

01.
Sun Oct 17 19:19:43 2010 OpenVPN 2.1.1 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Dec 11 2009 
02.
Sun Oct 17 19:19:43 2010 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info. 
03.
Sun Oct 17 19:19:43 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables 
04.
Sun Oct 17 19:19:43 2010 LZO compression initialized 
05.
Sun Oct 17 19:19:43 2010 Control Channel MTU parms [ L:1576 D:140 EF:40 EB:0 ET:0 EL:0 ] 
06.
Sun Oct 17 19:19:43 2010 Data Channel MTU parms [ L:1576 D:1450 EF:44 EB:135 ET:32 EL:0 AF:3/1 ] 
07.
Sun Oct 17 19:19:43 2010 Local Options hash (VER=V4): '1a40e822' 
08.
Sun Oct 17 19:19:43 2010 Expected Remote Options hash (VER=V4): 'd8e6e8ce' 
09.
Sun Oct 17 19:19:43 2010 Attempting to establish TCP connection with 12.34.56.789:443 
10.
Sun Oct 17 19:19:43 2010 TCP connection established with 12.34.56.789:443 
11.
Sun Oct 17 19:19:43 2010 Socket Buffers: R=[8192->8192] S=[8192->8192] 
12.
Sun Oct 17 19:19:43 2010 TCPv4_CLIENT link local: [undef] 
13.
Sun Oct 17 19:19:43 2010 TCPv4_CLIENT link remote: 12.34.56.789:443 
14.
Sun Oct 17 19:19:43 2010 TLS: Initial packet from 12.34.56.789:443, sid=daf8e6b0 65398b2d 
15.
Sun Oct 17 19:19:44 2010 VERIFY OK: depth=1, /C=DE/ST=stratoRZ5/L=Munich/O=besitzer/OU=dummy/CN=dumms1/name=Dummy_Dummy/emailAddress=Dummy@dummy.de 
16.
Sun Oct 17 19:19:44 2010 VERIFY OK: depth=0, /C=DE/ST=stratoRZ5/L=Munich/O=server/OU=dumms/CN=dumms1/name=Dummy_Dummy/emailAddress=Dummy@dummy.de 
17.
Sun Oct 17 19:19:46 2010 Data Channel Encrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key 
18.
Sun Oct 17 19:19:46 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication 
19.
Sun Oct 17 19:19:46 2010 Data Channel Decrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key 
20.
Sun Oct 17 19:19:46 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication 
21.
Sun Oct 17 19:19:46 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA 
22.
Sun Oct 17 19:19:46 2010 [dumms1] Peer Connection Initiated with 12.34.56.789:443 
23.
Sun Oct 17 19:19:48 2010 SENT CONTROL [dumms1]: 'PUSH_REQUEST' (status=1) 
24.
Sun Oct 17 19:19:48 2010 PUSH: Received control message: 'PUSH_REPLY,route 0.0.0.0 0.0.0.0 10.8.0.4,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 192.168.10.1,route-gateway 10.8.0.4,ping 10,ping-restart 120,ifconfig 10.8.0.6 255.255.255.0' 
25.
Sun Oct 17 19:19:48 2010 OPTIONS IMPORT: timers and/or timeouts modified 
26.
Sun Oct 17 19:19:48 2010 OPTIONS IMPORT: --ifconfig/up options modified 
27.
Sun Oct 17 19:19:48 2010 OPTIONS IMPORT: route options modified 
28.
Sun Oct 17 19:19:48 2010 OPTIONS IMPORT: route-related options modified 
29.
Sun Oct 17 19:19:48 2010 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified 
30.
Sun Oct 17 19:19:48 2010 ROUTE default_gateway=192.168.10.1 
31.
Sun Oct 17 19:19:48 2010 TAP-WIN32 device [VPN Device (TUN-TAP)] opened: \\.\Global\{91A9C3DE-A18E-36D2-85F6-32E0FA46C523F}.tap 
32.
Sun Oct 17 19:19:48 2010 TAP-Win32 Driver Version 9.6  
33.
Sun Oct 17 19:19:48 2010 TAP-Win32 MTU=1500 
34.
Sun Oct 17 19:19:48 2010 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.0 on interface {91A9C3DE-A18E-36D2-85F6-32E0FA46C523F} [DHCP-serv: 10.8.0.0, lease-time: 31536000] 
35.
Sun Oct 17 19:19:48 2010 Successful ARP Flush on interface [1441794] {91A9C3DE-A18E-36D2-85F6-32E0FA46C523F} 
36.
Sun Oct 17 19:19:53 2010 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up 
37.
Sun Oct 17 19:19:53 2010 C:\WINDOWS\system32\route.exe ADD 12.34.56.789 MASK 255.255.255.255 192.168.10.1 
38.
Sun Oct 17 19:19:53 2010 Warning: route gateway is ambiguous: 192.168.10.1 (2 matches) 
39.
Sun Oct 17 19:19:53 2010 Route addition via IPAPI failed [adaptive] 
40.
Sun Oct 17 19:19:53 2010 Route addition fallback to route.exe 
41.
Sun Oct 17 19:19:53 2010 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.4 
42.
Sun Oct 17 19:19:53 2010 Route addition via IPAPI succeeded [adaptive] 
43.
Sun Oct 17 19:19:53 2010 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.4 
44.
Sun Oct 17 19:19:53 2010 Route addition via IPAPI succeeded [adaptive] 
45.
Sun Oct 17 19:19:53 2010 WARNING: potential route subnet conflict between local LAN [192.168.10.0/255.255.255.0] and remote VPN [0.0.0.0/0.0.0.0] 
46.
Sun Oct 17 19:19:53 2010 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 0.0.0.0 10.8.0.4 
47.
Sun Oct 17 19:19:53 2010 Route addition via IPAPI succeeded [adaptive] 
48.
Sun Oct 17 19:19:53 2010 openvpn_execve: external program may not be called unless '--script-security 2' or higher is enabled.  Use '--script-security 3 system' for backward compatibility with 2.1_rc8 and earlier.  See --help text or man page for detailed info. 
49.
Sun Oct 17 19:19:53 2010 Route script failed: external program did not execute -- returned error code -1 
50.
Sun Oct 17 19:19:53 2010 Initialization Sequence Completed 
51.
 
52.
Sun Oct 17 19:20:14 2010 Connection reset, restarting [-1] 
53.
Sun Oct 17 19:20:14 2010 TCP/UDP: Closing socket 
54.
Sun Oct 17 19:20:14 2010 SIGUSR1[soft,connection-reset] received, process restarting 
55.
Sun Oct 17 19:20:14 2010 Restart pause, 5 second(s) 
56.
Sun Oct 17 19:20:19 2010 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info. 
57.
Sun Oct 17 19:20:19 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables 
58.
Sun Oct 17 19:20:19 2010 Re-using SSL/TLS context 
59.
Sun Oct 17 19:20:19 2010 LZO compression initialized 
60.
Sun Oct 17 19:20:19 2010 Control Channel MTU parms [ L:1576 D:140 EF:40 EB:0 ET:0 EL:0 ] 
61.
Sun Oct 17 19:20:19 2010 Data Channel MTU parms [ L:1576 D:1450 EF:44 EB:135 ET:32 EL:0 AF:3/1 ] 
62.
Sun Oct 17 19:20:19 2010 Local Options hash (VER=V4): '1a40e822' 
63.
Sun Oct 17 19:20:19 2010 Expected Remote Options hash (VER=V4): 'd8e6e8ce' 
64.
Sun Oct 17 19:20:19 2010 Attempting to establish TCP connection with 12.34.56.789:443
Ab 19:20:14 Uhr kann man sehen was passiert zu dem Zeitpunkt wenn sich die Farbe verändert.

Kann mir jemand sagen was ich falsch mache ? Wieso wird der VPN Tunnel aufgebaut, und was muss ich alles tun damit alles an Verbindungen ins Internet über den VPN Tunnel laufen?

Bitte Leute, daß ist sehr dringend !
Mitglied: aqui
18.10.2010 um 11:28 Uhr
Wie immer...einfach mal in die Dokumentation sehen ! Aber gerne machen wir das auch für dich....
http://openvpn.net/index.php/open-source/documentation/howto.html#redir ...
Da steht schwarz auf weiß wie es einfach im Setup einzustellen ist !
Bitte warten ..
Mitglied: Zoom78
18.10.2010 um 13:50 Uhr
Habe ich gemacht! Weiterhin werde ich rausgeschmissen nach einigen Sekunden. Und auch dazwischen gibt es keine Verbindung!

Hier meine heutige server config:
01.
;local a.b.c.d 
02.
 
03.
# Which TCP/UDP port should OpenVPN listen on? 
04.
# If you want to run multiple OpenVPN instances 
05.
# on the same machine, use a different port 
06.
# number for each one.  You will need to 
07.
# open up this port on your firewall. 
08.
port 443 
09.
 
10.
# TCP or UDP server? 
11.
proto tcp-server 
12.
;proto udp 
13.
 
14.
# "dev tun" will create a routed IP tunnel, 
15.
# "dev tap" will create an ethernet tunnel. 
16.
# Use "dev tap0" if you are ethernet bridging 
17.
# and have precreated a tap0 virtual interface 
18.
# and bridged it with your ethernet interface. 
19.
# If you want to control access policies 
20.
# over the VPN, you must create firewall 
21.
# rules for the the TUN/TAP interface. 
22.
# On non-Windows systems, you can give 
23.
# an explicit unit number, such as tun0. 
24.
# On Windows, use "dev-node" for this. 
25.
# On most systems, the VPN will not function 
26.
# unless you partially or fully disable 
27.
# the firewall for the TUN/TAP interface. 
28.
dev tap 
29.
;dev tun 
30.
 
31.
# Windows needs the TAP-Win32 adapter name 
32.
# from the Network Connections panel if you 
33.
# have more than one.  On XP SP2 or higher, 
34.
# you may need to selectively disable the 
35.
# Windows firewall for the TAP adapter. 
36.
# Non-Windows systems usually don't need this. 
37.
;dev-node MyTap 
38.
 
39.
# SSL/TLS root certificate (ca), certificate 
40.
# (cert), and private key (key).  Each client 
41.
# and the server must have their own cert and 
42.
# key file.  The server and all clients will 
43.
# use the same ca file. 
44.
45.
# See the "easy-rsa" directory for a series 
46.
# of scripts for generating RSA certificates 
47.
# and private keys.  Remember to use 
48.
# a unique Common Name for the server 
49.
# and each of the client certificates. 
50.
51.
# Any X509 key management system can be used. 
52.
# OpenVPN can also use a PKCS #12 formatted key file 
53.
# (see "pkcs12" directive in man page). 
54.
ca /etc/openvpn/easy-rsa/2.0/keys/ca.crt 
55.
cert /etc/openvpn/easy-rsa/2.0/keys/server.crt 
56.
key /etc/openvpn/easy-rsa/2.0/keys/server.key  # This file should be kept secret 
57.
 
58.
# Diffie hellman parameters. 
59.
# Generate your own with: 
60.
#   openssl dhparam -out dh1024.pem 1024 
61.
# Substitute 2048 for 1024 if you are using 
62.
# 2048 bit keys. 
63.
dh /etc/openvpn/easy-rsa/2.0/keys/dh1024.pem 
64.
 
65.
# Configure server mode and supply a VPN subnet 
66.
# for OpenVPN to draw client addresses from. 
67.
# The server will take 10.8.0.1 for itself, 
68.
# the rest will be made available to clients. 
69.
# Each client will be able to reach the server 
70.
# on 10.8.0.1. Comment this line out if you are 
71.
# ethernet bridging. See the man page for more info. 
72.
;server 10.8.0.0 255.255.255.0 
73.
 
74.
# Maintain a record of client <-> virtual IP address 
75.
# associations in this file.  If OpenVPN goes down or 
76.
# is restarted, reconnecting clients can be assigned 
77.
# the same virtual IP address from the pool that was 
78.
# previously assigned. 
79.
;ifconfig-pool-persist ipp.txt 
80.
 
81.
# Configure server mode for ethernet bridging. 
82.
# You must first use your OS's bridging capability 
83.
# to bridge the TAP interface with the ethernet 
84.
# NIC interface.  Then you must manually set the 
85.
# IP/netmask on the bridge interface, here we 
86.
# assume 10.8.0.4/255.255.255.0.  Finally we 
87.
# must set aside an IP range in this subnet 
88.
# (start=10.8.0.50 end=10.8.0.100) to allocate 
89.
# to connecting clients.  Leave this line commented 
90.
# out unless you are ethernet bridging. 
91.
server-bridge 10.8.0.1 255.255.255.0 10.8.0.50 10.8.0.60 
92.
 
93.
# Configure server mode for ethernet bridging 
94.
# using a DHCP-proxy, where clients talk 
95.
# to the OpenVPN server-side DHCP server 
96.
# to receive their IP address allocation 
97.
# and DNS server addresses.  You must first use 
98.
# your OS's bridging capability to bridge the TAP 
99.
# interface with the ethernet NIC interface. 
100.
# Note: this mode only works on clients (such as 
101.
# Windows), where the client-side TAP adapter is 
102.
# bound to a DHCP client. 
103.
;server-bridge 
104.
 
105.
# Push routes to the client to allow it 
106.
# to reach other private subnets behind 
107.
# the server.  Remember that these 
108.
# private subnets will also need 
109.
# to know to route the OpenVPN client 
110.
# address pool (10.8.0.0/255.255.255.0) 
111.
# back to the OpenVPN server. 
112.
;push "route 192.168.10.0 255.255.255.0" 
113.
;push "route 192.168.20.0 255.255.255.0" 
114.
push "route 0.0.0.0 0.0.0.0 10.8.0.1" 
115.
 
116.
# To assign specific IP addresses to specific 
117.
# clients or if a connecting client has a private 
118.
# subnet behind it that should also have VPN access, 
119.
# use the subdirectory "ccd" for client-specific 
120.
# configuration files (see man page for more info). 
121.
 
122.
# EXAMPLE: Suppose the client 
123.
# having the certificate common name "Thelonious" 
124.
# also has a small subnet behind his connecting 
125.
# machine, such as 192.168.40.128/255.255.255.248. 
126.
# First, uncomment out these lines: 
127.
;client-config-dir ccd 
128.
;route 192.168.40.128 255.255.255.248 
129.
 
130.
# Then create a file ccd/Thelonious with this line: 
131.
#   iroute 192.168.40.128 255.255.255.248 
132.
# This will allow Thelonious' private subnet to 
133.
# access the VPN.  This example will only work 
134.
# if you are routing, not bridging, i.e. you are 
135.
# using "dev tun" and "server" directives. 
136.
 
137.
# EXAMPLE: Suppose you want to give 
138.
# Thelonious a fixed VPN IP address of 10.9.0.1. 
139.
# First uncomment out these lines: 
140.
;client-config-dir ccd 
141.
;route 10.9.0.0 255.255.255.252 
142.
# Then add this line to ccd/Thelonious: 
143.
#   ifconfig-push 10.9.0.1 10.9.0.2 
144.
 
145.
# Suppose that you want to enable different 
146.
# firewall access policies for different groups 
147.
# of clients.  There are two methods: 
148.
# (1) Run multiple OpenVPN daemons, one for each 
149.
#     group, and firewall the TUN/TAP interface 
150.
#     for each group/daemon appropriately. 
151.
# (2) (Advanced) Create a script to dynamically 
152.
#     modify the firewall in response to access 
153.
#     from different clients.  See man 
154.
#     page for more info on learn-address script. 
155.
;learn-address ./script 
156.
 
157.
# If enabled, this directive will configure 
158.
# all clients to redirect their default 
159.
# network gateway through the VPN, causing 
160.
# all IP traffic such as web browsing and 
161.
# and DNS lookups to go through the VPN 
162.
# (The OpenVPN server machine may need to NAT 
163.
# or bridge the TUN/TAP interface to the internet 
164.
# in order for this to work properly). 
165.
;push "redirect-gateway def1 bypass-dhcp" 
166.
push "redirect-gateway def1" 
167.
 
168.
# Certain Windows-specific network settings 
169.
# can be pushed to clients, such as DNS 
170.
# or WINS server addresses.  CAVEAT: 
171.
# http://openvpn.net/faq.html#dhcpcaveats 
172.
# The addresses below refer to the public 
173.
# DNS servers provided by opendns.com. 
174.
;push "dhcp-option DNS 208.67.222.222" 
175.
;push "dhcp-option DNS 208.67.220.220" 
176.
push "dhcp-option DNS 10.8.0.1" 
177.
# clients to be able to "see" each other. 
178.
# By default, clients will only see the server. 
179.
# To force clients to only see the server, you 
180.
# will also need to appropriately firewall the 
181.
# server's TUN/TAP interface. 
182.
;client-to-client 
183.
 
184.
# Uncomment this directive if multiple clients 
185.
# might connect with the same certificate/key 
186.
# files or common names.  This is recommended 
187.
# only for testing purposes.  For production use, 
188.
# each client should have its own certificate/key 
189.
# pair. 
190.
191.
# IF YOU HAVE NOT GENERATED INDIVIDUAL 
192.
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT, 
193.
# EACH HAVING ITS OWN UNIQUE "COMMON NAME", 
194.
# UNCOMMENT THIS LINE OUT. 
195.
;duplicate-cn 
196.
 
197.
# The keepalive directive causes ping-like 
198.
# messages to be sent back and forth over 
199.
# the link so that each side knows when 
200.
# the other side has gone down. 
201.
# Ping every 10 seconds, assume that remote 
202.
# peer is down if no ping received during 
203.
# a 120 second time period. 
204.
keepalive 10 120 
205.
 
206.
# For extra security beyond that provided 
207.
# by SSL/TLS, create an "HMAC firewall" 
208.
# to help block DoS attacks and UDP port flooding. 
209.
210.
# Generate with: 
211.
#   openvpn --genkey --secret ta.key 
212.
213.
# The server and each client must have 
214.
# a copy of this key. 
215.
# The second parameter should be '0' 
216.
# on the server and '1' on the clients. 
217.
;tls-auth ta.key 0 # This file is secret 
218.
 
219.
# Select a cryptographic cipher. 
220.
# This config item must be copied to 
221.
# the client config file as well. 
222.
;cipher BF-CBC        # Blowfish (default) 
223.
;cipher AES-128-CBC   # AES 
224.
;cipher DES-EDE3-CBC  # Triple-DES 
225.
 
226.
# Enable compression on the VPN link. 
227.
# If you enable it here, you must also 
228.
# enable it in the client config file. 
229.
comp-lzo 
230.
 
231.
# The maximum number of concurrently connected 
232.
# clients we want to allow. 
233.
;max-clients 100 
234.
 
235.
# It's a good idea to reduce the OpenVPN 
236.
# daemon's privileges after initialization. 
237.
238.
# You can uncomment this out on 
239.
# non-Windows systems. 
240.
;user nobody 
241.
;group nobody 
242.
 
243.
# The persist options will try to avoid 
244.
# accessing certain resources on restart 
245.
# that may no longer be accessible because 
246.
# of the privilege downgrade. 
247.
persist-key 
248.
persist-tun 
249.
 
250.
# Output a short status file showing 
251.
# current connections, truncated 
252.
# and rewritten every minute. 
253.
status openvpn-status.log 
254.
 
255.
# By default, log messages will go to the syslog (or 
256.
# on Windows, if running as a service, they will go to 
257.
# the "\Program Files\OpenVPN\log" directory). 
258.
# Use log or log-append to override this default. 
259.
# "log" will truncate the log file on OpenVPN startup, 
260.
# while "log-append" will append to it.  Use one 
261.
# or the other (but not both). 
262.
;log         openvpn.log 
263.
;log-append  openvpn.log 
264.
 
265.
# Set the appropriate level of log 
266.
# file verbosity. 
267.
268.
# 0 is silent, except for fatal errors 
269.
# 4 is reasonable for general usage 
270.
# 5 and 6 can help to debug connection problems 
271.
# 9 is extremely verbose 
272.
verb 3 
273.
 
274.
# Silence repeating messages.  At most 20 
275.
# sequential messages of the same message 
276.
# category will be output to the log. 
277.
;mute 20
Auch die iptables Regel habe ich eingegeben.

Wenn es so einfach wäre, hätte ich doch nicht gefragt! Fakt ist, dass ich schon seit 3 Tagen daran sitze und nicht klar komme. Zunächst wird die Verbindung aufgebaut, doch ich kann nicht surfen. Dann, nach ca 15 Sekunden, wird die Verbindung wieder gelb. Und ich kann dann sowas lesen:

01.
Mon Oct 18 13:42:12 2010 TCP/UDP: Closing socket 
02.
Mon Oct 18 13:42:12 2010 C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 0.0.0.0 10.8.0.1 
03.
Mon Oct 18 13:42:12 2010 Route deletion via IPAPI succeeded [adaptive] 
04.
Mon Oct 18 13:42:12 2010 C:\WINDOWS\system32\route.exe DELETE 78.46.47.236 MASK 255.255.255.255 192.168.73.1 
05.
Mon Oct 18 13:42:12 2010 Warning: route gateway is ambiguous: 192.168.73.1 (2 matches) 
06.
Mon Oct 18 13:42:12 2010 Route deletion via IPAPI failed [adaptive] 
07.
Mon Oct 18 13:42:12 2010 Route deletion fallback to route.exe 
08.
Mon Oct 18 13:42:12 2010 C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 10.8.0.1 
09.
Mon Oct 18 13:42:12 2010 Route deletion via IPAPI succeeded [adaptive] 
10.
Mon Oct 18 13:42:12 2010 C:\WINDOWS\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 10.8.0.1 
11.
Mon Oct 18 13:42:12 2010 Route deletion via IPAPI succeeded [adaptive] 
12.
Mon Oct 18 13:42:12 2010 Closing TUN/TAP interface 
13.
Mon Oct 18 13:42:12 2010 SIGTERM[hard,init_instance] received, process exiting
Das ist doch nicht normal !?
Bitte warten ..
Mitglied: aqui
18.10.2010, aktualisiert 18.10.2012
Deine Gateway IP ist nicht eindeutig Warning: route gateway is ambiguous: 192.168.73.1 Irgendwas stimmt bei deiner IP Adressierung nicht !
Ist auch kein Wunder denn in der Server Konfig fehlt das server <ip_adr> <maske> Kommando !
DAS ist die Gateway IP des OpenVPN Servers im Tunnel ! der hat die .1 und diese IP ist im Gateway Komando anzugeben.
Als Leitfaden hilft dir ggf. dieses Tutorial:
http://www.administrator.de/wissen/openvpn-server-installieren-auf-dd-w ...
Die Konfig Schritte sind HW unabhängig bei OpenVPN.
Bitte warten ..
Mitglied: Zoom78
18.10.2010 um 19:32 Uhr
Meinst du Zeilen 65 bis 72? Wenn ich dort den Semikolon rausnehme und die IP des Server ( Internet IP - 214.xx.xxx.xx ) und dahinter die Maske 255.255.255.0 schreibe, dann startet OpenVPN Service nicht mehr. In /var/log/messages steht dann folgendes:

01.
Options error: --server directive network/netmask combination is invalid
Zudem muss ich statt tap auf tun ändern und das server-bridging auskomentieren.
Bitte warten ..
Mitglied: Zoom78
18.10.2010 um 20:30 Uhr
Ich glaube, ich weiß wieso wir aneinander vorbeireden - anscheinend.

Ich möchte nicht nur über das Internet auf einen Server über ein Tunell zugreifen. Ich möchte folgendes:

mein Notebook ---> Tunell durch das Internet ---> Server ---> ins WWW

Ich möchte also durch meinen Server "durchsurfen" und dabei ist mir wichtig, daß ich beim surfen nicht meine akutelle IP des Notebooks, sondern die IP des Servers benutze, als ob ich dort wäre.
Bitte warten ..
Neuester Wissensbeitrag
CPU, RAM, Mainboards

Angetestet: PC Engines APU 3a2 im Rack-Gehäuse

(1)

Erfahrungsbericht von ashnod zum Thema CPU, RAM, Mainboards ...

Ähnliche Inhalte
Netzwerkgrundlagen
gelöst Heimnetzwerk über Server im Internet und OpenVPN erreichbar machen (16)

Frage von byt0xm zum Thema Netzwerkgrundlagen ...

Linux Netzwerk
OpenVPN, zwei OpenWRT Router verbinden und VLAN durchs VPN leiten (6)

Frage von sharbich zum Thema Linux Netzwerk ...

Router & Routing
Vlan Verbindungsproblem mit WLAN Bridge (6)

Frage von MackDaddy zum Thema Router & Routing ...

Router & Routing
Eine Steuerung hinter dem OpenVPN Client erreichen (15)

Frage von cannonball zum Thema Router & Routing ...

Heiß diskutierte Inhalte
Switche und Hubs
Trunk für 2xCisco Switch. Wo liegt der Fehler? (14)

Frage von JayyyH zum Thema Switche und Hubs ...

DSL, VDSL
DSL-Signal bewerten (13)

Frage von SarekHL zum Thema DSL, VDSL ...

Windows Server
Mailserver auf Windows Server 2012 (9)

Frage von StefanT81 zum Thema Windows Server ...