Re: raw socket, IP_HDRINCL byteorder

>> 	outgoing:
>> 	ip_len: the whole IP packet length (not the payload)
>> 	ip_off: offset portion and MF bit has to be zero.
>> 	ip_id: overwritten by the kernel
>> 	ip_sum: overwritten by the kernel
>> 	ip option: ???? interaction with IP_OPTIONS?
>IMO, the outgoing packet shouldn't be touched at all - just written
>as-is to the wire. the proposed restriction on ip_off is problematic
>for applications which need to create IP fragments, and there are
>several awful workarounds people have had to resort to to acheive
>this, for example, on Solaris.

	we have bpf write/read for pure on-wire access.
	based on udp socket behavior, i thought it makes more sense to let
	kernel do fragment processing.

itojun

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