)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000002,"name":"cron2","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"9399e69ea847ab3ed2e49e9d7058c2a996b54fcb","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"624fdfbf_208bea35","updated":"2025-09-24 09:55:56.000000000","message":"Is this about `push-reply`, as the commit message says, or about `PUSH_UPDATE`, as the code suggests?","commit_id":"ffcd21b620b82fce60eed0be52076970fc613ec4"},{"author":{"_account_id":1000040,"name":"mrbff","email":"marco@mandelbit.com","username":"mrbff"},"change_message_id":"c2079e5623bde539bbaf8fd387ab3f11d880c432","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b2e2752c_9aa08f47","in_reply_to":"624fdfbf_208bea35","updated":"2025-09-24 10:10:15.000000000","message":"No push-reply is correct, but actually is for push-update too. The bug can be triggered just adding a sequence of remote-ipv4 and remote-ipv6, so if server disconnect, the connection is switched to the next remote and if the family is not the same it can creates some problems.","commit_id":"ffcd21b620b82fce60eed0be52076970fc613ec4"},{"author":{"_account_id":1000002,"name":"cron2","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"8f101364d782b1b7afbf085e9f2cca1b9e94abf1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fe307bd9_3c705f2a","in_reply_to":"b2e2752c_9aa08f47","updated":"2025-09-24 10:11:40.000000000","message":"Can you link to an issue having a full log showing what happens and why this is a problem?  I need to test this before merging, so need to know what to look for.","commit_id":"ffcd21b620b82fce60eed0be52076970fc613ec4"},{"author":{"_account_id":1000002,"name":"cron2","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"270f0e3113714b89fe05820bc34b2a7b816f95ca","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"eca47d34_4f3ef789","in_reply_to":"cf110d4f_14e94564","updated":"2025-10-06 09:17:47.000000000","message":"please do also link to the issue in the commit message (`Github: fixes OpenVPN/openvpn#850`)","commit_id":"ffcd21b620b82fce60eed0be52076970fc613ec4"},{"author":{"_account_id":1000040,"name":"mrbff","email":"marco@mandelbit.com","username":"mrbff"},"change_message_id":"af16a2fc3b9b065fc221f01a110291e974e76efc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"19f9054c_5cb3c4a2","in_reply_to":"eca47d34_4f3ef789","updated":"2025-10-10 15:50:09.000000000","message":"Done","commit_id":"ffcd21b620b82fce60eed0be52076970fc613ec4"},{"author":{"_account_id":1000040,"name":"mrbff","email":"marco@mandelbit.com","username":"mrbff"},"change_message_id":"d95f058c3a69fc7276733b8319a2f3893f048094","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cf110d4f_14e94564","in_reply_to":"fe307bd9_3c705f2a","updated":"2025-09-25 13:07:24.000000000","message":"https://github.com/OpenVPN/openvpn/issues/850\nIssue opened, hope it\u0027s clear enough. Anyway you can just watch the test logs provided in the issue. If you want to easily test by yourself i also provided some scripts i used.","commit_id":"ffcd21b620b82fce60eed0be52076970fc613ec4"},{"author":{"_account_id":1000002,"name":"cron2","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"0739cce6392ea863734d4c0a2be9dca06e268c4d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"8bd290cb_66c6725a","updated":"2025-10-06 09:15:29.000000000","message":"This looks like it\u0027s not actually the correct way to do it - with the patch, a client that has a local `--ifconfig` configured will lose that on PUSH_REPLY, no matter what the server pushes.  This is a valid use case and must not be broken.\n\nWe do have the concept of \"saved config data\" which preserves what is in the client config - so `ifconfig` and `ifconfig-ipv6` need to be reset to \"what is in the client config\" before connecting out (PUSH_REPLY), otherwise we will break existing setups.\n\nFor `PUSH_REPLY` I do not really care, as that\u0027s new functionality.","commit_id":"4201fe86354c478c4fd623961ead50133a1eefb1"},{"author":{"_account_id":1000002,"name":"cron2","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"c4f0d5744e387bdb3580da19481cacac1dfdd4d9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"d0cd4a61_fe074c9f","updated":"2025-10-11 11:12:31.000000000","message":"This has become nicely small :-)\n\nI still think it\u0027s not the fully correct fix (if we have a \"stale\" redirect-gateway ipv6, we should fix that at config saving/restoral, and not just ignore it later on).  But for beta3, we can move ahead, and in the new GH issue we can then revert it if we conclude that we want to.","commit_id":"ab351859532371fd3da5328307f6cf1e5b9e897a"}]}
