90 likes | 296 Views
NAT Traversal for LISP Mobile Node. Dominik Klein, Matthias Hartmann, and Michael Menth. Overview. Problem: Communication through NAT Solution: NAT traversal mechanism Idea Flow charts Summary & discussion. Problem: Communication through NAT. Observation
E N D
NAT Traversal for LISP Mobile Node Dominik Klein, Matthias Hartmann, and Michael Menth
Overview • Problem: Communication through NAT • Solution: NAT traversal mechanism • Idea • Flow charts • Summary & discussion
Problem: Communication through NAT • Observation • MN roams in domain with private addresses • Problem • MN registers private address as RLOC at mapping service • MN reachable only within own domain MS Internet LISP domain Non-LISP domain • NAT • 17.87.7.2 MN EID 1 10.0.0.1 ? ITR/ETR RLOC B SN EID 2
Solution: NAT Traversal Router • NAT traversal router (NTR) • NTR collocated with map server (MS) • MN registers at NTR • NTR adds own RLOC for MN in MS • Traffic from outside tunneled from NTR to MN through NAT MS NTR RLOC N Internet Non-LISP domain MN EID 1 10.0.0.1 Traffic for MN • NAT • 17.87.7.2
Registration Process • Internal IP:Port External IP:Port Peer IP:Port • -------------------------------------------------------------------- • 10.0.0.1:4341 17.87.7.2:20321 RLOC N:4342 EID-to-IP:Port Mapping -----------------------------------EID 1 17.87.7.2 :20321 EID-to-RLOC Mapping ------------------------------ EID 1 RLOC N MS Internet Non-LISP domain MN EID 1 10.0.0.1 • NAT • 17.87.7.2 NTR RLOC N
Incoming Traffic • Internal IP:Port External IP:Port Peer IP:Port • -------------------------------------------------------------------- • 10.0.0.1:4341 17.87.7.2:20321 RLOC N:4342 EID-to-IP:Port Mapping -----------------------------------EID 1 17.87.7.2 :20321 EID-to-RLOC Mapping ------------------------------ EID 1 RLOC N MS LISP domain Internet Non-LISP domain MN EID 1 10.0.0.1 SN EID 2 • NAT • 17.87.7.2 ITR/ETR RLOC B NTR RLOC N
Outgoing Traffic • Observation • NTR not necessarily required as relay for outgoing traffic • Example: MN sends traffic to stationary node in other LISP domain using a direct tunnel to destination ETR LISP domain Internet Non-LISP domain MN EID 1 10.0.0.1 SN EID 2 ITR/ETR RLOC B • NAT • 17.87.7.2
Summary & Discussion • Mobile nodes not reachable behind NAT • NAT traversal router (NTR) helps • Receives traffic for MN • Relays it through the NAT to the MN • Protocol implementation in Omnet++ • Discussion • Great for MN reachability? Standardize it! • Security risk? How to avoid it?
References • LISP (http://tools.ietf.org/html/draft-ietf-lisp-05) • LISP-MN (http://tools.ietf.org/html/draft-meyer-lisp-mn-00) • LISP-INT (http://tools.ietf.org/html/draft-ietf-lisp-interworking-00) • Most recent version published on LISP mailing list • (http://www.ietf.org/mail-archive/web/lisp/current/msg01964.html) • LISP-NAT paper (http://www3.informatik.uni-wuerzburg.de/~menth/Publications/papers/Menth10-Sub-2.pdf) • LISP-NAT draft (http://tools.ietf.org/html/draft-klein-lisp-mn-nat-traversal-00)