From: Samuel Jean <sj-netfilter@cookinglinux.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: New match ipt_nexthop
Date: Wed, 15 Sep 2004 21:20:32 -0400 [thread overview]
Message-ID: <4148EA60.6000106@cookinglinux.org> (raw)
In-Reply-To: <4148B820.3040301@trash.net>
Patrick McHardy wrote:
>>
>>
>> Bad and good comments are welcome!
>
>
>
> We already have the realm match in the kernel, which matches the
> routing realms. Is there anything you can't do with the realm
> match but with your new match ?
No, there isn't.
The realm match seems to do much more than what this new match can.
However, nexthop match doesn't require those realms routing keys and is
quite simple to set up.
router A : 192.168.0.1
router B : 192.168.0.2
iptables -A FORWARD -m nexthop --nexthop-ip 192.168.0.1 -j LOG
--log-prefix "Processed by A: "
iptables -A FORWARD -m nexthop --nexthop-ip 192.168.0.2 -j LOG
--log-prefix "Processed by B: "
I think it's not a question of functionnality, but simplicity.
Conclusion, I find this new match useless being given that realm match
can all do that.
>
> Regards
> Patrick
>
>
Cheers,
Samuel Jean
CookingLinux.org
prev parent reply other threads:[~2004-09-16 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 20:53 New match ipt_nexthop Samuel Jean
2004-09-15 21:46 ` Patrick McHardy
2004-09-16 1:20 ` Samuel Jean [this message]
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=4148EA60.6000106@cookinglinux.org \
--to=sj-netfilter@cookinglinux.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.