IETF Logo Mail Archive

Re: [100attendees] Incorrect GeoIP for IETF network addresses

"Carlos M. Martinez" <carlosm3011@gmail.com> Mon, 13 November 2017 02:39 UTC

Return-Path: <carlosm3011@gmail.com>
X-Original-To: 100attendees@ietfa.amsl.com
Delivered-To: 100attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B081271DF for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:39:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdVBqwQYcPD3 for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:39:49 -0800 (PST)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C466127A90 for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:38:53 -0800 (PST)
Received: by mail-pg0-x234.google.com with SMTP id j16so6111353pgn.9 for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:38:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:embedded-html; bh=5cCDfwzYrAWnaGy7ujbWpwxz3f1TkigOYAa9V4gJwIU=; b=O4vPDPgCz0uATQLgHN6ToSf41K/Xw7bqNATFWr4ZC3LGOThpwknEkisurG2vj+n3wD w11wKZuDmp0sB3GqHT8f1v3ZUATi5Yi9PXmDcLEnFYUftXx+XLTP2Q1FwgUqmETxwkWZ GudgyZtDbSXvSgh52f+1Tv93Jnr4KWXv2kSJhvPaRFHkbjab5EVkEgFK85jCtanO8l+D pr1tYrYMBi7EhUaZ633NEX9EzBL/GWS7KXZUdmK2zJ1XfMYH8f0wc0jV2d3XmuInSK1L /+2b1MOrT7ACUpQ7RN6ZK3L8H/m0akwZGnzGUaO3T1cENGng9DWRJNnj2zBCfGTLPJso hazg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding:embedded-html; bh=5cCDfwzYrAWnaGy7ujbWpwxz3f1TkigOYAa9V4gJwIU=; b=Z9bVN0UluRVRpiWGpxHm6BWmrsjwP9wbjW6jT1KUAMZT+rAcVwS6QLifyo13YEoUdp l39wGRVs+N1qChHq8mSKgO6yrJsEIL7xjFEmckgju3RQnkMCeI5dE/uJ0flB9Dw3MCvs aagfxxqr0iaXLQgbk8YooOxrycH9QMMCamGT3OK8uXGTnmaEV1oZ4prg+8uyLZ/P7MnU JVhsp45qYSDNxWci5qEUWsGn972t4sOib/QH6sp0ZZcRd7AISlQOk+UjY88szNdQofps 3fD0P4xUdYbI2tKnv3OoPssVJr3jNaP0KPIoWyfYzFbaGptUoIM9JW2so9gUHdkQYMBa ir+w==
X-Gm-Message-State: AJaThX7hMShGmZI+iDOvZ+DqanB9PqhkwIAs9VEzWuVesvJEmF4ggimy dq+tW0SlKbLl2jEjSCniRL4=
X-Google-Smtp-Source: AGs4zMb1dYxGMp1af/UNRqUJuyU2EoPWmn1L3udMXasAFTT9qs45R1o6RsxKLLg42APZUuNsaroYyg==
X-Received: by 10.159.255.70 with SMTP id u6mr7563631pls.41.1510540732446; Sun, 12 Nov 2017 18:38:52 -0800 (PST)
Received: from [169.254.137.137] ([2001:67c:370:1998:e4f8:1d6b:c49a:446e]) by smtp.gmail.com with ESMTPSA id q70sm34379343pfj.39.2017.11.12.18.38.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Nov 2017 18:38:51 -0800 (PST)
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
To: "Darshak Thakore" <d.thakore@cablelabs.com>
Cc: "100attendees@ietf.org" <100attendees@ietf.org>
Date: Mon, 13 Nov 2017 10:38:41 +0800
Message-ID: <A9C54905-07CB-40F1-B871-13BC0FB04E29@gmail.com>
In-Reply-To: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_DBE57006-423E-4930-B464-A32E88CC40C4_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[1514, 1256], "plain":[181, 597], "uuid":"130EDD6E-54DC-472D-9EC2-13D91F845F85"}]
X-Mailer: MailMate (1.9.7r5425)
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/fH1wjIN4knDK-VXPG5TzNvpJbbg>
Subject: Re: [100attendees] Incorrect GeoIP for IETF network addresses
X-BeenThere: 100attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Mailing list of IETF 100 attendees that have opted in on this list." <100attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/100attendees>, <mailto:100attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/100attendees/>
List-Post: <mailto:100attendees@ietf.org>
List-Help: <mailto:100attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/100attendees>, <mailto:100attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 02:39:51 -0000

Oh, behold the joys of the opaque world of GeoIP.

I don’t think there is a “magic” way of updating all GeoIP 
databases.

On 13 Nov 2017, at 10:34, Darshak Thakore wrote:

> Hi all,
>
> Is there a way to update the geoIP that the IETF IP addresses resolve 
> to? I’ve been seeing this behavior for the past few IETF’s where 
> on google maps (or on bing maps for that matter) in a browser, when I 
> allow geo-location (while connected to the IETF* networks) it always 
> resolves to the previous IETF venue. So today when I click “Your 
> location” button on google maps, it shows that I’m at Hilton 
> Prague and when I was in Prague, it showed me Chicago (and so on)
>
> Just wanted to know if there’s something I/we can do to make it 
> resolve to the right venue
>
> Darshak


> _______________________________________________
> 100attendees mailing list
> 100attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/100attendees

v2.8.7 | Report a Bug | By Email