[arch-security] strange netstat connections after having opened Firefox
estellnb at elstel.org
Fri Dec 4 23:26:31 UTC 2015
Whois; why have I not thought about it at once!
---- 126.96.36.199 ---
inetnum: 188.8.131.52 - 184.108.40.206
descr: Pool for mobile data users
descr: Dynamic IP
---- 220.127.116.11 ----
inetnum: 18.104.22.168 - 22.214.171.124
descr: Tiscali France Backbone
---- 126.96.36.199 ----
NetRange: 188.8.131.52 - 184.108.40.206
Parent: NET52 (NET-52-0-0-0-0)
NetType: Direct Allocation
Organization: Amazon Technologies Inc. (AT-88-Z)
---- 220.127.116.11 ----
inetnum: 18.104.22.168 - 22.214.171.124
descr: Hetzner Online AG
descr: Datacenter 13
So from my point there is still something to be said:
* What malware prevention service would connect to the IP of a !!mobile
device??!! - none!
* What has Amazon Technologies Inc. to do with all of that? - nothing!
* sometimes the kraken can also sit in a datacenter or a backbone and
this is known
-> I had just opened the page of the router in my LAN and nothing else.
Last but not least the most unerring sign that something went wrong was
in my mind the enduringly long and high CPU fan load (though it is a
pity that I did not have a closer look at least by system utilities). It
NEVER occurs with a Xi3650 unless it is put under 100% CPU load for
pretty much time!
Am 2015-12-04 um 21:59 schrieb mal:
> You can figure out who owns IP addresses using `whois`. I assume that's
> what was used.
> CPU fan speed is a bad measure of CPU usage; try `top`, `htop`, etc.
> If you value privacy, you should consider using your own recursive resolver.
> On 12/04/2015 05:46 PM, Elmar Stellnberger wrote:
>> ok; fine to know Remi; then there was already everything good with the
>> configuration Jonathan had recommended me! (Qwant will have been there
>> because of the search machine status bar)
>> However what I would find really interesting are the remaining servers
>> that there was a connection to when the '100% CPU fan' bug hit my
>> machine. I really did nothing at all when it heated up that much; - and
>> the desktop search should not have caused that, I would at least believe.
>> P.S.: By the way which name server did you use for reverse lookup, Remi?
>> 126.96.36.199 (OpenDNS server) did not do that for me in case of the
>> Qwant search engine; even sites like ping.eu do not succeed in the
>> reverse lookup of the 194.187.168.xx addresses.
More information about the arch-security