src-test2/sys/netinet/libalias/alias.c, branch releng/6.4

Libalias incorrectly applies proxy rules to the global divert

2005-06-27T22:21:42Z

socket: it should only look for existing translation entries, not create new ones (no matter how it got the idea). Approved by: re(scottl)

Always include alias.h before alias_local.h

2005-05-05T21:55:17Z

Play with includes so that libalias can be compiled both as userland

2005-05-05T19:27:32Z

library and kernel module.

natd core dumps when -reverse switch is used because of a bug in

2005-04-05T13:04:35Z

libalias. In /usr/src/lib/libalias/alias.c, the functions LibAliasIn and LibAliasOutTry call the legacy PacketAliasIn/PacketAliasOut instead of LibAliasIn/LibAliasOut when the PKT_ALIAS_REVERSE option is set. In this case, the context variable "la" gets lost because the legacy compatibility routines expect "la" to be global. This was obviously an oversight when rewriting the PacketAlias* functions to the LibAlias* functions. The fix (as shown in the patch below) is to remove the legacy subroutine calls and replace with the new ones using the "la" struct as the first arg. Submitted by: Gil Kloepfer Confirmed by: PR: 76839 MFC after: 3 days

Fix outgoing ICMP on global instance.

2004-08-14T14:21:09Z

Introduce inline {ip,udp,tcp}_next() functions which take a pointer to an

2004-07-06T12:13:28Z

{ip,udp,tcp} header and return a void * pointing to the payload (i.e. the first byte past the end of the header and any required padding). Use them consistently throughout libalias to a) reduce code duplication, b) improve code legibility, c) get rid of a bunch of alignment warnings.

Rewrite twowords() to access its argument through a char pointer and not

2004-07-06T09:22:18Z

a short pointer. The previous implementation seems to be in a gray zone of the C standard, and GCC generates incorrect code for it at -O2 or higher on some platforms.

Make libalias WARNS?=6-clean. This mostly involves renaming variables

2004-07-05T11:10:57Z

named link, foo_link or link_foo to lnk, foo_lnk or lnk_foo, fixing signed / unsigned comparisons, and shoving unused function arguments under the carpet. I was hoping WARNS?=6 might reveal more serious problems, and perhaps the source of the -O2 breakage, but found no smoking gun.

Parenthesize return values.

2004-07-05T10:55:23Z

Mechanical whitespace cleanup.

2004-07-05T10:53:28Z