Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Sep 2005 15:32:50 +0200 (CEST)
From:      Oliver Fromme <olli@lurza.secnetix.de>
To:        freebsd-ipfw@FreeBSD.ORG, vladone <vladone@spaingsm.com>
Subject:   Re: in via or in recv
Message-ID:  <200509151332.j8FDWoqd035125@lurza.secnetix.de>
In-Reply-To: <1126236392.20050901000512@spaingsm.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
The question is already a few days old, but I thought
I might throw in my answer nevertheless.  :-)

vladone <vladone@spaingsm.com> wrote:
 > What is difference between:
 >   1. in via - in recv

No difference.  When checking incoming packets (which "in"
means), only the receiving interface is known, but not yet
the transmitting interface, so "via" and "recv" do the same
thing in that case.

 >   2. out via - out xmit

When checking outgoing packets ("out"), both the receiving
and the transmitting interface are known, so "via" compares
with both, while "xmit" only compares with the transmitting
interface.  That's why "xmit" can only be used with "out",
not with "in", while "recv" can be used with both "out" and
"in".

All of that is explained in detail in the ipfw(8) manpage.

 > When need to use an variant or another?

That depends on what you want to do.  In my experience
there is rarely a need for "via".  Usually you only need
"recv" and "xmit" (optionally combined with "in" and "out"
as appropriate for your rules).

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

I suggested holding a "Python Object Oriented Programming Seminar",
but the acronym was unpopular.
        -- Joseph Strout



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?200509151332.j8FDWoqd035125>