| reply to yangman
Re: [BC] Week-long TSI outage, no resolution: seems to be Shaw i Some diags I sent to Chad at CSI
root@laptop1:~# ip route
69.172.154.64/26 dev eth0 proto kernel scope link src 69.172.154.75 metric 1
default via 69.172.154.65 dev eth0 proto static
Pings seem to get further if the record route option is used - not necessarily all hops but some indication of where packets are going.
Setting ttl manually allows traceroute like functionality without the host being ping-able.
for ((t=2;t10;t=t+1)) ;do echo $t;ping -R -t $t -c 1 76.10.191.198 &&break;done |tee -a /tmp/diags.txt
PING 76.10.191.198 (76.10.191.198) 56(124) bytes of data.
From 69.172.144.193 icmp_seq=1 Time to live exceeded
--- 76.10.191.198 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
3
PING 76.10.191.198 (76.10.191.198) 56(124) bytes of data.
From 76.10.191.33 icmp_seq=1 Time to live exceeded
--- 76.10.191.198 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
4
PING 76.10.191.198 (76.10.191.198) 56(124) bytes of data.
From 76.10.191.26 icmp_seq=1 Time to live exceeded
--- 76.10.191.198 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
5
PING 76.10.191.198 (76.10.191.198) 56(124) bytes of data.
64 bytes from 76.10.191.198: icmp_req=1 ttl=60 time=61.0 ms
RR: 69.172.154.75
76.10.191.28
76.10.191.198
76.10.191.33
10.93.128.1
69.172.154.75
--- 76.10.191.198 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 61.000/61.000/61.000/0.000 ms
google dns
for ((t=2;t10;t=t+1)) ;do echo $t;ping -R -t $t -c 1 8.8.8.8 &&break;done |tee -a /tmp/diags.txt
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 64.59.148.129 icmp_seq=28 Packet filtered
2
PING 8.8.8.8 (8.8.8.8) 56(124) bytes of data.
From 69.172.144.193 icmp_seq=1 Time to live exceeded
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
3
PING 8.8.8.8 (8.8.8.8) 56(124) bytes of data.
From 76.10.191.33 icmp_seq=1 Time to live exceeded
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
4
PING 8.8.8.8 (8.8.8.8) 56(124) bytes of data.
From 65.19.143.137 icmp_seq=1 Time to live exceeded
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
5
PING 8.8.8.8 (8.8.8.8) 56(124) bytes of data.
From 184.105.222.1 icmp_seq=1 Time to live exceeded
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
6
PING 8.8.8.8 (8.8.8.8) 56(124) bytes of data.
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
7
using shaw for dns over wireless tracepath to the border gateway
root@laptop1:~# tracepath -b 76.10.191.33
1: laptop1 (69.172.154.75) 0.281ms pmtu 1500
1: no reply
2: no reply
3: bdr01.van.cable.teksavvy.com (76.10.191.33) 14.065ms reached
Resume: pmtu 1500 hops 3 back 253
root@laptop1:~# tracepath -b 65.19.143.137
1: laptop1 (69.172.154.75) 0.257ms pmtu 1500
1: no reply
2: no reply
3: rh30ca-cmts.vc.shawcable.net (64.59.148.129) 11.386ms !H
Resume: pmtu 1500
from wireshark
60388 15518.112591 64.59.148.129 69.172.154.75 ICMP Destination unreachable (Communication administratively filtered)
packet filtering icmp comes back from 64.59.148.129
If the routing is correct then perhaps its an access list problem?
It is possible to ping from inside Sahw's network to 69.172.154.75.
From outside of Shaw's network (TSI) pings to 69.172.154.75 are received but the echo replies are blocked by the filtering so the sender never gets the reply. |
