Re: A bug in netinet/ip_esp.c function esp_output()

We seem to be looking at different versions of the file (which should only matter in terms of line numbers). The lines in question:

	/* Fix padding length and Next Protocol in padding itself. */
	pad[padding - 2] = padding - 2;
	m_copydata(m, protoff, sizeof(u_int8_t), pad + padding - 1);  ### 1 ###

	/* Fix Next Protocol in IPv4/IPv6 header. */
	prot = IPPROTO_ESP;
	m_copyback(m, protoff, sizeof(u_int8_t), (u_char *) &prot); ### 2 ###

### 1 ### stores the current Next Protocol (TCP, UDP, IPIP, whatever) at the end of the padding. ### 2 ### changes the IPv4 header or the previous header in IPv6 to say that this header is IPPROTO_ESP.

I suggest you run a test case before you report a problem. -Angelos

In message <5E8B940EF56DF846843D001B9E9DE8C90118DBB4@en3000ex01.ecs.avaya.com>,  Aref Taidi writes:
>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
>
>------_=_NextPart_001_01C2C93B.6C7956A0
>Content-Type: text/plain;
> charset="iso-8859-1"
>
>Hi Angelos,
Received on Fri Jan 31 10:22:05 2003