Date: Wed, 4 Jun 2008 19:23:25 GMT From: Scott Aitchison <saitchison@borderware.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/124282: INP_PORTHIGH and INP_ONESBCAST share same value Message-ID: <200806041923.m54JNPET057597@www.freebsd.org> Resent-Message-ID: <200806041930.m54JU1nm075051@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 124282 >Category: kern >Synopsis: INP_PORTHIGH and INP_ONESBCAST share same value >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 04 19:30:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Scott Aitchison >Release: 6.3-STABLE i386 >Organization: BorderWare Technologies >Environment: FreeBSD rush.borderware.com 6.3-RELEASE FreeBSD 6.3-RELEASE #1: Tue Jan 29 14:58:12 EST 2008 root@rush.borderware.com:/usr/obj/usr/src/sys/RUSH i386 >Description: If IP_PORTRANGE_HIGH is set as a socket option, it will set INP_PORTHIGH on inp_flags. However, since INP_ONESBCAST is the same value and is also set in inp_flags, this will cause some problems with UDP checksums on these sockets. This was fixed previously in kern/87306, however it was reintroduced in kern/99558 >How-To-Repeat: Call setsockopt() with IP_PORTRANGE_HIGH on a UDP socket. Send traffic through socket. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806041923.m54JNPET057597>