Hallo liebe Ubuntu-Users,
seit ein paar Tagen sitze ich an einem Problem und komme nicht weiter und wende mich hiermit an euch:
Ich möchte ein Ubuntu System mit einem Windows PPTP VPN (Unternehmensnetzwerk) verbinden.
Der VPN-Zugang und das Login funktioniert generell.
Nach dem erfolgreichen Connect kann ich jedoch auf keinerlei Ressourcen in meinem lokalen- und im Unternehmensnetzwerk zugreifen.
Nach einigen Recherchen und Analysen konnte ich fest stellen, dass es anscheinend ein Problem mit der Route gibt und ich diese anscheinend manuell selbst hinzufügen muss.
Über VPN über ein Windows System funktioniert problemlos.
Leider kann ich nicht heraus finden, warum Ubuntu die Route nicht automatisch hinzufügen kann.
Die Route selbst hinzufügen habe ich leider auch nicht geschafft und benötige an dieser Stelle Hilfe.
Hier die Daten dazu:
VPN Konfiguration (Über die GUI des Network-Managers konfiguriert):
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | adrian@prometheus:/etc/NetworkManager/system-connections$ sudo cat vpnconnection [connection] id=vpnkonnection uuid=7f7975de-4e3c-437b-9d31-614cdf0b1b8c type=vpn autoconnect=false permissions=user:adrian:; secondaries= timestamp=1498846474 [vpn] password-flags=1 no-vj-comp=yes user=K.Adrian refuse-eap=yes refuse-chap=yes nobsdcomp=yes gateway=91.208.13.21 refuse-mschap=yes refuse-pap=yes nodeflate=yes service-type=org.freedesktop.NetworkManager.pptp [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=ignore } |
IP Configuration ohne VPN Verbindung:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | adrian@prometheus:~$ ifconfig eno1 Link encap:Ethernet HWaddr 74:d4:35:e9:98:01 UP BROADCAST 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 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Memory:f7a00000-f7a20000 enp3s0 Link encap:Ethernet HWaddr 74:d4:35:e9:98:03 inet addr:192.168.178.43 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr: 2a02:810c:c840:3490:76d4:35ff:fee9:9803/64 Scope:Global inet6 addr: fe80::76d4:35ff:fee9:9803/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:106999 errors:0 dropped:0 overruns:0 frame:0 TX packets:51442 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:126148026 (126.1 MB) TX bytes:8297485 (8.2 MB) Interrupt:18 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:2769 errors:0 dropped:0 overruns:0 frame:0 TX packets:2769 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:266186 (266.1 KB) TX bytes:266186 (266.1 KB) |
Routing Tabelle ohne VPN-Verbindung:
1 2 3 4 5 6 | adrian@prometheus:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default fritz.box 0.0.0.0 UG 100 0 0 enp3s0 link-local * 255.255.0.0 U 1000 0 0 enp3s0 192.168.178.0 * 255.255.255.0 U 100 0 0 enp3s0 |
IP Configuration mit VPN Verbindung:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 | adrian@prometheus:~$ ifconfig eno1 Link encap:Ethernet HWaddr 74:d4:35:e9:98:01 UP BROADCAST 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 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Memory:f7a00000-f7a20000 enp3s0 Link encap:Ethernet HWaddr 74:d4:35:e9:98:03 inet addr:192.168.178.43 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr: 2a02:810c:c840:3490:76d4:35ff:fee9:9803/64 Scope:Global inet6 addr: fe80::76d4:35ff:fee9:9803/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:106623 errors:0 dropped:0 overruns:0 frame:0 TX packets:51116 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:126077596 (126.0 MB) TX bytes:8250140 (8.2 MB) Interrupt:18 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:2664 errors:0 dropped:0 overruns:0 frame:0 TX packets:2664 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:257201 (257.2 KB) TX bytes:257201 (257.2 KB) ppp0 Link encap:Point-to-Point Protocol inet addr:150.100.210.236 P-t-P:150.100.254.252 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:68 (68.0 B) TX bytes:4402 (4.4 KB) |
Roting Tabelle mit VPN-Verbindung: adrian@prometheus:~$ route
1 2 3 4 5 6 7 8 | Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default * 0.0.0.0 U 50 0 0 ppp0 default fritz.box 0.0.0.0 UG 100 0 0 enp3s0 021-013-208-091 fritz.box 255.255.255.255 UGH 0 0 0 enp3s0 150.100.254.252 * 255.255.255.255 UH 50 0 0 ppp0 link-local * 255.255.0.0 U 1000 0 0 enp3s0 192.168.178.0 * 255.255.255.0 U 100 0 0 enp3s0 |
syslog bei Verbindungsaufbau:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 | Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.5790] audit: op="connection-activate" uuid="7f7975de-4e3c-437b-9d31-614cdf0b1b8c" name="vpnconnection" pid=4911 uid=1000 result="success" Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.5813] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",0]: Started the VPN service, PID 5248 Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.5849] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",0]: Saw the service appear; activating connection Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.6509] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",0]: VPN connection: (ConnectInteractive) reply received Jun 30 20:11:13 prometheus NetworkManager[951]: ** Message: pppd started with pid 5255 Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.6527] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",0]: VPN plugin: state changed: starting (3) Jun 30 20:11:13 prometheus pppd[5255]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jun 30 20:11:13 prometheus NetworkManager[951]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jun 30 20:11:13 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Jun 30 20:11:13 prometheus pppd[5255]: pppd 2.4.7 started by root, uid 0 Jun 30 20:11:13 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Jun 30 20:11:13 prometheus pppd[5255]: Using interface ppp0 Jun 30 20:11:13 prometheus NetworkManager[951]: Using interface ppp0 Jun 30 20:11:13 prometheus NetworkManager[951]: Connect: ppp0 <--> /dev/pts/1 Jun 30 20:11:13 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Jun 30 20:11:13 prometheus NetworkManager[951]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Jun 30 20:11:13 prometheus pppd[5255]: Connect: ppp0 <--> /dev/pts/1 Jun 30 20:11:13 prometheus pptp[5260]: nm-pptp-service-5248 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.6569] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/5) Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.6602] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Jun 30 20:11:13 prometheus NetworkManager[951]: <info> [1498846273.6602] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Jun 30 20:11:13 prometheus pptp[5273]: nm-pptp-service-5248 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 'Start-Control-Connection-Request' Jun 30 20:11:13 prometheus pptp[5273]: nm-pptp-service-5248 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Jun 30 20:11:13 prometheus pptp[5273]: nm-pptp-service-5248 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Jun 30 20:11:14 prometheus pptp[5273]: nm-pptp-service-5248 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 7 'Outgoing-Call-Request' Jun 30 20:11:14 prometheus pptp[5273]: nm-pptp-service-5248 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Jun 30 20:11:14 prometheus pptp[5273]: nm-pptp-service-5248 log[ctrlp_disp:pptp_ctrl.c:939]: Outgoing call established (call ID 44201, peer's call ID 194). Jun 30 20:11:14 prometheus pptp[5273]: nm-pptp-service-5248 log[logecho:pptp_ctrl.c:719]: Echo Request received. Jun 30 20:11:14 prometheus pptp[5273]: nm-pptp-service-5248 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 6 'Echo-Reply' Jun 30 20:11:14 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' Jun 30 20:11:15 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... Jun 30 20:11:15 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (get_credentials): got credentials from NetworkManager-pptp Jun 30 20:11:15 prometheus pppd[5255]: CHAP authentication succeeded Jun 30 20:11:15 prometheus NetworkManager[951]: CHAP authentication succeeded Jun 30 20:11:15 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network' Jun 30 20:11:15 prometheus pppd[5255]: local IP address 150.100.210.236 Jun 30 20:11:15 prometheus pppd[5255]: remote IP address 150.100.254.252 Jun 30 20:11:15 prometheus NetworkManager[951]: local IP address 150.100.210.236 Jun 30 20:11:15 prometheus NetworkManager[951]: remote IP address 150.100.254.252 Jun 30 20:11:15 prometheus NetworkManager[951]: primary DNS address 150.100.1.200 Jun 30 20:11:15 prometheus NetworkManager[951]: secondary DNS address 150.100.1.201 Jun 30 20:11:15 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 9 / phase 'running' Jun 30 20:11:15 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): ip-up event Jun 30 20:11:15 prometheus NetworkManager[951]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): sending Ip4Config to NetworkManager-pptp... Jun 30 20:11:15 prometheus pppd[5255]: primary DNS address 150.100.1.200 Jun 30 20:11:15 prometheus pppd[5255]: secondary DNS address 150.100.1.201 Jun 30 20:11:15 prometheus NetworkManager[951]: ** Message: PPTP service (IP Config Get) reply received. Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1033] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",0]: VPN connection: (IP4 Config Get) reply received from old-style plugin Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1037] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: VPN Gateway: 91.208.13.21 Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1037] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Tunnel Device: "ppp0" Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1037] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: IPv4 configuration: Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1037] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Internal Address: 150.100.210.236 Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Internal Prefix: 32 Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Internal Point-to-Point Address: 150.100.254.252 Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Maximum Segment Size (MSS): 0 Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Forbid Default Route: no Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Internal DNS: 150.100.1.200 Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: Internal DNS: 150.100.1.201 Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: DNS Domain: '(none)' Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1038] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: Data: No IPv6 configuration Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1039] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: VPN plugin: state changed: started (4) Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1047] vpn-connection[0x270c5e0,7f7975de-4e3c-437b-9d31-614cdf0b1b8c,"vpnconnection",6:(ppp0)]: VPN connection: (IP Config Get) complete Jun 30 20:11:15 prometheus NetworkManager[951]: <info> [1498846275.1070] dns-mgr: Writing DNS information to /sbin/resolvconf Jun 30 20:11:15 prometheus dnsmasq[1121]: setting upstream servers from DBus Jun 30 20:11:15 prometheus dnsmasq[1121]: using nameserver 150.100.1.200#53(via ppp0) Jun 30 20:11:15 prometheus dnsmasq[1121]: using nameserver 150.100.1.200#53 for domain 236.210.100.150.in-addr.arpa Jun 30 20:11:15 prometheus dnsmasq[1121]: using nameserver 150.100.1.201#53 for domain 236.210.100.150.in-addr.arpa Jun 30 20:11:15 prometheus dnsmasq[1121]: using nameserver 150.100.1.201#53(via ppp0) Jun 30 20:11:15 prometheus dnsmasq[1121]: using nameserver 192.168.178.1#53(via enp3s0) Jun 30 20:11:15 prometheus dbus[934]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jun 30 20:11:15 prometheus systemd[1]: Starting Network Manager Script Dispatcher Service... Jun 30 20:11:15 prometheus dbus[934]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jun 30 20:11:15 prometheus systemd[1]: Started Network Manager Script Dispatcher Service. Jun 30 20:11:15 prometheus nm-dispatcher: req:1 'vpn-up' [ppp0]: new request (1 scripts) Jun 30 20:11:15 prometheus nm-dispatcher: req:1 'vpn-up' [ppp0]: start running ordered scripts... Jun 30 20:11:15 prometheus systemd[1]: Reloading OpenBSD Secure Shell server. Jun 30 20:11:15 prometheus systemd[1]: Reloaded OpenBSD Secure Shell server. |
Zum Vergleich ein Windows System:
Route ohne VPN Verbindung:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 | Schnittstellenliste 27...c4 7d 46 16 0b 31 ......Intel(R) Ethernet Connection I218-LM 25...0a 00 27 00 00 19 ......VirtualBox Host-Only Ethernet Adapter #2 12...02 50 f2 00 00 01 ......Citrix Virtual Adapter 3...ac fd ce f2 3a c4 ......Microsoft Wi-Fi Direct Virtual Adapter 29...ac fd ce f2 3a c3 ......Intel(R) Dual Band Wireless-N 7260 1...........................Software Loopback Interface 1 23...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter 24...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 10...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #9 18...84 83 88 5a 47 4a ......EM7305 =========================================================================== IPv4-Routentabelle =========================================================================== Aktive Routen: Netzwerkziel Netzwerkmaske Gateway Schnittstelle Metrik 0.0.0.0 0.0.0.0 192.168.178.1 192.168.178.24 45 127.0.0.0 255.0.0.0 Auf Verbindung 127.0.0.1 331 127.0.0.1 255.255.255.255 Auf Verbindung 127.0.0.1 331 127.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 331 192.168.56.0 255.255.255.0 Auf Verbindung 192.168.56.1 281 192.168.56.1 255.255.255.255 Auf Verbindung 192.168.56.1 281 192.168.56.255 255.255.255.255 Auf Verbindung 192.168.56.1 281 192.168.178.0 255.255.255.0 Auf Verbindung 192.168.178.24 301 192.168.178.24 255.255.255.255 Auf Verbindung 192.168.178.24 301 192.168.178.255 255.255.255.255 Auf Verbindung 192.168.178.24 301 224.0.0.0 240.0.0.0 Auf Verbindung 127.0.0.1 331 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.178.24 301 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.56.1 281 255.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 331 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.178.24 301 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.56.1 281 =========================================================================== Ständige Routen: Keine IPv6-Routentabelle =========================================================================== Aktive Routen: If Metrik Netzwerkziel Gateway 23 331 ::/0 Auf Verbindung 1 331 ::1/128 Auf Verbindung 23 331 2001::/32 Auf Verbindung 23 331 2001:0:9d38:78cf:382d:2587:3f57:4de7/128 Auf Verbindung 25 281 fe80::/64 Auf Verbindung 23 331 fe80::/64 Auf Verbindung 25 281 fe80::1406:1ec5:66d5:708f/128 Auf Verbindung 23 331 fe80::382d:2587:3f57:4de7/128 Auf Verbindung 1 331 ff00::/8 Auf Verbindung 25 281 ff00::/8 Auf Verbindung 23 331 ff00::/8 Auf Verbindung =========================================================================== Ständige Routen: Keine |
IP Config mit VPN Verbindung:
1 2 3 4 5 6 | PPP-Adapter VPN: Verbindungsspezifisches DNS-Suffix: IPv4-Adresse . . . . . . . . . . : 150.100.210.236 Subnetzmaske . . . . . . . . . . : 255.255.255.255 Standardgateway . . . . . . . . . : 0.0.0.0 |
Routing Tabelle mit VPN:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 | Schnittstellenliste 27...c4 7d 46 16 0b 31 ......Intel(R) Ethernet Connection I218-LM 25...0a 00 27 00 00 19 ......VirtualBox Host-Only Ethernet Adapter #2 12...02 50 f2 00 00 01 ......Citrix Virtual Adapter 3...ac fd ce f2 3a c4 ......Microsoft Wi-Fi Direct Virtual Adapter 74...........................VPN 1...........................Software Loopback Interface 1 23...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter 24...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 8...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4 10...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #9 29...ac fd ce f2 3a c3 ......Intel(R) Dual Band Wireless-N 7260 18...84 83 88 5a 47 4a ......EM7305 =========================================================================== IPv4-Routentabelle =========================================================================== Aktive Routen: Netzwerkziel Netzwerkmaske Gateway Schnittstelle Metrik 0.0.0.0 0.0.0.0 192.168.178.1 192.168.178.24 4270 0.0.0.0 0.0.0.0 Auf Verbindung 150.100.210.236 36 91.208.13.21 255.255.255.255 192.168.178.1 192.168.178.24 4271 127.0.0.0 255.0.0.0 Auf Verbindung 127.0.0.1 4556 127.0.0.1 255.255.255.255 Auf Verbindung 127.0.0.1 4556 127.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 4556 150.100.210.236 255.255.255.255 Auf Verbindung 150.100.210.236 291 192.168.56.0 255.255.255.0 Auf Verbindung 192.168.56.1 4506 192.168.56.1 255.255.255.255 Auf Verbindung 192.168.56.1 4506 192.168.56.255 255.255.255.255 Auf Verbindung 192.168.56.1 4506 192.168.178.0 255.255.255.0 Auf Verbindung 192.168.178.24 4526 192.168.178.24 255.255.255.255 Auf Verbindung 192.168.178.24 4526 192.168.178.255 255.255.255.255 Auf Verbindung 192.168.178.24 4526 224.0.0.0 240.0.0.0 Auf Verbindung 127.0.0.1 4556 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.178.24 4526 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.56.1 4506 224.0.0.0 240.0.0.0 Auf Verbindung 150.100.210.236 36 255.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 4556 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.178.24 4526 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.56.1 4506 255.255.255.255 255.255.255.255 Auf Verbindung 150.100.210.236 291 =========================================================================== Ständige Routen: Keine IPv6-Routentabelle =========================================================================== Aktive Routen: If Metrik Netzwerkziel Gateway 1 331 ::1/128 Auf Verbindung 25 281 fe80::/64 Auf Verbindung 25 281 fe80::1406:1ec5:66d5:708f/128 Auf Verbindung 1 331 ff00::/8 Auf Verbindung 25 281 ff00::/8 Auf Verbindung =========================================================================== Ständige Routen: Keine |
Ich hoffe es kann mir mit diesem sehr speziellen Problem jemand weiter helfen.
Vorab vielen Dank für die Unterstützung.