From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add support for ttl translation
Date: Mon, 4 Jan 2016 18:44:33 +0100 [thread overview]
Message-ID: <20160104174433.GA3947@salvia> (raw)
In-Reply-To: <CAKHNQQG5oxf2cZ-36ohksHC+rSxGJzFGo2a-Ov_gjbCGh8_WvQ@mail.gmail.com>
On Mon, Jan 04, 2016 at 11:12:55PM +0530, Shivani Bhardwaj wrote:
> On Mon, Jan 4, 2016 at 11:10 PM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > On Mon, Jan 04, 2016 at 10:49:10PM +0530, Shivani Bhardwaj wrote:
> >> This patchset adds ttl translation to nftables by adding ip ttl to
> >> the buffer everytime a ttl match is hit as it is necessary to mention
> >> the protocol version with ttl, that is,
> >> $ sudo nft .. ttl 3 .. won't work but
> >> $ sudo nft .. ip ttl 3 .. would work.
> >
> > This above is the right syntax.
> >
> >> Also, since adding ip to the buffer in the code for ttl won't look
> >> suitable, some amendments have been done in the nft-ipv4 code.
> >>
> >> Shivani Bhardwaj (2):
> >> iptables: nft-ipv4: Add ip ttl to the buffer
> >
> > I don't think you need this change for nft-ipv4.
>
> Hi Pablo,
>
> Should I be doing xt_buf_add("ip ttl") in the code for ttl?
Yes, that should be fine.
prev parent reply other threads:[~2016-01-04 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 17:19 [PATCH 0/2] Add support for ttl translation Shivani Bhardwaj
2016-01-04 17:19 ` [PATCH 1/2] iptables: nft-ipv4: Add ip ttl to the buffer Shivani Bhardwaj
2016-01-04 17:20 ` [PATCH 2/2] extensions: libipt_ttl: Add translation to nft Shivani Bhardwaj
2016-01-04 17:40 ` [PATCH 0/2] Add support for ttl translation Pablo Neira Ayuso
2016-01-04 17:42 ` Shivani Bhardwaj
2016-01-04 17:44 ` Pablo Neira Ayuso [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=20160104174433.GA3947@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shivanib134@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).