NAT Traversal in HIP

Xiang LIUTML/HIIT

(frogsir@gmail.com)

Agenda

• On Current Internet• Traversal technologies (General vs. HIP)• DEMO details

On Current Internet

• Popular of NAT(IPv4)• NATs understand TCP & UDP, but not HIP

Behave/MMusic NAT traversal Solution

• STUN (Hole Punching Technology)• TURN• ICE• Others (configure in NAT box)

Solutions for HIP

• HIP over UDP (port 50500)• STUN <----> RVS• TURN <---->HIP relay(FULL relay)• ICE (design for SIP) <----> HIP ICE– code borrowed from PJ project

Demo Set Up

VM ware NAT

FROG(HIP RELAY)

OOPS(VM host)

CRASH(VM host)

DEMO Background

• Preconditions (registration):– FROG offers HIP Relay service• All the basic HIP exchange will go thorough FROG

– Crash knows the HIT of OOPS– Crash Knows the IP of OOPS, which actually

belongs to FROG (public IP)

• Phases:– Locator exchange, candidates pairing, reachability

testing

Registration

• OOPS register itself to FROG using the basic exchange.

• OOPS sends keep-live messages to refresh the NAT state

Locator exchange

• Crash --I1-- >FROG(relay server) ---I1---> OOPS • Crash <--R1--FROG<---R1--- OOPS • Crash –I2-->FROG---I2--- >OOPS • Crash <--R2--FROG<---R2--- OOPS

• Locators are exchanged in R1 and I2

FULL Relay

VM ware NAT

FROG(HIP RELAY)

OOPS(VM host)

CRASH(VM host)

ICE Session

• After the basic exchange, the OOPS and Crash start ICE session at the same time.

• Reachability testing starts.

Reachability Testing

VM ware NAT

FROG(HIP RELAY)

OOPS(VM host)

CRASH(VM host)

Establish Security Policies and Associations

• ICE will give the best IP:port pair for the SA connection.

SP/SA

VM ware NAT

FROG(HIP RELAY)

OOPS(VM host)

CRASH(VM host)

Questions?