Re: Bad Checksum on i386-current

2012-02-11 Thread Henning Brauer
* Christiano F. Haesbaert [2012-02-11 14:25]: > I think pf is not recalculating the checksum after nating, not sure if > it should, henning ? ip_output does that unconditionally, and i fixed the bridge to do that too -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://b

Re: Bad Checksum on i386-current

2012-02-11 Thread Christiano F. Haesbaert
On 11 February 2012 09:43, Insan Praja SW wrote: > Hi Misc@, > > Could someone elaborate me with this tcpdump I had? After nat-ing, checksum > error shows, on the same packet.. > > rule 173.home.8/(match) [uid 0, pid 9731] pass in on vlan516: > 172.16.33.254.64264 > 188.255.110.14.51413: S [tcp su

Re: Bad Checksum on i386-current

2012-02-11 Thread Christiano F. Haesbaert
On 11 February 2012 11:00, Tomas Bodzar wrote: > On Sat, Feb 11, 2012 at 12:43 PM, Insan Praja SW > wrote: >> Hi Misc@, >> >> Could someone elaborate me with this tcpdump I had? After nat-ing, checksum >> error shows, on the same packet.. >> >> rule 173.home.8/(match) [uid 0, pid 9731] pass in on

Re: Bad Checksum on i386-current

2012-02-11 Thread Tomas Bodzar
On Sat, Feb 11, 2012 at 12:43 PM, Insan Praja SW wrote: > Hi Misc@, > > Could someone elaborate me with this tcpdump I had? After nat-ing, checksum > error shows, on the same packet.. > > rule 173.home.8/(match) [uid 0, pid 9731] pass in on vlan516: > 172.16.33.254.64264 > 188.255.110.14.51413: S

Bad Checksum on i386-current

2012-02-11 Thread Insan Praja SW
Hi Misc@, Could someone elaborate me with this tcpdump I had? After nat-ing, checksum error shows, on the same packet.. rule 173.home.8/(match) [uid 0, pid 9731] pass in on vlan516: 172.16.33.254.64264 > 188.255.110.14.51413: S [tcp sum ok] 260322197:260322197(0) win 8192 [tos 0x28] (ttl