Date: Wed, 6 May 2015 14:51:19 +0200 From: Martin Larsson <martin.larsson2@gmail.com> To: freebsd-net@freebsd.org Subject: FreeBSD makes linux think other subet is in same lan. Message-ID: <CABUmD9toVsmOo=sfosBO2Tv_ZU35odpM5MNaLNtzZhZpAXLjgQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABUmD9toVsmOo=sfosBO2Tv_ZU35odpM5MNaLNtzZhZpAXLjgQ>