SNI extension possibly not recognized #9
Description
I have set up PVE with OPNsense and other virtual machines. sniproxy with other software runs inside LXC inside PVE. This all setup works fine for browser, for the same server, but not for .NET-based application, Discord Update, which is open source Squirrel Update. It looks like application talks differently compared to browser, and sniproxy does not recognize SNI. I have dumped TCP stream:
00000000 16 03 03 00 ba 01 00 00 b6 03 03 68 2a ac cb 8f ........ ...h*...
00000010 03 d2 a0 6e bf db 09 70 0c 15 12 00 77 ef fb fd ...n...p ....w...
00000020 62 be 77 f3 07 9a 25 e4 3c 84 4e 00 00 34 c0 2c b.w...%. <.N..4.,
00000030 c0 2b c0 30 c0 2f 00 9f 00 9e c0 24 c0 23 c0 28 .+.0./.. ...$.#.(
00000040 c0 27 c0 0a c0 09 c0 14 c0 13 00 9d 00 9c 00 3d .'...... .......=
00000050 00 3c 00 35 00 2f 00 0a c1 00 c1 01 c1 02 ff 85 .<.5./.. ........
00000060 00 81 01 00 00 59 00 00 00 18 00 16 00 00 13 75 .....Y.. .......u
00000070 70 64 61 74 65 73 2e 64 69 73 63 6f 72 64 2e 63 pdates.d iscord.c
00000080 6f 6d 00 0a 00 08 00 06 00 1d 00 17 00 18 00 0b om...... ........
00000090 00 02 01 00 00 0d 00 1a 00 18 08 04 08 05 08 06 ........ ........
000000A0 04 01 05 01 02 01 04 03 05 03 02 03 02 02 06 01 ........ ........
000000B0 06 03 00 23 00 00 00 17 00 00 ff 01 00 01 00 ...#.... .......
Application sends this and receives nothing in return. Then there are only TCP keep-alive packets.