[Twisted-Python] Layer 2 and Twitsted

[outcast]

On Tue, Jan 15, 2013 at 2:19 PM, <exarkun at twistedmatrix.com> wrote:

> On 06:06 pm, james.voip+twisted at gmail.com wrote:
> >On Tue, Jan 15, 2013 at 12:58 PM, outcast
> ><james.voip+twisted at gmail.com>wrote:
> >>
> >>I have been working on a kernel module to allow me to get the packets
> >>out
> >>of kernel land and into user space ATM. Not sure how twisted.pair does
> >>that. I will go and google but the ultimate goal is to have a complete
> >>network stack in python. So any information would be greatly
> >>appreciated.
> >>If I can get some good traction I might bring it to the next
> >>hack-a-thon
> >>just learning ATM but I have purpose in mind.
> >>
> >>
> >>
> >>
> >>
> >>Just looked at the documentation. it looks like it using libpcap and
> >>tun
> >interface. No real hooks into ethX type devices.
>
> How is that different from what you want?  Are you looking to get
> ethernet frames instead of IP datagrams?  You can do that with tun
> devices too (perhaps they're called "tap" devices when used in that
> context, though there's basically no difference in how they are set up
> and used).
>
> Jean-Paul
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>


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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20130115/5d20ada7/attachment.html>