Sorry about that. I was interpretating raw packets as raw sockets. I did find a link that gave some info. about sending raw ethernet frames in Windows. Although not quite enough info.
http://codeproject.com/csharp/SendRawPacket.asp I'll have to dig some more to see what else I can find. Rob > > On Jun 15, 2004, at 11:13 AM, Rob Turpin wrote: > >> Some clarification. >> >> 1. WinPcap (Windows), libpcap(Unix) have nothing to do with sending >> packets. > > Perhaps they don't have anything to do with sending packets; > nevertheless, WinPcap has, for several releases, had an API that sends > packets, and some versions of libpcap such as the OpenBSD one also has > such an API - the current CVS version of libpcap has the original > WinPcap API (not the buffered-send APIs) and the OpenBSD API. > >> cap - as in capture. > > That was its original purpose, perhaps, but it's expanded over time to > offer more functionality useful for various types of applications > dealing with raw link-layer packets, such as an API to get lists of > network interfaces and those interfaces' addresses (as the way that's > done is platform-dependent, just as the way raw packets are captured > and transmitted are platform-dependent). > >> 2. Windows does have an API to create and send raw packets. > > Raw *link-layer* packets, or just raw IP/ICMP/etc. packets? > > > > ================================================================== > This is the WinPcap users list. It is archived at > http://www.mail-archive.com/[EMAIL PROTECTED]/ > > To unsubscribe use > mailto: [EMAIL PROTECTED] > ================================================================== ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
