This link was posted the other day. Check out:
http://www.cisco.com/cgi-bin/Support/browse/psp_view.pl?p=Internetworking:NA T watch the wrap this is a jump page, with links to a number of resources, including RFC 1631. The process is quite simple. For normal NAT, the NAT engine replaces the source address with an address from the NAT pool. Contrary to popular believe, you can NAT private to private, private to public, public to public, and every variation you can think of. The NAT engine maintains a table of translations, and rewrites the source address to outbound packets, and destination address for inbound packets. For static NAT, the translations come from a fixed table, not a dynamic pool. For NAT overload ( multiple addresses translated to a single address) the NAT engine will rewrite the source address and source TCP port for all packets outbound. the NAT engine maintains a state table and reverses the process for inbound packets. I.e. destination address and destination port. BTW, I was browsing a NAT document, published by Cisco, that states that Cisco developed NAT. I did not see any indication of this in the RFC, written by two people apparently not associated with Cisco that I could tell. Anyone got the skinny? -- TANSTAAFL "there ain't no such thing as a free lunch" ""Dwayne Saunders"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Hi all, > Was just wondering if any one could put me on to a good link in > regards NAT and packet headers, simply what I am trying to find out is the > packet header total rewritten or just the ip address part of the header and > checksum, Or is a new header written to envelope the original header. > > Or does each application do it differently. > > Any help would be great. > > Regards > > D'Wayne Saunders Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60787&t=60784 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
