Yesterday's Windows update causes IPv4 to be default
dwing at cisco.com
Thu Nov 15 18:07:52 CET 2012
> -----Original Message-----
> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de [mailto:ipv6-
> ops-bounces+dwing=cisco.com at lists.cluenet.de] On Behalf Of Nick Hilliard
> Sent: Thursday, November 15, 2012 5:50 AM
> To: Eric Vyncke (evyncke)
> Cc: IPv6 Ops list
> Subject: Re: Yesterday's Windows update causes IPv4 to be default
> On 15/11/2012 13:47, Eric Vyncke (evyncke) wrote:
> > Is there really application injecting cookies linked to an IP address
> > and not to a domain? I have always assumed that cookies were linked to
> > a domain.
> yes, piles :-(
Mostly they are using the client's IP address as part of the junk
encoded into the cookie. So if the client's IP address changes
unexpectedly, things break. Usually it is authentication to the
web site that breaks.
This is why all the NAT specifications encourage strongly that
the client's IP address needs to stay the same for the duration
of all the client's connections, for both NAT44 and NAT64.
More information about the ipv6-ops