On 7/31/06, Rick Jones <[EMAIL PROTECTED]> wrote:
I thought that one thread was send/recv and the other was send. The "send only"
thread ostensibly would not need to be in promiscuous mode right?
Sort of. Promiscous mode on the NIC and promiscous on the STREAM are
two different things. Libp
Harley Stenzel wrote:
On 7/28/06, Guy Harris <[EMAIL PROTECTED]> wrote:
On Jul 28, 2006, at 12:51 PM, Harley Stenzel wrote:
> Show that this happens when 2 threads use pcap_t at the same time:
libpcap is, for better or worse, not thread-safe,
Good to know, thanks.
Using *different* pca
On 7/28/06, Guy Harris <[EMAIL PROTECTED]> wrote:
On Jul 28, 2006, at 12:51 PM, Harley Stenzel wrote:
> Show that this happens when 2 threads use pcap_t at the same time:
libpcap is, for better or worse, not thread-safe,
Good to know, thanks.
Using *different* pcap_t's in two threads shoul
On Jul 28, 2006, at 12:51 PM, Harley Stenzel wrote:
Show that this happens when 2 threads use pcap_t at the same time:
libpcap is, for better or worse, not thread-safe, in the sense that
no locking is done on the pcap_t structure to prevent concurrent
accesses from stepping on each other,
Greetings--
I'm seeing something quite strange.
I have a libpcap stack application. One thread may send while another
thread both receives and sends. (Sends in response to a packet, and
send in response to a timeout).
This works fine on Solaris, which also uses DLPI.
On HP-UX, transmission f
