From owner-freebsd-net@freebsd.org Wed Jul 26 10:23:32 2017 Return-Path: Delivered-To: freebsd-net@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 DEBE0DB6EFD for ; Wed, 26 Jul 2017 10:23:32 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward2j.cmail.yandex.net (forward2j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 719B28200C for ; Wed, 26 Jul 2017 10:23:32 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [IPv6:2a02:6b8:0:1619::15:6]) by forward2j.cmail.yandex.net (Yandex) with ESMTP id 58F9820BEA; Wed, 26 Jul 2017 13:23:29 +0300 (MSK) Received: from smtp4j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp4j.mail.yandex.net (Yandex) with ESMTP id BCE7132410E3; Wed, 26 Jul 2017 13:23:02 +0300 (MSK) Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 0tBg1jw8yC-N1Um0L3A; Wed, 26 Jul 2017 13:23:01 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1501064581; bh=vRgn4yKelrISx7m8ijP3KRVu9yV+v8ZoGfHFRYhniAg=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=f7IzZaW6vrsmFTuzggD0OkqDeZNm8s1601kddFVaRQ5762kgUFAic52WYFyYMH5nY zICFH8WT84OyXCMIgVJaLEeLyniXb4tmxhA4FGpW67kon4pHtueSJQHO13F5gPjAWT pQo03TyCahJ/afvRiocckVYPQt1lf0PsC7v9XI2Y= Authentication-Results: smtp4j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: NAT before IPSEC - reply packets stuck at enc0 To: "Muenz, Michael" , freebsd-net@freebsd.org References: <459d59f7-2895-8aed-d547-be46a0fbb918@spam-fetish.org> <3344e189-cdf0-a2c9-3a2a-645460866f2d@yandex.ru> <1279753e-9ad1-2c02-304e-5001e2bbc82f@spam-fetish.org> <15e6eb38-ef0c-7bfd-5f2c-d2acc8ea1af4@yandex.ru> <63e80fcf-915e-2dd5-d8c9-1904c8261c6f@yandex.ru> <1c91cd8f-105d-e886-3126-67505c6c3900@spam-fetish.org> <1e889acf-49d1-b70f-7097-82e6e4dfabb6@spam-fetish.org> <454ed1b7-a80f-b096-cfa1-3c32d1e60f7d@yandex.ru> <5dfdfbb3-1046-5abe-b23a-b62c215b5d08@yandex.ru> <860b48aa-b99e-7b71-3724-587ee0a7fe80@spam-fetish.org> <1b831b84-1d3f-38cb-acee-07a339315417@yandex.ru> <0bbf5bb9-8089-f9ce-3b1d-e9bcbdbc6c76@spam-fetish.org> <3a7d5a5b-3b72-4cfe-2d8e-c832f7bfab5c@spam-fetish.org> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <2672efbc-49f2-efba-07d6-feeb5c8e3757@yandex.ru> Date: Wed, 26 Jul 2017 13:20:23 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <3a7d5a5b-3b72-4cfe-2d8e-c832f7bfab5c@spam-fetish.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KTku6E83IiNAwI8fFTSlIMxH5QMdS3WaB" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2017 10:23:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --KTku6E83IiNAwI8fFTSlIMxH5QMdS3WaB Content-Type: multipart/mixed; boundary="Uwkop2JDIUdsxAMKW56xT5iwUQCK7AK7f"; protected-headers="v1" From: "Andrey V. Elsukov" To: "Muenz, Michael" , freebsd-net@freebsd.org Message-ID: <2672efbc-49f2-efba-07d6-feeb5c8e3757@yandex.ru> Subject: Re: NAT before IPSEC - reply packets stuck at enc0 References: <459d59f7-2895-8aed-d547-be46a0fbb918@spam-fetish.org> <2d607e1a-a2c0-0f85-1530-c478962a76cd@spam-fetish.org> <3344e189-cdf0-a2c9-3a2a-645460866f2d@yandex.ru> <1279753e-9ad1-2c02-304e-5001e2bbc82f@spam-fetish.org> <15e6eb38-ef0c-7bfd-5f2c-d2acc8ea1af4@yandex.ru> <63e80fcf-915e-2dd5-d8c9-1904c8261c6f@yandex.ru> <1c91cd8f-105d-e886-3126-67505c6c3900@spam-fetish.org> <1e889acf-49d1-b70f-7097-82e6e4dfabb6@spam-fetish.org> <454ed1b7-a80f-b096-cfa1-3c32d1e60f7d@yandex.ru> <5dfdfbb3-1046-5abe-b23a-b62c215b5d08@yandex.ru> <860b48aa-b99e-7b71-3724-587ee0a7fe80@spam-fetish.org> <1b831b84-1d3f-38cb-acee-07a339315417@yandex.ru> <0bbf5bb9-8089-f9ce-3b1d-e9bcbdbc6c76@spam-fetish.org> <3a7d5a5b-3b72-4cfe-2d8e-c832f7bfab5c@spam-fetish.org> In-Reply-To: <3a7d5a5b-3b72-4cfe-2d8e-c832f7bfab5c@spam-fetish.org> --Uwkop2JDIUdsxAMKW56xT5iwUQCK7AK7f Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 26.07.2017 12:47, Muenz, Michael wrote: > When I type setkey -PD I get: >=20 > 10.24.66.0/24[any] 10.26.1.0/24[any] any > in ipsec > esp/tunnel/81.24.74.3-213.244.192.191/unique:2 > created: Jul 26 11:03:53 2017 lastused: Jul 26 11:40:02 2017 > lifetime: 9223372036854775807(s) validtime: 0(s) > spid=3D5 seq=3D1 pid=3D4292 > refcnt=3D1 > 10.26.1.0/24[any] 10.24.66.0/24[any] any > out ipsec > esp/tunnel/213.244.192.191-81.24.74.3/unique:2 > created: Jul 26 11:03:53 2017 lastused: Jul 26 11:40:02 2017 > lifetime: 9223372036854775807(s) validtime: 0(s) > spid=3D6 seq=3D0 pid=3D4292 > refcnt=3D1 >=20 >=20 > So it's in use. >=20 > But when I type in your command it just "hangs". Not the system, but th= e > command doesn't get completed. >=20 > root@PB-FW1-FRA:~ # setkey -v -c spdadd -4 10.26.2.0/24 10.24.66.0/24 > any -P out ipsec esp/tunnel/213.244.192.191-81.24.74.3/require ; > You need to do it this way: 1. setkey -v -c 2. type the policy specification 3. press Enter and then press ^D # setkey -v -c spdadd -4 10.26.2.0/24 10.24.66.0/24 any -P out ipsec esp/tunnel/213.244.192.191-81.24.74.3/unique:2 ; ^D Also, since your policies uses "unique" level, you need to specify the same level using "unique:N" syntax. Also if it is interesting to you, I patched ipfw_nat to be able specify needed direction. The patch is untested at all :) https://people.freebsd.org/~ae/nat_in_out.diff You need to rebuild ipfw(4) and ipfw_nat(4) kernel modules, and also ipfw(8) binary. With this patch you can use the following commands: ipfw nat 1 config ip 10.26.1.1 log ipfw add 179 nat-out 1 all from 10.26.2.0/24 to 10.24.66.0/24 in recv vtn= et1 ipfw add 179 nat-in 1 all from 10.24.66.0/24 to 10.26.1.1 in recv enc0 or these: ipfw nat 1 config ip 10.26.1.1 log reverse ipfw add 179 nat-in 1 all from 10.26.2.0/24 to 10.24.66.0/24 in recv vtne= t1 ipfw add 179 nat-out 1 all from 10.24.66.0/24 to 10.26.1.1 in recv enc0 Or maybe guys from OpenSense can help with testing. --=20 WBR, Andrey V. Elsukov --Uwkop2JDIUdsxAMKW56xT5iwUQCK7AK7f-- --KTku6E83IiNAwI8fFTSlIMxH5QMdS3WaB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAll4bOcACgkQAcXqBBDI oXqF/Qf+MuC1dSCmhz9Yenv0ygR8/tL3Hx1HQ3k7VbT7Zsm+q2dVY1D+VoSbVIMq COPTADflXhE7mzwIxopEaat262gfg+FOl7XDSR6AK2ZaBUMjG4Iee00KUy4B+YKx Uu+GVx9lqkGablS3wmUPxnhGzDErwPhAafH1qXz5la1//U0JmyMNqM5L9QhNZXJ0 w1FQu4NJHAAbSm0GWCJPTHO+/PN9djd5mkWuu8+1p1b8xU4SCqB82Kjh7TIB1MMm eOdbqFTN4H/+HPR55mHUTs5Hi34776GL4HRq2Nhz6h2OK7aLe9jiADnJtp192076 koi2s1u+bB/b05vhQVu7SlkV1T73Ig== =/AC2 -----END PGP SIGNATURE----- --KTku6E83IiNAwI8fFTSlIMxH5QMdS3WaB--