|
From: | Enrico Lehmann |
Subject: | Re: [lwip-devel] ipv6 processing - Edge router implementation |
Date: | Sun, 06 May 2012 23:19:09 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 |
Since RPL is not the only way to doing 6LoWPAN routing, I'am using a 'mesh-under' solution. But certainly RPL is the preferred way that should be used for 6LoWPAN. Which is obviously the case, since RPL is standardized in march as RFC6550. Maybe later a jump to RPL is necessary and thats the point where implement RPL over lwIP.I would like to at some point code a 6LowPAN netif for LwIP that would handle fragmentation and reassembly, but I haven't found the time yet.I'm using such a 6LoWPAN solution supporting fragmentation/reassembly and header compression. This function is installed as ip6_output() for the 6LoWPAN netif. So any received wireless packet is going through the reassembly/header-compression part and than goes to ip6_input(). Any packet on Border Router which is destined to a wireless node is processed by ip6_input() and further processed by fragmentation/header-compression layer.That's the way to do it. One obstacle I've faced with this approach is that I would need to implement RPL over LwIP. This is too much work for me at the moment.
In accordance to my free time, I will start a implementation. If the code reaches a level to share, I'll come back up here.Other than that, you can always use LWIP_IP6_FORWARDING and that has been working well for me.In fact thats true - I already using that. But I was thinking of a 'real' Router which is capable to transmit Router Advertisements and process Router Solicitations. So I have to think about to implement such a solution - maybe we can support and share some knowledge to each other?!Router advertisements and solicitations are a TODO in the current code, so any contribution here is very welcome!
Cheers Ivan
[Prev in Thread] | Current Thread | [Next in Thread] |