Mailing List Archive

who do i contact regarding being blocked from accessing www.mythtv.org?
I seem to be blocked from accessing www.mythtv.org:

$ traceroute -q 1 www.mythtv.org
traceroute to www.mythtv.org (140.211.167.216), 30 hops max, 60 byte packets
...
10 corv-p2-gw.nero.net (207.98.64.27) 105.712 ms
11 corv-car1-gw.nero.net (207.98.64.17) 107.506 ms
12 mizar.mythtv.org (140.211.167.216) 120.241 ms !X

Who do I contact to find out why this is and what needs to be done to
rectify it?

b.
Re: who do i contact regarding being blocked from accessing www.mythtv.org? [ In reply to ]
Brian J. Murrell <brian@interlinx.bc.ca> wrote:

> I seem to be blocked from accessing www.mythtv.org:
>
> $ traceroute -q 1 www.mythtv.org
> traceroute to www.mythtv.org (140.211.167.216), 30 hops max, 60 byte packets
> ...
> 10 corv-p2-gw.nero.net (207.98.64.27) 105.712 ms
> 11 corv-car1-gw.nero.net (207.98.64.17) 107.506 ms
> 12 mizar.mythtv.org (140.211.167.216) 120.241 ms !X
>
> Who do I contact to find out why this is and what needs to be done to
> rectify it?

In what way blocked ?
I get identical traceroute results, and can access the website. Is it simply a case of nothing returned and your browser times out, or you get an error, or ... ?

What does wget say ?

