No Logfiles... Maybe this could help a litte bit...:? Two times seq 1984 with same chksum - is that normal?
09:11:16.453942 IP (tos 0x0, ttl 127, id 9250, offset 0, flags [DF], proto TCP (6), length 114) 192.168.98.7.53479 > 192.168.1.21.993: Flags [P.], cksum 0x04c1 (correct), seq 1910:1984, ack 19602, win 16286, length 74 09:11:16.467028 IP (tos 0x0, ttl 127, id 9284, offset 0, flags [DF], proto TCP (6), length 162) 192.168.98.7.53479 > 192.168.1.21.993: Flags [P.], cksum 0xdabb (correct), seq 1984:2106, ack 19692, win 16263, length 122 09:11:16.773648 IP (tos 0x0, ttl 127, id 9452, offset 0, flags [DF], proto TCP (6), length 162) 192.168.98.7.53479 > 192.168.1.21.993: Flags [P.], cksum 0xdabb (correct), seq 1984:2106, ack 19692, win 16263, length 122 09:11:16.774403 IP (tos 0x0, ttl 127, id 9453, offset 0, flags [DF], proto TCP (6), length 52) 192.168.98.7.53479 > 192.168.1.21.993: Flags [.], cksum 0x9c66 (correct), seq 2106, ack 19692, win 16263, options [nop,nop,sack 1 {25532:26980}], length 0 09:11:16.775437 IP (tos 0x0, ttl 127, id 9454, offset 0, flags [DF], proto TCP (6), length 52) 192.168.98.7.53479 > 192.168.1.21.993: Flags [.], cksum 0x9610 (correct), seq 2106, ack 21152, win 16425, options [nop,nop,sack 1 {25532:26980}], length 0 09:11:16.776425 IP (tos 0x0, ttl 127, id 9455, offset 0, flags [DF], proto TCP (6), length 52) 192.168.98.7.53479 > 192.168.1.21.993: Flags [.], cksum 0x905c (correct), seq 2106, ack 22612, win 16425, options [nop,nop,sack 1 {25532:26980}], length 0 09:11:16.777020 IP (tos 0x0, ttl 127, id 9456, offset 0, flags [DF], proto TCP (6), length 52) 192.168.98.7.53479 > 192.168.1.21.993: Flags [.], cksum 0x8e54 (correct), seq 2106, ack 22612, win 16425, options [nop,nop,sack 1 {25532:27500}], length 0 09:11:16.777792 IP (tos 0x0, ttl 127, id 9457, offset 0, flags [DF], proto TCP (6), length 52) 192.168.98.7.53479 > 192.168.1.21.993: Flags [.], cksum 0x88a0 (correct), seq 2106, ack 24072, win 16425, options [nop,nop,sack 1 {25532:27500}], length 0 09:11:16.778118 IP (tos 0x0, ttl 127, id 9458, offset 0, flags [DF], proto TCP (6), length 40) 192.168.98.7.53479 > 192.168.1.21.993: Flags [.], cksum 0x0acb (correct), seq 2106, ack 27500, win 16425, length 0 09:11:16.859798 IP (tos 0x0, ttl 127, id 9472, offset 0, flags [DF], proto TCP (6), length 114) 192.168.98.7.53479 > 192.168.1.21.993: Flags [P.], cksum 0x182a (correct), seq 2106:2180, ack 27500, win 16425, length 74 09:11:17.060652 IP (tos 0x0, ttl 127, id 9684, offset 0, flags [DF], proto TCP (6), length 40) 192.168.98.7.53479 > 192.168.1.21.993: Flags [.], cksum 0x0a4a (correct), seq 2180, ack 27574, win 16406, length 0 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1337281 Title: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot Status in “linux” package in Ubuntu: Confirmed Bug description: Since we installed the latest kernel update on our firewall this weekend (3.2.0-65.98) we got massive problems connecting from thunderbird (windows client) to an external imap-server (dovecot with tls). With our Linux client we got no problems. Opening or sending mails with attachments which was done in a second before the update, took some minutes after the update to kernel 3.2.0-65! Installing the kernel version 3.2.0-64 on our firewall system fixed the problem, also the newer kernel linux-generic-lts-trusty did fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp