reported that the modules loaded fine.
Thanks for all your help!
Richard
> -Original Message-
> From: KP Kirchdoerfer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 27, 2005 1:10 AM
> To: leaf-user@lists.sourceforge.net
> Subject: Re: [leaf-user] CONNMARK in uC
Am Donnerstag, 27. Oktober 2005 00:21 schrieb Richard Amerman:
> Thanks Tom,
>
> > -Original Message-
> > From: Tom Eastep [mailto:[EMAIL PROTECTED]
> >
> > On Wednesday 26 October 2005 14:40, Richard Amerman wrote:
> > > That command includes the following:
> > >
> > > CONNMARK target v1.3
Thanks Tom,
> -Original Message-
> From: Tom Eastep [mailto:[EMAIL PROTECTED]
>
> On Wednesday 26 October 2005 14:40, Richard Amerman wrote:
>
> >
> > That command includes the following:
> >
> > CONNMARK target v1.3.3 options:
> > --set-mark value[/mask] Set conntrack mark val
On Wednesday 26 October 2005 14:40, Richard Amerman wrote:
>
> That command includes the following:
>
> CONNMARK target v1.3.3 options:
> --set-mark value[/mask] Set conntrack mark value
> --save-mark [--mask mask] Save the packet nfmark in the connection
> --restore-mark [--mask m
>The Extended MARK Target is irrelevant -- nothing in Shorewall
currently uses
>it and detection and reporting of that capability are removed in
Shorewall
>3.0.
> Does "iptables -j CONNMARK --help" display CONNMARK-related help?
> -Tom
Tom: Thanks for the reply
That command includes the
On Monday 24 October 2005 14:45, Richard Amerman wrote:
>
> When I restart shorewall I still get:
>
> Extended MARK Target: Not available
> CONNMARK Target: Not available
> Connmark Match: Available
>
The Extended MARK Target is irrelevant -- nothing in Shorewall currently uses
it and detection