$ wget -O /dev/null www.mythtv.org
--2017-08-08 15:12:26-- http://www.mythtv.org/
Resolving www.mythtv.org... 140.211.167.216
Connecting to www.mythtv.org|140.211.167.216|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.mythtv.org/ [following]
--2017-08-08 15:12:27-- https://www.mythtv.org/
Connecting to www.mythtv.org|140.211.167.216|:443... connected.
ERROR: cannot verify www.mythtv.org's certificate, issued by ?CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US?:
Unable to locally verify the issuer's authority.
To connect to www.mythtv.org insecurely, use `--no-check-certificate'.



or

$ wget -O /dev/null --no-check-certificate www.mythtv.org
--2017-08-08 15:14:05-- http://www.mythtv.org/
Resolving www.mythtv.org... 140.211.167.216
Connecting to www.mythtv.org|140.211.167.216|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.mythtv.org/ [following]
--2017-08-08 15:14:05-- https://www.mythtv.org/
Connecting to www.mythtv.org|140.211.167.216|:443... connected.
WARNING: cannot verify www.mythtv.org's certificate, issued by ?CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US?:
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ?/dev/null?

/dev/null [ <=> ] 8.97K --.-KB/s in 0s

2017-08-08 15:14:06 (49.5 MB/s) - ?/dev/null? saved [9188]



_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: who do i contact regarding being blocked from accessing www.mythtv.org? [ In reply to ]
On Tue, 2017-08-08 at 15:14 +0100, Simon Hobson wrote:
>
> In what way blocked ?

$ telnet www.mythtv.org 443
Trying 140.211.167.216...
telnet: connect to address 140.211.167.216: Connection timed out

> What does wget say ?

wget will be pointless if I cannot even make a TCP connection to the
server, but just for completeness:

$  wget -O /dev/null www.mythtv.org
--2017-08-08 10:25:47--  http://www.mythtv.org/
Resolving www.mythtv.org (www.mythtv.org)... 140.211.167.216
Connecting to www.mythtv.org (www.mythtv.org)|140.211.167.216|:80... 

Which just times out after some retries, unsurprisingly.

Cheers,
b.
Re: who do i contact regarding being blocked from accessing www.mythtv.org? [ In reply to ]
Brian J. Murrell <brian@interlinx.bc.ca> wrote:

> On Tue, 2017-08-08 at 15:14 +0100, Simon Hobson wrote:
>>
>> In what way blocked ?
>
> $ telnet www.mythtv.org 443
> Trying 140.211.167.216...
> telnet: connect to address 140.211.167.216: Connection timed out

Curious.
Can you telnet to port 25 - I see the mail list is run on the same server.
And port 80 ?


Unrelated, but a while ago I got called out to a client who couldn't access things. Pings etc were fine, and after some work I figured that all connections to port 80 or 443 (but nothing else) were being blocked by their ISP. When I phoned their ISP they CS rep was adamant that there was no filtering in place, absolutely, none whatsoever ... then came a "um" from them.
Their billing system had had a hiccup on a public holiday, and although the customer had paid, their web traffic was filtered for non payment - but not properly as what should have happened was a redirect for all pages to the "you haven't paid your bill" page.

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: who do i contact regarding being blocked from accessing www.mythtv.org? [ In reply to ]
On Tue, 08 Aug 2017 10:30:19 -0400, you wrote:

>On Tue, 2017-08-08 at 15:14 +0100, Simon Hobson wrote:
>>
>> In what way blocked ?
>
>$ telnet www.mythtv.org 443
>Trying 140.211.167.216...
>telnet: connect to address 140.211.167.216: Connection timed out
>
>> What does wget say ?
>
>wget will be pointless if I cannot even make a TCP connection to the
>server, but just for completeness:
>
>$ ?wget -O /dev/null www.mythtv.org
>--2017-08-08 10:25:47--??http://www.mythtv.org/
>Resolving www.mythtv.org (www.mythtv.org)... 140.211.167.216
>Connecting to www.mythtv.org (www.mythtv.org)|140.211.167.216|:80...?
>
>Which just times out after some retries, unsurprisingly.
>
>Cheers,
>b.

www.mythtv.org works for me too, and comes up with the same IP
address. So your problem would seem to be one for your ISP to
resolve. If you have a VPN to some other site in the world available
to you, it may well work via that.

Or it could even be your own router - if it was somehow blocking that
IP address. It seems you are not getting through on either port 80 or
port 443.

It would be worth trying an ICMP traceroute also, to see if ICMP
packets are also blocked. Run this from Linux:

root@mypvr:~# traceroute -I www.mythtv.org --resolve
traceroute to www.mythtv.org (140.211.167.216), 64 hops max
1 10.0.2.251 (erlg.jsw.gen.nz) 0.324ms 0.249ms 0.244ms
2 111.69.7.104 (104.7.69.111.static.snap.net.nz) 0.980ms 1.059ms
1.018ms
3 * * *
4 4.16.192.146 (TWO-DEGREES.bar1.SanFrancisco1.Level3.net)
134.369ms 134.142ms 133.753ms
5 4.16.192.145 (xe-4-2-0.bar1.SanFrancisco1.Level3.net) 135.435ms
135.816ms 135.540ms
6 4.69.147.139 (ae-1-51.edge2.Seattle3.Level3.net) 153.160ms
153.292ms 153.224ms
7 4.69.147.139 (ae-1-51.edge2.Seattle3.Level3.net) 153.934ms
153.269ms 153.209ms
8 4.59.234.70 (UNIVERSITY.edge2.Seattle3.Level3.net) 156.891ms
157.296ms 157.291ms
9 207.98.64.170 (ptck-p2-gw.nero.net) 158.934ms 158.584ms
158.745ms
10 207.98.64.27 (corv-p2-gw.nero.net) 156.230ms 156.252ms
160.995ms
11 207.98.64.17 (corv-car1-gw.nero.net) 154.873ms 154.781ms
154.596ms
12 140.211.167.216 (mizar.mythtv.org) 154.356ms 154.447ms
154.212ms

An ICMP traceroute for me gets responses from 140.211.167.216.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: who do i contact regarding being blocked from accessing www.mythtv.org? [ In reply to ]
On Wed, 2017-08-09 at 03:12 +1200, Stephen Worthington wrote:
> Or it could even be your own router - if it was somehow blocking that
> IP address.

This is what made me think more deeply about this problem.

There was an incident a week or so ago that resulted in some false
positive fail2ban rules being implemented on what should have been
legitimate SMTP traffic, but instead it was being seen as "not allowed"
and being added to fail2ban blacklisting.

One has to remember that an IP address can be blocked at one's own
router such that one's SYN to that IP address can get out but the
responding SYN-ACK gets blocked coming back in.

Cheers Mr. Worthington for making me think a bit more deeply about
potential causes of this problem.

b.