Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Nov 2015 09:29:18 -0800
From:      Kevin Oberman <rkoberman@gmail.com>
To:        Daniel Bilik <ddb@neosystem.org>
Cc:        Gary Palmer <gpalmer@freebsd.org>,  "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   Re: Outgoing packets being sent via wrong interface
Message-ID:  <CAN6yY1vECcj5_4n0fRv6j-2CUJ8mHDoDaxBkYsKZaornQm2CKg@mail.gmail.com>
In-Reply-To: <20151125141626.6f9579478e1b9d0eb1d4a84f@neosystem.cz>
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> <20151125141626.6f9579478e1b9d0eb1d4a84f@neosystem.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 25, 2015 at 5:16 AM, Daniel Bilik <ddb@neosystem.org> wrote:

> 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


Have you looked for ICMP redirect traffic? Does your firewall allow them?
If so, could you try adding a rule to block them? I can't provide a sample
rule as I don't use pf, but you want to block ICMP type 5 messages.

For a good overview of redirects, see either Wikipedia
<https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol#Redirect>;
or Cisco
<http://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/13714-43.html>;
articles (or Google for many others).
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vECcj5_4n0fRv6j-2CUJ8mHDoDaxBkYsKZaornQm2CKg>