Just updated to 2.0.22 and everything so far so good. Thank you.
I just noticed that some cksum is flagged as incorrect in terminal log as show in the sample below. I guess is normal but why this can happen ?
Thank you in advance.
gCs-MacBook-Pro:~ gc$ sudo tcpdump -i en5 -vvv 'port 443'
Password:
tcpdump: listening on en5, link-type EN10MB (Ethernet), capture size 262144 bytes
02:24:59.078265 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 699, bad cksum 0 (->6310)!)
192.168.1.5.50414 > 95.101.180.26.https: Flags [P.], cksum 0xd7da (incorrect -> 0x3a06), seq 1885994789:1885995436, ack 579696828, win 20588, options [nop,nop,TS val 569486357 ecr 3914559841], length 647
02:24:59.101860 IP (tos 0x0, ttl 56, id 31019, offset 0, flags [DF], proto TCP (6), length 1492)
95.101.180.26.https > 192.168.1.5.50414: Flags [.], cksum 0xd5be (correct), seq 1:1441, ack 647, win 1392, options [nop,nop,TS val 3914561767 ecr 569486357], length 1440
etc...
Just updated to 2.0.22 and everything so far so good. Thank you.
I just noticed that some cksum is flagged as incorrect in terminal log as show in the sample below. I guess is normal but why this can happen ?
Thank you in advance.
gCs-MacBook-Pro:~ gc$ sudo tcpdump -i en5 -vvv 'port 443'
Password:
tcpdump: listening on en5, link-type EN10MB (Ethernet), capture size 262144 bytes
02:24:59.078265 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 699, bad cksum 0 (->6310)!)
192.168.1.5.50414 > 95.101.180.26.https: Flags [P.], cksum 0xd7da (incorrect -> 0x3a06), seq 1885994789:1885995436, ack 579696828, win 20588, options [nop,nop,TS val 569486357 ecr 3914559841], length 647
02:24:59.101860 IP (tos 0x0, ttl 56, id 31019, offset 0, flags [DF], proto TCP (6), length 1492)
95.101.180.26.https > 192.168.1.5.50414: Flags [.], cksum 0xd5be (correct), seq 1:1441, ack 647, win 1392, options [nop,nop,TS val 3914561767 ecr 569486357], length 1440
etc...