Hi there Janne. Result is the same in both endpoints. With or without ipcomp.
Any others suggestions? Nice regards to you all misc@ On Thu, Feb 6, 2020 at 8:10 AM Janne Johansson <icepic...@gmail.com> wrote: > Den ons 5 feb. 2020 kl 21:01 skrev Riccardo Giuntoli <tag...@gmail.com>: > >> If i sniff traffic over enc0 interface I found a strange error about ip >> chksum: >> >> (DF) (ttl 63, id 43164, len 52) (DF) (ttl 64, id 18753, len 72, bad ip >> cksum 0! -> c48a) >> This is the error as you can review. >> >> I cannot find solution in Internet and the real think is that in many >> others post people copy and paste packets and this error is visible but no >> one think that is in effect an error or do not speak about. >> > > You often see 0 in packet checksum fields if the packet is heading out on > a device > which claims to do ipv4 checksum offloading in hardware. In such cases, > the OS will > not spend time doing software checksums, but the hardware will do it just > before the > packet leaves for the network, so that is why the software sniffer will > see 0 there, but > the remote end (you do look for errors from both ends, right?) will see > something else > there. > > -- > May the most significant bit of your life be positive. > -- Name: Riccardo Giuntoli Email: tag...@gmail.com Location: Canyelles, BCN, España PGP Key: 0x67123739 PGP Fingerprint: CE75 16B5 D855 842FAB54 FB5C DDC6 4640 6712 3739 Key server: hkp://wwwkeys.eu.pgp.net
