This blog was originally started to better help me understand the technologies in the CCIE R&S blueprint; after completing the R&S track I have decided to transition the blog into a technology blog.

CCIE #29033

This blog will continue to include questions, troubleshooting scenarios, and references to existing and new technologies but will grow to include a variety of different platforms and technologies. Currently I have created over 185 questions/answers in regards to the CCIE R&S track!! Note: answers are in the comment field or within "Read More" section.

You can also follow me on twitter @FE80CC1E


Saturday, July 2, 2011

TURN

TURN - Traversal Using Relay NAT - allows a device that is behind a firewall or NAT (Symmetric NAT or better known as Bi Directional NAT) device to receive incoming data leveraging TCP or UDP. TURN will most likely provide connectivity to the client but it does come at a high price to the provider. STUN is generally used first and TURN is used as a last resort.

The host sitting behind the NAT device is called a TURN client which connects the the TURN server on the public internet which acts as a relay. The TURN client communicates and arranges with the TURN server to have the server relay the packets to the desired peer. When the TURN client and peer want to communicate, the communication from the TURN client to the TURN Server is encapsulated within a TURN MESSAGE. The communication between the peer and the TURN server is not encapsulated.

TURN - RFC 5766

0 comments:

Post a Comment