Quote from: nero355 on February 04, 2026, 06:57:01 PM- Multi CPU a.k.a. Multi Core Support.
- Single-threaded vs. Multi-threaded Support.
Quotethere are always multiple threads within any application that is just one big single thread,
Quote from: Patrick M. Hausen on February 04, 2026, 02:43:10 PMIf "Home" is the name of your interface then "Home address" is all addresses assigned to that interface, not only the "primary" one configured in the interface setup form.
Quote from: adv on February 04, 2026, 06:50:45 PMFrom my local Windows 11 computer:Who is this IP address ?
Local network:ping -n 1 192.168.1.24
Pinging 192.168.1.24 with 32 bytes of data:
Reply from 192.168.1.24: bytes=32 time=22ms TTL=64
Ping statistics for 192.168.1.24:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 22ms, Average = 22ms
QuoteRemote netowrk:This is the subnet on the OpenVPN connection and the IP address of the Remote Desktop PC ?!ping -n 1 192.168.90.17
Pinging 192.168.90.17 with 32 bytes of data:
Reply from 192.168.90.17: bytes=32 time=23ms TTL=63
Ping statistics for 192.168.90.17:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 23ms, Average = 23ms
QuoteInternet:You ping without DNS resolving, but is the VPN active ? On which Client/Server ?ping -n 1 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=19ms TTL=114
Ping statistics for 8.8.8.8:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 19ms, Average = 19ms
QuotePing of local network, remote network, and Google get quick replies. So, there is some Internet connectivity but I am still unable to browse.On the Remote Desktop PC or your Local PC ?
Quotetracert 8.8.8.8
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 12 ms 10 ms 10.61.193.35
3 12 ms 13 ms 10 ms 162.151.216.241
4 12 ms 9 ms 18 ms po-2-rur201.exeter.nh.boston.comcast.net [68.86.224.229]
5 38 ms 19 ms 124 ms po-200-xar01.exeter.nh.boston.comcast.net [96.110.22.29]
6 109 ms 16 ms 23 ms be-301-arsc1.needham.ma.boston.comcast.net [162.151.150.125]
7 23 ms 28 ms 18 ms 96.110.42.9
8 25 ms 22 ms 20 ms 96.110.34.26
9 * * * Request timed out.
10 25 ms 18 ms 19 ms 142.251.225.89
11 25 ms 19 ms 21 ms 142.251.60.235
12 20 ms 18 ms 18 ms dns.google [8.8.8.8]
Trace complete.Who is : 2 10 ms 12 ms 10 ms 10.61.193.35Exactly ?Quotenslookup 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 207.172.3.9
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-outThis should tell you dns.google as answer, but usually you nslookup opnsense.org for example and then it gives you an IP address.Quote from: adv on February 04, 2026, 06:50:45 PMAgain, not sure what this really means for me.I would say you have no DNS Server on the OpenVPN connection ?
Quote from: OPNenthu on February 04, 2026, 06:33:03 PMIDS/IDP is CPU bound and in many cases they are single-threaded applications.I am 100% sure Suricata has a config option where you assign the amount of Cores/CPU's it is allowed to use : Ubiquiti made a mess with that one on their UniFi UDM models :P
Quote from: nero355 on February 04, 2026, 05:50:53 PMWhat did ping/tracert/traceroute/nslookup/dig had to say about this ?? ;)
ping -n 1 192.168.1.24
Pinging 192.168.1.24 with 32 bytes of data:
Reply from 192.168.1.24: bytes=32 time=22ms TTL=64
Ping statistics for 192.168.1.24:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 22ms, Average = 22msping -n 1 192.168.90.17
Pinging 192.168.90.17 with 32 bytes of data:
Reply from 192.168.90.17: bytes=32 time=23ms TTL=63
Ping statistics for 192.168.90.17:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 23ms, Average = 23msping -n 1 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=19ms TTL=114
Ping statistics for 8.8.8.8:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 19ms, Average = 19mstracert 8.8.8.8
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 12 ms 10 ms 10.61.193.35
3 12 ms 13 ms 10 ms 162.151.216.241
4 12 ms 9 ms 18 ms po-2-rur201.exeter.nh.boston.comcast.net [68.86.224.229]
5 38 ms 19 ms 124 ms po-200-xar01.exeter.nh.boston.comcast.net [96.110.22.29]
6 109 ms 16 ms 23 ms be-301-arsc1.needham.ma.boston.comcast.net [162.151.150.125]
7 23 ms 28 ms 18 ms 96.110.42.9
8 25 ms 22 ms 20 ms 96.110.34.26
9 * * * Request timed out.
10 25 ms 18 ms 19 ms 142.251.225.89
11 25 ms 19 ms 21 ms 142.251.60.235
12 20 ms 18 ms 18 ms dns.google [8.8.8.8]
Trace complete.nslookup 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 207.172.3.9
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out