From owner-freebsd-net@FreeBSD.ORG  Wed May  6 12:51:20 2015
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 43D653CC
 for <freebsd-net@freebsd.org>; Wed,  6 May 2015 12:51:20 +0000 (UTC)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com
 [IPv6:2607:f8b0:4002:c07::233])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 04A661139
 for <freebsd-net@freebsd.org>; Wed,  6 May 2015 12:51:20 +0000 (UTC)
Received: by ykeo186 with SMTP id o186so2082629yke.0
 for <freebsd-net@freebsd.org>; Wed, 06 May 2015 05:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=pvkh9wwgE9VDXRh2I1A80Mm7vnRPsj5gT7/4rptR1Zs=;
 b=CRJ22O3FCpZhUInzeIEVLBtVrj+xJihNq1ZITrlW1SLWZaZaMeyplEK44q+NTna7ZH
 pnS+hX0sN3rq0fyZAOBXCqrTdFXzOv53eKT+X7OS7+DiLhu1JaHoUondQIoYn+6dldgz
 p4QBKokst7HntC//WiESlUDqE0vhWvKfjgfKRbP1wtWjCcD+ApdIRbskH6NUg+evXnvN
 6PKbGBDtEsO21IsrllJ0ddhlaFZdXsDtweDQ/ow72Ze9UgSx42nPYuSi6hLYRvK5Ws0c
 Uw6uPkdRBzcI5C1LSNsULk5YCFbBEhtg6MUZmHza7c2l2qY8uCs9cK1Q74xx8YGAAan9
 y8yQ==
MIME-Version: 1.0
X-Received: by 10.170.60.13 with SMTP id c13mr28163038ykc.72.1430916679068;
 Wed, 06 May 2015 05:51:19 -0700 (PDT)
Received: by 10.13.252.6 with HTTP; Wed, 6 May 2015 05:51:19 -0700 (PDT)
Date: Wed, 6 May 2015 14:51:19 +0200
Message-ID: <CABUmD9toVsmOo=sfosBO2Tv_ZU35odpM5MNaLNtzZhZpAXLjgQ@mail.gmail.com>
Subject: FreeBSD makes linux think other subet is in same lan.
From: Martin Larsson <martin.larsson2@gmail.com>
To: freebsd-net@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 May 2015 12:51:20 -0000

This is a small summary of
https://forums.freebsd.org/threads/routing-issue-with-ipsec-windows-works-linux-doesnt.51201/
.


Setup:
My side
192.168.1.0/24
Freebsd (default gateway and ipsec gateway, 192.168.1.1)
windows, linux etc

10.11.12.0/24
other net

1: connect with ipsec to another subnet.
When tunnel is up, all computers behind can ping the remote subnet, but not
freebsd itself.
So, I add a route: route add -net 10.11.12.0/24 192.168.1.1

Now, FreeBSD itselt can also ping 10.11.12.0/24 host, but Linux stop
working.
windows can ping in both cases though.

Here is arp -n on linux after the route is added on the freebsd gateway.

Linux:~ # arp -a
? (10.11.12.13) at <incomplete>  on eth0
? (192.168.1.125) at b4:52:7e:95:2a:f5 [ether]  on eth0
? (192.168.1.1) at 00:1b:21:00:62:62 [ether]  on eth0
? (192.168.1.160) at 84:38:38:6a:ec:91 [ether]  on eth0
? (192.168.1.6) at 1c:6f:65:21:36:96 [ether]  on eth0
? (192.168.1.5) at 00:1a:4d:63:d8:5c [ether]  on eth0

So somehow it thinks 10.11.12.0/24 is in its lan.
This very same scenario works fine if I replace my freebsd gateway with
openbsd or linux.
So could this be a bug or am I doing something wrong?

Best regards
Niklas