How to capture Wireshark logs for OpenVPN client-server setup? #279
Replies: 3 comments 2 replies
-
if client and server talk to each other inside the WSL instance, you will not see anything when looking on the outside ("there is nothing to see"). But even then, looking at the packets is not what will make you understand how openvpn works - these are encrypted, so you'll see a TLS handshake (which is not that different from a web server TCP handshake) and then "encrypted packets". |
Beta Was this translation helpful? Give feedback.
-
you see connection attempts in your wireshark and icmp rejects because nothing is listening on the other side. IT seems you need to fix your VPN setup first. This wireshark dump does not match a fine running client. And we are not expert in this strange setup. As a sidenote, with tls-crypt-v2 active you will not see much anyway as it using symmetric outer encryption. See openvpn manpage. |
Beta Was this translation helpful? Give feedback.
-
Hello All, as a workaround I have installed wirehshark in my WSL ubuntu distro, and I'm able to capture the packets, not sure why windows hyper-v interface does not capture all the traffic, closing the discussion for now. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello All,
Execution steps
Expectations
I need to learn how OpenVPN works and this is one of the way in which (per my understanding
till now) that will help me to learn the connection process.
note:
When I change my client ip to some other ip (which will fail intentionally) I do see 'OpenVPN' packets which fail.
I want to capture the entire connection process of client connecting to server
(if possible with TLS decoded)
Beta Was this translation helpful? Give feedback.
All reactions