Thus spake "Tony Li" <tony.li@tony.li>
|> Simply this: if return packets leaving a LISP site, headed |> for a non-LISP site, use a EID as the source address, then it |> is highly likely that the packets will be dropped due to the |> source address filtering. | |It would pass a lose-mode check since the route is in the table, which |is the current best practice for multi-homed networks. Ok, but as you're transitioning to LISP, you want to remove routes to EID prefixes from the routing table. That breaks loose or strict mode.
Presumably, the EID _aggregate_ would be in the routing table, so loose mode would succeed. However, the route would be pointing in the "wrong" direction, so strict mode would fail. Putting a static route (not redistributed) for the customer's EID on their interface would make both succeed.
S Stephen Sprunk "God does not play dice." --Albert Einstein CCIE #3723 "God is an inveterate gambler, and He throws theK5SSS dice at every possible opportunity." --Stephen Hawking
-- to unsubscribe send a message to rrg-request@psg.com with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg