[afnog] Resolver issues

[Michuki Mwangi]

Geert Jan de Groot wrote:
> 
> Caution: certain OS-es, when used with network cards with checksum offloading,
> will generate tcpdump checksum errors on perfectly good packets with
> only partially calculated (and hence incorrect) checksums.
>
Its been running Freebsd 4.11 for a couple of months now without any 
problems.


> Whether that is happening can be seen with netstat -s (check 'bad checksum'
> under UDP and IP).
> 

There are no bad checksum counts under UDP & IP

udp:
         2925 datagrams received
         0 with incomplete header
         0 with bad data length field
         0 with bad checksum
         0 with no checksum
         300 dropped due to no socket
         0 broadcast/multicast datagrams dropped due to no socket
         0 dropped due to full socket buffers
         0 not for hashed pcb
         2625 delivered
         5485 datagrams output
ip:
         69708 total packets received
         0 bad header checksums
         0 with size smaller than minimum
         0 with data size < data length
         0 with ip length > max ip packet size
         0 with header length < data size
         0 with data length < header length
         0 with bad options
         0 with incorrect version number
         0 fragments received
         0 fragments dropped (dup or out of space)
         0 fragments dropped after timeout
         0 packets reassembled ok
         66821 packets for this host
         236 packets for unknown/unsupported protocol
         0 packets forwarded (0 packets fast forwarded)
         0 packets not forwardable
         0 packets received for unknown multicast group
         0 redirects sent
         76534 packets sent from this host
         0 packets sent with fabricated ip header
         0 output packets dropped due to no bufs, etc.
         0 output packets discarded due to no route
         0 output datagrams fragmented
         0 fragments created
         0 datagrams that can't be fragmented
         0 tunneling packets that can't find gif
         0 datagrams with bad address in header


> As long as the netstat error counters stay motionless, I'd suggest
> to look at the other suggestions first.
> 
This is where i am at ... :)