Open zxcvbnmkl112 opened 11 months ago
This is my code about the handshake:
i follow this step . https://www.ntkernel.com/boringtun-based-wireguard-client-for-windows/
It could be related to the size of the packet not being 100% Wireguard spec:
encrypted_static: &src[40..88], // SIZE u8;32, 88-40 = 48 bytes, seems too big for the spec (32) encrypted_timestamp: &src[88..116], // SIZE u8;12, 116-88 = 28 bytes, seems too big for the spec (12)
It could be related to the size of the packet not being 100% Wireguard spec:
encrypted_static: &src[40..88], // SIZE u8;32, 88-40 = 48 bytes, seems too big for the spec (32) encrypted_timestamp: &src[88..116], // SIZE u8;12, 116-88 = 28 bytes, seems too big for the spec (12)
Is there something wrong with my handshake data? How do I deal with this? Thank you for your reply。
I am afraid you need to do the analysis yourself. It may be related to handshake field length, but this is for you to find out...
Hi!
client: windows 10 server : centos 9
I used wireguard.exe and the allowed IP is 8.8.8.8.When I ping 8.8.8.8, I find that the original ICMP packet size is 60bit. 64bit after being encrypted by wireguard.
When I use wireguard_write, I find that it is still 60bit after encryption, and my server is not responding to the package.
My IP packet processing flow: 1.use windivert to get the IP package (60bit)