Note that large web pages being retried over an IPIP tunnel via UCSD
are bound to encounter packet loss, which will greatly impact performance.
It's not a high bandwidth path, folks. And never will be.
- Brian
On Tue, May 07, 2019 at 06:56:44PM -0500, David McAnally via 44Net wrote:
> Date: Tue, 7 May 2019 18:56:44 -0500
> From: David McAnally <david.mcanally(a)gmail.com>
> To: AMPRNet working group <44net(a)mailman.ampr.org>
> Subject: Re: [44net] Google indexing
>
> Roger,
>
> May I suggest looking at your web site home page load / rendering
> performance? I tried loading your page in the Google Page speed Insights
> <https://developers.google.com/speed/pagespeed/insights/> tool. It will
> not complete loading your URL for analysis, returning the much too common
> NO_FCP error message. (see their tool's references for details on FCP. I
> was able to load your URL in the analyze.websiteoptimization.com tool,
> which shows the page is almost 3MB in size, mostly images and javascript,
> which may be slowing the page load/rendering. While 3MB may not seem all
> that much in today's fast networks, home page size and load times have been
> known to cause crawling index systems to skip the site due their limited
> budget in time and resources. Poor performance scripting can be an issue
> too. If your network route to users, or in this case analysis tool, crosses
> a slower network gateway, the size of your page and content rendering
> performance could have even more impact. Don't know if improving page
> performance will make Google indexing happier, but can't hurt to try.
>
> At one time I had access to better tools for web site analysis, but I've
> retired, so I no longer get to play with that stuff.
>
> Regards,
> David M.
> WD5M
Pete,
Mine is https with a valid letsencrypt. They will not index.
Sent from my iPhone
> On May 7, 2019, at 10:25, pete M <petem001(a)hotmail.com> wrote:
>
> If I am not crazy. Google wont index new web site if not https.
>
> Télécharger Outlook pour Android<https://aka.ms/ghei36>
>
> ________________________________
> From: 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> on behalf of Rob Janssen <pe1chl(a)amsat.org>
> Sent: Tuesday, May 7, 2019 12:10:52 PM
> To: 44net(a)mailman.ampr.org
> Subject: Re: [44net] Google indexing
>
>> Rob,
>> Sorry, I forgot to say which site: separs.ampr.org <http://separs.ampr.org/>.
>> Yes, there are indexed ampr.org <http://ampr.org/> subdomains, but I don’t seem to be getting my point access. Those domains are older and indexing no longer works.
>
> You can keep iterating that, but it is simply not true.
> You undoubtedly have difficulties and I'm sure they are difficult to solve, but they aren't ampr.org wide.
>
>> Eventually according to Google, they will fall off their indexing. Google indexing can no longer reach them or any new site.
>
> Maybe your friend has told you that, but he has told you other things that are wrong. So I would not count on that.
>
>> 5) I asked Brian to add a TXT entry, as per the Google Search console instructions.
>
> It is in fact not required to do that, you can create a textfile with a name that is the same as what you put in the TXT record and it will work the same way.
> I have added sites to the search console in the past and used that method, it worked fine.
>
>> 6) Initialy Brian did not want to do it, saying he didn’t want Google crawling all the 44net IPs
>
> Contrary to what some "researchers" (and some of our fellow amateur radio operators) enjoy doing, Google is not portscanning the IP space to find sites to crawl.
> Google indexes HTTP links and follows them. Of course this takes bandwidth, but that is not much when compared to the many many black-hat and white-hat portscanners.
>
>> 9)I attempted to have the Google Search Console crawl the site. It declined indicating "no errors" but an “anomaly”
>
> I cannot help you with that. Your site appears OK from the outside, and my site(s) are indexed just fine.
> There is only one thing I cannot check: there could be some firewall filter that drops Google indexing (usually from 66.249.64.0/19) in the ampr gateway or in another system in the path to you.
> (our local sites within 44.137.0.0/16 are not routed via that gateway so we are not subject to that filter if it exists)
>
> However I don't think that is the case because there are other sites that are being indexed.
>
> Rob
>
>
>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
>
Ronen,
I run OpenWrt as my home router and AMPR Gateway. I created a separate VLAN for AMPRLAN (per the Wiki). The routing information and configs are listed on the WIki. Ampr-ripd must be cross-compiled (information on Wiki). Otherwise, I can only assist by providing a copy if your CPU device target is apm821xx or ar71xx (your device appears to be a mips_mips32). Roger, VA7LBB also runs OpenWrt, he may have ampr-ripd compiled for another target already.
I've ran OpenWrt on: Western Digital, X86_64, Meraki and MikroTik devices. I've never had stability issues with it. Although, your router's last supported version is 10.03, I would advise using a device that can run the current 18.06.2 and newer releases.
Regarding LAN IPs, you can also customize NATs for any local IP you wish to use AMPR. Such a config is more complex, and I have not configured that for normal use. I wrote the wiki when only ampr-ripd or rip44d were available, using kmod-ipip allows you to firewall ALL traffic on the tunnel interface (your option). If you have another border router doing DMZ, just forward IPENCAP (IP Protocol No.4) to the OpenWrt device.
If you have any more questions regarding the OpenWrt Wiki, let me know.
73,
- Lynwood
KB3VWG
PS: https://openwrt.org/toh/hwdata/d-link/d-link_dsl-2650ubrud
Per the Techdata page, your device only has 300 MHz processor, 32 MB RAM and 8 MB flash. You should be OK on flash; but CPU and RAM may be a limitation. Also be advised, OpenWrt doesn't fully support the closed source Broadcom WiFi driver.
John, and everyone else that says to just wait. It’s been 4-5 weeks at least. Again, I talked to google. They will not index.
Sent from my iPhone
> On May 7, 2019, at 11:00, K7VE - John <k7ve(a)k7ve.org> wrote:
>
> Google indexes both http and https sites -- it is giving more 'points' to
> https (e.g. they rank higher in the index) -- the top result for site:*.
> ampr.org is http://vkfaq.ampr.org which was last cached on April 8th.
> (Note: https://vkfaq.ampr.org is returning a security cert for a different
> site, the author should set up his server to return a proper cert for vkfaq
> -- it can be obtained at https://letsencrypt.org, set up to auto renew the
> cert).
>
> Setup your site in https://search.google.com/search-console and wait a few
> days to see if it shows up.
>
> [I do some of this from time to time as part of my job running IT/Web
> Development/Telecom for an eCommerce company -
> https://mavericklabel.com/company/about-maverick.html] -- btw, if you need
> ID stickers for your equipment, we also have https://idmystuff.com
>
> ------------------------------
> John D. Hays
> K7VE
> <http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
> <http://www.facebook.com/john.d.hays>
>
It’s been 4 weeks, and yes they crawl. They are crawling mine daily. I can see that in the Google Search Console. They won’t index though and that’s the important bit.
Roger
On May 6, 2019, at 12:22, Rob Janssen <pe1chl(a)amsat.org> wrote:
>> All,Don't these sites all appear to be indexed in the past?73,- LynwoodKB3VWG
>> null
>
> When checking for a site within our network, I see that Googlebot comes by almost every day, and
> when I check the site on Google and retrieve the page "from cache", I get pages dated April 9th and 10th.
>
> This reconfirms my earlier observation that it may take a couple of weeks for crawled pages to appear
> on the Google site.
>
> Rob
>
>
Time limit is when the content on the site was updated
Ruben - ON3RVH
> On 7 May 2019, at 19:37, Bill Vodall via 44Net <44net(a)mailman.ampr.org> wrote:
>
> <mime-attachment>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
> Rob,
> Sorry, I forgot to say which site: separs.ampr.org <http://separs.ampr.org/>.
> Yes, there are indexed ampr.org <http://ampr.org/> subdomains, but I don’t seem to be getting my point access. Those domains are older and indexing no longer works.
You can keep iterating that, but it is simply not true.
You undoubtedly have difficulties and I'm sure they are difficult to solve, but they aren't ampr.org wide.
> Eventually according to Google, they will fall off their indexing. Google indexing can no longer reach them or any new site.
Maybe your friend has told you that, but he has told you other things that are wrong. So I would not count on that.
> 5) I asked Brian to add a TXT entry, as per the Google Search console instructions.
It is in fact not required to do that, you can create a textfile with a name that is the same as what you put in the TXT record and it will work the same way.
I have added sites to the search console in the past and used that method, it worked fine.
> 6) Initialy Brian did not want to do it, saying he didn’t want Google crawling all the 44net IPs
Contrary to what some "researchers" (and some of our fellow amateur radio operators) enjoy doing, Google is not portscanning the IP space to find sites to crawl.
Google indexes HTTP links and follows them. Of course this takes bandwidth, but that is not much when compared to the many many black-hat and white-hat portscanners.
> 9)I attempted to have the Google Search Console crawl the site. It declined indicating "no errors" but an “anomaly”
I cannot help you with that. Your site appears OK from the outside, and my site(s) are indexed just fine.
There is only one thing I cannot check: there could be some firewall filter that drops Google indexing (usually from 66.249.64.0/19) in the ampr gateway or in another system in the path to you.
(our local sites within 44.137.0.0/16 are not routed via that gateway so we are not subject to that filter if it exists)
However I don't think that is the case because there are other sites that are being indexed.
Rob
Hi there
Has anyone done / do Gateway with home router running OpenWrt ?
If yes I have some questions as the WIKI is not so clear to non software man like me .
How the routing made ? does the ADSL interface get the home address (i.e 192.168.1.x in my case) and the lan port get the 44 Net address ?
or one Interface deal with Both network like i do in my MikroTik ?
what about configuration ? is there any way to do it via the GUI ? or only with the line mode ?
I mean that the Router sit on the home DMZ (that supplied from the main home router) and the Adress of the outside world arrive to it for the tunnel from UCSD
I saw that there is IPIP Package that support IPIP so what the difference and why the Kernel_ipip mode needed ?
and last where can i get executable of the ripd ? i can not compile ...
the router planed for the task is D-Link DSL2650 with broadcom 6358 That I Flashed for OpenWRT
I have heard that the OPENWRT is not a stable system and get stuck and needed reset here and there can someone confirm that ?
Thanks in advance
Ronen - 4Z4ZQ
http://www.ronen.org
Ronen Pinchooks (4Z4ZQ) WebSite<http://www.ronen.org/>
ronen.org (Ronen Pinchooks (4Z4ZQ) WebSite) is hosted by domainavenue.comwww.ronen.org
> All,Don't these sites all appear to be indexed in the past?73,- LynwoodKB3VWG
> null
When checking for a site within our network, I see that Googlebot comes by almost every day, and
when I check the site on Google and retrieve the page "from cache", I get pages dated April 9th and 10th.
This reconfirms my earlier observation that it may take a couple of weeks for crawled pages to appear
on the Google site.
Rob
