Re: raw socket, IP_HDRINCL byteorder

>>sensible, though if you wish to prevent a program from sending ip
>>fragments, would it not make sense to prevent it from receiving them
>>as well, and reassemble packets before passing them up?
>
>In fact, it'd be awfully hard to get ip_input() to supply a fragment.
>If we're not proposing massive changes to the stack, then raw input
>only returns reassembled packets, presumably with ip_off and MF = 0.

i'll admit to not having looked for fragments in reads from a raw ip
socket, however, i still think that the application should not be
prevented from sending them, or is that another thing (along with a
correct ip_sum field) that the kernel is expected to do on behalf of
the application?

-- 
|-----< "CODE WARRIOR" >-----|
[email protected]             * "ah!  i see you have the internet
twofsonet-X5LO1RRdYLVWk0Htik3J/[email protected] (Andrew Brown)                that goes *ping*!"
werdna-aTR67+QfzahWk0Htik3J/[email protected]       * "information is power -- share the wealth."

---------------------------------------------------------------------
The BSD APIs Discussion Mailing List
To unsubscribe:
send "unsubscribe bsd-api-discuss" to majordomo-DZEk9q7Sfju/3pe1ocb+swC/[email protected]