From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@eurodev.net>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: [LIBNFNETLINK] Introduce nfnl_listen_for_msecs
Date: Tue, 07 Feb 2006 20:55:45 +0100 [thread overview]
Message-ID: <43E8FB41.2000905@trash.net> (raw)
In-Reply-To: <43E8CCBD.6050807@eurodev.net>
Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
>
>>I got that :) What I actually wanted to know is what kind of program
>>would need this, and if its not likely that most programs need their
>>own select-loop for dealing with other fds anyway. Or in other words,
>>I'm not convinced this feature belongs inside libnfnetlink.
>
>
> But if I want to poll events, I'll have to work with the netfilter
> netlink socket from, say libnetfilter_conntrack or a normal program. So
> it will have to know about the netlink details.
Not the details, just the fd.
> AFAICS that would be a layer violation since libnfnetlink contains all
> the low level communication system with the netlink socket.
>From a poll/select perspective, the fd itself has nothing to do with
nfnetlink, its just a fd. I don't think this belongs inside
libnfnetlink, it has no direct relationship to nfnetlink. Even
nfnl_listen is questionable, the only reason it exists is probably
that it got copied from iproute's libnetlink.
prev parent reply other threads:[~2006-02-07 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 1:47 [LIBNFNETLINK] Introduce nfnl_listen_for_msecs Pablo Neira Ayuso
2006-02-07 14:00 ` Patrick McHardy
2006-02-07 14:33 ` Pablo Neira Ayuso
2006-02-07 14:39 ` Patrick McHardy
2006-02-07 16:37 ` Pablo Neira Ayuso
2006-02-07 19:55 ` Patrick McHardy [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=43E8FB41.2000905@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.net \
/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.