This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ping via SSL VPN zu HPBX Anlage geht nur von manchen Geräten

Hallo, 

komisches Phänomen seit 2 Tagen, hoffe ihr bekomme gut beschrieben, was ich meine.

Wir haben einen Hauptstandort mit diversen Servern, dort laufen auch zwei SG210 mit UTM 9 mit der Firmware Version 9.714-4.
Bei Netcologne haben wir eine Hosted PBX Anlage im Rechenzentrum. Ebenfalls von Netcologne haben wir Cisco Switche, die von Netcologne betreut werden, wo ich auch nicht drauf komme. Sowohl physische Telefone, als auch die Telefonsoftware können sich aus dem Firmennetzwerk heraus mit der HPBX verbinden oder man kann diese testweise auch anpingen.

Kollegen aus dem Homeoffice wählen sich entweder via SSL VPN auf die SG210 ein um dann auf unseren Terminalservern zu arbeiten und via Softphone zu telefonieren oder sie haben eine RED zu Hause stehe, über die Sie dann arbeiten bzw. haben sie dort ein Physisches IP Telefon angeschlossen.

Soweit so gut funktionierte das nun jahrelang so problemlos.

Seit 2 Tagen haben einige Homeoffice User keine Verbindung mehr zur HPBX Anlage, auch ein Ping läuft ins leere.
Es sind sowohl RED als auch Software VPN User betroffen. Arbeiten auf unseren Terminalservern klappt ohne Probleme.

Unsererseits wurde nichts geupdates etc. und Netcologne verweist auf unsere Firewall welche mit Sicherheit ein Problem mit dem Routing hat.

Das Kuriose ist nun, ich wähl mich zu Hause mit 2 Surface Geräten via Software VPN ein.
Mit dem einen kann ich den Hostnamen (oder die IP, geht beides) anpingen, mit dem anderen nicht?

Hat jemand den Ansatz einer Idee, woran das liegen könnte?

Vielen Dank!



