PDA

View Full Version : Awstats: IP resolution


Michael Laudahn
11-23-05, 06:20 AM
I've tried earlier to solve this mystery, but without success. There always were contradictions between theory and practice that I couldn't solve. Still I'd like to give it another try. Somewhere there must be a way...

I didn't find any hints at the KB. Would Extras, Richard or some other equally knowledgeable and helpful soul attempt to get me out of this messy situation?

During my earlier attempts, I mean to have understood that our webhost tries to avoid too many such users, because of the additional traffic generated. Well, I would be willing to have this traffic deducted from my overall allowance. Apart from that, with an average of two thousand visitors per month, I assume the additional traffic wouldn't unduly load neither the switching nor the line infrastructures.

Looking forward to any interesting responses!

extras
11-23-05, 08:48 AM
Are you using Awstats supplied by PowWeb?
If so, you can't change the setting.

If you installed Awstats on your own, I think there is a setting you can change in awstats.pl or conf file, but
I don't remember.
I'm sure you can find it by searching this forum, or by reading Awstats documents/FAQ.

Probably, JJ or someone else knows about it.

Michael Laudahn
11-23-05, 12:54 PM
Yes, it is Powweb's version. 'searching this forum': I just looked around and found the discussion at

http://forum.powweb.com/showthread.php?t=58559 .

After that, and considering my abilities regarding these more advanced (?) functionalities, I've decided to abandon the project until I can get personal assistance by my (real, not virtual) side. Thanks for trying!

Michael Laudahn
11-24-05, 06:12 AM
I've just sent this suggestion to Powweb, aiming at an overall solution of the problem - 'they do the work once for uns, and we then just choose by clicking a key':


'I am still unhappy with the fact that your system doesn't resolve the
visitors' IP numbers then shown in the (Awstats) statistics. We've talked
earlier about that, and you said this would generate more traffic.

Well, why don't you then solve this issue the smart way: Leave your
customers the choice if they prefer IP resolution. If they do, then deduct
the additional traffic from their monthly allowance.

Please consider and let me know your decision.'


Any useful commentaries welcome.

Mirzabah
11-24-05, 06:39 AM
The reason that PowWeb's awstats doesn't resolve IPs is because it chews through server resources like you wouldn't believe.

Michael Laudahn
11-24-05, 09:22 AM
Really? Well they do allow it, don't they. They just don't promote it. So my conclusion was, they can bear it as long as not too many have implemented it.

Still, this leaves my question unanswered why they don't come up with an official offer for those interested in it. And all of those who maintain not just an english, but polyglot website like myself aiming at a worldwide audience (cf http://www.worldimprover.net/ ) are likely to be interested.

I maintain a second, free and less sophisticated statistics at http://www.webstats4u.com/s?tab=1&link=3&id=2050359&cou=all . There you can see the countries where my visitors come from. The drawback with this statistics is (among others), that it counts only those who come across their language's respective starting page. Those navigating past it are thus not counted.

extras
11-24-05, 09:43 AM
You answered your own question, I guess.

If "they can bear it as long as not too many have implemented it",
"an official offer for those interested in it" can increase the number of users who activate it too high to bear.
With the current setup, only those who really need it bother to install Awstats on their own.

You can request the new feature to PowWeb support,
and if they feel it's alright, they may implement it.
(Personally, I doubt it, though.)

Michael Laudahn
11-24-05, 10:00 AM
You'll know them better than I do, I guess. Still based on my previous experience with them I see a good chance that your pre-assessment of their reaction is ultimately right - unfortunately, one might add.