Hi Guy,
On Thu, Jan 14, 2016 at 2:00 AM, Guy Harris <[email protected]> wrote: > > On Jan 13, 2016, at 8:16 AM, Yang Luo <[email protected]> wrote: > > > I want to implement a feature that Npcap can send packets to Rx (receive > path) instead of the current Tx (send path). > > What do you mean by "send packets to the receive path"? > > Does that mean that a packet "sent" to the receive path is *not* > transmitted on the network interface, but, instead, appears as if it were a > packet that had arrived on that interface (and is processed by the Windows > networking stack)? > Yes, this is exactly what I want. > > If so, then... > > > I know how to implement this in the driver layer. But I don't know how > to add this interface to wpcap.dll. I don't want to change too much like > adding a function call. What's the best practice to do this? Thanks. > > ...it is *completely unrelated* to anything libpcap/WinPcap currently > does, and therefore *should* be done with a new function call. > I admit injecting packets into the receive path is a bit weird, but there's a guy asking for an adapter forwarding function, and I believe adding such a injecting means is a solution for him. Maybe there's a better way to do this job. I will forward his mail here. Cheers, Yang > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected] > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
