From: IT Superhack <itsuperhack@web.de>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Add GeoIP location to nameservers
Date: Sun, 10 Jan 2016 17:25:10 +0100 [thread overview]
Message-ID: <569285E6.6060601@web.de> (raw)
In-Reply-To: <1451926780.31655.263.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
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.
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.
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.
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.
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?
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: 455 bytes --]
next prev parent reply other threads:[~2016-01-10 16:25 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 [this message]
2016-01-10 22:15 ` Michael Tremer
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=569285E6.6060601@web.de \
--to=itsuperhack@web.de \
--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