I don't think there is an issue with Google indexing, they index my/our servers just fine.
As Brian already wrote, a http://ampr.org/robots.txt file should have no effect on that.
Besides (at least in the current version) there is nothing in that file that would prevent such indexing
aside from a /wp-admin/ directory.
What you need for Google indexing is links from other sites, that are already being indexed, that point to you.
And some patience. It is not like a newly crawled site will appear in the index the next day. Or even the next week.
(maybe they do some re-crawling to avoid indexing scams and other malicious sites)
Rob
Hi,
I recently talked with Brian briefly about this and wanted to throw it out to the group. It’s incredibly rare to see any of the tunnels that have been created, represented in a Google search. While I understand and agree that any site that will become a high volume site has no place on Amprnet (we have to share resources) it also seems pointless to create a website that is undiscoverable. After all, isn’t the primary purpose of a website to share it’s content with others. I recently created a website on a 44net gateway and after several weeks, (and even convincing Brian to add a meta TXT entry allowing me to ask google to crawl), I am not seeing any content on Google. I put in a service request to google (not the easiest task) and I was advised that robots.txt or some other prevention device is blocking indexing all the subdirectories on amp.org. I was told that the few gateways that I see in the results were likely crawled before the restriction on ampr.org <http://ampr.org/> was applied. I created the website for our ARES group and placed it on an ampr gateway because we don’t have funds, and in reality, see very little traffic. We had a .net site last year and averaged about 50 visitors a month. My question is - is it really necessary to prevent the whole of ampr.org <http://ampr.org/> from being crawled (except of course the top domain which does show up). So many ip addresses, but almost none visible seems a real pity.
Thanks for listening. My only hope is that this creates a little bit of debate around the issue.
73
Roger
VA7LBB
Hello,
amprd 3.0 is available in the usual locations.
http://yo2tm.ampr.org/hamprojectshttp://www.yo2loj.ro/hamprojects
What's new:
- Added support for AMPR subnets in ignore list
- Added disable/enable option for incoming multicast and broadcast traffic
- Added support for selectable PID file
In regard of the issues with those ICMP unreachable messages:
For those keen ones, I added an optional kernel module, which needs to
be compiled and installed (howto is in the module subfolder).
Also, there is a new global option in the config file to enable its use.
This is a netfilter module which intercepts the IPIP 4 protocol and
converts it to protocol 94 and the other way around, circumventing the
series 4 kernel behavior that triggered the sending of those messages.
So those that want to try it: compile it (you will need to have the
kernel toolset and kernel headers installed), install it and enable the
use_redirector option.
For the rest, the filtering option will still work as expected.
Setails are in the readme files.
Have fun!
Marius, YO2LOJ
