!X just means the server has a firewall rule blocking traceroute. There are two common kinds of traceroute, one uses ICMP Echo (ping) packets, the other uses UDP packets usually in the range 33434-33625. Linux defaults to UDP (Windows uses ICMP). You can use ICMP on Linux traceroute with the -I option. But either way, the traceroute you show was successful despite the last hop prohibiting UDP packets to those ports.
On Wed, May 20, 2020 at 03:08:48PM -0400, Jerry Feldman wrote: > This is my current traceroute about 5 mins after resetting my cable modem > Note the !X. Note that vranix is a cname for driftwood.blu.org > [gaf@gaf ~]$ traceroute blu.org > traceroute to blu.org (216.235.254.230), 30 hops max, 60 byte packets > 1 * * * > 2 96.120.64.29 (96.120.64.29) 20.949 ms 22.637 ms 22.027 ms > 3 162.151.169.205 (162.151.169.205) 21.398 ms 22.473 ms 22.657 ms > 4 be-310-ar01.woburn.ma.boston.comcast.net (96.108.44.221) 22.884 ms > 34.046 ms 35.013 ms > 5 96.108.71.30 (96.108.71.30) 35.387 ms 36.020 ms 35.471 ms > 6 50.231.30.210 (50.231.30.210) 36.075 ms 17.799 ms 18.689 ms > 7 vranix.blu.org (216.235.254.230) 17.894 ms !X 16.698 ms !X 30.475 ms > !X > > On Wed, May 20, 2020 at 3:01 PM Jerry Feldman <gaf.li...@gmail.com> wrote: > > > Thanks Derek. > > I've spent hours chatting and speaking with Comcast. They elevated me to > > 'advanced repair'. The first advanced guy I chatted with seemed to be > > pretty sharp, but resetting the modem broke off the chat. The second guy I > > spoke to over the phone elevated me to 'advanced repair' and this guy > > wasn't too sharp. First he always went to the browser, and I told him it > > was on the terminal. He finally said it wasn't comcast. One thing I wanted > > to do was to have comcast reset dhcp so I could get a different IP address. > > > > I reset the cable modem/gateway a few minutes ago and I am able to access > > blu.org. I did this so I could display the meeting page. As long as I > > don't refresh that tab, I can display it on jitsi so if I lose connectivity > > with blu, I can still display the web site. > > > > On Wed, May 20, 2020 at 8:41 AM Derek Atkins <de...@ihtfp.com> wrote: > > > >> Here is another question for you: what is your local network > >> configuration? Are you using Comcast's modem/router directly or do you > >> have your own router behind their modem? If the latter, what happens if > >> you try to "remove" your own router? Does that change anything? > >> > >> Another avenue to look at is whether you might be filling up the modem's > >> NAT table? A very unlikely scenario, but it's certainly one I've hit (on > >> AT&T). > >> > >> IF you can display the problem with only comcast equipment I'd phone into > >> their tech support. > >> > >> -derek > >> > >> On Wed, May 20, 2020 8:11 am, Jerry Feldman wrote: > >> > 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 <j...@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 _______________________________________________ Discuss mailing list Discuss@lists.blu.org http://lists.blu.org/mailman/listinfo/discuss
