Odd problem under OS X:
I've tried using both pcap_inject() and pcap_sendpacket() to send raw
ethernet frames and I've found that pcap_sendpacket() has no problem
sending a 1514byte frame (14 byte ethernet header w/ 1500 bytes of
data) while pcap_inject() complains that the frame is too large (er
Aaron Turner wrote:
Long story short, I just figured out that both pcap_inject() and
pcap_sendpacket() have the same problem (a bug in my code was hiding
the error returned by pcap_sendpacket()).
However the bug doesn't seem to affect directly sending using BPF
directly or using Libnet (which a
My code is indeed based on the libnet code and does not use
BIOCSHDRCMPLT on OS X.
Looks like I'll need to see if my contacts @ Apple can get this bug
fixed. Thanks for the info Guy.
--
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing & replay tools for Unix
On 4/3/
Aaron Turner wrote:
Looks like I'll need to see if my contacts @ Apple can get this bug
fixed.
Do you have an ADC account? If so, file a bug (and send me the bug number).
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
Bug ID# 5108045
I'm going to see if I can get one of my contacts at apple to nudge it
along in the system. Unfortunately, neither of them work with the OS
X kernel, so not sure what they can do.
-Aaron
On 4/3/07, Guy Harris <[EMAIL PROTECTED]> wrote:
Aaron Turner wrote:
> Looks like I'll nee
*sigh*
Long story short, I just figured out that both pcap_inject() and
pcap_sendpacket() have the same problem (a bug in my code was hiding
the error returned by pcap_sendpacket()).
However the bug doesn't seem to affect directly sending using BPF
directly or using Libnet (which also goes throu
