Date: Mon, 13 Aug 2012 12:44:57 GMT From: Freek Dijkstra <public@macfreek.nl> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/170604: [ipfw] ipv6 reass broken Message-ID: <201208131244.q7DCiv6r075305@red.freebsd.org> Resent-Message-ID: <201208131250.q7DCo1bQ029275@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 170604 >Category: kern >Synopsis: [ipfw] ipv6 reass broken >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: Mon Aug 13 12:50:01 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Freek Dijkstra >Release: 9.0-RELEASE >Organization: >Environment: FreeBSD 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: Summary: Packet reassembly is only implemented for IPv4, not for IPv6. This is a request to: * Support IPv6 packet reassembly with the "reass" command in ipfw. * Update the documentation and/or ignore the ip6 reass command (to avoid someone bricking a device) in the mean time Notes: I presume this is the same problem as reported earlier by someone else on the freebsd-ipfw list: http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-October/004918.html The bug report/feature request is meant to keep track of that issue. >How-To-Repeat: Steps to reproduce: 1. Add the following rules to ipfw: # sysctl net.inet.ip.fw.one_pass=0 # ipfw add 100 reass ipv6 from any to any in 2. Try to connect to the device (with any means, e.g. ssh over either IPv4 or IPv6) Expected result: I expect the device to be reachable Actual result: I bricked my device >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208131244.q7DCiv6r075305>