Bad route in comcast router in Fort Collins, Colorado

I am seeing a bad route in a comcast router. It prevents access between two comcast business modems in Fort Collins.

Trace routes show the packets getting lost at the comcast router at 67.162.148.1 or one hop beyond it.

This is the second time this has happened. The router was bad for about one week in may.

The problem has been occuring again since July 7.

I would like to see this fixed and then have the cause corrected so that it will remain working.

Bad result from comcast IP 67.162.150.127

$ mtr -rw fcs-cable.lunarg.com
Start: Fri Jul 11 09:21:09 2014
HOST: xxxxxxxx        Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.2.3.1      0.0%    10    0.3   0.3   0.2   0.3   0.0
  2.|-- 67.162.148.1  0.0%    10   23.2  24.9  16.2  38.4   5.7
  3.|-- ???          100.0    10    0.0   0.0   0.0   0.0   0.0

Good result from comcast IP 173.160.41.154

$ mtr -r -w fcs-cable.lunarg.com
HOST: xxxxxxxxxxxxxxxxx                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.1.2                                       0.0%    10    0.2   0.2   0.2   0.2   0.0
  2.|-- SPI-router.lunarg                                 0.0%    10    0.2   0.2   0.2   0.3   0.0
  3.|-- 10.1.10.1                                         0.0%    10    0.7   0.9   0.7   2.3   0.5
  4.|-- 73.83.242.1                                       0.0%    10   17.8  26.4  17.8  34.6   5.4
  5.|-- ge-2-1-sr01.steamboat.co.denver.comcast.net       0.0%    10   25.8  24.7   9.8 137.6  40.0
  6.|-- te-0-2-0-7-ur12.denver.co.denver.comcast.net      0.0%    10   18.3  20.8  17.9  35.4   5.2
  7.|-- xe-15-1-0-0-ar01.aurora.co.denver.comcast.net     0.0%    10   19.6  19.0  18.2  20.2   0.6
  8.|-- te-7-3-ur02.fortcollins.co.denver.comcast.net     0.0%    10   21.1  26.7  21.1  38.4   6.6
  9.|-- te-17-10-cdn12.fortcollins.co.denver.comcast.net  0.0%    10   38.6  37.4  32.8  43.2   3.4
 10.|-- 50-78-83-34-static.hfc.comcastbusiness.net        0.0%    10   40.9  37.8  30.1  50.5   7.0

Good result from comcast IP 173.160.41.154

$ mtr -rw fcs-cable.lunarg.com
HOST: xxxxxxxxxx                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.0.0.1                                    0.0%    10    0.2   0.2   0.2   0.4   0.1
  2.|-- 67.174.104.1                                0.0%    10   14.1  21.5   9.8  37.8   8.3
  3.|-- 50-78-83-34-static.hfc.comcastbusiness.net  0.0%    10   22.0  20.0  17.1  22.7   1.9

Responses

kraze

Problem solver

•

305 Messages

10 years ago

Do you have longer results from the "bad" test? I'm having a bit of trouble following it. You may also wish to run an inbound/outbound from each end and post those results as well.

0

LunarG

New problem solver

•

12 Messages

10 years ago

That short report is as far as packets go.

The router at 67.162.148.1 is the first step beyond that cable modem, which has a WAN address of 67.162.150.127.

When trying to reach 50.78.83.34 packets dead end after one hop.

Using traceroute from the other side is interesting. Starting from the comcast cable modem at 50.78.83.34, traceroute reports "!H" (host unreachable) immediately. Perhaps that is the device with bad routing tables.

traceroute to 67.162.150.127 (67.162.150.127), 30 hops max, 60 byte packets
 1 10.2.2.1 0.619 ms 1.519 ms 1.925 ms
 2 50.78.83.34 3010.994 ms !H 3010.293 ms !H 3010.076 ms !H

Here is a traceroute from the 67.162.150.127 cable modem with a 30 hop max TTL.

That result could be from a lack of replies to packets that were sent on from 67.162.148.1 to 50.78.83.34 but never returned a response packet.

Performing traceroute to (fcs-cable.lunarg.com[50.78.83.34]) from (67.162.150.127), 30 hops max

1.   67.162.150.127    *  30 ms  30 ms

2.   67.162.148.1      * * *  (Request timed out)

3.   67.162.148.1      * * *  (Request timed out)

4.   67.162.148.1      * * *  (Request timed out)

5.   67.162.148.1      * * *  (Request timed out)

6.   67.162.148.1      * * *  (Request timed out)

7.   67.162.148.1      * * *  (Request timed out)

8.   67.162.148.1      * * *  (Request timed out)

9.   67.162.148.1      * * *  (Request timed out)

10.   67.162.148.1      * * *  (Request timed out)

11.   67.162.148.1      * * *  (Request timed out)

12.   67.162.148.1      * * *  (Request timed out)

13.   67.162.148.1      * * *  (Request timed out)

14.   67.162.148.1      * * *  (Request timed out)

15.   67.162.148.1      * * *  (Request timed out)

16.   67.162.148.1      * * *  (Request timed out)

17.   67.162.148.1      * * *  (Request timed out)

18.   67.162.148.1      * * *  (Request timed out)

19.   67.162.148.1      * * *  (Request timed out)

20.   67.162.148.1      * * *  (Request timed out)

21.   67.162.148.1      * * *  (Request timed out)

22.   67.162.148.1      * * *  (Request timed out)

23.   67.162.148.1      * * *  (Request timed out)

24.   67.162.148.1      * * *  (Request timed out)

25.   67.162.148.1      * * *  (Request timed out)

26.   67.162.148.1      * * *  (Request timed out)

27.   67.162.148.1      * * *  (Request timed out)

28.   67.162.148.1      * * *  (Request timed out)

29.   67.162.148.1      * * *  (Request timed out)

30.   67.162.148.1      * * *  (Request timed out)

Traceroute complete.

0

LunarG

New problem solver

•

12 Messages

10 years ago

The routing between these two devices just started to work again.

Hopefully it will be many months before it goes wrong for a third time.

Thanks for trying to help, kraze.

0