On Thu, Oct 24, 2013 at 11:00:49AM -0300, Werner Almesberger wrote: > Alexander Aring wrote: > > On receiving side we don't need to set any headers in skb. The deliver > > function delivers the skb to ipv6 handler and the ipv6 handler will set > > these headers. > > If with "the ipv6 handler" you mean the things that happen after > calling netif_rx, then part of the comment is misleading. > > ipv6/ip6_input.c:ipv6_rcv sets skb->transport_header, so this is > indeed IPv6. However, the network header is reset by > core/dev.c:__netif_receive_skb_core which isn't IPv6-specific. > mhh, I can just leave it there. I test it and it works without setting of any headers position. Or should I say the headers are set in the upcomming processes.
The current process looks like that: ieee802154_rx_irqsafe -> mac -> netif_rx -> lowpan -> netif_rx -> __netif_receive_skb_core -> ipv6 so somewhere in "__netif_receive_skb_core -> ipv6" the headers are set and we don't need to access this to replace the 6LoWPAN header with ipv6/udp headers. - Alex ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
