-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/26/2016 05:11 AM, jone...@teksavvy.com wrote:
> On Sat, 23 Jul 2016 08:22:02 -0700 Tom Eastep
> wrote:
>
>> On 07/20/2016 02:21 PM, jonetsu wrote:
>>> Hello,
>>>
>>> Some time ago I did a user interface for DSCP marking, taking
>>> the docum
On Sat, 23 Jul 2016 08:22:02 -0700
Tom Eastep wrote:
> On 07/20/2016 02:21 PM, jonetsu wrote:
> > Hello,
> >
> > Some time ago I did a user interface for DSCP marking, taking the
> > documentation from the tcrules of that time, in which it was
> > mentioned that the DSCP mark can be follwoed b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/20/2016 02:21 PM, jonetsu wrote:
> Hello,
>
> Some time ago I did a user interface for DSCP marking, taking the
> documentation from the tcrules of that time, in which it was
> mentioned that the DSCP mark can be follwoed by either F (forwar
Hello,
Some time ago I did a user interface for DSCP marking, taking the documentation
from the tcrules of that time, in which it was mentioned that the DSCP mark can
be follwoed by either F (forward chain) or T (postrouting - default). The
current mangle documentation page does not have these
On 04/20/2012 06:47 AM, Fred Maillou wrote:
> Hello,
>
> As the 4.5.2.2 tcrules manpage shows, the default chain for DSCP marks
> is postrouting. Is this still true if shorewall.conf has the
> 'MARK_IN_FORWARD_CHAIN=Yes' option ?
Actually, the manpage is wrong -- the default chain is the same
Hello,
As the 4.5.2.2 tcrules manpage shows, the default chain for DSCP marks is
postrouting. Is this still true if shorewall.conf has the
'MARK_IN_FORWARD_CHAIN=Yes' option ?
Thanks.
--
For Developers, A Lot Can Hap
