<br><br><div class="gmail_quote">On Tue, Jan 15, 2013 at 2:19 PM, <span dir="ltr"><<a href="mailto:exarkun@twistedmatrix.com" target="_blank">exarkun@twistedmatrix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 06:06 pm, <a href="mailto:james.voip%2Btwisted@gmail.com">james.voip+twisted@gmail.com</a> wrote:<br>
>On Tue, Jan 15, 2013 at 12:58 PM, outcast<br>
><<a href="mailto:james.voip%2Btwisted@gmail.com">james.voip+twisted@gmail.com</a>>wrote:<br>
>><br>
</div><div class="im">>>I have been working on a kernel module to allow me to get the packets<br>
>>out<br>
>>of kernel land and into user space ATM. Not sure how twisted.pair does<br>
>>that. I will go and google but the ultimate goal is to have a complete<br>
>>network stack in python. So any information would be greatly<br>
>>appreciated.<br>
>>If I can get some good traction I might bring it to the next<br>
>>hack-a-thon<br>
>>just learning ATM but I have purpose in mind.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>>Just looked at the documentation. it looks like it using libpcap and<br>
>>tun<br>
>interface. No real hooks into ethX type devices.<br>
<br>
</div>How is that different from what you want? Are you looking to get<br>
ethernet frames instead of IP datagrams? You can do that with tun<br>
devices too (perhaps they're called "tap" devices when used in that<br>
context, though there's basically no difference in how they are set up<br>
and used).<br>
<br>
Jean-Paul<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a></div></div></blockquote><div><br></div><div> </div></div>Don't want to use tap type of devices. Want to be able to handle packets natively from the interface with minimal amount of overhead. Basically want my own rx_handler to python call back. Yes I want the raw ethernet frames. Looking at an embedded solution so its a case of less is more.<div>
<br></div><div><br><div><br></div><div><br></div></div>