Gleb Smirnoff 8f134647ca Switch the entire IPv4 stack to keep the IP packet header ... in network byte order. Any host byte order processing is done in local variables and host byte order values are never[1] written to a packet. After this change a packet processed by the stack isn't modified at all[2] except for TTL. After this change a network stack hacker doesn't need to scratch his head trying to figure out what is the byte order at the given place in the stack. [1] One exception still remains. The raw sockets convert host byte order before pass a packet to an application. Probably this would remain for ages for compatibility. [2] The ip_input() still subtructs header len from ip->ip_len, but this is planned to be fixed soon. Reviewed by: luigi, Maxim Dounin <mdounin mdounin.ru> Tested by: ray, Olivier Cochard-Labbe <olivier cochard.me>		2012-10-22 21:09:03 +00:00
..
if_pflog.c	Make the "struct if_clone" opaque to users of the cloning API. Users	2012-10-16 13:37:54 +00:00
if_pfsync.c	Switch the entire IPv4 stack to keep the IP packet header	2012-10-22 21:09:03 +00:00
in4_cksum.c
pf_if.c
pf_ioctl.c	Revert previous commit...	2012-10-10 08:36:38 +00:00
pf_lb.c	Make ruleset anchors in pf(4) reentrant. We've got two problems here:	2012-09-18 10:54:56 +00:00
pf_norm.c
pf_osfp.c
pf_ruleset.c
pf_table.c	When connection rate hits and we overload a source to a table,	2012-09-22 10:14:47 +00:00
pf.c	Switch the entire IPv4 stack to keep the IP packet header	2012-10-22 21:09:03 +00:00