On 24 Aug, Hiroki Sato wrote:
> Don Lewis wrote
> in <201508240052.t7o0qsff002...@gw.catspoiler.org>:
>
> tr> > A TCP setup packet coming from a host on the internal LAN to the NAPT
> tr> > router falls into the last deny-all rule because it does not match if
> tr> > you added "out via ${oif
Don Lewis wrote
in <201508240052.t7o0qsff002...@gw.catspoiler.org>:
tr> > A TCP setup packet coming from a host on the internal LAN to the NAPT
tr> > router falls into the last deny-all rule because it does not match if
tr> > you added "out via ${oif}" to that rule. Does the following
tr> >
On 23 Aug, Hiroki Sato wrote:
> Don Lewis wrote
> in <201508222103.t7ml3gax000...@gw.catspoiler.org>:
>
> tr> The example /etc/rc.firewall has provisions to use either in-kernel NAT
> tr> or natd for the open and client firewall types, but the simple filewall
> tr> type only has code for natd.
On 23 Aug, Ian Smith wrote:
> On Sun, 23 Aug 2015 08:44:53 +0900, Hiroki Sato wrote:
> > Don Lewis wrote
> > in <201508222103.t7ml3gax000...@gw.catspoiler.org>:
> >
> > tr> The example /etc/rc.firewall has provisions to use either in-kernel NAT
> > tr> or natd for the open and client firew
On Sat, Aug 22, 2015 at 8:00 PM, Ian Smith wrote:
> On Sun, 23 Aug 2015 08:44:53 +0900, Hiroki Sato wrote:
> > Don Lewis wrote
> > in <201508222103.t7ml3gax000...@gw.catspoiler.org>:
> >
> > tr> The example /etc/rc.firewall has provisions to use either in-kernel
> NAT
> > tr> or natd for
On Sun, 23 Aug 2015 08:44:53 +0900, Hiroki Sato wrote:
> Don Lewis wrote
> in <201508222103.t7ml3gax000...@gw.catspoiler.org>:
>
> tr> The example /etc/rc.firewall has provisions to use either in-kernel NAT
> tr> or natd for the open and client firewall types, but the simple filewall
> tr
Don Lewis wrote
in <201508222103.t7ml3gax000...@gw.catspoiler.org>:
tr> The example /etc/rc.firewall has provisions to use either in-kernel NAT
tr> or natd for the open and client firewall types, but the simple filewall
tr> type only has code for natd. Is there any reason that in-kernel NAT
tr
The example /etc/rc.firewall has provisions to use either in-kernel NAT
or natd for the open and client firewall types, but the simple filewall
type only has code for natd. Is there any reason that in-kernel NAT
could not be used with the simple firewall type?
After allowing connections to select
