limpens
commented
2 years ago I have got a use case, in which the power of the esp32 can (and will) be cut by external means and the esp32 is not able to properly close the wireguard connection.
Due to this, it might take up to 180 seconds for the esp32 to be able to setup a wireguard connection. This is -as far as the documentation of the wireguard I read explains- normal behavior.
Perhaps you should have more patience and wait for several minutes for the connection to complete.
https://www.wireguard.com/papers/wireguard.pdf
Paragraph 6.1
Regards, Eric
On Sat, Jul 9, 2022, 15:01 Simone Rossetto @.***> wrote:
Hello trombik, I'm facing this odd behavior: if the esp device looses its main network for whatever reason (reboot, link error, wifi change, etc), it cannot reconnect to the wireguard server. In the dmesg I see "Invalid handshake initiation from ww.ww.ww.ww:kkkkk" (either if the source IP is the same or not).
In order to have the device connected again I need to remove the peer from server with wg set wg0 peer AAAABBBB....FFFF= remove and re-add it.
It looks like a server-side bug but I don't have such behavior with other peers (all Linux peers).
When the esp device looses the main connection I see the following in dmesg of the server:
wireguard: wg0: Retrying handshake with peer 97 (xx.xx.xx.xx:yyyyy) because we stopped hearing back after 15 seconds wireguard: wg0: Sending handshake initiation to peer 97 (xx.xx.xx.xx:yyyyy) wireguard: wg0: Handshake for peer 97 (xx.xx.xx.xx:yyyyy) did not complete after 5 seconds, retrying (try 2) wireguard: wg0: Sending handshake initiation to peer 97 (xx.xx.xx.xx:yyyyy) wireguard: wg0: Handshake for peer 97 (xx.xx.xx.xx:yyyyy) did not complete after 5 seconds, retrying (try 3) wireguard: wg0: Sending handshake initiation to peer 97 (xx.xx.xx.xx:yyyyy) wireguard: wg0: Handshake for peer 97 (xx.xx.xx.xx:yyyyy) did not complete after 5 seconds, retrying (try 4) [...]
When the esp device is online again and starts the handshake I see:
wireguard: wg0: Retrying handshake with peer 97 (xx.xx.xx.xx:yyyyy) because we stopped hearing back after 15 seconds wireguard: wg0: Handshake for peer 97 (xx.xx.xx.xx:yyyyy) did not complete after 5 seconds, retrying (try 2) wireguard: wg0: Sending handshake initiation to peer 97 (xx.xx.xx.xx:yyyyy) wireguard: wg0: Handshake for peer 97 (xx.xx.xx.xx:yyyyy) did not complete after 5 seconds, retrying (try 4) wireguard: wg0: Invalid handshake initiation from ww.ww.ww.ww:kkkkk wireguard: wg0: Handshake for peer 97 (xx.xx.xx.xx:yyyyy) did not complete after 5 seconds, retrying (try 5) wireguard: wg0: Sending handshake initiation to peer 97 (xx.xx.xx.xx:yyyyy) wireguard: wg0: Retrying handshake with peer 97 (xx.xx.xx.xx:yyyyy) because we stopped hearing back after 15 seconds wireguard: wg0: Invalid handshake initiation from ww.ww.ww.ww:kkkkk wireguard: wg0: Handshake for peer 97 (xx.xx.xx.xx:yyyyy) did not complete after 5 seconds, retrying (try 2) wireguard: wg0: Sending handshake initiation to peer 97 (xx.xx.xx.xx:yyyyy) wireguard: wg0: Invalid handshake initiation from ww.ww.ww.ww:kkkkk [...]
ad so on, being xx.xx.xx.xx and ww.ww.ww.ww the same IP or not.
If you need more information or tests feel free to ask, I'll do my best to support you.
— Reply to this email directly, view it on GitHub https://github.com/trombik/esp_wireguard/issues/29, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALNYC75SMHF6H74N3COOF43VTFZYZANCNFSM53DLFKDA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
trombik
droscy
ChSotiriou
Pecius
nikp123
Hello trombik, I'm facing this odd behavior: if the esp device looses its main network for whatever reason (reboot, link error, wifi change, etc), it cannot reconnect to the wireguard server. In the
dmesgI see "Invalid handshake initiation from ww.ww.ww.ww:kkkkk" (either if the source IP is the same or not).In order to have the device connected again I need to remove the peer from server with
wg set wg0 peer AAAABBBB....FFFF= removeand re-add it.It looks like a server-side bug but I don't have such behavior with other peers (all Linux peers).
When the esp device looses the main connection I see the following in
dmesgof the server:When the esp device is online again and starts the handshake I see:
ad so on, being
xx.xx.xx.xxandww.ww.ww.wwthe same IP or not.If you need more information or tests feel free to ask, I'll do my best to support you.