Ok thank you!

Im a little knowledgeable with this stuff but i do not know how to see the “handshake” itself, but maybe this is synonymous with what i am doing:

Right click any of the packets (TCP or SSH) > Follow > TCP stream

From there i can see some info about the ssh protocol and connection, as well as the 2 devices communicating (Operating systems used) followed by random gibberish which is the encrypted data.

When I analyze the TCP packet “frames”, they contain data including the motherboard manufacturer, but packets themselves look like its just gibberish.

Thanks by the way for trying to help me :)

It looks like everything is in 1 stream, maybe that answers your question? I am capturing traffic only on port 22 briefly while the rsync is running to look at the packets

The only thing missing is a random arrow

Only way is to run to Lichess

I figured its another black box hell like a google meets or something similar where itll try to grab any detail, data or info about what i am connecting with, and also how trustworthy the E2E encryption is if its proprietary

Thank you both

Awesome now I understand what you and the other commenter were talking about with aliasing. Well this works perfect without the alias, many thanks

Well my other comement saying this is exactly what i need did not get posted as a reply to your comment, my mistake. I followed rhe example for “/usr/bin/wg/” intending to be able to use

wg show

but it still requires sudo. I tried rebooting and nothing changed, any ideas? I did

type -a wg

to get the command location for the sudoer file.

Thank you

This does seem to be exactly what i am looking for. I implemented this and tested it and the command still isn’t working yet but i will keep troubleshooting, its probably a silly quirk on my end. Thank you very much!

Thank you for the info! This is very helpful to me.

But the router must forward the port to allow the VPN to be utilized , meaning that port being forwarded can be scanned/detected i thought?

This is the first that I have heard about setting the SSH port to only accept connections from the VPN, is there a term or something I can search about this online? Or is this basically just allowing port 22 open on a device and not forwarding the port on the router as when a different device tunnels into the same network through the VPN it can already talk to the first device?

But wouldn’t the port being open alert anyone who looks for that? Network security is not my specialty but I believe I have read that people can ping/scan ip addresses easily and quickly to determine if any ports are open / forwarded, so if Wireguard was used or any VPN software, they could pick up on that as an attack vector?

I am aware that opening / forwarding ports are attack vectors and they become unavoidable though if i need the vpn and ssh capability, however, in theory the ssh port could be closed/not forwarded if traffic/connection was tunneled through the VPN. Those are my thoughts

Thank you

Both require opening a port but theoretically ssh going through the vpn would mean port 22 does not need to be open/forwarded right, as opposed to both port 22 and whichever for the VPN open?

Thank you for this excellent answer

Honestly i never see any resistance to these kinds of steps forward