Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (7)
to General by teroyk - 7 hrs, 39 mins ago - more...
|
2013-08-06
, 20:46
|
|
Posts: 35 |
Thanked: 3 times |
Joined on Dec 2011
|
#12
|
Originally Posted by reinob
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?
@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.
|
|
2013-08-07
, 07:58
|
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#13
|
Originally Posted by amigo
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".
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?
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
Last edited by reinob; 2013-08-07 at 08:00. Reason: added /etc/hostname
| The Following User Says Thank You to reinob For This Useful Post: | ||
|
|
2013-08-08
, 21:36
|
|
Posts: 35 |
Thanked: 3 times |
Joined on Dec 2011
|
#14
|
Originally Posted by reinob
Here you are:
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
So what do you make out of it?
Last edited by amigo; 2013-08-08 at 21:42.
| The Following User Says Thank You to amigo For This Useful Post: | ||
|
|
2013-08-09
, 07:42
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#15
|
You definitely have some resolving problem, as address for doubleclick.net should be something like 70.32.146.212, certainly not all zeroes 
Either you have crap on your /etc/hosts, or your resolvconf is all noodles...
Either you have crap on your /etc/hosts, or your resolvconf is all noodles...
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2013-08-09
, 14:06
|
|
Posts: 35 |
Thanked: 3 times |
Joined on Dec 2011
|
#16
|
@ 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?
I tried two versions of resolv.conf
Code:
nameserver 127.0.0.1
Code:
# nameserver 127.0.0.1 nameserver 81.89.98.6 nameserver 213.73.91.35
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?
|
|
2013-08-11
, 15:09
|
|
Posts: 35 |
Thanked: 3 times |
Joined on Dec 2011
|
#18
|
Originally Posted by juiceme
I'm more concerned that there is something missing that should be there
Well, what about your /etc/hosts file, does it contain anything that should not be there?
Code:
127.0.0.1 RM696 localhost 127.0.0.1 adition.com 127.0.0.1 affili.net 127.0.0.1 chat.ovi.com 127.0.0.1 code.google.com 127.0.0.1 doubleclick.net 127.0.0.1 facebook.com 127.0.0.1 gmail.com 127.0.0.1 google-analytics.com 127.0.0.1 google.com 127.0.0.1 googleadservices.com 127.0.0.1 googleapis.com 127.0.0.1 googlemail.com 127.0.0.1 googlesyndication.com 127.0.0.1 googletagservices.com 127.0.0.1 googleusercontent.com 127.0.0.1 gstatic.com 127.0.0.1 m.facebook.com 127.0.0.1 play.google.com 127.0.0.1 plus.google.com 127.0.0.1 rackspace.com 127.0.0.1 sites.google.com 127.0.0.1 supl.google.com 127.0.0.1 talkgadget.google.com 127.0.0.1 tradedoubler.com 127.0.0.1 urlfixer.org 127.0.0.1 webmasterplan.com 127.0.0.1 www.facebook.com 127.0.0.1 www.google.com 127.0.0.1 yieldkit.com
|
|
2013-08-11
, 20:02
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#19
|
Originally Posted by amigo
I'm more concerned that there is something missing that should be there
Code:127.0.0.1 RM696 localhost 127.0.0.1 adition.com 127.0.0.1 affili.net 127.0.0.1 chat.ovi.com 127.0.0.1 code.google.com 127.0.0.1 doubleclick.net 127.0.0.1 facebook.com 127.0.0.1 gmail.com 127.0.0.1 google-analytics.com 127.0.0.1 google.com 127.0.0.1 googleadservices.com 127.0.0.1 googleapis.com 127.0.0.1 googlemail.com 127.0.0.1 googlesyndication.com 127.0.0.1 googletagservices.com 127.0.0.1 googleusercontent.com 127.0.0.1 gstatic.com 127.0.0.1 m.facebook.com 127.0.0.1 play.google.com 127.0.0.1 plus.google.com 127.0.0.1 rackspace.com 127.0.0.1 sites.google.com 127.0.0.1 supl.google.com 127.0.0.1 talkgadget.google.com 127.0.0.1 tradedoubler.com 127.0.0.1 urlfixer.org 127.0.0.1 webmasterplan.com 127.0.0.1 www.facebook.com 127.0.0.1 www.google.com 127.0.0.1 yieldkit.com
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.
| The Following User Says Thank You to juiceme For This Useful Post: | ||
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.