Per Jessen wrote:
I can't personally blame NAT for that - the range of RFC1918 address is so vast that the risk of a clash is minimal - unless you choose to use a commonly used range. My VPN runs on 10.221.78.0/22.
Choose whatever you want, you cannot guarantee someone else won't choose it. When I found out about the clash, I wasn't in a position to change my home network, as I was a four hour flight from home.
I'm sure there are some, although I haven't heard of nor had any hard problems in that respect. Which, quite selfishly, makes me conclude that there aren't any_real_ problems. In another note, I mentioned the authentication header problem with IPSec when NAT is used. This means anyone using NAT will not be able to use that security feature. There are others.
All I'm saying is - don't start using NAT tomorrow if you aren't already, but if you're using it today, do carry on using it tomorrow too.
Or, perhaps start moving towards a situation where you no longer need NAT. As long as people maintain the position that NAT is good enough, despite the problems it causes, then we'll never be able to move fully to IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org