From owner-freebsd-bugs@freebsd.org Mon Feb 29 18:52:43 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B270AB8804 for ; Mon, 29 Feb 2016 18:52:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 42398124D for ; Mon, 29 Feb 2016 18:52:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1TIqhqF046236 for ; Mon, 29 Feb 2016 18:52:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 207598] pf adds icmp unreach somehow Date: Mon, 29 Feb 2016 18:52:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: emz@norma.perm.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 18:52:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207598 Bug ID: 207598 Summary: pf adds icmp unreach somehow Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: emz@norma.perm.ru FreeBSD: FreeBSD moscow-alpha 10.2-STABLE FreeBSD 10.2-STABLE #0 r286954: Fri Aug 21 08:33:14 MSK 2015 emz@moscow-alpha:/usr/obj/usr/src/sys/MOSCOW amd64 Network scheme: (FreeBSD A) <---(gre inside ipsec)---> (FreeBSD B) <---gre inside ipsec---> (FreeBSD C) (uname taken from B) Issue: PF is on A pings B with icmp packets < gre MTU =3D everything is OK A pings C with icmp packets < gre MTU =3D everything is OK A pings B with icmp packets > gre MTU =3D everything is OK A pings C with icmp packets > gre MTU =3D got two answers, a normal ICMP re= ply from C, and an ICMP unreach from B: [emz@big-cherkiz5-1:~]# ping -s 4096 192.168.7.127 PING 192.168.7.127 (192.168.7.127): 4096 data bytes 36 bytes from 172.16.5.214: Destination Host Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 055c a28a 0 0000 40 01 3908 172.16.5.215 192.168.7.127=20 4104 bytes from 192.168.7.127: icmp_seq=3D0 ttl=3D61 time=3D62.119 ms ^C --- 192.168.7.127 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 62.119/62.119/62.119/0.000 ms Workaround: disable pf on B. With pf disabled on B, situation resolves back= to normal. The issue was first seen somewhere on 10-STABLE, didn't resolve so far. I've talk with tough guys, like ae@, he told me to report it, since it cannot be explained by configuration errors. --=20 You are receiving this mail because: You are the assignee for the bug.=