Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Dec 2015 16:48:05 +0100
From:      Daniel Bilik <ddb@neosystem.org>
To:        Julian Elischer <julian@freebsd.org>
Cc:        freebsd-net@freebsd.org
Subject:   Re: Outgoing packets being sent via wrong interface
Message-ID:  <20151202164805.575ce2d315fc8708f660d861@neosystem.cz>
In-Reply-To: <20151201121645.dbcf4bf900fd657a6e4ae3b4@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> <20151127101349.752c94090e78ca68cf0f81fc@neosystem.org> <56597CB5.7030307@freebsd.org> <20151130101838.e59be3db0eb3922d87544b16@neosystem.cz> <565C6F86.7090108@freebsd.org> <20151201090332.09b038935b8eabf33288c24c@neosystem.cz> <565D7552.30806@freebsd.org> <20151201121645.dbcf4bf900fd657a6e4ae3b4@neosystem.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Dec 2015 12:16:45 +0100
Daniel Bilik <ddb@neosystem.org> wrote:

> But next time it happens, I'll try to reload pf rules, and also to
> disable pf completely...

Done. First I've tried to flush nat...

# pfctl -f /etc/pf.conf -F nat -O -N
nat cleared

... then rules...

# pfctl -f /etc/pf.conf -F rules -O -R -Tl
rules cleared

... but neither has helped.

Ping to affected host has been reporting the known error all the time...

ping: sendto: Operation not permitted

Next, I've disabled pf completely...

# pfctl -d
pf disabled

... which changed ping error message to...

ping: sendto: Host is down

... and tcpdump(1) confirmed that packets are still going via wrong
interface...

# tcpdump -i re0 -n icmp
07:54:44.538326 IP 82.x.y.50 > 192.168.2.33: ICMP echo request, id 54720, seq 24, length 64

... now not being dropped by pf, but without any echo response (for
obvious reasons).

Again, refreshing default route solved the problem instantly.

--
						Dan



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