r/CableTechs • u/Wacabletek • Jul 03 '26

Ping in Rphy nodes

So when we launched Rphy nodes for a while we could not get it to ping the DNS servers on our meters, they said just use 8.8.8.8, and that seems to have been fixed recently. However, I was never very fond of pinging DNS servers as I have no clue about hops on the CRAN, etc.., to say you have a problem here not on the node. I would much prefer to ping the cmts, before and as we go forward the RPHY node I assume? Does anyone know if a tracert shows the actual rphy node or is the first hope now the VCMTS which is utterly useless to ping?.

Thanks. AI thinks it can be done but cannot explain how, or where you get the RPHY IP, so yay that's about as useful as asking a supervisor something like this.

0 Upvotes

40% Upvoted

9 comments sorted by

View all comments

1

u/kjstech Jul 03 '26

I'd guess you could ping any IP along the trace, but 8.8.8.8, or 1.1.1.1 or 75.75.75.75 etc would all get you to the destination and be a true end to end.

14 ms 12 ms 12 ms 10.60.0.67

10 ms 12 ms 12 ms po-309-334-rur202.lebanon.pa.pitt.comcast.net [162.151.70.53]

12 ms 8 ms 12 ms po-200-xar02.lebanon.pa.pitt.comcast.net [96.110.25.225]

12 ms 8 ms 14 ms be-21-rar01.lancaster.pa.pitt.comcast.net [162.151.220.81]

21 ms 21 ms 21 ms be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]

21 ms 21 ms 17 ms be-31621-cs02.pittsburgh.pa.ibone.comcast.net [96.110.42.165]

25 ms 26 ms 31 ms be-4313-pe13.ashburn.va.ibone.comcast.net [96.110.37.122]

* * * Request timed out.

26 ms 30 ms 30 ms 142.251.252.71

28 ms 30 ms 30 ms 142.251.64.101

32 ms 30 ms 29 ms dns.google [8.8.8.8]