cancel
Showing results for 
Search instead for 
Did you mean: 

is this bad, tracert and ping for cbc.ca

ravonic
I've Been Here Awhile

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Jonas>tracert cbc.ca

Tracing route to cbc.ca [159.33.3.85]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  phub.net.cable.rogers.com [192.168.0.1]
  2     6 ms     7 ms    10 ms  10.77.104.1
  3     8 ms     7 ms     5 ms  67.231.221.169
  4    10 ms    11 ms    11 ms  69.63.251.46
  5    15 ms    13 ms    13 ms  64.71.240.174
  6    13 ms    16 ms    12 ms  gw-cbc.torontointernetxchange.net [198.32.245.36
]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Jonas>ping cbc.ca

Pinging cbc.ca [159.33.3.85] with 32 bytes of data&colon;
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 159.33.3.85:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Jonas>

 

 

***edited labels***

1 ACCEPTED SOLUTION

Accepted Solutions

Re: is this bad, tracert and ping for cbc.ca

skinorth
I'm an Advisor

@ravonic:

 

there is no real problem with both the trace route and the ping results you got.

 

I guess that the CBC, being likely more cautious about network security than some other organizations, does not repond to external ping or trace route requests on its internal network.

 

Trace route information can be used by hackers in order to obtain information about the internal structure of the CBC network.  This information could potentially be used for nefarious purposes.

 

Ping can be used in denial of service attacks.  Many networked devices are set up not to respond to a "ping".

 

You will notice in the trace route info you put in your posting that information was not returned once your trace route had gone past the gw-cbc.torontointernetxchange.net address.  This seems to be the Toronto gateway into the CBC internal network as the name suggests.

 

I just did a "ping" on that Toronto gateway, and it does return a ping:

 

**********************************************************************************************
Pinging gw-cbc.torontointernetexchange.net [67.215.65.132] with 32 bytes of data
:
Reply from 67.215.65.132: bytes=32 time=350ms TTL=46
Reply from 67.215.65.132: bytes=32 time=108ms TTL=46
Reply from 67.215.65.132: bytes=32 time=137ms TTL=46
Reply from 67.215.65.132: bytes=32 time=93ms TTL=46

Ping statistics for 67.215.65.132:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 350ms, Average = 172ms

********************************************************************************************

 

skinorth

 

 

View solution in original post

1 REPLY 1

Re: is this bad, tracert and ping for cbc.ca

skinorth
I'm an Advisor

@ravonic:

 

there is no real problem with both the trace route and the ping results you got.

 

I guess that the CBC, being likely more cautious about network security than some other organizations, does not repond to external ping or trace route requests on its internal network.

 

Trace route information can be used by hackers in order to obtain information about the internal structure of the CBC network.  This information could potentially be used for nefarious purposes.

 

Ping can be used in denial of service attacks.  Many networked devices are set up not to respond to a "ping".

 

You will notice in the trace route info you put in your posting that information was not returned once your trace route had gone past the gw-cbc.torontointernetxchange.net address.  This seems to be the Toronto gateway into the CBC internal network as the name suggests.

 

I just did a "ping" on that Toronto gateway, and it does return a ping:

 

**********************************************************************************************
Pinging gw-cbc.torontointernetexchange.net [67.215.65.132] with 32 bytes of data
:
Reply from 67.215.65.132: bytes=32 time=350ms TTL=46
Reply from 67.215.65.132: bytes=32 time=108ms TTL=46
Reply from 67.215.65.132: bytes=32 time=137ms TTL=46
Reply from 67.215.65.132: bytes=32 time=93ms TTL=46

Ping statistics for 67.215.65.132:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 350ms, Average = 172ms

********************************************************************************************

 

skinorth

 

 

We Want Your Opinion
Would you be interested in becoming a Community Testing Lab member?
Topic Stats
  • 1 reply
  • 1539 views
  • 0 Likes
  • 2 in conversation