Author
Message
blackout79 DD-WRT Novice Joined: 20 Feb 2021 Posts: 12
Posted: Mon Feb 22, 2021 15:34 Post subject:
Ok muss das nicht verstehen.
Habe eigentlich nichts gemacht.
Nur bei Addional Config nochmal den Text eingegeben und nun mit einmal geht alles.
Kann Internetseiten öffnen.
Muss ich nicht verstehen. Mal sehen wie lange.
Im Status steht nun:
State
Client: CONNECTED SUCCESS
Local Address: 10.203.10.189
Remote Address: 10.203.10.189
Status
VPN Client Stats
TUN/TAP read bytes 3643608
TUN/TAP write bytes 10492219
TCP/UDP read bytes 11455641
TCP/UDP write bytes 4200616
Auth read bytes 10492251
Log
Clientlog:
20210222 16:21:12 W WARNING: 'auth' is used inconsistently local='auth SHA256' remote='auth [null-digest]'
20210222 16:21:12 W WARNING: 'keysize' is used inconsistently local='keysize 256' remote='keysize 128'
20210222 16:21:12 Control Channel: TLSv1.3 cipher TLSv1.3 TLS_AES_256_GCM_SHA384 4096 bit RSA
20210222 16:21:12 I [frankfurt-rack437.nodes.gen4.ninja] Peer Connection Initiated with [AF_INET]84.17.49.236:443
20210222 16:21:13 SENT CONTROL [frankfurt-rack437.nodes.gen4.ninja]: 'PUSH_REQUEST' (status=1)
20210222 16:21:13 PUSH: Received control message: 'PUSH_REPLY redirect-gateway def1 route-ipv6 2000::/3 dhcp-option DNS 10.101.0.243 route-gateway 10.203.10.1 topology subnet ping 10 ping-restart 60 ifconfig 10.203.10.189 255.255.255.0 peer-id 61'
20210222 16:21:13 W WARNING: You have specified redirect-gateway and redirect-private at the same time (or the same option multiple times). This is not well supported and may lead to unexpected results
20210222 16:21:13 OPTIONS IMPORT: timers and/or timeouts modified
20210222 16:21:13 OPTIONS IMPORT: --ifconfig/up options modified
20210222 16:21:13 OPTIONS IMPORT: route options modified
20210222 16:21:13 NOTE: --mute triggered...
20210222 16:21:13 4 variation(s) on previous 3 message(s) suppressed by --mute
20210222 16:21:13 Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
20210222 16:21:13 Outgoing Data Channel: Using 256 bit message hash 'SHA256' for HMAC authentication
20210222 16:21:13 Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
20210222 16:21:13 NOTE: --mute triggered...
20210222 16:21:13 1 variation(s) on previous 3 message(s) suppressed by --mute
20210222 16:21:13 net_route_v4_best_gw query: dst 0.0.0.0
20210222 16:21:13 net_route_v4_best_gw result: via 192.168.178.44 dev eth0
20210222 16:21:13 GDG6: remote_host_ipv6=n/a
20210222 16:21:13 net_route_v6_best_gw query: dst ::
20210222 16:21:13 W sitnl_send: rtnl: generic error (-95): Not supported
20210222 16:21:13 I TUN/TAP device tun1 opened
20210222 16:21:13 do_ifconfig ipv4=1 ipv6=0
20210222 16:21:13 I net_iface_mtu_set: mtu 1500 for tun1
20210222 16:21:13 I net_iface_up: set tun1 up
20210222 16:21:13 I net_addr_v4_add: 10.203.10.189/24 dev tun1
20210222 16:21:18 net_route_v4_add: 84.17.49.236/32 via 192.168.178.44 dev [NULL] table 0 metric -1
20210222 16:21:18 net_route_v4_add: 0.0.0.0/1 via 10.203.10.1 dev [NULL] table 0 metric -1
20210222 16:21:18 net_route_v4_add: 128.0.0.0/1 via 10.203.10.1 dev [NULL] table 0 metric -1
20210222 16:21:18 I WARNING: OpenVPN was configured to add an IPv6 route. However no IPv6 has been configured for tun1 therefore the route installation may fail or may not work as expected.
20210222 16:21:18 I add_route_ipv6(2000::/3 -> :: metric -1) dev tun1
20210222 16:21:18 net_route_v6_add: 2000::/3 via :: dev tun1 table 0 metric -1
20210222 16:21:18 W sitnl_send: rtnl: generic error (-95): Not supported
20210222 16:21:18 W ERROR: Linux IPv6 route can't be added
20210222 16:21:18 I Initialization Sequence Completed
20210222 16:21:25 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:21:25 D MANAGEMENT: CMD 'state'
20210222 16:21:25 MANAGEMENT: Client disconnected
20210222 16:21:25 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:21:25 D MANAGEMENT: CMD 'state'
20210222 16:21:25 MANAGEMENT: Client disconnected
20210222 16:21:25 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:21:25 D MANAGEMENT: CMD 'state'
20210222 16:21:25 MANAGEMENT: Client disconnected
20210222 16:21:25 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:21:25 D MANAGEMENT: CMD 'status 2'
20210222 16:21:25 MANAGEMENT: Client disconnected
20210222 16:21:25 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:21:25 D MANAGEMENT: CMD 'log 500'
20210222 16:21:25 MANAGEMENT: Client disconnected
20210222 16:21:29 N write UDPv4: Message too large (code=90)
20210222 16:21:29 N write UDPv4: Message too large (code=90)
20210222 16:21:29 N write UDPv4: Message too large (code=90)
20210222 16:21:29 NOTE: --mute triggered...
20210222 16:29:42 128 variation(s) on previous 3 message(s) suppressed by --mute
20210222 16:29:42 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:29:42 D MANAGEMENT: CMD 'state'
20210222 16:29:42 MANAGEMENT: Client disconnected
20210222 16:29:43 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:29:43 D MANAGEMENT: CMD 'state'
20210222 16:29:43 MANAGEMENT: Client disconnected
20210222 16:29:43 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:29:43 D MANAGEMENT: CMD 'state'
20210222 16:29:43 MANAGEMENT: Client disconnected
20210222 16:29:43 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:29:43 D MANAGEMENT: CMD 'status 2'
20210222 16:29:43 MANAGEMENT: Client disconnected
20210222 16:29:43 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:29:43 D MANAGEMENT: CMD 'log 500'
20210222 16:29:43 MANAGEMENT: Client disconnected
20210222 16:30:22 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:30:22 D MANAGEMENT: CMD 'state'
20210222 16:30:22 MANAGEMENT: Client disconnected
20210222 16:30:22 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:30:22 D MANAGEMENT: CMD 'state'
20210222 16:30:22 MANAGEMENT: Client disconnected
20210222 16:30:22 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:30:22 D MANAGEMENT: CMD 'state'
20210222 16:30:22 MANAGEMENT: Client disconnected
20210222 16:30:22 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:30:22 D MANAGEMENT: CMD 'status 2'
20210222 16:30:22 MANAGEMENT: Client disconnected
20210222 16:30:22 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:30:22 D MANAGEMENT: CMD 'log 500'
20210222 16:30:22 MANAGEMENT: Client disconnected
20210222 16:32:28 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:32:28 D MANAGEMENT: CMD 'state'
20210222 16:32:28 MANAGEMENT: Client disconnected
20210222 16:32:28 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:32:28 D MANAGEMENT: CMD 'state'
20210222 16:32:28 MANAGEMENT: Client disconnected
20210222 16:32:28 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:32:28 D MANAGEMENT: CMD 'state'
20210222 16:32:28 MANAGEMENT: Client disconnected
20210222 16:32:28 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:32:28 D MANAGEMENT: CMD 'status 2'
20210222 16:32:28 MANAGEMENT: Client disconnected
20210222 16:32:28 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20210222 16:32:28 D MANAGEMENT: CMD 'log 500'
19700101 01:00:00
Description:
Filesize:
145.14 KB
Viewed:
6516 Time(s)
Back to top
Sponsor
egc DD-WRT Guru Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Mon Feb 22, 2021 16:54 Post subject:
Super, dass es jetzt funktioniert.
Aber um Probleme in Zukunft zu vermeiden, ist es besser, alles in Additional Config zu löschen
_________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read): https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Back to top
blackout79 DD-WRT Novice Joined: 20 Feb 2021 Posts: 12
Posted: Tue Feb 23, 2021 8:32 Post subject:
egc wrote: Super, dass es jetzt funktioniert.
Aber um Probleme in Zukunft zu vermeiden, ist es besser, alles in Additional Config zu löschen
Habe ich voll Angst vor Das zu löschen.
Back to top
blackout79 DD-WRT Novice Joined: 20 Feb 2021 Posts: 12
Posted: Tue Feb 23, 2021 8:49 Post subject:
egc wrote: Super, dass es jetzt funktioniert.
Aber um Probleme in Zukunft zu vermeiden, ist es besser, alles in Additional Config zu löschen
Gerade mal gemacht. Alles gelöscht, geht wieder kein Internet.
Bei Status zeigte er mir dann direkt wieder den Fehler:
Client: RECONNECTING process-push-msg-failed
Als ich dann wieder diese Zeilen eingetragen habe, ging es wieder normal:
resolv-retry infinite
redirect-gateway def1
persist-key
persist-tun
nobind
cipher AES-256-CBC
ncp-disable
auth SHA256
ping 5
ping-exit 60
ping-timer-rem
explicit-exit-notify 2
script-security 2
remote-cert-tls server
route-delay 5
verb 4
So nun muss ich nur doch die Smart DNS Einstellungen bei der PS4 hinbekommen.
Denn wenn ich diese bei der PS4 eintrage, bekomme ich immer einen NAT Fehler. Würde mich nicht wundern, wenn dies an Cyberghost liegt.
Aber ich Danke Dir sehr, hier ist wirklich ein sehr freundlicher Umgang.
War auf einen Forum, da kamen erstmal nur blöde Kommentare, statt Hilfe.
Aber hier ist es Mega.
Back to top