Date: Sat, 17 Jan 2004 23:22:33 +0100 (CET) From: Roderick van Domburg <r.s.a.vandomburg@student.utwente.nl> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/61502: Incorrect ip6fw output when adding rules Message-ID: <200401172222.i0HMMXGL084521@stud187236.mobiel.utwente.nl> Resent-Message-ID: <200401172230.i0HMUKAO042308@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 61502
>Category: bin
>Synopsis: Incorrect ip6fw output when adding rules
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Jan 17 14:30:19 PST 2004
>Closed-Date:
>Last-Modified:
>Originator: Roderick van Domburg
>Release: FreeBSD 5.2-CURRENT sparc64
>Organization:
University of Twente
>Environment:
System: FreeBSD stud187236.mobiel.utwente.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Sun Jan 11 14:03:52 CET 2004 roderick@magog.student.utwente.nl:/usr/obj/usr/src/sys/MAGOG sparc64
>Description:
When adding IPv6 firewall rules without specifying a set rulenumber,
'ip6fw' incorrectly lists the new rule as being added as number 0000
even though it is added under a different rulenumber.
>How-To-Repeat:
1. Enable the IPv6 firewall service
2. Add any rule without specifying a number.
Example: `ip6fw add allow tcp from any to any`
ip6fw reports the rule being added as 0000.
3. Execute `ip6fw show`. The rule will have been added as 0100, assuming
the ruleset was flushed. No matter if it was, the rule will have been
assigned a correct number different from 0000.
However, executing `ip6fw add 100 allow tcp from any to any` during (2)
produces output as expected.
This incorrect behavior is _not_ displayed on plain IPv6 ipfw on sparc64.
I had no architectures readily available to see if all this was platform-
specific.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted:
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401172222.i0HMMXGL084521>