Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Oct 2011 05:15:27 -0700
From:      Jeremy Chadwick <freebsd@jdc.parodius.com>
To:        Stefan Bethke <stb@lassitu.de>
Cc:        kapral <kapral@toya.net.pl>, freebsd-stable@freebsd.org
Subject:   Re: unix browsers problem
Message-ID:  <20111015121527.GA99555@icarus.home.lan>
In-Reply-To: <D860B6CF-A122-464A-8B24-379B037472F4@lassitu.de>
References:  <1b39c8399c008e3ee437586e0a408865@toya.net.pl> <D860B6CF-A122-464A-8B24-379B037472F4@lassitu.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 15, 2011 at 01:49:59PM +0200, Stefan Bethke wrote:
> Am 15.10.2011 um 12:34 schrieb kapral:
> 
> > When I connect with any freebsd 8.2 browsers  like epithany konqueror
> > firefox7.0.1 and under open bsd 4.9 with firefox 3.6.13 en i have  strange
> > connections too le100.net i checkt the ip and this is seedo in germany i
> > also have other strange connections any idea what to do with this bug ?
> 
> I think you need to be much more specific about what you're seeing, and why you think that it is a problem.
> 
> I got curious, so I fired up a fresh Firefox, and indeed saw that I have open connections to a couple of IPs:
> $ netstat -anfinet
> Active Internet connections (including servers)
> Proto Recv-Q Send-Q Local Address          Foreign Address        (state)
> tcp4       0      0 92.231.160.45.14944    74.125.43.120.80       ESTABLISHED
> tcp4       0      0 92.231.160.45.62441    74.125.43.104.80       ESTABLISHED
> tcp4       0      0 92.231.160.45.41710    74.125.43.104.80       ESTABLISHED
> tcp4       0      0 92.231.160.45.56705    195.95.193.85.80       ESTABLISHED
> tcp4       0      0 92.231.160.45.14474    195.95.193.78.80       TIME_WAIT
> tcp4       0      0 92.231.160.45.64333    195.95.193.78.80       ESTABLISHED
> tcp4       0      0 92.231.160.45.36191    68.232.35.119.80       TIME_WAIT
> tcp4       0      0 92.231.160.45.40339    63.245.217.43.443      TIME_WAIT
> tcp4       0      0 92.231.160.45.51785    63.245.217.43.443      ESTABLISHED
> tcp4       0      0 92.231.160.45.51321    74.125.43.190.443      ESTABLISHED
> 
> The 74.125.43.* addresses do resolve to 1e100.net, as you're seeing:
> $ host 74.125.43.190
> 190.43.125.74.in-addr.arpa domain name pointer bw-in-f190.1e100.net.
> $ host 74.125.43.104
> 104.43.125.74.in-addr.arpa domain name pointer bw-in-f104.1e100.net.
> 
> whois shows who's using them:
> $ whois 74.125.43.104
> ...
> NetRange:       74.125.0.0 - 74.125.255.255
> CIDR:           74.125.0.0/16
> OriginAS:
> NetName:        GOOGLE
> NetHandle:      NET-74-125-0-0-1
> Parent:         NET-74-0-0-0-0
> NetType:        Direct Allocation
> RegDate:        2007-03-13
> Updated:        2007-05-22
> Ref:            http://whois.arin.net/rest/net/NET-74-125-0-0-1
> 
> Considering that Firefox by default will open up the Firefox Google page, I don't find this surprising at all.

More useful details:

http://www.google.com/support/bin/answer.py?hl=en&answer=174717
http://www.pcmech.com/article/the-mysterious-1e100-net/
http://www.theregister.co.uk/2010/02/08/google_mystery_domain/

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                   Mountain View, CA, US |
| Making life hard for others since 1977.               PGP 4BD6C0CB |




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111015121527.GA99555>