44net

44net@mailman.ampr.org

4 participants
3196 discussions

Re: [44net] Google indexing
by Roger 04 May '19

04 May '19

Brian, My friend at google isn’t 100% sure what’s happening, just that when the crawler attempts the crawl, it comes back with the same code it gets for a robots.txt or something similar. So to clarify, google claims, something at the “top domain” (their words) has prevented almost all subdomains from being crawled. And whatever that is, it clearly has an affect because I really don’t find any results for ampr.org, except the main site, portal and wiki. Jann: I realize there are many other reasons and uses for amprnet. I was just talking about webserving some sort of content out to the internet at large. The issue I’m having affects anyone using 44Net, including those in your examples, that are wanting it discoverable by the world at large. 73 Roger VA7LBB > On May 2, 2019, at 19:31, Brian Kantor <Brian(a)bkantor.net> wrote: > > Having the robots.txt file at the site AMPR.ORG apply to pages > served by that host is completely reasonable. > > Having the robots.txt file at the site AMPR.ORG apply to pages > served from an entirely separate site called, e.g., VA7LBB.AMPR.ORG > is one of the most colossal pieces of internet engineering stupidity > I have ever encountered. > > Yet it would appear that is what the person at Google is telling > you is happening to your site. > >> From Wikipedia: > "A robots.txt file covers one origin. For websites with multiple > subdomains, each subdomain must have its own robots.txt file. > If example.com had a robots.txt file but a.example.com did not, > the rules that would apply for example.com WOULD NOT APPLY to > a.example.com. In addition, each protocol and port needs its own > robots.txt file; http://example.com/robots.txt does not apply > to pages under http://example.com:8080/ or https://example.com/" > > If that's not what their crawlers are doing, their crawlers are broken. > They broke it, they get to fix it. It's not our problem. > - Brian > > > > >> On Thu, May 02, 2019 at 06:13:40PM -0700, Roger Andrews wrote: >> 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 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 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 >

2 1

Re: [44net] Google indexing
by Roger 03 May '19

03 May '19

Steve, I’m wondering how long ago google crawled your site. You can’t just ask them to crawl a site anymore like the old days. You need to prove ownership before you can request it. According to my friend at google, none of the ampr subdomains have been crawled in a couple years. > On May 2, 2019, at 22:35, Steve L <kb9mwr(a)gmail.com> wrote: > > I have had google crawl and index my ampr.org site. I have since > blocked that though, as I don't really even need what I am running to > be accessible outside of the 44 netspace. > > Keep in mind webservers are just one type of service. My most > frequent non 44 net type of traffic is SMTP. > > If you are trying to get a feel for what is out there, here is a > message from a few years ago. (Note: Most are only accessible from > within the network) > > ---- Begin Forwarded Message ---- >> [44net] 44net cool toys >> Jann Traschewski jann at gmx.de >> Wed Mar 19 15:21:05 PDT 2014 > >> Ok what are people actually DOING over their Internet-connected 44 radio >> net? >> >> VOIP? APRS? Video links? Repeater linking? IP cameras? Remote bases? > > All of them! You might want to click around: > > Web: > http://web.db0avh.ampr.org > http://db0bi.ampr.org > http://db0dah.ampr.org > http://db0eeo.ampr.org > http://db0end.ampr.org > http://db0fhn.ampr.org > http://db0res-svr.ampr.org > http://db0gos.ampr.org > http://db0dz.ampr.org > http://db0ii.ampr.org > http://db0iuz.ampr.org > http://44.225.56.72/cms25 > http://db0kwe.ampr.org > http://srv.db0lj.ampr.org > http://db0nis.ampr.org > http://db0ovn.ampr.org > http://44.225.60.2 > http://db0sda.ampr.org > http://db0ach.ampr.org > http://db0pra.ampr.org > http://websrv.db0pdf.ampr.org > http://db0wet.ampr.org > http://db0ham.ampr.org > http://44.143.10.90 > http://web.oe2xzr.at.ampr.org > http://dm0ha.ampr.org > http://dm0zgw.ampr.org > http://db0erf.ampr.org > http://web.oe5xbl.at.ampr.org > http://web.oe7xci.ampr.at > http://44.168.12.11 > http://server.db0anf.ampr.org > http://www.db0fuz.ampr.org > http://linux.db0zeh.ampr.org > http://monitor.db0mhb.ampr.org > http://db0bul.ampr.org > http://rpt.db0pob.ampr.org > http://db0kpg.ampr.org > http://db0lip.ampr.org > http://44.225.76.161 > http://db0zdf-srv01.db0zdf.ampr.org > http://raspberry.db0abz.ampr.org > http://db0fc.ampr.org > http://cloud.db0fc.ampr.org > http://db0oha.ampr.org > http://dk0mav.ampr.org > > SDR: > http://dstar.db0vox.ampr.org:8901 > http://debian.vm.db0tvm.ampr.org:8901 > http://websdr.db0iuz.ampr.org:8901 > http://websdr.oe4xlc.at.ampr.org > http://db0tv.ampr.org/index.php?option=com_content&task=view&id=38&Itemid=47 > > Fotocam: > http://db0bi.ampr.org/webcam/bielefeld > > Maps: > http://osm.oe2xzr.ampr.at > http://tileserver.db0fc.ampr.org > > Packet Radio: > http://xnet.db0eeo.ampr.org > http://dlc7.oe7xgr.at.ampr.org > http://dlc7.db0kv.ampr.org > http://dhcp200.db0wal.ampr.org > http://db0res-node2.ampr.org > http://pr-srv.db0gis.ampr.org > > APRS: > http://aprs.db0res.ampr.org > > ATV: > http://db0ko.ampr.org > http://testpc.db0res.ampr.org > http://db0ntv.ampr.org > http://db0tv.ampr.org/index.php?option=com_content&task=view&id=71&Itemid=76 > > BBS: > http://db0ii.ampr.org:8080 > http://db0iuz.ampr.org:8080 > > Convers: > http://db0iuz.ampr.org/cgi-bin/dlwwc.php > > DX-Cluster: > http://dxcluster.oe1xhq.ampr.at > http://db0iuz.ampr.org/cgi-bin/spider.cgi > > Pager: > http://db0ii.ampr.org:9080 > http://db0iuz.ampr.org:8081 > http://db0fhn.ampr.org:4780 > > Webcam: > http://webcam.oe1xar.at.ampr.org > http://webcam.oe2xzr.at.ampr.org > http://video.oe5xll.at.ampr.org > http://webcam.oe7xzr.at.ampr.org > http://webcam.oe8xdr.at.ampr.org > http://db0iuz.ampr.org/webcam/webcam_radom.php > http://db0iuz.ampr.org/webcam/webcam_techniker.php > http://srv.db0lj.ampr.org/spycam.html > http://webcam.db0zdf.ampr.org/view/index.shtml > http://webcam.db0pob.ampr.org > > Active Hosts: > http://hamnetdb.net/?m=host&as=0 > > 73, > Jann > DG8NGN > > > -- > Jann Traschewski, Lenbachstr. 6, D-90489 Nuernberg, Germany > Tel.: +49-911-696971, Mobile: +49-170-1045937, E-Mail: jann at gmx.de > Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn > >> On Thu, May 2, 2019 at 8:16 PM Roger Andrews <va7lbb(a)rezgas.com> wrote: >> >> 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 >> >> _________________________________________ >> 44Net mailing list >> 44Net(a)mailman.ampr.org >> https://mailman.ampr.org/mailman/listinfo/44net > >

