From: Brad Hards <bhards@bigpond.net.au>
To: Oliver Neukum <oliver@neukum.name>,
"Folkert van Heusden" <folkert@vanheusden.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: local link configuration daemon?
Date: Wed, 20 Nov 2002 10:10:09 +1100 [thread overview]
Message-ID: <200211201010.16500.bhards@bigpond.net.au> (raw)
In-Reply-To: <200211192351.50618.oliver@neukum.name>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 20 Nov 2002 09:51, Oliver Neukum wrote:
> > It was originally done by Sebastian Kuzminsky. It basically uses the
> > kernel's packet filter (BPF) and socket code, via Libnet and libpcap. You
> > can get it from your friendly kernel.org mirror
> > (http://www.XX.kernel.org/pub/software/network/zcip/, where XX is your
> > country code).
> >
> > In the longer term, it might be appropriate to move some of it (the
> > defend part of the claim-and-defend sequence) into kernel space. I don't
> > think it makes sense to have it all in kernel space.
>
> Definitely, however you've never convinced me how you do the arp related
> part in user space at all. It seems to me that you cannot do that unless
> you take all arp handling into user space.
The approach is that there are really two different things happening:
1. Detecting when someone is trying to use our IP
2. Generating an ARP packet (which might be set to our IP, depending on
whether we are claiming or defending)
The first part is easy, as long as you have BPF support. Consider that it is
just a peer to tcpdump, only we don't want all the packets.
The second part is OK, you just need to generate raw packets. The real
functionality is in net/packet/af_packet.c, although I use Libnet
http://www.packetfactory.net/projects/libnet/
in an attempt at portability.
It might help to think of it as generating a single ARP packet (or a packet
that has the ARP format, on the wire), rather than performing the ARP
functionality.
Brad
- --
http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE92sTYW6pHgIdAuOMRApPFAJ92t006oLBNNw8munGv6K0/aFAtSACeJr+e
A7QQlOwzkRhhhGK+EuyX+D8=
=vGOO
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-11-19 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 17:02 Folkert van Heusden
2002-11-19 17:27 ` Oliver Neukum
2002-11-19 21:15 ` Brad Hards
2002-11-19 22:51 ` Oliver Neukum
2002-11-19 23:10 ` Brad Hards [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=200211201010.16500.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.name \
/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®