From: gah@ugcs.caltech.edu   
      
   Jorgen Grahn  wrote:   
   (snip, someone wrote)   
      
   >> So do all the tunnel protocols, so people like us can have our own   
   >> addressed network on top of the Internet infrastructure, no matter now   
   >> much NAT stuff the underlying routers deal with.   
      
   > Uh, *which* NAT mode are we talking about, here? I was under the   
   > impression that we were discussing a scenario where you could send a   
   > number of packets from A to B, and B would see source address C on   
   > some of them and D on others, depending which path they took.   
      
   > I hope no NAT works like that.   
      
   Well, it would have to be constant for a whole TCP connection,   
   but could change between them.  It could be useful as defense   
   against someone doing correlations between different TCP streams.   
      
   For example, a web site trying to do statistical analysis on   
   user preference by correlating search terms and IP addresses.   
   If every search has a different IP address, such would fail.   
      
   Traditionally, browswers start a new TCP connection for each   
   request, though maybe they don't always do that now.   
      
   Many ISPs now assign DHCP addresses for a very long time.   
   Mine changes every few years or so.  They could change much   
   more often if there was a reason to do it.  (Most likely   
   they would still keep logs of the assigned addresses, though.)   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)