1 0

Re: [44net] Google indexing
by Rob Janssen 03 May '19

03 May '19

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

1 0

Google indexing
by Roger Andrews 03 May '19

03 May '19

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

4 3

amprd 3.0 released
by Marius Petrescu 02 May '19

02 May '19

Hello, amprd 3.0 is available in the usual locations. http://yo2tm.ampr.org/hamprojects http://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

1 0

Block or error?
by Marius Petrescu 29 Apr '19

29 Apr '19

I have a question to the sysops running gateways in Europe. Lately, my subnets (44.182.21.0/24, 44.182.20.0/24 and 44.182.21.253 using gw 89.122.215.236 and yo2loj.go.ro) seem to have been lockout from different regions like Germany, Poland, Portugal and Bulgaria, while access from 44.182.21.1/32 still works. Is this intentional or just a configuration issue? Marius, YO2LOJ

3 4

VPN Broken link
by KJ7DMC 22 Apr '19

22 Apr '19

Subject: VPN Hello, Due to some annoying ISP firewalling that I cant control, I'm going to have to VPN into the network, or set up a vps somewhere and vpn into that. Ideally the first option since its cheaper :) The link to www.arrl.org/instructions under this article http://wiki.ampr.org/wiki/AMPRNet_VPN is invalid however. I'm not sure who exactly to contact about this, since I cant find an author's name in the wiki. Any help would be appreciated. Thanks! -Nate

3 2

Re: [44net] AX25 support on Linux based (Raspberry PI) node
by Lorenzo Simoncello 19 Apr '19

19 Apr '19

Il giorno mer 13 mar 2019 alle ore 16:43 Thomas Osterried < thomas(a)osterried.de> ha scritto: > > It's always the best choice to use the official repo. See > http://www.linux-ax25.org/wiki/GIT > http://www.linux-ax25.org/wiki/Compilation > > It would always have been a good idea to send patches upstream. > Since three days ago, the official ax25 site is not available.... are there any news? Very recent, there were some updates... and there was a new release canidates (RC5) - thanks to maintainers :) May be they are are fixing all the issues that have been fixed in the VE7FET repos and also others issues??? At the moment i would like to thanks and i'm hoping something new... Lorenzo iw3her

2 1

Re: [44net] RIP problems?
by Rob Janssen 18 Apr '19

18 Apr '19

> Google says it's my fault; I say Google has its collective head up > its ass in marking a valid email as spam. Their official word is > "Don't act like the bad guys" and you won't have problems. Never > mind that it's 100% RFC-compliant, they say it's bad guy behaviour. I agree. Sending mail to google (and also hotmail/outlook) has become very unreliable. E.g. when using @amsat.org or other forwarding services like @veron.nl or @vrza.nl (Dutch amateur radio societies) it will usually not work. I do not really want to use my ISP mail address, so it looks like I have to register my own domain to get this fixed. For now, I have set an autoreply (from the ISP mail address) encouraging people to use a different address and look in their spambox when they expect a reply. I hear that it is customary in the circles of gmail/hotmail/outlook users to send a Whatsapp message "I have sent you an e-mail"... Rob

1 0

DNS
by monsieurmarc＠btinternet.com 18 Apr '19

18 Apr '19

Hi all, Who do I contact these days about getting a dns entry for 44.131.192.128 All help appreciated. Regards Marc (2W0PNT)

18 25

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net