From owner-freebsd-current@freebsd.org Wed Aug 15 20:47:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1985D1070056 for ; Wed, 15 Aug 2018 20:47:33 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from madarka.gustik.eu (madarka.gustik.eu [IPv6:2a01:4f8:150:80b1:fe57:f772:524c:99d0]) (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 ADDE87AB58 for ; Wed, 15 Aug 2018 20:47:32 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from romy.j20.helspy.pw (unknown [IPv6:2a01:c844:107f:1620:b3d:c003:d132:e3aa]) by madarka.gustik.eu (Postfix) with ESMTPSA id A8E2E140C7 for ; Wed, 15 Aug 2018 22:47:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gustik.eu; s=mail; t=1534366035; bh=iygXExs0Rlft0hdhjfD17/mOv0ehEnJEwVRf5Y4GzXc=; h=Date:From:To:Subject; b=v/H2/r3zUqpGMM1FUApigE2tw9OApYqcN70Br3ODGRVHAk0POnRV19mYXMcxkyIKO n7iJxLBIyjnId7g6jFdaxlxaGmc23KSNJhmsewiM8WzLz/xmAaaxCUzsE3JYWIC8Ze y1ZXfMIbkNRzH38gImlpiKBNs1GOTgZmdERFIM7w= Date: Wed, 15 Aug 2018 22:47:22 +0200 From: Lars Schotte To: FreeBSD current Subject: gif does not work when going over IPv6 on current Message-ID: <20180815224722.48071501@romy.j20.helspy.pw> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 20:47:33 -0000 Hey folks, when you create a gif with IPv6 tunnel endpoints tcpdump on the underlying interface will show you some kind of error that 0 != 6 and packets will be dropped. IP6 version error: 0 != 6 repeating for each packet. happens only while sending. receiving works. This happens only on 12-current as I am aware, 11-stable works good. I worked around this issue by setting IPv4 tunnel endpoints. And this issue is not related to what you transport. You can do IPv4 or IPv6 ( proto 4 or proto 41 ) the issue remains the same. With IPv4 tunnel endpoints ( inet tunnel ) it does dualstack w/o any issues. Strange. Isn't it? -- Lars Schotte Mudroňova 13 92101 Piešťany