I believe the list of IP ranges which I linked above is incorrect. After much trial and error, using the below range instead results in a fully working setup without having to manually edit on the client:

1.0.0.0/8, 2.0.0.0/8, 3.0.0.0/8, 4.0.0.0/6, 8.0.0.0/7, 11.0.0.0/8, 12.0.0.0/6, 16.0.0.0/4, 32.0.0.0/3, 64.0.0.0/2, 128.0.0.0/3, 160.0.0.0/5, 168.0.0.0/6, 172.0.0.0/12, 172.32.0.0/11, 172.64.0.0/10, 172.128.0.0/9, 173.0.0.0/8, 174.0.0.0/7, 176.0.0.0/4, 192.0.0.0/9, 192.128.0.0/11, 192.160.0.0/13, 192.169.0.0/16, 192.170.0.0/15, 192.172.0.0/14, 192.176.0.0/12, 192.192.0.0/10, 193.0.0.0/8, 194.0.0.0/7, 196.0.0.0/6, 200.0.0.0/5, 208.0.0.0/4, 1.1.1.1/32, 1.0.0.1/32

still doesn't work for me (loses all connectivity) with both netclient and external clients, the exact same issue while using an egress gateway with ios, macos, linux clients

Maybe your problem is different to mine? My issue always felt like a routing problem, the listen port would appear and then disappear and it would never show data being sent or transmitted.

We have also noticed this bug in testing, even with the modified cidr list. We're tracking it internally and will come up with a fix