On Oct 14, 2010, at 4:47 PM, Joel Jaeggli wrote:

> On 10/11/10 7:40 AM, Rémi Després wrote:
>> 
>> Le 9 oct. 2010 à 02:50, Fred Baker a écrit :
>>>> That's not limited to Germany. Would that dtag.de would use 172.16/12 
>>>> rather than 10/8 or 192.168/16, as the latter two seem to find their way 
>>>> into so many home configurations.
>> 
>>> Having the same prefix on each side of the residential NAT could be a real 
>>> pain...
>> 
>> With my understanding of how NATs work, I don't see why.
>> Could you elaborate?
> 
> I can cause problems, it doesn't have to... there's a reason why nat
> rewriting occurs before forwarding in for example linux iptables.
> 
> if you expect to connect to host in a overlapping assignment you're
> going to have a problem but I think that's assumed.

Yes. The simplest case is: the host you want to contact has the same address 
that your host does. Widen that to: the host you want to contact has an address 
that happens to also exists in your routing domain. In such cases, the datagram 
you send will not go to the NAT.

>> Regards,
>> RD
>> 
>> 
>>> 
>>>> Kind regards
>>>> Peter
>>>> 
>>>> 
>>>> -- 
>>>> Peter and Karin Dambier
>>>> Cesidian Root - Radice Cesidiana
>>>> Rimbacher Strasse 16
>>>> D-69509 Moerlenbach-Bonsweiher
>>>> +49(6209)795-816 (Telekom)
>>>> +49(6252)750-308 (VoIP: sipgate.de)
>>>> mail: [email protected]
>>>> http://www.peter-dambier.de/
>>>> http://iason.site.voila.fr/
>>>> https://sourceforge.net/projects/iason/
>>>> ULA= fd80:4ce1:c66a::/48
>>>> _______________________________________________
>>>> Ietf mailing list
>>>> [email protected]
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>> 
>>> _______________________________________________
>>> Ietf mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/ietf
>> 
>> 
>> _______________________________________________
>> Ietf mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/ietf
>> 
> 

_______________________________________________
Ietf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf

Reply via email to