Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LVS\s+TCP\s+package\s+fragment\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LVS\s+TCP\s+package\s+fragment\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: LVS TCP package fragment (score: 1): Author: <pickup112@xxxxxxxxx>; Date: Tue, 26 Dec 2017 21:42:42 +0800; Thanks for reply. It seems not the problem of checksum. Because the LVS send a 252 length package and checksum of 0x5d97, but real server get a 248 package with the same checksum 0x5d97. I still want; /html/lvs-devel/2017-12/msg00010.html (13,267 bytes)
2. Re: LVS TCP package fragment (score: 1): Author: Paolo Schiro <paolo@xxxxxxxxx>; Date: Mon, 24 Jul 2017 10:47:47 +0200; Checksum problems are usally caused by ethernet offloads. try play with ethtool -k -K. Il 17/07/2017 16:04, ha scritto: I have meet a very strange problem in my LVS environment. when I connect to mys; /html/lvs-devel/2017-07/msg00007.html (11,787 bytes)
3. Re: LVS TCP package fragment (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Wed, 19 Jul 2017 10:25:17 +0300 (EEST); Hello, There can be a problem with fragments but your tcpdump output does not show such fragments, even in previous emails. According to 'man tcpdump': Fragmented Internet datagrams are printed as (f; /html/lvs-devel/2017-07/msg00006.html (12,623 bytes)
4. LVS TCP package fragment (score: 1): Author: <pickup112@xxxxxxxxx>; Date: Mon, 17 Jul 2017 22:04:52 +0800; I have meet a very strange problem in my LVS environment. when I connect to mysqld real server, mysql client is ok. when I connect to LVS to access to the real server, mysql client report error. I co; /html/lvs-devel/2017-07/msg00004.html (10,912 bytes)

Current List: 1 - 4
Page: [1]