I only know of M$ NetMeeting being broken because with NAT in general your
pumping your whole internal network out on one real world Address, so what
actually breaks in netmeeting is the ability for an OUTSIDE party to contact
someone behind the NATed connection, the person inside can still initiate a
connection and both people can talk.
Other than that, it's not been in my experience for ANYTHING else to get
broken behind NAT, that's not to say that a really off the wall application
wouldn't break, I've just never seen that happen...
>This may not be specific to firewalls, but infrastructure design around a
>firewall seems appropriate, so I'm going to ask anyway. :-)
>
>I've got a client that is looking to implement RFC1918 addressing
>internally
>and implementing NAT at the gateways to a couple of ISP connections. I
>made
>mention of the fact that certain protocols get broken with NAT. Protocols
>that have IP address information embedded in the data portion of the
>packet,
>for example, would be broken, since NAT only rewrites the packet headers
>and
>doesn't deal with the data portion.
>
>The client is leaning toward a solution using NAT, but they want to know
>exactly what protocols would be broken and want to understand the issues
>they may be facing. I believe H.323 and Microsoft NetMeeting (not the
>same?) are among those which NAT breaks. I'm looking for others.
>
>Does anybody know of a list of protocols NAT is known to break? Any
>pointers to related information would be greatly appreciated.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
