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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151125141626.6f9579478e1b9d0eb1d4a84f>