On 08/30/2012 07:47 AM, Mark van Dijk wrote:
>
> I am not sure about is why this does not seem to do anything when it's
> added to FORWARD chain.. any idea?
>
The TTL is decremented during routing. If it is zero after being
decremented, an ICMP response is generated.
With the rule in the FORWAR
On 08/30/2012 12:58 AM, Mark van Dijk wrote:
>>>
>>> TTL(+1):P eth0 eth1 all
>>
>> With the patch I posted, you don't want 'eth1' in the DEST column
>>
>
>
> Good morning,
>
> Thanks for the patch Tom, I'll test it today. I'm not sure why I
> don't want eth1 as the destination; could you exp
> >
> > TTL(+1):P eth0 eth1 all
>
> With the patch I posted, you don't want 'eth1' in the DEST column
>
Good morning,
Thanks for the patch Tom, I'll test it today. I'm not sure why I
don't want eth1 as the destination; could you explain? What /do/ I want
to put in DEST, if anything at a
On 08/28/2012 11:12 AM, Mark van Dijk wrote:
> Tom hi,
>
> Back in 2011 you added the TTL target in tcrules per my request:
>
> http://www.mail-archive.com/shorewall-users@lists.sourceforge.net/msg12420.html
>
> Today I tried adding the rule to tcrules in shorewall 4.5.5.3 on the
> following (typic
On 08/28/2012 11:12 AM, Mark van Dijk wrote:
Tom hi,
Back in 2011 you added the TTL target in tcrules per my request:
http://www.mail-archive.com/shorewall-users@lists.sourceforge.net/msg12420.html
Today I tried adding the rule to tcrules in shorewall 4.5.5.3 on the
following (typical) setup:
Tom hi,
Back in 2011 you added the TTL target in tcrules per my request:
http://www.mail-archive.com/shorewall-users@lists.sourceforge.net/msg12420.html
Today I tried adding the rule to tcrules in shorewall 4.5.5.3 on the
following (typical) setup:
Internet -> eth0(in) -> Shorewall -> eth1(out)
