BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Problem accessing blu.org
- Subject: [Discuss] Problem accessing blu.org
- From: gaf.linux at gmail.com (Jerry Feldman)
- Date: Wed, 20 May 2020 08:11:08 -0400
- In-reply-to: <AD05672A-4B2D-40D8-9A33-638B00F43918@Polcari.com>
- References: <CAEvgogF_9dWGUS926zoF6CRTOcW0zJkSb=aGYiYsz7SDf_msAA@mail.gmail.com> <CALdxGnwDS24TBFTYthwY_ZXC-vZ8XMd-BFxjcfVxQus0dFGtHw@mail.gmail.com> <CAEvgogEDrNUdAXoF6ONcTQT4AgUq_YHsbMQbprwgkgZOiYNj5w@mail.gmail.com> <e5d377429d75bc523ea5a40cc3410782.squirrel@mail2.ihtfp.org> <CAAbKA3USn__u5cgu65WuSmE9A5qvOyqROtvnOsfVEHKvD4s12w@mail.gmail.com> <AD05672A-4B2D-40D8-9A33-638B00F43918@Polcari.com>
I've rebooted the router a few times. After I reboot the router, I am able to access the site for about 5 minutes. I am certain the blocking is relatively local. On Tue, May 19, 2020 at 2:41 PM Joe Polcari <Joe at polcari.com> wrote: > FYI ? I am inside Comcast?s network ? so not blocked in any manner, in > fact nothing is blocked in any manner in the ISP part of the network. > > ? let me see how much of this I can paste here > > > > $ traceroute blu.org > > traceroute to blu.org (216.235.254.230), 64 hops max, 52 byte packets > > 1 * * * > > 2 192.168.1.1 (192.168.1.1) 3.825 ms 3.507 ms 4.291 ms > > > > Suffice it to say that from Florida it routes through Georgia, to Chicago, > to Woburn to blu.org. > > > > 22 50.231.30.210 (50.231.30.210) 72.456 ms 71.796 ms 70.346 ms > > 23 vranix.blu.org (216.235.254.230) 71.067 ms !Z 79.478 ms !Z 71.794 > ms !Z > > > > $ ping blu.org > > PING blu.org (216.235.254.230): 56 data bytes > > 64 bytes from 216.235.254.230: icmp_seq=0 ttl=45 time=70.776 ms > > 64 bytes from 216.235.254.230: icmp_seq=1 ttl=45 time=69.724 ms > > 64 bytes from 216.235.254.230: icmp_seq=2 ttl=45 time=70.567 ms > > 64 bytes from 216.235.254.230: icmp_seq=3 ttl=45 time=70.714 ms > > ^C > > --- blu.org ping statistics --- > > 4 packets transmitted, 4 packets received, 0.0% packet loss > > round-trip min/avg/max/stddev = 69.724/70.445/70.776/0.423 ms > > > > > > From: Discuss <discuss-bounces+joe=polcari.com at lists.blu.org> on behalf > of Bill Ricker <bill.n1vux at gmail.com> > Date: Tuesday, May 19, 2020 at 11:22 AM > To: Derek Atkins <derek at ihtfp.com> > Cc: "discuss at blu.org" <discuss at blu.org> > Subject: Re: [Discuss] Problem accessing blu.org > > > > One wonders if COMCAST is an ISP or just an infotainment company providing > > Web access to related media properties only. > > > > Perhaps COMCAST has blackholed the BLU IP address because it has a > > mailserver/Listserve and isn't named Google or Yahoo or AOL and thus is > > misdiagnosed as an infected site or worm control node :-/ . > > > > If it helps, from VZ FIOS > > traceroute to 216.235.254.230 (216.235.254.230), 30 hops max, 60 byte > > packets > > 1 172.17.2.1 (172.17.2.1) 0.573 ms 2.032 ms 2.167 ms > > 2 * * * > > 3 B3367.BSTNMA-LCR-21.verizon-gni.net (100.41.9.174) 9.625 ms > > B3367.BSTNMA-LCR-22.verizon-gni.net (100.41.9.176) 13.575 ms > > B3367.BSTNMA-LCR-21.verizon-gni.net (100.41.9.174) 11.152 ms > > 4 * * * > > 5 * * * > > 6 0.ae13.GW13.NYC1.ALTER.NET (140.222.234.193) 24.780 ms 11.364 ms > > 0.ae11.GW13.NYC1.ALTER.NET (140.222.234.191) 17.289 ms > > 7 windstream-gw.customer.alter.net (204.148.1.234) 17.595 ms 17.132 ms > > 17.585 ms > > 8 ae10-0.cr01.nycm01-ny.us.windstream.net (40.129.35.248) 15.832 ms > > 14.770 ms 15.087 ms > > 9 h255.81.138.40.static.ip.windstream.net (40.138.81.255) 15.009 ms > > 14.565 ms 13.248 ms > > 10 te-0-4-0-0.wrcmankgs04.onecommunications.net (64.69.99.239) 15.371 ms > > 15.149 ms 17.693 ms > > 11 te-3-1.wrcsmank-r76-02.onecommunications.net (64.69.99.234) 15.472 ms > > 22.063 ms 22.031 ms > > 12 static-72-248-107-33.mas.onecommunications.net (72.248.107.33) 17.148 > > ms 15.806 ms 15.384 ms > > 13 vranix.blu.org (216.235.254.230) 11.826 ms !X 16.396 ms !X 9.762 ms > > !X > > > > > > I do like how an HTTP connection to the real hostname or IP address > > provides a choice page to select the virtual site ! Nice touch. > > > > 216.235.254.230 > > > > This server belongs to Boston Linux & UNIX <http://blu.org>, a Linux and > > UNIX user group. > > ------------------------------ > > Guest Websites > > > > 1. BUGC <http://www.bugc.org> > > 2. HeliVets <http://www.heli-vets.net> > > 3. VHCMA <http://www.vhcma.org> > > 4. VHFCN <http://www.vhfcn.org> > > 5. VHPAF <http://www.vhpaf.org> > > > > > > _______________________________________________ > > Discuss mailing list > > Discuss at lists.blu.org > > http://lists.blu.org/mailman/listinfo/discuss > > > > _______________________________________________ > Discuss mailing list > Discuss at lists.blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- -- Jerry Feldman <gaf.linux at gmail.com> Boston Linux and Unix PGP key id: 6F6BB6E7 Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6B B6E7
- Follow-Ups:
- [Discuss] Problem accessing blu.org
- From: derek at ihtfp.com (Derek Atkins)
- [Discuss] Problem accessing blu.org
- References:
- [Discuss] Problem accessing blu.org
- From: gaf.linux at gmail.com (Jerry Feldman)
- [Discuss] Problem accessing blu.org
- From: agabriel2 at gmail.com (Dr. Anthony Gabrielson)
- [Discuss] Problem accessing blu.org
- From: gaf.linux at gmail.com (Jerry Feldman)
- [Discuss] Problem accessing blu.org
- From: derek at ihtfp.com (Derek Atkins)
- [Discuss] Problem accessing blu.org
- From: bill.n1vux at gmail.com (Bill Ricker)
- [Discuss] Problem accessing blu.org
- From: Joe at Polcari.com (Joe Polcari)
- [Discuss] Problem accessing blu.org
- Prev by Date: [Discuss] Problem accessing blu.org
- Next by Date: [Discuss] Problem accessing blu.org
- Previous by thread: [Discuss] Problem accessing blu.org
- Next by thread: [Discuss] Problem accessing blu.org
- Index(es):