AT&T u-verse: traceroute to members.iinet.net.au (203.0.178.90), 32 hops max, 3 probe packets per hop, 72 byte packets 1 192.168.1.254 <dsldevice.attlocal.net> 0.846 ms 0.641 ms 0.662 ms 2 107.142.108.1 <107-142-108-1.lightspeed.sntcca.sbcglobal.net> 17.638 ms 20.339 ms 17.964 ms 3 71.148.149.214 17.900 ms 20.301 ms 17.417 ms 4 71.145.0.232 18.536 ms 18.924 ms 18.716 ms 5 71.145.1.17 18.858 ms 19.400 ms 18.651 ms 6 12.83.39.145 21.443 ms 20.766 ms 20.336 ms 7 12.122.114.5 20.711 ms 21.881 ms 23.593 ms 8 192.205.37.70 30.408 ms 22.952 ms 22.109 ms 9 63.243.205.73 <if-ae-18-2.tcore2.SV1-Santa-Clara.as6453.net> 207.503 ms 192.832 ms 201.769 ms 10 209.58.86.143 <if-et-5-2.hcore1.KV8-Chiba.as6453.net> 139.729 ms * 135.563 ms 11 120.29.217.66 <if-ae-21-2.tcore1.TV2-Tokyo.as6453.net> 199.597 ms 199.886 ms 200.544 ms 12 180.87.15.40 <if-ae-31-2.tcore2.SVW-Singapore.as6453.net> 193.209 ms 196.146 ms 191.521 ms 13 180.87.96.21 <if-ae-20-2.tcore1.SVQ-Singapore.as6453.net> 191.687 ms 191.156 ms 189.702 ms 14 120.29.215.250 207.450 ms 207.377 ms 207.168 ms 15 * * * 16 * * * ^C17 * FGT30E3U16019987 # execute ping members.iinet.net.au PING members.iinet.net.au (203.0.178.90): 56 data bytes 64 bytes from 203.0.178.90: icmp_seq=0 ttl=236 time=309.1 ms 64 bytes from 203.0.178.90: icmp_seq=1 ttl=236 time=308.9 ms Unreachable from Bay Area comcast. PING members.iinet.net.au (203.0.178.90): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 ^C --- members.iinet.net.au ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss mar@maelona ~> traceroute members.iinet.net.au traceroute to members.iinet.net.au (203.0.178.90), 64 hops max, 52 byte packets 1 10.12.0.1 (10.12.0.1) 1.263 ms 0.393 ms 0.377 ms 2 96.120.88.17 (96.120.88.17) 9.911 ms 11.016 ms 11.396 ms 3 po-102-rur02.hayward.ca.sfba.comcast.net (68.85.190.177) 11.463 ms 10.225 ms 10.568 ms 4 * * * 5 * * * On Thu, Apr 5, 2018, at 18:23, Dean Notarnicola via vcf-midatlantic wrote:

Comcast here. No go. Via Verizon, no issues. Comcast has a routing issue.

On Thu, Apr 5, 2018 at 9:19 PM malcolm--- via vcf-midatlantic < vcf-midatlantic@lists.vintagecomputerfederation.org> wrote:

...

Hi Mike,

I'm *not* on Comcast, but I can confirm I can reach him through my ISP (iiNet, in Australia). Mind you, he is only 30 minutes by car from my place!

Malcolm.

...

-----Original Message----- From: vcf-midatlantic [mailto:vcf-midatlantic- bounces@lists.vintagecomputerfederation.org] On Behalf Of Mike Loewen via vcf-midatlantic Sent: Friday, 6 April 2018 11:06 To: vcf-midatlantic@lists.vintagecomputerfederation.org Cc: Mike Loewen Subject: [vcf-midatlantic] Comcast

My ISP is Comcast, and I'm unable to reach Ian Mavrick's TRS-80 site in Australia (http://members.iinet.net.au/~ianmav/). Traceroute hangs up as follows:

traceroute to members.iinet.net.au (203.0.178.90), 30 hops max, 60 byte packets

1 gateway (192.168.202.38) 0.434 ms 0.721 ms 0.913 ms 2 96.120.x.xxx (96.120.x.xxx) 10.537 ms 16.796 ms 18.177 ms 3 68.85.46.1 (68.85.46.1) 17.772 ms 18.027 ms 17.762 ms 4 be-45-ar01.lancaster.pa.pitt.comcast.net (96.108.4.89) 24.188 ms 23.207 ms 24.317 ms 5 * * *

Can any other Comcast users reach his site? This has been going on for at least a week.

Mike Loewen mloewen@cpumagic.scol.pa.us Old Technology http://q7.neurotica.com/Oldtech/

-- Madeline Autumn-Rose b4@gewt.net

On Apr 5, 2018, at 9:50 PM, Dave McGuire via vcf-midatlantic <vcf-midatlantic@lists.vintagecomputerfederation.org> wrote:

Routing has absolutely nothing to do with DNS.

Unless you're using Cloudflare's new 1.1.1.1 service, whereupon you learn just how broken some routers are when they treat 1.1.1.1 as an internal resource, even though it's a non-reserved number or network. :-) But that's not what we're talking about here. Unless for some reason Ian's server is resolving to a different address on Comcast (it's not; they're all showing 203.0.178.90), DNS isn't the problem here. I've had routing breakages somewhere a few hops downstream of me on Comcast and Verizon in the past; sometimes a router just dies in a datacenter somewhere and it takes a while for BGP to catch up. - Dave

I worked for an ISP that for a significant time was announcing 1.1.1.1 publicly into TorIX...

But you might want to check the "from" field in your email, Cory S. :)

