From owner-freebsd-ipfw@FreeBSD.ORG Sun Apr 21 12:30:01 2013 Return-Path: Delivered-To: freebsd-ipfw@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7EB6135D for ; Sun, 21 Apr 2013 12:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7173C120E for ; Sun, 21 Apr 2013 12:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r3LCU1RX021174 for ; Sun, 21 Apr 2013 12:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r3LCU1Sq021173; Sun, 21 Apr 2013 12:30:01 GMT (envelope-from gnats) Date: Sun, 21 Apr 2013 12:30:01 GMT Message-Id: <201304211230.r3LCU1Sq021173@freefall.freebsd.org> To: freebsd-ipfw@FreeBSD.org Cc: From: Ian Smith Subject: Re: kern/177948: [ipfw] ipfw fails to parse port ranges (p1-p2) for udp X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Ian Smith List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2013 12:30:01 -0000 The following reply was made to PR kern/177948; it has been noted by GNATS. From: Ian Smith To: Jukka Ukkonen Cc: bug-followup@FreeBSD.org Subject: Re: kern/177948: [ipfw] ipfw fails to parse port ranges (p1-p2) for udp Date: Sun, 21 Apr 2013 22:21:06 +1000 (EST) On Sun, 21 Apr 2013 14:33:07 +0300, Jukka Ukkonen wrote: > On 04/21/13 05:17, Ian Smith wrote: > > I can't reproduce this on 9.1-RELEASE, unless I put a space anywhere > > amongst p1, '-' and p2, in which case I see the same error you show. [..] > Right, > > After some further inspection I have news... > > This seems to be a problem in clang-cpp which adds an extra space > before the dash in a macro which should have a value of the format > "number1-number2". So, e.g. "1024-65535" becomes "1024 -65535". Naughty clang! For one thing, that's emitting two values .. > If I use gcpp instead, everything works just fine with ipfw. > > The fact that I did not see this happening with TCP rules as well was > just lucky coincidence. > > So, this is a clang problem, not an ipfw problem!!! > > Cheers, > --jau Good news for ipfw, anyway. I don't know the correct form .. should this PR be reassigned, or closed with a reference in a fresh clang PR? cheers, Ian