Re: [tcpdump-workers] pcap_inject() fails with rc 0 on HP-UX

2006-04-07 Thread Harley Stenzel
[ I really can't seem to set the proper account for these responses Here's to fooling the duplicate message detector ] On 4/4/06, Guy Harris <[EMAIL PROTECTED]> wrote: > Harley Stenzel wrote: > > 2) It's not clear under what circumstances a rc 0 could ever be > > returned. Only on retrun from

Re: [tcpdump-workers] pcap_inject() fails with rc 0 on HP-UX

2006-04-04 Thread Guy Harris
On Apr 4, 2006, at 8:51 AM, Harley Stenzel wrote: On 4/3/06, Rick Jones <[EMAIL PROTECTED]> wrote: I believe this is a long-standing limitation of promiscuous mode support in HP-UX - only one process may have a promiscuous stream open on an interface at one time. I believe that is the cas

Re: [tcpdump-workers] pcap_inject() fails with rc 0 on HP-UX

2006-04-04 Thread Harley Stenzel
On 4/3/06, Rick Jones <[EMAIL PROTECTED]> wrote: > > 4) What is the expected interaction of multiple libpcap instances on > > HP-UX? I can't use my program and tcpdump at the same time; something > > I can do on other OSes. > > I believe this is a long-standing limitation of promiscuous mode suppo

Re: [tcpdump-workers] pcap_inject() fails with rc 0 on HP-UX

2006-04-03 Thread Guy Harris
Harley Stenzel wrote: However, on HP-UX, that same call returns rc 0. I was not able to find a pre-existing bug for this problem, however I was able to find this message: http://www.tcpdump.org/lists/workers/2004/03/msg00103.html indicating that at least in 2004, HP-UX send would not work

Re: [tcpdump-workers] pcap_inject() fails with rc 0 on HP-UX

2006-04-03 Thread Rick Jones
WRT the return of zero as the number of bytes - perhaps some of the code in pcap_dpli is ass-u-me-ing the return value from a call will give that? I've not looked at that source in a very long time though... 4) What is the expected interaction of multiple libpcap instances on HP-UX? I can't

[tcpdump-workers] pcap_inject() fails with rc 0 on HP-UX

2006-04-03 Thread Harley Stenzel
Greetings-- [ obligatory new content because I messed up the content the first time around. ] I opened a bug report on sourceforge about this, but now have some additional observations, and I would like some guidance about how to best further debug the problem. I've included that bug report here