From: "Jörg Harmuth" <harmuth@mnemon.de>
To: netfilter@lists.netfilter.org
Subject: Re: layer7 problem
Date: Wed, 24 Aug 2005 14:22:53 +0200 [thread overview]
Message-ID: <430C669D.7020501@mnemon.de> (raw)
In-Reply-To: <430C62F7.9040703@telefonica.net>
Antonio Pérez schrieb:
> Jörg Harmuth wrote:
>
>> Antonio Pérez schrieb:
>>
>>
>>> Hi Joerg,
>>>
>>> Thanks for your reply, I also tried PREROUTING and also many different
>>> protocols, not only http and the problem remains the same, everything
>>> seems to work properly, no errors, but the number of marked packets
>>> remains empty.
>>> Any idea will be apreciated, thanks.
>>>
>>
>>
>> Could you please post the output of iptables-save ? I assume, that some
>> other rules are the culprit ;)
>>
>> Have a nice time,
>>
>> Joerg
>>
>>
>>
>>
> iptables-save
> # Generated by iptables-save v1.3.3 on Wed Aug 24 14:05:01 2005
> *mangle
> :PREROUTING ACCEPT [633:402628]
> :INPUT ACCEPT [633:402628]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [606:91422]
> :POSTROUTING ACCEPT [606:91422]
> -A PREROUTING -m layer7 --l7proto http -j MARK --set-mark 0x1
> -A PREROUTING -m layer7 --l7proto dns -j MARK --set-mark 0x1
> -A POSTROUTING -m layer7 --l7proto http -j MARK --set-mark 0x1
> -A POSTROUTING -m layer7 --l7proto dns -j MARK --set-mark 0x1
> COMMIT
> # Completed on Wed Aug 24 14:05:01 2005
[SNIP]
> I applied layer7 patch to kernel and iptables, do I need to add any
> other path?
No, that will do. Well, these rules are fine - but it's only mangle
table. What about filter / nat table ? Any rules in these chains ? Any
policies set to DROP ?
Have a nice time,
Joerg
next prev parent reply other threads:[~2005-08-24 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 0:54 layer7 problem Antonio Pérez
2005-08-24 8:57 ` Jörg Harmuth
2005-08-24 9:30 ` Antonio Pérez
2005-08-24 10:27 ` Jörg Harmuth
2005-08-24 12:07 ` Antonio Pérez
2005-08-24 12:22 ` Jörg Harmuth [this message]
2005-08-24 13:59 ` Antonio Pérez
2005-08-24 14:32 ` Jörg Harmuth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=430C669D.7020501@mnemon.de \
--to=harmuth@mnemon.de \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox