Re: [PATCH] udp6: fix UDP/IPv6 encap resubmit path

From: Bill Sommerfeld Date: Fri, 4 Mar 2016 14:47:21 -0800 > IPv4 interprets a negative return value from a protocol handler as a > request to redispatch to a new protocol. In contrast, IPv6 interprets a > negative value as an error, and interprets a positive value as a

Re: [PATCH] udp6: fix UDP/IPv6 encap resubmit path

From: Bill Sommerfeld Date: Fri, 4 Mar 2016 14:47:21 -0800 > IPv4 interprets a negative return value from a protocol handler as a > request to redispatch to a new protocol. In contrast, IPv6 interprets a > negative value as an error, and interprets a positive value as a request > for

Re: [PATCH] udp6: fix UDP/IPv6 encap resubmit path

On 03/04/2016 04:47 PM, Bill Sommerfeld wrote: IPv4 interprets a negative return value from a protocol handler as a request to redispatch to a new protocol. In contrast, IPv6 interprets a negative value as an error, and interprets a positive value as a request for redispatch. UDP for IPv6 was

Re: [PATCH] udp6: fix UDP/IPv6 encap resubmit path

On 03/04/2016 04:47 PM, Bill Sommerfeld wrote: IPv4 interprets a negative return value from a protocol handler as a request to redispatch to a new protocol. In contrast, IPv6 interprets a negative value as an error, and interprets a positive value as a request for redispatch. UDP for IPv6 was

[PATCH] udp6: fix UDP/IPv6 encap resubmit path

IPv4 interprets a negative return value from a protocol handler as a request to redispatch to a new protocol. In contrast, IPv6 interprets a negative value as an error, and interprets a positive value as a request for redispatch. UDP for IPv6 was unaware of this difference. Change

[PATCH] udp6: fix UDP/IPv6 encap resubmit path

IPv4 interprets a negative return value from a protocol handler as a request to redispatch to a new protocol. In contrast, IPv6 interprets a negative value as an error, and interprets a positive value as a request for redispatch. UDP for IPv6 was unaware of this difference. Change