<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 25 Sep 2013, at 11:17, Sander Steffann <<a href="mailto:sander@steffann.nl">sander@steffann.nl</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br><blockquote type="cite">But I note that the OP is *currently* testing with a single hosts w/ two interfaces, so host-based source address selection is what's in play here, not (s,d) routing.<br></blockquote><br>It's not source address selection if the host is replying to an incoming (ICMP ping) packet. The source address is fixed, and the OP wants the host to route the outgoing packet through the correct interface.<br></blockquote><div><br></div>And to complement that the homenet scenario is to ensure the packet gets routed out the right exit to avoid ISP ingress filtering, given a host may not have the information required to perform optimal source address selection for a communication - it's then down to the routing system to push the packet out the right way.</div><div><br></div><div>We saw at an IETF last year a nice demo of zero configuration OSPF being used to both automatically configure prefixes in a home network, and to route based on source and destination. You can find that code (for Bird) and other interesting stuff here <a href="https://github.com/fingon">https://github.com/fingon</a>. We also have the zero config OSPF stuff implemented in Quagga, to demonstrate interop (though personally I like Bird).</div><div><br></div><div>It would be good for people to read and comment on Ole's SADR draft, <a href="http://tools.ietf.org/html/draft-troan-homenet-sadr-01">http://tools.ietf.org/html/draft-troan-homenet-sadr-01</a>.</div><div><br></div><div>Tim<br></div><br></body></html>