On Thu, 2014-07-31 at 19:18 +0800, ?? wrote: > > I'd quite like to see *why* we get such large packets though. Please > > could you try this patch and see what it dumps? > > > Thanks a lot , I have try this patch , the "error1.log" shows the result. Thanks... ERROR: Tun device returned packet of 1500 bytes which is larger than MTU 1337 0000: 45 00 05 dc c9 2f 40 00 40 06 62 7e 0a 01 01 d1 0010: 70 5a 8d 42 39 44 00 50 8c cc eb 53 3b 57 74 9d 0020: 50 10 80 00 40 35 00 00 47 45 54 20 2f 70 6f 6c That genuinely does look like an IPv4 packet with length 0x5dc (1500), so it's the Windows network stack misbehaving and sending packets larger than the MTU, rather than the TAP driver doing something odd like combining different packets. Unless there's something wrong with the way we're setting the MTU, I'm not sure there's much we can do about this. As long as we cope with it, I think we're fine. > Sorry,I am not familiar with the git . > Using the "git clone git://git.infradead.org/users/dwmw2/openconnect.git",I can get the project . > There is no "configure" file in it,so how can I build it ? Must I use the "autoconf " or use other method based on the "openconnect-6.00.tar.gz"? You need to run ./autogen.sh to generate the configure file. -- dwmw2 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5745 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20140731/1420a2d8/attachment.bin>
