Re: User-space controlled raw ethernet - Is this the way to go?

On Mon, 25 Feb 2008 04:24:57 -0800 (PST) David Schwartz <davids@xxxxxxxxxxxxx> wrote:
| On Feb 25, 2:54 am, Andrew Greensted <ajg...@xxxxxxxxxxxxxx> wrote:
|
|> Hi David,
|>
|> Actually this was my first approach. But I really wasn't that happy with
|> the overhead of the IP and UDP headers.
|
| Then you will need to provide a driver to figure out what goes where.
| Otherwise, there is simply no way for the kernel to arbitrate who gets
| the data.

I've said this years ago. It applies here, too. All network interfaces
should have been device nodes. Then you could let a process open one of
them in the normal I/O way (as long as it is not busy from being an active
network interface). An ethernet port is really not much more than a fancy
serial port. Then the answer to the OPs question (if even asked) would be
something like: give permission for the user in question via permission on
the device node file, and let it open it as needed.

--
|---------------------------------------/----------------------------------|
| Phil Howard KA9WGN (ka9wgn.ham.org) / Do not send to the address below |
| first name lower case at ipal.net / spamtrap-2008-02-25-0816@xxxxxxxx |
|------------------------------------/-------------------------------------|
.