Date: Wed, 26 Sep 2012 17:10:13 +0300 (EEST)
From: Kaarle Ritvanen <kaarle.ritvanen@datakunkku.fi>
To: Natanael Copa <ncopa@alpinelinux.org>
cc: "jeremy@thomersonfamily.com" <jeremy@thomersonfamily.com>,
        Alpine-devel <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] awall - forward to/from same port
In-Reply-To: <20120926090749.4523d331@ncopa-desktop.nor.wtbts.net>
Message-ID: <alpine.LFD.2.02.1209261704360.5933@kunkku.net>
References: <CADVmKVB+6-FzXoX-t8jxgOjpCRN4Dv=xeX8vYvqjw1jsi8kRRg@mail.gmail.com> <20120926090749.4523d331@ncopa-desktop.nor.wtbts.net>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
Precedence: list
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Wed, 26 Sep 2012, Natanael Copa wrote:

> On Tue, 25 Sep 2012 12:34:53 -0500
> Jeremy Thomerson <jeremy@thomersonfamily.com> wrote:
>> The problem is that awall didn't create a rule in the forward chain
>> for -i gre1 -o gre1.
>
> Not that it means that awall should do the same, but in shorewall you
> add an option called "routeback" to the interface definition.

Well, we could add similar attribute to zone definitions or just make 
awall always generate such rules. The downside of the latter option is 
that those rules are likely unnecessary in most cases, causing a slight 
penalty in performance. What do you think?

BR,
Kaarle


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---