On Sat, Jan 19, 2002 at 09:50:07PM -0500, Michael Richardson wrote: > My understanding is that QNX never contributed their patches back to > tcpdump.org, so we can't even read the code to help you. In any case, we have > no QNX boxes to test on anyway. > I suggest contacting QNX directly to find out who ported the code.
Here's the message I sent out the last time somebody asked about QNX support; the person who apparently did the port was Chris McKillop <[EMAIL PROTECTED]>. From: Guy Harris <[EMAIL PROTECTED]> Subject: Re: [tcpdump-workers] QNX port for tcpdump To: Ravi Puvvala <[EMAIL PROTECTED]> Date: Wed, 17 Oct 2001 13:31:52 -0700 (PDT) CC: [EMAIL PROTECTED] > I can't get the tcpdump stuff to run on a QNX machine. That's because none of us with commit privileges have, as far as I know, any idea what the QNX mechanism for packet capture is (I certainly don't), and nobody's sent us a patch to add support for libpcap. > I get the following error > > # ./tcpdump -i en0 > tcpdump: live packet capture not supported on this system That's correct - tcpdump.org's libpcap does not support live packet capture on QNX, because we have no idea how to make it do so, and nobody's told us how to make it do so. > But I know that there was some port for QNX at onepoint > from the QNX website, which I can't access any longer. Send mail to [EMAIL PROTECTED] asking him to please send patches for QNX support to [EMAIL PROTECTED], so that we can add that support. (Ask him to do so based on the current CVS version, so that, if possible, he can make the new APIs for getting lists of interfaces and network addresses work on QNX.) If that bounces, that may mean he's no longer at QNX, so you may have to ask QNX for help. - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
