> Oh, why do we always go through this..... If you have a device that
> imposes some byte and bit position specific protocol, you cannot assume
> that you can coerce a C structure to it *anyway*- you may get lucky for
> platform #N, but if you're writing portable code you should also include
> macroized or inlined (de)canonicalization functions. 

I think I'm being pretty careful in defining and accessing the data in
those structs.  All fields in the struct have byte size, so I don't
assume much of the C compiler.  I certainly assume less than e.g. the
netinet/ip.h definition of struct ip does.

        -- Lennart