From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Add GeoIP location to nameservers
Date: Sun, 10 Jan 2016 22:15:43 +0000 [thread overview]
Message-ID: <1452464143.5665.14.camel@ipfire.org> (raw)
In-Reply-To: <569285E6.6060601@web.de>
[-- Attachment #1: Type: text/plain, Size: 2581 bytes --]
Hi,
On Sun, 2016-01-10 at 17:25 +0100, IT Superhack wrote:
> Hello Michael, hello Matthias,
>
> Michael Tremer:
> > Just out of curiosity, why do you find this information so helpful?
>
> As Matthias said already, is is more a "nice to have" than something
> which is seriously needed.
This is not too much of an argument. My argument against this is that
it brings down page load times because of a not too useful information.
> I wrote this patch because a friend of mine in France discovered that
> his ISP assigns DNS servers from Australia and Great Britain, which
> was slowing down DNS resolving a lot.
I get that and this is actually a pretty good one.
That only leaves resolvers like 8.8.8.8 which will show "US" but
actually are located at many places around the world. Let's hope that
people don't get the wrong thing from the flag - or actually start
changing their DNS servers to something else :)
> Therefore I thougt it might be useful to see in which countries your
> DNS servers are located, just in case you didn't set some by your
> own.
It is sometimes. Although geographic location doesn't mean that it is
close on the network.
A system in GB is probably not an issue. Australia actually is a bit
far away.
> In general, adding geographic information to IP addresses is very
> helpful in my point of view because anomalies can be detected much
> better and more precise firewall rules are possible.
I don't get why.
> However, some thing might still be improved: For example, the
> ipinfo.cgi
> file shows the IP address, the rDNS name, whois information, but not
> the appropriate flag. So, if someone scrolls through the connection
> tracking
> page, he/she/it sees the source and destination IPs of any active
> (and
> recently closed) connection. At the moment, there is no way of
> telling
> which country an IP belongs to - without using additional web
> services, of
> course - since the flag is shown neither at the connection tracking
> page
> nor at the ipinfo.cgi page. This isn't very helpful, is it?
The ipinfo.cgi page shows the whois information for an IP address. That
may contain the name and HQ location of a company this IP address
belongs to, but that does *not* mean that the host is actually located
in that country - and almost certainly not at that address.
The GeoIP database is a completely different thing.
Judging by the location of the host does make any sense if you care
about security.
>
> That is basically the motivation behind the two patches I submitted
> recently.
>
> Best regards,
> Timmothy Wilson
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-10 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5686D08D.7000802@ipfire.org>
2016-01-04 16:59 ` Michael Tremer
2016-01-04 17:16 ` Matthias Fischer
2016-01-10 16:25 ` IT Superhack
2016-01-10 22:15 ` Michael Tremer [this message]
2016-01-11 8:10 ` IT Superhack
2016-01-19 1:30 ` Michael Tremer
2016-01-19 6:57 ` IT Superhack
2016-01-01 17:11 IT Superhack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1452464143.5665.14.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox