Martti Kuparinen wrote: > Hi, > > After upgrading to the latest NetBSD/amd64 4.0_BETA2 (and therefore to > IPF 4.1.20) I'm getting a lot of these errors. Before the upgrade (IPF > 4.1.13) everything was working just fine. > > > May 10 10:20:48 p130 ipmon[377]: 10:20:48.692051 bnx0 @0:37 b > d146.mydomain.com[xxx.xxx.xxx.146],smtp -> > p130.mydomain.com[xxx.xxx.xxx.130],52997 PR tcp len 20 52 -A IN > May 10 10:20:49 p130 ipmon[377]: 10:20:49.684257 bnx0 @0:37 b > d146.mydomain.com[xxx.xxx.xxx.146],smtp -> > p130.mydomain.com[xxx.xxx.xxx.130],52997 PR tcp len 20 52 -AF IN > May 10 10:20:49 p130 ipmon[377]: 10:20:49.694822 bnx0 @0:37 b > d146.mydomain.com[xxx.xxx.xxx.146],smtp -> > p130.mydomain.com[xxx.xxx.xxx.130],52997 PR tcp len 20 64 -A IN > May 10 10:20:51 p130 ipmon[377]: 10:20:51.684376 bnx0 @0:37 b > d146.mydomain.com[xxx.xxx.xxx.146],smtp -> > p130.mydomain.com[xxx.xxx.xxx.130],52997 PR tcp len 20 52 -AF IN > May 10 10:20:51 p130 ipmon[377]: 10:20:51.703369 bnx0 @0:37 b > d146.mydomain.com[xxx.xxx.xxx.146],smtp -> > p130.mydomain.com[xxx.xxx.xxx.130],52997 PR tcp len 20 64 -A IN > ... > How should I debug this?
I think the first thing to try is to also record the state log data...so look at adding "-a" to the ipmon command line. This will help you determine if the packets above are just arriving "late" or if they're not being matched up correctly. Check the changes to the timeouts in ip_state.c Darren
