How to use ip_queue without linking libipq?

How to use ip_queue without linking libipq?

[Luca Abeni]

Hi all,

I've been asked to develop a user-space application receiving packets
from the ip_queue module. I know the simplest solution would be to use
libipq, but unfortunately the application cannot be released under GPL
(because it also uses some proprietary code).

So, I am thinking about directly interacting with the ip_queue module by
using netlink. However, I know how to open a netlink socket, but I've
not been able to find any documentation about how to use a netlink
socket to communicate with ipqueue...

I think that looking at libipq code for understanding how to use ipqueue
would be a license violation (I would end up with a code too similiar to
libipq), right?

Is some documentation about directly using ipqueue available somewhere?
Can anyone help me?

			Thanks,
				Luca

(P.S.: please cc me because I am not subscribed to the mailing list)
-- 
_____________________________________________________________________________
Copy this in your signature, if you think it is important:
                               N O    W A R ! ! !

Re: How to use ip_queue without linking libipq?

[Tobias DiPasquale]

On 6/20/05, Luca Abeni <lucabe72@email.it> wrote:
> I think that looking at libipq code for understanding how to use ipqueue
> would be a license violation (I would end up with a code too similiar to
> libipq), right?

I believe it would.
 
> Is some documentation about directly using ipqueue available somewhere?
> Can anyone help me?

IANAL, but...

You'd have to clean-room it: get someone else to study the libipq
source and write you a document specifying how to interface with the
ip_queue module via netlink. Yourself, you should not look at the
libipq source, only this other person. That would then allow you to
write a non-GPL interface to ip_queue functionality. This is how the
original third-party BIOS was designed and implemented, circumventing
IBM's proprietary license on it.

-- 
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d