Re: bridge_pfil: m_pullup failed

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:> Think you should mark this irreproducible or so, if there are no such 
:> messages within a few days.
:
:Sorry for the suggestion, but could it be bad hardware?

    It's unlikely to be bad hardware within the PC.  It could be any
    number of things but the most likely cause is that the packet was
    constructed that way.

    The only way to tell for sure would be to add some code to the kernel
    to dump the packet out along with the error message and then examine
    the packet(s) looking for commonality (such as they all come from the
    same originating IP), then use tcpdump to monitor for the pattern
    and diagnose where it is coming from.

    It also depends on the type of traffic being bridged.  Any environment
    exposed to the outside world will *ALWAYS* see weird, malformed, or
    corrupted packets, both accidental and intentional.  Internal 
    environments will also often see weird packets, particularly from 
    Windows boxes (and double particularly if they are infected with a
    few viruses, which many windows boxes are to some degree or other).

						-Matt