From owner-freebsd-net@freebsd.org  Wed Nov 25 13:20:01 2015
Return-Path: <owner-freebsd-net@freebsd.org>
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 8B4E1A36109
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed, 25 Nov 2015 13:20:01 +0000 (UTC)
 (envelope-from daniel.bilik@neosystem.cz)
Received: from mail.neosystem.cz (mail.neosystem.cz
 [IPv6:2001:41d0:2:5ab8::10:15])
 (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 5149512F3;
 Wed, 25 Nov 2015 13:20:01 +0000 (UTC)
 (envelope-from daniel.bilik@neosystem.cz)
Received: from mail.neosystem.cz (unknown [127.0.10.15])
 by mail.neosystem.cz (Postfix) with ESMTP id 77BCEBBCE;
 Wed, 25 Nov 2015 14:19:58 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.neosystem.cz
Received: from dragon.sn.neosystem.cz (unknown
 [IPv6:2001:41d0:2:5ab8::100:101])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.neosystem.cz (Postfix) with ESMTPSA id 60FA7BBC8;
 Wed, 25 Nov 2015 14:19:57 +0100 (CET)
Date: Wed, 25 Nov 2015 14:16:26 +0100
From: Daniel Bilik <ddb@neosystem.org>
To: Gary Palmer <gpalmer@freebsd.org>
Cc: freebsd-net@freebsd.org
Subject: Re: Outgoing packets being sent via wrong interface
Message-Id: <20151125141626.6f9579478e1b9d0eb1d4a84f@neosystem.cz>
In-Reply-To: <20151125122033.GB41119@in-addr.com>
References: <20151120155511.5fb0f3b07228a0c829fa223f@neosystem.org>
 <C1D7F956-81C9-4ED4-99B8-E0C73A3ECB37@FreeBSD.org>
 <20151120163431.3449a473db9de23576d3a4b4@neosystem.org>
 <20151121212043.GC2307@vega.codepro.be>
 <20151122130240.165a50286cbaa9288ffc063b@neosystem.cz>
 <20151125092145.e93151af70085c2b3393f149@neosystem.cz>
 <20151125122033.GB41119@in-addr.com>
Organization: neosystem.cz
X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; x86_64-portbld-dragonfly4.3)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Nov 2015 13:20:01 -0000

On Wed, 25 Nov 2015 12:20:33 +0000
Gary Palmer <gpalmer@freebsd.org> wrote:

> When the problem happens, what does the output of
> route -n get <unreachable IP>
> show?

I'll check this next time it happens. Thanks for the tip. Right now it
seems correct:

   route to: 192.168.2.33
destination: 192.168.2.0
       mask: 255.255.255.0
        fib: 0
  interface: re1
      flags: <UP,DONE,PINNED>
 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1500         1         0 

>  It would also be worth checking the arp table.

Yes, checking arp table was one of the first things I did when analyzing
the problem. All arp entries seem correct, and do not change
before-during-after the problem. I've also tried to manually remove arp
entry for affected address (ie. forcing it to be refreshed), but it
does not help.

--
						Dan