From: "Juraj Gabčík" <juraj.gabcik@gmail.com>
To: netfilter@vger.kernel.org
Subject: Fwd: nftables
Date: Fri, 29 Apr 2011 11:33:38 +0200 [thread overview]
Message-ID: <BANLkTik1LTarzTzAm_9OuD8XkhsXcpVCZg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikT_ETuEE2e7Khip9xJKFiDgBe7Qg@mail.gmail.com>
Hi people!
First, I would like to introduce myself to you. My name is Juraj
Gabèík and I am a student at the Faculty of Informatics at the
University of ®ilina, Slovakia. My reason for writing to you is that I
would like to ask you for a favour. Now I am writing my bachelor's
theses about nftables and I would be grateful to you for some
information I need concerning this issue. I found something on the
internet but it wasn't enough.
I am interested in the background of the processing of packet after
it's received by NIC: what queues it passes, where the rules can be
applied etc. Neither I could find any information about whether
nftables have the same structure of classes INPUT, OUTPUT and FORWARD
as iptables.
I need to compare the efficiency of the firewall created by iptables
and nftables and I would be very grateful if you could explain to me
the main differences between the processing of packet by means of
iptables and nftables. Also a demonstration of some rules written by
means of iptables and nftables (rules of the same meaning in both
cases) would be very helpful.
How to compile kernel supporting nftables?
If you would come up with something more that would help me or that
would be useful for my theses I would highly appreciate it. As I have
already mentioned, I am mainly concerned about the information related
to the background of the processing of the packet and the comparison
of the efficiency of iptables and nftables.
Hope to hear from you soon,
Juraj Gabèík
next parent reply other threads:[~2011-04-29 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikT_ETuEE2e7Khip9xJKFiDgBe7Qg@mail.gmail.com>
2011-04-29 9:33 ` Juraj Gabčík [this message]
2011-04-29 10:06 ` nftables Jan Engelhardt
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=BANLkTik1LTarzTzAm_9OuD8XkhsXcpVCZg@mail.gmail.com \
--to=juraj.gabcik@gmail.com \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).