mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@kabuki.eyep.net>
To: scaramanga@barrysworld.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Firewall netlink question...
Date: 23 Jan 2001 18:33:48 +1100	[thread overview]
Message-ID: <E14Kxxd-0000LD-00@kabuki.eyep.net> (raw)
In-Reply-To: <20010122115826.A11297@lemsip.lan>
In-Reply-To: <20010122073343.A3839@lemsip.lan>   <Pine.LNX.4.21.0101221045380.25503-100000@titan.lahn.de>   <20010122102600.A4458@lemsip.lan> <E14Kf9W-0008PJ-00@kabuki.eyep.net>   <20010122115826.A11297@lemsip.lan>

On 22 Jan 2001 11:58:26 +0000, Scaramanga wrote:
> Hi,
> >> What was wrong with the firewall netlink? My re-implementation works great
> >> here. I can't see why anything else would be needed, QUEUE seems twice as
> >> complex. Unless with QUEUE the userspce applications can make decisions on
> >> what to do with the packet? In which case, it would be far too inefficient
> >> for an application like mine, where all i need is to be able to read the
> >> IP datagrams..
> > 
> > It can modify and then reinject the packet if it so wishes.
> 
> Excellent, I didn't pick up on that, with the cursory glance at the code i took.
> 
> I wonder, would there be any interest/point in my NETLINK module, which
> provides a backward compatible netlink interface. There are a good few
> apps out there which rely on it, and its nice not to have to run a daemon
> and install a new library, and re-write them just to continue using them...

This is a great idea.
Seeing as we have the compatability for ipchains and ipfwadm, this can't
be an altogether thing. Plus, userspace hacks to detect kernel versions
are always bad.

> egg.microsoft.com: Remote operating system guess: Solaris 2.6 - 2.7

My all-time favourite is Microsoft-IIS/4.0 (Unix) mod_ssl/2.<whatever>
OpenSSL/0.9.4

-- 
Daniel Stone
Linux Kernel Developer
daniel@kabuki.eyep.net

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
G!>CS d s++:- a---- C++ ULS++++$>B P---- L+++>++++ E+(joe)>+++ W++ N->++ !o
K? w++(--) O---- M- V-- PS+++ PE- Y PGP>++ t--- 5-- X- R- tv-(!) b+++ DI+++ 
D+ G e->++ h!(+) r+(%) y? UF++
------END GEEK CODE BLOCK------



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-01-23  7:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22  7:33 Scaramanga
2001-01-22  9:46 ` Philipp Matthias Hahn
2001-01-22 10:26   ` Scaramanga
2001-01-24 12:27     ` Harald Welte
2001-01-22 11:28   ` Daniel Stone
2001-01-22 11:58     ` Scaramanga
2001-01-24  4:28       ` Scaramanga
2001-01-24 12:30         ` Harald Welte
2001-01-24 15:26           ` Scaramanga
2001-01-23  7:33     ` Daniel Stone [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=E14Kxxd-0000LD-00@kabuki.eyep.net \
    --to=daniel@kabuki.eyep.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scaramanga@barrysworld.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

all inboxes | Powered by JetHome®