[sf-lug] Website itself and others hosted on BALUG.org's VM?

[aaronco36 at sdf.org]

Thanks for speaking-up, folks :-)

Previously, I wrote ..
> Anyone know what's happening with the unresponsiveness
> of www.sf-lug.{com}{org} itself?
>
> Over the last day or so, have unsuccessfully attempted to reach both
> the SF-LUG website, the BALUG website, and the BALUG
> offered_wanted_hardware_etc webpage that Michael posted in the lower half
> of [1] regarding the "Aruba Wi-Fi access points still being available as
> free giveaways - while they last".

Well, coincidentally (or not so) during or after the time of writing the
OP, the BALUG website's administrator or even a time-based service may
have started or re-started during that time to re-activate full site
functionality!

>From yesterday afternoon to earlier today, PST, unsuccessfully tried to
visit {sf[-]?lug.{org,com,net},balug.org} through both Brave
(Chrome-based) and Firefox web browsers.
Note that this timerange turned out to be 2021-12-14 00:00:00 UTC thru
2021-12-15 00:00:00 UTC for you straightforward and trustworthy
troubleshooters!! ;-o )

So sure, for the times I did visit {sf[-]?lug.{org,com,net},balug.org} , I
also ran basic 'traceroute' commandlines commands to note if these
websites' same IP address was responding.

'traceroute' results similar to the following snippet...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
traceroute to www.balug.org (96.86.170.229), 30 hops max, 60 byte packets
 1  unknown (192.168.11.1)  0.847 ms  1.192 ms  1.554 ms
 2  173-228-119-1.dsl.dynamic.fusionbroadband.com (173.228.119.1)  30.318
ms  31.437 ms  32.660 ms
 3  xe-0-0-18.cr2.hywrca01.sonic.net (75.101.36.17)  55.154 ms  55.422 ms 
56.149 ms
 4  * * *
 5  * * *
 6  100.ae1.nrd1.equinix-sj.sonic.net (75.101.33.185)  41.388 ms  32.131
ms  33.311 ms
 7  102.ae1.nrd1.pao1.sonic.net (70.36.205.6)  35.286 ms  30.887 ms 
32.346 ms
 8  hu0-3-0-2.ccr31.sjc04.atlas.cogentco.com (38.104.141.81)  33.377 ms 
31.398 ms  32.731 ms
 9  be-200-pe02.529bryant.ca.ibone.comcast.net (50.248.118.237)  32.514 ms
 31.462 ms  31.574 ms
10  be-3202-cs02.sunnyvale.ca.ibone.comcast.net (96.110.41.213)  33.287 ms
be-3302-cs03.sunnyvale.ca.ibone.comcast.net (96.110.41.217)  34.249 ms
be-3402-cs04.sunnyvale.ca.ibone.comcast.net (96.110.41.221)  32.003 ms
11  96.110.41.70 (96.110.41.70)  32.499 ms 96.110.41.78 (96.110.41.78) 
31.946 ms  32.251 ms
12  be-298-rar01.pinole.ca.sfba.comcast.net (162.151.86.58)  34.280 ms 
34.859 ms  34.202 ms
13  po-1-rur01.pinole.ca.sfba.comcast.net (162.151.78.186)  33.453 ms 
33.376 ms  33.787 ms
14  96.110.179.114 (96.110.179.114)  33.303 ms  33.525 ms  34.023 ms
15  c-73-189-65-18.hsd1.ca.comcast.net (73.189.65.18)  43.361 ms  45.687
ms  44.342 ms
16  balug.org (96.86.170.229)  48.891 ms  44.132 ms  47.978 ms
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

So it looks like at least one of the servers hosting
{sf[-]?lug.{org,com,net},balug.org} has continued to respond throughout at
least the last day.

-A