Hi folks,
from a previous thread on this list I learned that
keep state (no-sync) should be added to all rules
concerning either a local service or local client
running on the gateway itself.
Esp. when you do nat this becomes pretty error-prone.
Its easy to forget.
AFAICS something like
* Harald Dunkel harald.dun...@aixigo.de [2011-02-04 14:31]:
Is there some other way to avoid a lot of keep state (no-sync)
statements?
is there some other way to make people READ the fucking mnapages we
put so much effort in?
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web
El 04/02/2011 18:56, Henning Brauer escribis:
* Harald Dunkelharald.dun...@aixigo.de [2011-02-04 14:31]:
Is there some other way to avoid a lot of keep state (no-sync)
statements?
is there some other way to make people READ the fucking mnapages we
put so much effort in?
You're talking
On Fri, 4 Feb 2011 18:56:28 +0100
Henning Brauer lists-open...@bsws.de wrote:
is there some other way to make people READ the fucking mnapages we
put so much effort in?
laser etcher + contact lens and super glue
Kevin Chadwick wrote:
On Fri, 4 Feb 2011 18:56:28 +0100
Henning Brauer lists-open...@bsws.de wrote:
is there some other way to make people READ the fucking mnapages we
put so much effort in?
laser etcher + contact lens and super glue
I'm positive that that still won't work for some
Henning Brauer wrote:
* Harald Dunkel harald.dun...@aixigo.de [2011-02-04 14:31]:
Is there some other way to avoid a lot of keep state (no-sync)
statements?
is there some other way to make people READ the fucking mnapages we
put so much effort in?
If you figure that out, I think you'll be a
6 matches
Mail list logo
