>> >> Let me first describe one-interface routers as I understand are proposed >> in 6LoWPAN: >> >> +------------------------+---------------+ >> | | | >> 2001:db8:1::1/128 2001:db8:1::2/128 2001:db8:1::3/128 >> _|eth0 _|eth0 _|eth0 >> |R1 | |R2 | |R3 | >> --- --- --- >> >> R1 sends an IP packet to R3 but this reaches only R2. R2 picks the >> packet, looks at the dst address, finds it's not for self, consults >> routing table, finds a host-based route and sends it to R3. This can >> work ok. > >Exactly, you pictured this nicely. This is how LoWPAN Routing works. >I'll get back to the definition of that in your other thread.
Note that over the Ethernet backbone shown here, if R1 and R3 are edge routers then R1 will reach R3 directly. This will happen because R1 still has a connected route 2001:db8:1::/64 over the backbone, and it will use RFC 4861 to locate R3 there. The binding table will be consulted first but that will fail because R3 is not a 6LoWPAN node registered to R1. Very much like a Home Agent operation on a Home link if you wish. Pascal _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
