[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-dev
Subject: Re: [Wireshark-dev] Adding interface to wpcap/libpcap for sending packets to Rx path
From: Yang Luo <hsluoyb () gmail ! com>
Date: 2016-01-14 15:41:47
Message-ID: CAM_tFoag-vWw=yZQhcm=exd76voDpJ-ZFtgB5_MxtKr0POBX8Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Guy,
On Thu, Jan 14, 2016 at 2:00 AM, Guy Harris <guy@alum.mit.edu> wrote:
>
> On Jan 13, 2016, at 8:16 AM, Yang Luo <hsluoyb@gmail.com> 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 <wireshark-dev@wireshark.org>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@wireshark.org
> ?subject=unsubscribe
>
[Attachment #5 (text/html)]
<div dir="ltr"><div>Hi Guy,</div><br><div class="gmail_extra"><br><div \
class="gmail_quote">On Thu, Jan 14, 2016 at 2:00 AM, Guy Harris <span \
dir="ltr"><<a href="mailto:guy@alum.mit.edu" \
target="_blank">guy@alum.mit.edu</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class=""><br> On Jan 13, 2016, at 8:16 AM, Yang Luo \
<<a href="mailto:hsluoyb@gmail.com">hsluoyb@gmail.com</a>> wrote:<br> <br>
> I want to implement a feature that Npcap can send packets to Rx (receive path) \
instead of the current Tx (send path).<br> <br>
</span>What do you mean by "send packets to the receive path"?<br>
<br>
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)?<br></blockquote><div><br></div><div>Yes, this is exactly what I \
want.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
If so, then...<br>
<span class=""><br>
> 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.<br> <br>
</span>...it is *completely unrelated* to anything libpcap/WinPcap currently does, \
and therefore *should* be done with a new function \
call.<br></blockquote><div><br></div><div>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.</div><div><br></div><div>Cheers,</div><div>Yang</div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> \
___________________________________________________________________________<br> Sent \
via: Wireshark-dev mailing list <<a \
href="mailto:wireshark-dev@wireshark.org">wireshark-dev@wireshark.org</a>><br>
Archives: <a href="https://www.wireshark.org/lists/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/lists/wireshark-dev</a><br>
Unsubscribe: <a href="https://wireshark.org/mailman/options/wireshark-dev" \
rel="noreferrer" target="_blank">https://wireshark.org/mailman/options/wireshark-dev</a><br>
mailto:<a \
href="mailto:wireshark-dev-request@wireshark.org">wireshark-dev-request@wireshark.org</a>?subject=unsubscribe<br>
</blockquote></div><br></div></div>
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic