doublelick.net : ssh ~ QNetMan2
 

Recently I installed QNetMan2 and looked what will show up. What now worries me is, that my N9 is constantly waiting for a ssh connection with doubleclick.net. What does this mean? No app is running other than QNetMan2.
http://666kb.com/i/cegu3d37plffyxv5t.png

Why does my phone mess whith doubleclick.net??

Re: doublelick.net : ssh ~ QNetMan2
 

doubleclick.net is a 'ad banner' company. does the app has any commercials/banners?

Re: doublelick.net : ssh ~ QNetMan2
 

I bet you EUR 100 that if you look in /etc/hosts you will find a line like:

127.0.0.1 doubleclick.net

This is what happens when you follow dubious "tricks" to avoid ads by messing with stuff you're not supposed to mess with. Unless you understand what you're doing, that is.

Re: doublelick.net : ssh ~ QNetMan2
 

There is in fact a line of the kind in my hosts file:

0.0.0.0 doubleclick.net

MintNanny uses exactly this trick to easily block sites. That's why I thaught it was no nonsense or in any way dubious. So tell us please whats wrong with such an entry.

Re: doublelick.net : ssh ~ QNetMan2
 

Let me re-phrase your question: "why did I post this thread?" that's one of the problems.

The general problem is using something for an unintended purpose. In some cases this may be OK, until it's not OK anymore.

/etc/hosts is used for resolving network names into IP addresses (like a local DNS cache), not for ad blocking.

So the general thinking goes "if a assign an invalid/local address to an advertising server no connection will ever be made to it", disregarding that "if I want to find the name of a given IP address I will get ambiguous, invalid, results."

You've been hit by the latter in trying to achieve the former.

Note that a server bound to 0.0.0.0 as a listening address means that the server accepts connection on any address, normally meaning from any interface (as opposed to, say, only from localhost, only from WAN address, etc.)

So whenever a networking tool wants to show a nice name for 0.0.0.0 (it should not, but it may try) then you get that doubleclick.

Re: doublelick.net : ssh ~ QNetMan2
 

In the following thread, an easy and save way is described how to block almost all ad servers:

http://talk.maemo.org/showthread.php?t=82180

This is working for the N900 and the N9.

Re: doublelick.net : ssh ~ QNetMan2
 

@HolgerN,

The method in the thread you posted is exactly the same one being used by the OP. Perhaps 127.0.0.1 will have other (also unintended) consequences as 0.0.0.0, but, at least in my book, it will be exactly as wrong as the other one.

Obviously many people use /etc/hosts for ad blocking, and I guess most live with it OK, but then they should not be surprised if something goes wrong, as the case is in this thread.

Re: doublelick.net : ssh ~ QNetMan2
 

Unfortunately I did not grasp this yet. Thank you anyway for your answer!

In my hosts file there are a few additional entries for 0.0.0.0. Doubleclick.net is neither the first nor the last entry. So why does it as the only one out of all appear? Can one rule out that some app or something actually tries to connect to doubleclick.net, but keeps waiting forever exactly due to that hosts file?

Re: doublelick.net : ssh ~ QNetMan2
 

Probably because the app can't continue without loading the adds...
Maybe it's designed that way. Maybe it's just a bug.

Re: doublelick.net : ssh ~ QNetMan2
 

The only running app in my scenario is QNetMan2 and it's not stalled but working fine...

Re: doublelick.net : ssh ~ QNetMan2
 

@amigo,

If you want to confirm that your problem is merely a user error (misuse of /etc/hosts) combined with a bug in QNetMan2 (there's no reason why it should attempt to get a DNS name for 0.0.0.0), you could just delete all 0.0.0.0-related entries in /etc/hosts and see how QNetMan2 works OK without showing any doubleclick.net address.

Re: doublelick.net : ssh ~ QNetMan2
 

As you told me, I now removed all of the 0.0.0.0 entries from the hosts file and then rebooted the phone. This did not cause any change to the strange effect. But to tell the whole story, before I applied the changes to the phone I already had blocked these sites by means of the child protetection blacklist within my router. So my conclusion still is, that something (not necessarily QNetMan2) really is trying (in vain) to establish a connection with doubleclick.net. What do you think?

Re: doublelick.net : ssh ~ QNetMan2
 

Based only on the picture you posted in the initial post, and explicitly considering that I haven't read the source code of QNetMan nor have any knowledge of your router's child protection blacklist, I can say that the QNetMan shows a ssh server in a listening state (good), where the "local address" is resolved as "doubleclick.net".

Now for obvious reasons doubleclick.net is not a local address (unless doubleclick.net is actually hosted on your phone. Let me doubt that :).

Usually a ssh server will be listening on "0.0.0.0". For some reason the reverse lookup that QNetMan does shows "doubleclick.net".

Please run this commands on a terminal and post here the exact output:
$ netstat -atn
$ netstat -at
$ nslookup doubleclick.net
$ host doubleclick.net
$ cat /etc/hostname

The first command will display all active connections (including listening connections, i.e. servers) without resolving IP addresses (option "n") so we can see under which IP address ssh is listening.

The second will do the same but resolving the IP addresses (this is to rule out an error in QNetMan).

The third and fourth commands should show the (real) IP address of doubleclick.net. If a local address is shown, then either your /etc/hosts is still bad or your router's blacklist is seriously broken.

The fifth is just to verify that you're not kidding (me :)

Re: doublelick.net : ssh ~ QNetMan2
 

Here you are: http://666kb.com/i/cghwkxylug3ui6yl3.png

So what do you make out of it?

Re: doublelick.net : ssh ~ QNetMan2
 

You definitely have some resolving problem, as address for doubleclick.net should be something like 70.32.146.212, certainly not all zeroes :D

Either you have crap on your /etc/hosts, or your resolvconf is all noodles...

Re: doublelick.net : ssh ~ QNetMan2
 

@ juiceme
I tried two versions of resolv.conf
and and I tried both of them via WLAN and via mobile data connection.

QNetMan2 delivered in every case the result, that I had postetd in my initial question. I think this rules out an issue with resolv.conf, doesn't it?

Re: doublelick.net : ssh ~ QNetMan2
 

Well, what about your /etc/hosts file, does it contain anything that should not be there?

Re: doublelick.net : ssh ~ QNetMan2
 

I'm more concerned that there is something missing that should be there :)

Re: doublelick.net : ssh ~ QNetMan2
 

Well, humour me and please try the following:
Just put a hash (that's #-character) in the front of the line "127.0.0.1 doubleclick.net" and try what you see after that. No need to boot the phone or anything, but you can also try that if you like.

That might just make the differnce.

Re: doublelick.net : ssh ~ QNetMan2
 

i bet google and facebook as well not working on your device. Just leave "127.0.0.1 RM696 localhost" in hosts file and delete all others.

Re: doublelick.net : ssh ~ QNetMan2
 

If people dont want ads then fuking pay for the apps or use free apps or make your own. Damn *****s.

Re: doublelick.net : ssh ~ QNetMan2
 

What do you think why I put them there. Because I wanted them to work?? I put them there because I do not want to be bothered by those parasites. And because I am not allowed to clean the facebook or google plugin from my N9 from, I will not buy a Jolla device: same makers, same patronizing, I expect.

Re: doublelick.net : ssh ~ QNetMan2
 

But, if you have yourself put local entries to your /etc/hosts, why are you asking about the way your device presents resolved information?

Re: doublelick.net : ssh ~ QNetMan2
 

[QUOTE]
I bet you EUR 100 that if you look in /etc/hosts you will find a line like:

127.0.0.1 doubleclick.net
[QUOTE]

Note: you owe me EUR 100 :)

Well, either that wasn't true, or is not true anymore.

Please do everyone (trying to help you) a favour and remove all entries but the first one from /etc/hosts. At least temporarily. Once you confirm that your "issue" is solved you have your answer, the thread can be closed, and you can continue polluting your /etc/hosts with invalid data.

Re: doublelick.net : ssh ~ QNetMan2
 

It was true until I removed the whole bunch of these entries:
So I already have done once what you are proposing now again:
After I had run the commands posted in #14 I added the entries again but this time I used 127.0.0.1 instead of 0.0.0.0

I don't understand why I should repeat the removal of these enties and why you do expect to gain new information from it. Would you kindly explain it to me? Thank for the patience you exercised so far!

Re: doublelick.net : ssh ~ QNetMan2
 

When you remove all the excess entries from your hosts file, and check again the qnetman output, I would expect you will not see anything about doubleclick there.

I think that was your original concern, yes?

Re: doublelick.net : ssh ~ QNetMan2
 

Well, I was kinda surprised that you had (again) bad stuff in your /etc/hosts, but anyway.

I looked again at the screenshot you posted, in particular the nslookup output. Which DNS server have you configured?

1.Is your N9 using DHCP or a manually set (list of) DNS addresses?
2.If manual, which DNSs have you configured?
3.If DHCP, from where is it getting the IP/DNS addresses? (probably from router, but check)
4.If router, what DNS addresses are configured in the router?

Somehow you seem to be using an "OpenNIC" DNS server which (COULD BE) seems to be the one resolving doubleclick.net to 0.0.0.0 (VERY BAD FOR A DNS SERVER).

BTW your DNS server doesn't seem to be up?
According to http://wiki.opennicproject.org/Tier2 your DNS is not even on the list (but appears on Wikipedia?).

Please answer the above 1-4 questions and let's take it from there.