This thread was automatically locked due to age.
Parents
  • Can you provide any logs of the connectivity error for VPN?

    (Bitte fahren Sie auf Deutsch fort)

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • There is no connectivity error. Only the Ping to an adress in the netcologne data center won`t work.

    Thu Feb 16 07:08:18 2023 OpenVPN 2.5.0 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 6 2020
    Thu Feb 16 07:08:18 2023 Windows version 6.2 (Windows 8 or greater) 64bit
    Thu Feb 16 07:08:18 2023 library versions: OpenSSL 1.1.1e 17 Mar 2020, LZO 2.10
    Enter Management Password:
    Thu Feb 16 07:08:18 2023 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
    Thu Feb 16 07:08:18 2023 Need hold release from management interface, waiting...
    Thu Feb 16 07:08:19 2023 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'state on'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'log all on'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'echo all on'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'bytecount 5'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'hold off'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'hold release'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'username "Auth" martin.lenz'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'password [...]'
    Thu Feb 16 07:08:19 2023 TCP/UDP: Preserving recently used remote address: [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:19 2023 Socket Buffers: R=[65536->65536] S=[65536->65536]
    Thu Feb 16 07:08:19 2023 Attempting to establish TCP connection with [AF_INET]213.168.XXX.XXX:4443 [nonblock]
    Thu Feb 16 07:08:19 2023 MANAGEMENT: >STATE:1676527699,TCP_CONNECT,,,,,,
    Thu Feb 16 07:08:20 2023 TCP connection established with [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:20 2023 TCP_CLIENT link local: (not bound)
    Thu Feb 16 07:08:20 2023 TCP_CLIENT link remote: [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:20 2023 MANAGEMENT: >STATE:1676527700,WAIT,,,,,,
    Thu Feb 16 07:08:20 2023 MANAGEMENT: >STATE:1676527700,AUTH,,,,,,
    Thu Feb 16 07:08:20 2023 TLS: Initial packet from [AF_INET]213.168.XXX.XXX:4443, sid=737297ca 18a56ee4
    Thu Feb 16 07:08:20 2023 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
    Thu Feb 16 07:08:20 2023 VERIFY OK: depth=1, C=de, L=Bonn, O=ImmoConcept Verwaltungsgruppe, CN=ImmoConcept Verwaltungsgruppe VPN CA, emailAddress=administrator@ic-verwaltungsgruppe.de
    Thu Feb 16 07:08:20 2023 VERIFY X509NAME OK: C=de, L=Bonn, O=ImmoConcept Verwaltungsgruppe, CN=utm.ic-verwaltungsgruppe.de, emailAddress=administrator@ic-verwaltungsgruppe.de
    Thu Feb 16 07:08:20 2023 VERIFY OK: depth=0, C=de, L=Bonn, O=ImmoConcept Verwaltungsgruppe, CN=utm.ic-verwaltungsgruppe.de, emailAddress=administrator@ic-verwaltungsgruppe.de
    Thu Feb 16 07:08:20 2023 Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
    Thu Feb 16 07:08:20 2023 [utm.ic-verwaltungsgruppe.de] Peer Connection Initiated with [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:21 2023 MANAGEMENT: >STATE:1676527701,GET_CONFIG,,,,,,
    Thu Feb 16 07:08:21 2023 SENT CONTROL [utm.ic-verwaltungsgruppe.de]: 'PUSH_REQUEST' (status=1)
    Thu Feb 16 07:08:21 2023 PUSH: Received control message: 'PUSH_REPLY,route-gateway 10.242.2.1,route-gateway 10.242.2.1,topology subnet,ping 10,ping-restart 120,route 192.168.58.0 255.255.255.0,route 192.168.54.0 255.255.255.0,route 192.168.59.0 255.255.255.0,route 192.168.70.0 255.255.255.0,route 192.168.56.0 255.255.255.0,route 192.168.10.0 255.255.255.0,route 192.168.30.0 255.255.255.0,route 192.168.57.0 255.255.255.0,route 172.31.5.0 255.255.255.240,route 192.168.50.0 255.255.255.0,route 192.168.53.0 255.255.255.0,route 192.168.60.0 255.255.255.0,route 192.168.51.0 255.255.255.0,dhcp-option DNS 192.168.10.253,dhcp-option DOMAIN icgruppe.local,ifconfig 10.242.2.9 255.255.255.0'
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: timers and/or timeouts modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: --ifconfig/up options modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: route options modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: route-related options modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Thu Feb 16 07:08:21 2023 Outgoing Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key
    Thu Feb 16 07:08:21 2023 Outgoing Data Channel: Using 256 bit message hash 'SHA256' for HMAC authentication
    Thu Feb 16 07:08:21 2023 Incoming Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key
    Thu Feb 16 07:08:21 2023 Incoming Data Channel: Using 256 bit message hash 'SHA256' for HMAC authentication
    Thu Feb 16 07:08:21 2023 interactive service msg_channel=572
    Thu Feb 16 07:08:21 2023 ROUTE_GATEWAY 192.168.178.1/255.255.255.0 I=2 HWADDR=2c:f0:5d:d3:93:b5
    Thu Feb 16 07:08:21 2023 open_tun
    Thu Feb 16 07:08:21 2023 tap-windows6 device [Ethernet 2] opened
    Thu Feb 16 07:08:21 2023 TAP-Windows Driver Version 1.0
    Thu Feb 16 07:08:21 2023 Set TAP-Windows TUN subnet mode network/local/netmask = 10.242.2.0/10.242.2.9/255.255.255.0 [SUCCEEDED]
    Thu Feb 16 07:08:21 2023 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.242.2.9/255.255.255.0 on interface {3BCD04A2-AEF7-41BC-9753-EC44AB43DB31} [DHCP-serv: 10.242.2.254, lease-time: 31536000]
    Thu Feb 16 07:08:21 2023 Successful ARP Flush on interface [6] {3BCD04A2-AEF7-41BC-9753-EC44AB43DB31}
    Thu Feb 16 07:08:22 2023 MANAGEMENT: >STATE:1676527702,ASSIGN_IP,,10.242.2.9,,,,
    Thu Feb 16 07:08:26 2023 TEST ROUTES: 14/14 succeeded len=14 ret=1 a=0 u/d=up
    Thu Feb 16 07:08:26 2023 MANAGEMENT: >STATE:1676527706,ADD_ROUTES,,,,,,
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 213.168.XXX.XXX MASK 255.255.255.255 192.168.178.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.58.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.54.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.59.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.70.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.56.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.10.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.30.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.57.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 172.31.5.0 MASK 255.255.255.240 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.50.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.53.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.60.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.51.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 Initialization Sequence Completed
    Thu Feb 16 07:08:26 2023 MANAGEMENT: >STATE:1676527706,CONNECTED,SUCCESS,10.242.2.9,213.168.XXX.XXX,4443,192.168.178.76,50217

Reply
  • There is no connectivity error. Only the Ping to an adress in the netcologne data center won`t work.

    Thu Feb 16 07:08:18 2023 OpenVPN 2.5.0 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 6 2020
    Thu Feb 16 07:08:18 2023 Windows version 6.2 (Windows 8 or greater) 64bit
    Thu Feb 16 07:08:18 2023 library versions: OpenSSL 1.1.1e 17 Mar 2020, LZO 2.10
    Enter Management Password:
    Thu Feb 16 07:08:18 2023 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
    Thu Feb 16 07:08:18 2023 Need hold release from management interface, waiting...
    Thu Feb 16 07:08:19 2023 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'state on'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'log all on'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'echo all on'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'bytecount 5'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'hold off'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'hold release'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'username "Auth" martin.lenz'
    Thu Feb 16 07:08:19 2023 MANAGEMENT: CMD 'password [...]'
    Thu Feb 16 07:08:19 2023 TCP/UDP: Preserving recently used remote address: [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:19 2023 Socket Buffers: R=[65536->65536] S=[65536->65536]
    Thu Feb 16 07:08:19 2023 Attempting to establish TCP connection with [AF_INET]213.168.XXX.XXX:4443 [nonblock]
    Thu Feb 16 07:08:19 2023 MANAGEMENT: >STATE:1676527699,TCP_CONNECT,,,,,,
    Thu Feb 16 07:08:20 2023 TCP connection established with [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:20 2023 TCP_CLIENT link local: (not bound)
    Thu Feb 16 07:08:20 2023 TCP_CLIENT link remote: [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:20 2023 MANAGEMENT: >STATE:1676527700,WAIT,,,,,,
    Thu Feb 16 07:08:20 2023 MANAGEMENT: >STATE:1676527700,AUTH,,,,,,
    Thu Feb 16 07:08:20 2023 TLS: Initial packet from [AF_INET]213.168.XXX.XXX:4443, sid=737297ca 18a56ee4
    Thu Feb 16 07:08:20 2023 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
    Thu Feb 16 07:08:20 2023 VERIFY OK: depth=1, C=de, L=Bonn, O=ImmoConcept Verwaltungsgruppe, CN=ImmoConcept Verwaltungsgruppe VPN CA, emailAddress=administrator@ic-verwaltungsgruppe.de
    Thu Feb 16 07:08:20 2023 VERIFY X509NAME OK: C=de, L=Bonn, O=ImmoConcept Verwaltungsgruppe, CN=utm.ic-verwaltungsgruppe.de, emailAddress=administrator@ic-verwaltungsgruppe.de
    Thu Feb 16 07:08:20 2023 VERIFY OK: depth=0, C=de, L=Bonn, O=ImmoConcept Verwaltungsgruppe, CN=utm.ic-verwaltungsgruppe.de, emailAddress=administrator@ic-verwaltungsgruppe.de
    Thu Feb 16 07:08:20 2023 Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
    Thu Feb 16 07:08:20 2023 [utm.ic-verwaltungsgruppe.de] Peer Connection Initiated with [AF_INET]213.168.XXX.XXX:4443
    Thu Feb 16 07:08:21 2023 MANAGEMENT: >STATE:1676527701,GET_CONFIG,,,,,,
    Thu Feb 16 07:08:21 2023 SENT CONTROL [utm.ic-verwaltungsgruppe.de]: 'PUSH_REQUEST' (status=1)
    Thu Feb 16 07:08:21 2023 PUSH: Received control message: 'PUSH_REPLY,route-gateway 10.242.2.1,route-gateway 10.242.2.1,topology subnet,ping 10,ping-restart 120,route 192.168.58.0 255.255.255.0,route 192.168.54.0 255.255.255.0,route 192.168.59.0 255.255.255.0,route 192.168.70.0 255.255.255.0,route 192.168.56.0 255.255.255.0,route 192.168.10.0 255.255.255.0,route 192.168.30.0 255.255.255.0,route 192.168.57.0 255.255.255.0,route 172.31.5.0 255.255.255.240,route 192.168.50.0 255.255.255.0,route 192.168.53.0 255.255.255.0,route 192.168.60.0 255.255.255.0,route 192.168.51.0 255.255.255.0,dhcp-option DNS 192.168.10.253,dhcp-option DOMAIN icgruppe.local,ifconfig 10.242.2.9 255.255.255.0'
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: timers and/or timeouts modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: --ifconfig/up options modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: route options modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: route-related options modified
    Thu Feb 16 07:08:21 2023 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Thu Feb 16 07:08:21 2023 Outgoing Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key
    Thu Feb 16 07:08:21 2023 Outgoing Data Channel: Using 256 bit message hash 'SHA256' for HMAC authentication
    Thu Feb 16 07:08:21 2023 Incoming Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key
    Thu Feb 16 07:08:21 2023 Incoming Data Channel: Using 256 bit message hash 'SHA256' for HMAC authentication
    Thu Feb 16 07:08:21 2023 interactive service msg_channel=572
    Thu Feb 16 07:08:21 2023 ROUTE_GATEWAY 192.168.178.1/255.255.255.0 I=2 HWADDR=2c:f0:5d:d3:93:b5
    Thu Feb 16 07:08:21 2023 open_tun
    Thu Feb 16 07:08:21 2023 tap-windows6 device [Ethernet 2] opened
    Thu Feb 16 07:08:21 2023 TAP-Windows Driver Version 1.0
    Thu Feb 16 07:08:21 2023 Set TAP-Windows TUN subnet mode network/local/netmask = 10.242.2.0/10.242.2.9/255.255.255.0 [SUCCEEDED]
    Thu Feb 16 07:08:21 2023 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.242.2.9/255.255.255.0 on interface {3BCD04A2-AEF7-41BC-9753-EC44AB43DB31} [DHCP-serv: 10.242.2.254, lease-time: 31536000]
    Thu Feb 16 07:08:21 2023 Successful ARP Flush on interface [6] {3BCD04A2-AEF7-41BC-9753-EC44AB43DB31}
    Thu Feb 16 07:08:22 2023 MANAGEMENT: >STATE:1676527702,ASSIGN_IP,,10.242.2.9,,,,
    Thu Feb 16 07:08:26 2023 TEST ROUTES: 14/14 succeeded len=14 ret=1 a=0 u/d=up
    Thu Feb 16 07:08:26 2023 MANAGEMENT: >STATE:1676527706,ADD_ROUTES,,,,,,
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 213.168.XXX.XXX MASK 255.255.255.255 192.168.178.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.58.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.54.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.59.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.70.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.56.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.10.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.30.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.57.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 172.31.5.0 MASK 255.255.255.240 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.50.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.53.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.60.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 C:\WINDOWS\system32\route.exe ADD 192.168.51.0 MASK 255.255.255.0 10.242.2.1
    Thu Feb 16 07:08:26 2023 Route addition via service succeeded
    Thu Feb 16 07:08:26 2023 Initialization Sequence Completed
    Thu Feb 16 07:08:26 2023 MANAGEMENT: >STATE:1676527706,CONNECTED,SUCCESS,10.242.2.9,213.168.XXX.XXX,4443,192.168.178.76,50217

Children
No Data