> The NAT problems only > start when the protocol carries IP address/port information (such > as the FTP 'PORT' command), and the NAT isn't aware of that protocol's > translation requirements this is a popular misconception; it's a bit like saying that y2k only breaks programs that store years in two digits. see http://www.cs.utk.edu/~moore/what-nats-break.html for my attempt to list the various ways that programs can lose in the presence of NATs. Keith
- Re: IP network address assignments/allocation... Keith Moore
- Re: IP network address assignments/alloca... Richard Shockey
- Re: IP network address assignments/allocations inf... Steve Hultquist
- RE: IP network address assignments/allocations inf... Tony Hain (Exchange)
- RE: IP network address assignments/allocation... Pete Loshin
- RE: IP network address assignments/allocation... Paul Ferguson
- Re: IP network address assignments/alloca... Daniel Senie
- RE: IP network address assignments/alloca... Matt Holdrege
- RE: IP network address assignments/allocations inf... Ian King
- Re: IP network address assignments/allocation... Valdis . Kletnieks
- Re: IP network address assignments/alloca... Keith Moore
- Re: IP network address assignments/alloca... John Day
- X.25 as a model for NAT boxes - NOT Harald Tveit Alvestrand
- Re: X.25 as a model for NAT boxes... John Day
- Re: IP network address assignments/allocation... Keith Moore
- Re: IP network address assignments/allocation... Perry E. Metzger
- RE: IP network address assignments/allocations inf... Steve Hultquist
- RE: IP network address assignments/allocations inf... Melinda . Shore
- Re: IP network address assignments/allocation... Henning Schulzrinne
- RE: IP network address assignments/allocations inf... Steve Hultquist
- Re: IP network address assignments/allocations inf... Pyda Srisuresh