On Aug 4, 2006, at 8:06 AM, Issac Goldstand wrote:
Not necessarily so. Like Jonathan mentioned, many huge ISPs (like
AOL,
for example, IIRC) route requests through load balanced transparent
proxies. This can cause the same person to appear to browse from a
number of different IPs - changing perhaps even more often than
Jonathan
reported.
Uh, that's extreme. But I'd call it a broken network, not a problem
with the idea of matching IP. With something like this, any service
using long-lasting connections will have problems.
Yea. For example, the 192.168.1.x network is my isp. i connect to
it, get an internal 10.0.1.1 address.
8:00am - http request funneled through 192.168.1.1
8:01am - http request funneled through 192.168.1.2
8:02am - http request funneled through 192.168.1.3
8:03am - ftp transfer funneled through 192.168.1.100
8:04am - http request funneled through 192.168.1.3 -- ftp still going
internally, my ip doesn't change- and lengty connections are fine.
but every new request goes through a different transparent proxy
( dialup109.aol.com, dialup200f.aol.com , etc )
i don't use aol. i just see tons of stuff like that in my click-
visit logs
sometimes isps are nice and will do some internal stuff so that all
requests go through a common proxy ( map a hash of user/domain onto a
server? or actually track who uses what? i dunno ). but i wouldn't
count on that.