Long story there; it’s correct and matches the legal name ;)

Sorry, didn't know! Welcome back to the group, Madeline.

On 04/05/2018 09:56 PM, David Riley wrote:

...

Routing has absolutely nothing to do with DNS.

Unless you're using Cloudflare's new 1.1.1.1 service, whereupon you learn just how broken some routers are when they treat 1.1.1.1 as an internal resource, even though it's a non-reserved number or network. :-)

soda -> keyboard

But that's not what we're talking about here. Unless for some reason Ian's server is resolving to a different address on Comcast (it's not; they're all showing 203.0.178.90), DNS isn't the problem here. I've had routing breakages somewhere a few hops downstream of me on Comcast and Verizon in the past; sometimes a router just dies in a datacenter somewhere and it takes a while for BGP to catch up.

Yup. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

On 04/06/2018 12:46 AM, Mike Loewen via vcf-midatlantic wrote:

   I just spent 40 minutes chatting online with a trained monkey at Comcast. He persisted in blaming my computer for the problem, despite my providing the traceroute listing.  I finally got tired of it when he wanted my to connect my computer directly to the modem, and suggested he forward my message to someone who understands how traceroute works, as a ROUTING issue.

I've run into this way too many times. Tried to explain that they had an issue with their equipment (something going bad) and for 6 months we went back and forth until the pay-per-view folks were being affected. Then it was fixed PDQ. Let's assume I went on a rant here and leave it at that. -- Linux Home Automation Neil Cherry ncherry@linuxha.com http://www.linuxha.com/ Main site http://linuxha.blogspot.com/ My HA Blog Author of: Linux Smart Homes For Dummies

On Fri, 6 Apr 2018, Christian Liendo wrote:

According to Hurricane Electric, Comcast has a route server you can telnet into a trace from there

telnet to route-server.newyork.ny.ibone.comcast.net user: rviews

This is the Hurricane Electric site. https://bgp.he.net/AS7922

You should be able to telnet to this and test from there.

Ian's site is unreachable from there, as well. Mike Loewen mloewen@cpumagic.scol.pa.us Old Technology http://q7.neurotica.com/Oldtech/

... not anymore! mar@maelona ~> telnet route-server.newyork.ny.ibone.comcast.net Trying 66.208.229.1... telnet: connect to address 66.208.229.1: Connection refused Trying 2001:558:0:f425::1... telnet: connect to address 2001:558:0:f425::1: No route to host On Fri, Apr 6, 2018, at 06:31, Christian Liendo via vcf-midatlantic wrote:

According to Hurricane Electric, Comcast has a route server you can telnet into a trace from there

telnet to route-server.newyork.ny.ibone.comcast.net user: rviews

This is the Hurricane Electric site. https://bgp.he.net/AS7922

You should be able to telnet to this and test from there.

I have telnet disabled at work so I cannot get to just open up telnet without someone giving me grief.

-- Madeline Autumn-Rose b4@gewt.net

route-server.newyork.ny.ibone>traceroute 203.0.178.90 Type escape sequence to abort. Tracing the route to members.iinet.net.au (203.0.178.90) 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * route-server.newyork.ny.ibone>ping 203.0.178.90 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 203.0.178.90, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) route-server.newyork.ny.ibone> On Fri, Apr 6, 2018, at 14:48, Mike Loewen via vcf-midatlantic wrote:

If the route server is too busy, it will deny a connection. Try it again.

On Fri, 6 Apr 2018, Madeline Autumn-Rose via vcf-midatlantic wrote:

...

... not anymore!

mar@maelona ~> telnet route-server.newyork.ny.ibone.comcast.net Trying 66.208.229.1... telnet: connect to address 66.208.229.1: Connection refused Trying 2001:558:0:f425::1... telnet: connect to address 2001:558:0:f425::1: No route to host

On Fri, Apr 6, 2018, at 06:31, Christian Liendo via vcf-midatlantic wrote:

...

According to Hurricane Electric, Comcast has a route server you can telnet into a trace from there

telnet to route-server.newyork.ny.ibone.comcast.net user: rviews

This is the Hurricane Electric site. https://bgp.he.net/AS7922

You should be able to telnet to this and test from there.

I have telnet disabled at work so I cannot get to just open up telnet without someone giving me grief.

-- Madeline Autumn-Rose b4@gewt.net

Mike Loewen mloewen@cpumagic.scol.pa.us Old Technology http://q7.neurotica.com/Oldtech/

-- Madeline Autumn-Rose b4@gewt.net