My goal is to setup openvpn Daemon on a DD-WRT V24SP2 right: for ping and reach networks behind a WAN.
But after I connected to the wan 192.168.0.9 (Remote IP) I cannot reach the LAN behind 192.168.103.0/24.
The structure
10.8.1.0 (OpenVPN daemon)
192.168.0.11 connects to -> 192.168.0.9 -> 192.168.103.0/24
Client Routes:
C:\Windows\system32>route print
===========================================================================
Schnittstellenliste
18...00 ff 8b be 60 22 ......TAP-Windows Adapter V9
14...00 1b 77 05 78 ae ......Intel(R) PRO/Wireless 3945ABG-Netzwerkverbindung
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft-ISATAP-Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
31...00 00 00 00 00 00 00 e0 Microsoft-ISATAP-Adapter #5
28...00 00 00 00 00 00 00 e0 Microsoft-ISATAP-Adapter #6
33...00 00 00 00 00 00 00 e0 Microsoft-ISATAP-Adapter #7
===========================================================================
IPv4-Routentabelle
===========================================================================
Aktive Routen:
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Metrik
0.0.0.0 0.0.0.0 192.168.103.1 192.168.103.85 25
127.0.0.0 255.0.0.0 Auf Verbindung 127.0.0.1 306
127.0.0.1 255.255.255.255 Auf Verbindung 127.0.0.1 306
127.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 306
192.168.103.0 255.255.255.0 Auf Verbindung 192.168.103.85 281
192.168.103.85 255.255.255.255 Auf Verbindung 192.168.103.85 281
192.168.103.255 255.255.255.255 Auf Verbindung 192.168.103.85 281
224.0.0.0 240.0.0.0 Auf Verbindung 127.0.0.1 306
224.0.0.0 240.0.0.0 Auf Verbindung 192.168.103.85 281
255.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 306
255.255.255.255 255.255.255.255 Auf Verbindung 192.168.103.85 281
===========================================================================
Ständige Routen:
Keine
IPv6-Routentabelle
===========================================================================
Aktive Routen:
If Metric Destination Gateway
13 58 ::/0 Auf Verbindung
1 306 ::1/128 Auf Verbindung
13 58 2001::/32 Auf Verbindung
13 306 2001:0:9d38:953c:34ac:1b85:e0ed:9a62/128
Auf Verbindung
14 281 fe80::/64 Auf Verbindung
13 306 fe80::/64 Auf Verbindung
13 306 fe80::34ac:1b85:e0ed:9a62/128
Auf Verbindung
14 281 fe80::c8df:c7d7:1eb7:a740/128
Auf Verbindung
1 306 ff00::/8 Auf Verbindung
13 306 ff00::/8 Auf Verbindung
14 281 ff00::/8 Auf Verbindung
===========================================================================
Staic Routes:
Keine
ipconfig shows:
C:\Windows\system32>ipconfig /all
Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : cb-s-pc
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
Ethernet-Adapter LAN-Verbindung 2:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : TAP-Windows Adapter V9
Physikalische Adresse . . . . . . : 00-FF-8B-BE-60-22
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG-Netzwerkver
bindung
Physikalische Adresse . . . . . . : 00-1B-77-05-78-AE
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::c8df:c7d7:1eb7:a740%14(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.103.85(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Montag, 5. August 2013 17:54:36
Lease läuft ab. . . . . . . . . . : Dienstag, 6. August 2013 17:54:35
Standardgateway . . . . . . . . . : 192.168.103.1
DHCP-Server . . . . . . . . . . . : 192.168.103.1
DHCPv6-IAID . . . . . . . . . . . : 234888055
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-19-5B-3A-6A-00-1B-24-2F-33-A7
DNS-Server . . . . . . . . . . . : 192.168.103.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert
Tunneladapter isatap.{8BBE6022-780D-4288-B6B8-84D102A3DA4A}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter LAN-Verbindung* 13:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:953c:34ac:1b85:e0ed:9a62(Bevo
rzugt)
Verbindungslokale IPv6-Adresse . : fe80::34ac:1b85:e0ed:9a62%13(Bevorzugt)
Standardgateway . . . . . . . . . : ::
NetBIOS über TCP/IP . . . . . . . : Deaktiviert
Tunneladapter Reusable ISATAP Interface {D9D8F001-66A1-4E3E-AE00-AA5F0F332F09}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #5
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter isatap.{0584E89F-172E-496D-8A19-AECC156D002A}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #6
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter Reusable ISATAP Interface {CFBFC6C7-CF04-4D31-8600-735888807310}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #7
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
OpenVPN Client config:
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################
# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client
# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap
#dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
#proto tcp
proto udp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
#remote 2.241.24.120 1194
remote 192.168.0.9 1194
#remote my-server-2 1194
# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random
# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite
# Most clients don't need to bind to
# a specific local port number.
nobind
# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nobody
# Try to preserve some state across restarts.
persist-key
persist-tun
# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]
# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca ca.crt
cert openvpnrmeier.crt
key openvpnrmeier.key
# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
#
http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
ns-cert-type server
# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x
cipher AES-128-CBC
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo
# Set log file verbosity.
verb 4
# Silence repeating messages
;mute 20
#route 192.168.103.0 255.255.255.0
DD-WRT V24 ifconfig:
root@DD-WRT:~# ifconfig
br0 Link encap:Ethernet HWaddr C0:C1:C0:D7:A5:98
inet addr:192.168.103.1 Bcast:192.168.103.255 M ask:255.255.255.0
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1380 errors:0 dropped:0 overruns:0 fra me:0
TX packets:807 errors:0 dropped:0 overruns:0 carr ier:0
collisions:0 txqueuelen:0
RX bytes:175219 (171.1 KiB) TX bytes:121060 (118 .2 KiB)
br0:0 Link encap:Ethernet HWaddr C0:C1:C0:D7:A5:98
inet addr:169.254.255.1 Bcast:169.254.255.255 M ask:255.255.0.0
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
eth0 Link encap:Ethernet HWaddr C0:C1:C0:D7:A5:98
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric: 1
RX packets:3332 errors:0 dropped:0 overruns:0 fra me:0
TX packets:2286 errors:0 dropped:0 overruns:0 car rier:0
collisions:0 txqueuelen:1000
RX bytes:438499 (428.2 KiB) TX bytes:285396 (278 .7 KiB)
Interrupt:4 Base address:0x2000
eth1 Link encap:Ethernet HWaddr C0:C1:C0:D7:A5:9A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame: 154380
TX packets:515 errors:2 dropped:0 overruns:0 carr ier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:104995 (102.5 KiB)
Interrupt:3 Base address:0x1000
eth2 Link encap:Ethernet HWaddr C0:C1:C0:D7:A5:9B
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame: 0
TX packets:0 errors:0 dropped:0 overruns:0 carrie r:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:6 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric: 1
RX packets:45 errors:0 dropped:0 overruns:0 frame :0
TX packets:45 errors:0 dropped:0 overruns:0 carri er:0
collisions:0 txqueuelen:0
RX bytes:4347 (4.2 KiB) TX bytes:4347 (4.2 KiB)
tap0 Link encap:Ethernet HWaddr 00:FF:98:B9:9F:4D
inet addr:10.8.1.1 Bcast:10.8.1.255 Mask:255.25 5.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric: 1
RX packets:158 errors:0 dropped:0 overruns:0 fram e:0
TX packets:0 errors:0 dropped:0 overruns:0 carrie r:0
collisions:0 txqueuelen:100
RX bytes:6466 (6.3 KiB) TX bytes:0 (0.0 B)
vlan1 Link encap:Ethernet HWaddr C0:C1:C0:D7:A5:98
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric: 1
RX packets:1384 errors:0 dropped:0 overruns:0 fra me:0
TX packets:807 errors:0 dropped:0 overruns:0 carr ier:0
collisions:0 txqueuelen:0
RX bytes:181571 (177.3 KiB) TX bytes:124288 (121 .3 KiB)
vlan2 Link encap:Ethernet HWaddr C0:C1:C0:D7:A5:99
inet addr:192.168.0.9 Bcast:192.168.0.255 Mask: 255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric: 1
RX packets:1948 errors:0 dropped:0 overruns:0 fra me:0
TX packets:1479 errors:0 dropped:0 overruns:0 car rier:0
collisions:0 txqueuelen:0
RX bytes:196952 (192.3 KiB) TX bytes:161108 (157 .3 KiB)
Route shows:
root@DD-WRT:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.1 * 255.255.255.255 UH 0 0 0 vlan2
192.168.103.0 * 255.255.255.0 U 0 0 0 br0
10.8.1.0 * 255.255.255.0 U 0 0 0 tap0
192.168.0.0 * 255.255.255.0 U 0 0 0 vlan2
169.254.0.0 * 255.255.0.0 U 0 0 0 br0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.0.1 0.0.0.0 UG 0 0 0 vlan2
iptables list:
root@DD-WRT:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- 10.8.0.0/16 anywhere
ACCEPT 0 -- 192.168.0.0/16 anywhere
ACCEPT tcp -- anywhere anywhere tcp dpt:1194
DROP tcp -- anywhere anywhere tcp dpt:webcache
DROP tcp -- anywhere anywhere tcp dpt:www
DROP tcp -- anywhere anywhere tcp dpt:https
LOG 0 -- anywhere anywhere limit: avg 5/min burst 5 LOG level debug prefix `iptables denied: '
DROP tcp -- anywhere anywhere tcp dpt:69
DROP tcp -- anywhere anywhere tcp dpt:ssh
DROP tcp -- anywhere anywhere tcp dpt:ssh
DROP tcp -- anywhere anywhere tcp dpt:telnet
DROP tcp -- anywhere anywhere tcp dpt:telnet
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- 192.168.0.0/16 anywhere
ACCEPT 0 -- 10.8.0.0/16 anywhere
ACCEPT 0 -- 10.8.0.0/24 anywhere
ACCEPT 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere
ACCEPT 0 -- 10.8.0.0/24 anywhere
ACCEPT 0 -- anywhere anywhere
TCPMSS tcp -- anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU
lan2wan 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere state RELATED,ESTABLISHED
TRIGGER 0 -- anywhere anywhere TRIGGER type:in match:0 relate:0
trigger_out 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere state NEW
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain advgrp_1 (0 references)
target prot opt source destination
Chain advgrp_10 (0 references)
target prot opt source destination
Chain advgrp_2 (0 references)
target prot opt source destination
Chain advgrp_3 (0 references)
target prot opt source destination
Chain advgrp_4 (0 references)
target prot opt source destination
Chain advgrp_5 (0 references)
target prot opt source destination
Chain advgrp_6 (0 references)
target prot opt source destination
Chain advgrp_7 (0 references)
target prot opt source destination
Chain advgrp_8 (0 references)
target prot opt source destination
Chain advgrp_9 (0 references)
target prot opt source destination
Chain grp_1 (0 references)
target prot opt source destination
Chain grp_10 (0 references)
target prot opt source destination
Chain grp_2 (0 references)
target prot opt source destination
Chain grp_3 (0 references)
target prot opt source destination
Chain grp_4 (0 references)
target prot opt source destination
Chain grp_5 (0 references)
target prot opt source destination
Chain grp_6 (0 references)
target prot opt source destination
Chain grp_7 (0 references)
target prot opt source destination
Chain grp_8 (0 references)
target prot opt source destination
Chain grp_9 (0 references)
target prot opt source destination
Chain lan2wan (1 references)
target prot opt source destination
Chain logaccept (0 references)
target prot opt source destination
ACCEPT 0 -- anywhere anywhere
Chain logdrop (0 references)
target prot opt source destination
DROP 0 -- anywhere anywhere
Chain logreject (0 references)
target prot opt source destination
REJECT tcp -- anywhere anywhere tcp reject-with tcp-reset
Chain trigger_out (1 references)
target prot opt source destination
openvpnserver config
push "route 192.168.0.0 255.255.255.0"
server 10.8.0.0 255.255.255.0
dev tun0
#proto tcp
proto udp
keepalive 10 120
dh /tmp/openvpn/dh.pem
ca /tmp/openvpn/ca.crt
cert /tmp/openvpn/cert.pem
key /tmp/openvpn/key.pem
# Only use crl-verify if you are using the revoke list &#-106; otherwise leave it commented out
# crl-verify /tmp/openvpn/ca.crl
# management parameter allows DD-WRT&#-110;s OpenVPN Status web page to access the server&#-110;s management port
# port must be 5001 for scripts embedded in firmware to work
management localhost 5001
cipher AES-128-CBC
Here are pings logged and traceroute:
Jan 1 00:00:49 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=c0:c1:c0:d7:a5:98:98:4b:e1:af:5a:10:08:00 SRC=192.168.103.119 DST=192.168.103.1 LEN=52 TOS=0x00 PREC=0x00 TTL=128 ID=5759 DF PROTO=TCP SPT=26271 DPT=22 WINDOW=16568 RES=0x00 ACK URGP=0
Jan 1 00:00:50 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1b:24:2f:33:a7:08:00:45:00:00:4e SRC=192.168.0.11 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=165 PROTO=UDP SPT=137 DPT=137 LEN=58
Jan 1 00:00:50 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1b:24:2f:33:a7:08:00:45:00:00:4e SRC=192.168.0.11 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=166 PROTO=UDP SPT=137 DPT=137 LEN=58
Jan 1 00:00:51 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=c0:c1:c0:d7:a5:98:98:4b:e1:af:5a:10:08:00 SRC=192.168.103.119 DST=192.168.103.1 LEN=200 TOS=0x00 PREC=0x00 TTL=128 ID=5760 DF PROTO=TCP SPT=26271 DPT=22 WINDOW=16568 RES=0x00 ACK PSH URGP=0
Jan 1 00:00:51 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=c0:c1:c0:d7:a5:98:98:4b:e1:af:5a:10:08:00 SRC=192.168.103.119 DST=192.168.103.1 LEN=52 TOS=0x00 PREC=0x00 TTL=128 ID=5761 DF PROTO=TCP SPT=26271 DPT=22 WINDOW=16531 RES=0x00 ACK URGP=0
Jan 1 00:01:18 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:2a SRC=192.168.0.11 DST=192.168.0.9 LEN=42 TOS=0x00 PREC=0x00 TTL=128 ID=171 PROTO=UDP SPT=53309 DPT=1194 LEN=22
Jan 1 00:01:18 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:32 SRC=192.168.0.11 DST=192.168.0.9 LEN=50 TOS=0x00 PREC=0x00 TTL=128 ID=172 DF PROTO=UDP SPT=53309 DPT=1194 LEN=30
Jan 1 00:01:18 DD-WRT daemon.err openvpn[959]: 192.168.0.11:53309 VERIFY ERROR: depth=1, error=certificate is not yet valid: /C=DE/ST=HH/L=Hamburg/O=advancedsolution/OU=advancedsolution/CN=operations/name=advancedsolution/emailAddress=
info@advancedsolution.de
Jan 1 00:01:18 DD-WRT daemon.err openvpn[959]: 192.168.0.11:53309 TLS_ERROR: BIO read tls_read_plaintext error: error:140890B2:lib(20):func(137):reason(178)
Jan 1 00:01:18 DD-WRT daemon.err openvpn[959]: 192.168.0.11:53309 TLS Error: TLS object -> incoming plaintext read error
Jan 1 00:01:18 DD-WRT daemon.err openvpn[959]: 192.168.0.11:53309 TLS Error: TLS handshake failed
Jan 1 00:01:25 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:8e SRC=192.168.0.11 DST=192.168.0.9 LEN=142 TOS=0x00 PREC=0x00 TTL=128 ID=235 DF PROTO=UDP SPT=53309 DPT=1194 LEN=122
Jan 1 00:01:47 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:8e SRC=192.168.0.11 DST=192.168.0.9 LEN=142 TOS=0x00 PREC=0x00 TTL=128 ID=242 DF PROTO=UDP SPT=53309 DPT=1194 LEN=122
Jan 1 00:01:50 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:8e SRC=192.168.0.11 DST=192.168.0.9 LEN=142 TOS=0x00 PREC=0x00 TTL=128 ID=243 DF PROTO=UDP SPT=53309 DPT=1194 LEN=122
Jan 1 00:02:02 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=c0:c1:c0:d7:a5:98:98:4b:e1:af:5a:10:08:00 SRC=192.168.103.119 DST=192.168.103.1 LEN=104 TOS=0x00 PREC=0x00 TTL=128 ID=5885 DF PROTO=TCP SPT=26271 DPT=22 WINDOW=16416 RES=0x00 ACK PSH URGP=0
Jan 1 00:02:14 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=c0:c1:c0:d7:a5:98:98:4b:e1:af:5a:10:08:00 SRC=192.168.103.119 DST=192.168.103.1 LEN=104 TOS=0x00 PREC=0x00 TTL=128 ID=5912 DF PROTO=TCP SPT=26271 DPT=22 WINDOW=16548 RES=0x00 ACK PSH URGP=0
Aug 5 17:36:02 DD-WRT user.debug syslog: ttraff: data collection started
Aug 5 17:36:02 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53310 Re-using SSL/TLS context
Aug 5 17:36:02 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53310 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53310
Aug 5 17:36:07 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1b:24:2f:33:a7:08:00:45:00:00:4e SRC=192.168.0.11 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=357 PROTO=UDP SPT=137 DPT=137 LEN=58
Aug 5 17:36:06 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=c0:c1:c0:d7:a5:98:98:4b:e1:af:5a:10:08:00 SRC=192.168.103.119 DST=192.168.103.1 LEN=104 TOS=0x00 PREC=0x00 TTL=128 ID=5976 DF PROTO=TCP SPT=26271 DPT=22 WINDOW=16487 RES=0x00 ACK PSH URGP=0
Aug 5 17:36:19 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1b:24:2f:33:a7:08:00:45:00:00:4e SRC=192.168.0.11 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=428 PROTO=UDP SPT=137 DPT=137 LEN=58
Aug 5 17:36:31 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:e3:d0:65:71:08:00 SRC=192.168.103.2 DST=192.168.103.255 LEN=252 TOS=0x00 PREC=0x00 TTL=64 ID=872 PROTO=UDP SPT=138 DPT=138 LEN=232
Aug 5 17:36:46 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=449 DF PROTO=UDP SPT=53310 DPT=1194 LEN=77
Aug 5 17:36:55 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=450 DF PROTO=UDP SPT=53310 DPT=1194 LEN=77
Aug 5 17:37:10 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=452 DF PROTO=UDP SPT=53310 DPT=1194 LEN=77
Aug 5 17:37:21 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=453 PROTO=UDP SPT=53310 DPT=1194 LEN=77
Aug 5 17:37:22 DD-WRT authpriv.notice dropbear[1612]: password auth succeeded for 'root' from 192.168.103.119:26272
Aug 5 17:37:31 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=454 DF PROTO=UDP SPT=53310 DPT=1194 LEN=77
Aug 5 17:37:54 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:2a SRC=192.168.0.11 DST=192.168.0.9 LEN=42 TOS=0x00 PREC=0x00 TTL=128 ID=456 PROTO=UDP SPT=53313 DPT=1194 LEN=22
Aug 5 17:37:54 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53313 Re-using SSL/TLS context
Aug 5 17:37:54 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53313 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53313
Aug 5 17:37:56 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:84 SRC=192.168.0.11 DST=192.168.0.9 LEN=132 TOS=0x00 PREC=0x00 TTL=128 ID=534 DF PROTO=UDP SPT=53313 DPT=1194 LEN=112
Aug 5 17:38:11 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=539 PROTO=UDP SPT=53313 DPT=1194 LEN=77
Aug 5 17:38:27 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=552 DF PROTO=UDP SPT=53313 DPT=1194 LEN=77
Aug 5 17:38:37 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=553 PROTO=UDP SPT=53313 DPT=1194 LEN=77
Aug 5 17:38:48 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=554 DF PROTO=UDP SPT=53313 DPT=1194 LEN=77
Aug 5 17:38:58 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=555 PROTO=UDP SPT=53313 DPT=1194 LEN=77
Aug 5 17:39:12 DD-WRT user.debug kernel: iptables denied: IN=vlan2 OUT= MAC=c0:c1:c0:d7:a5:99:00:1b:24:2f:33:a7:08:00:45:00:00:61 SRC=192.168.0.11 DST=192.168.0.9 LEN=97 TOS=0x00 PREC=0x00 TTL=128 ID=557 DF PROTO=UDP SPT=53313 DPT=1194 LEN=77
Aug 5 17:39:20 DD-WRT user.debug kernel: iptables denied: IN=br0 OUT= MAC=c0:c1:c0:d7:a5:98:98:4b:e1:af:5a:10:08:00 SRC=192.168.103.119 DST=192.168.103.1 LEN=152 TOS=0x00 PREC=0x00 TTL=128 ID=6153 DF PROTO=TCP SPT=26272 DPT=22 WINDOW=16391 RES=0x00 ACK PSH URGP=0
Aug 5 17:39:59 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53314 Re-using SSL/TLS context
Aug 5 17:39:59 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53314 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53314
Aug 5 17:40:37 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53317 Re-using SSL/TLS context
Aug 5 17:40:38 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53317 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53317
Aug 5 17:42:43 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53320 Re-using SSL/TLS context
Aug 5 17:42:43 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53320 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53320
Aug 5 17:44:47 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53321 Re-using SSL/TLS context
Aug 5 17:44:48 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53321 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53321
Aug 5 17:46:52 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53322 Re-using SSL/TLS context
Aug 5 17:46:52 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53322 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53322
Aug 5 17:48:56 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53323 Re-using SSL/TLS context
Aug 5 17:48:56 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53323 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53323
Aug 5 17:51:01 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53324 Re-using SSL/TLS context
Aug 5 17:51:01 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53324 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53324
Aug 5 17:53:06 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53325 Re-using SSL/TLS context
Aug 5 17:53:06 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:53325 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:53325
Aug 5 17:54:42 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:54:52 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:55:02 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:55:12 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:55:22 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:55:32 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:55:42 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:55:52 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:56:03 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:56:13 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:56:23 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:56:33 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:56:43 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:56:53 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:57:03 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:57:14 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:57:24 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:57:34 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:57:44 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:57:54 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:58:04 DD-WRT daemon.err openvpn[959]: read UDPv4 [EHOSTUNREACH]: No route to host (code=148)
Aug 5 17:58:06 DD-WRT daemon.notice openvpn[959]: openvpnrmeier/192.168.0.11:53325 [openvpnrmeier] Inactivity timeout (--ping-restart), restarting
Aug 5 18:05:34 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:55597 Re-using SSL/TLS context
Aug 5 18:05:34 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:55597 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:55597
Aug 5 18:07:38 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60059 Re-using SSL/TLS context
Aug 5 18:07:39 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60059 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:60059
Aug 5 18:09:43 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60060 Re-using SSL/TLS context
Aug 5 18:09:43 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60060 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:60060
Aug 5 18:11:48 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60061 Re-using SSL/TLS context
Aug 5 18:11:48 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60061 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:60061
Aug 5 18:13:52 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60062 Re-using SSL/TLS context
Aug 5 18:13:52 DD-WRT daemon.notice openvpn[959]: 192.168.0.11:60062 [openvpnrmeier] Peer Connection Initiated with 192.168.0.11:60062
Many thanks for every help
