Rogers Household to Rogers Household Ping Issues - Routing Issues

[Yatti420]

Hello everybody, 

Sad that I have to come on the forums to get a second opinion on this.. I think I have a routing issues between to rogers IP blocks.. 99x to 173x .. Doesn't seem to be functioning when I attempt to ping my secondary household both with Rogers packages.. 

There seems to be either a server blocking my requests (one way only) or a big routing issue on this block.. 

House 1 - Cisco DPC3825 Bridged to D-Link DIR-655 (rogers DNS for testing) {WAN Ping Allowed}

House 2 - Hitron CGN2-ROG Gateway/Router (rogers DNS for testing) {WAN Ping Allowed}

Pings to google/hitron from house 2.. 

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

ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64

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

ping google.ca

Pinging google.ca [64.71.249.49] with 32 bytes of data:
Reply from 64.71.249.49: bytes=32 time=13ms TTL=57
Reply from 64.71.249.49: bytes=32 time=16ms TTL=57
Reply from 64.71.249.49: bytes=32 time=18ms TTL=57
Reply from 64.71.249.49: bytes=32 time=15ms TTL=57

Ping statistics for 64.71.249.49:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 18ms, Average = 15ms

Tracert from House 1 to google.. 

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

tracert google.ca

Tracing route to google.ca [64.71.249.49]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2    10 ms    10 ms     9 ms  7.8.0.1
  3    17 ms    13 ms    10 ms  69.63.254.229
  4    15 ms    13 ms    15 ms  24.156.157.86
  5    15 ms    18 ms    15 ms  69.63.249.205
  6    13 ms    18 ms    18 ms  69.63.249.61
  7    14 ms    14 ms    17 ms  69.63.248.170
  8    16 ms    12 ms    17 ms  64.71.249.49

Trace complete.

Now I can ping from House1 to House 2 without issues.. However attempting to go from House 2 (non bridge) to House 1 (bridged) results in destination host unreachable or requests time out.. This is not the case the other way around.. 

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

tracert 173.32.75.8

Tracing route to CPE1caff7df5aba-CMbcc8101002de.cpe.net.cable.rogers.com [173.32
.75.8]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2     9 ms     8 ms    13 ms  7.8.0.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *     69.63.254.229  reports: Destination net unreachable.

Trace complete.

tracert 173.32.75.8

Tracing route to CPE1caff7df5aba-CMbcc8101002de.cpe.net.cable.rogers.com [173.32
.75.8]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2    11 ms    10 ms    10 ms  7.8.0.1
  3     *     69.63.254.229  reports: Destination net unreachable.

Trace complete.

 This is driving me nuts not being able to ping or connect to my secondary household.. Oddly I can access the router (dlink) at house #1 via webgui on a different port.. 

Any help would be greatly appreciated as my connection works one way.. But not the other.. Dissapointed to say the least.. It's been a week like this.. The only thing I could consider on my end (house 1) is debridge the cisco and try again.. 69.63.254.229 what is this? Why is is it blocking my connection to the 173x block? Yet from 173x I can ping and router 99x no issues.. 

Thanks in advance, 
Yatti420

***edited labels***

[Gdkitty]

nothing is jumping right out to me at first look.. i will think on it and see if i can come up with anything.

Are you able to post the tracert of the one that DOES work? just for comparison?

And roughly where are these two locations located?  Just wondering if greatly different areas.

[Yatti420]

I will post it shortly.. As far as I can tell the 69.63.254.229 ip is blocking my request.. I did notice the blocks are different.. House in Waterloo has a KWC block.. House in Cambridge looks like etobicoke? I will post tracert from both connections tomorrow.. 

Has anybody else had problems with pinging their networks?

[Gdkitty]

Not myself, though not going from Rogers to Rogers though. Usually from a bell one at work, etc.
and I also live in a very different area than you.

From work I can ping, I can connect into my FTP, web, and media server within issue. This is on an SMC, non bridged.

[Yatti420]

From House 2 to House 1 ...

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

ping 173.32.75.8

Pinging 173.32.75.8 with 32 bytes of data:
Reply from 69.63.254.229: Destination net unreachable.
Reply from 69.63.254.229: Destination net unreachable.
Reply from 69.63.254.229: Destination net unreachable.
Reply from 69.63.254.229: Destination net unreachable.

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

tracert 173.32.75.8

Tracing route to 173.32.75.8 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2     9 ms     9 ms    19 ms  7.8.0.1
  3  69.63.254.229  reports: Destination net unreachable.

Trace complete.

C:\Users\Greg>tracert 173.32.75.8

Tracing route to 173.32.75.8 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2    10 ms     9 ms    10 ms  7.8.0.1
  3  69.63.254.229  reports: Destination net unreachable.

Trace complete.

I think I'm gonna debridge and reset everything up.. I don't have much hope.. Might have to call rogers.. Don't expect much though..

[Yatti420]

PING 99.236.194.239 (99.236.194.239) 56(84) bytes of data.
64 bytes from 99.236.194.239: icmp_req=1 ttl=59 time=58.0 ms
64 bytes from 99.236.194.239: icmp_req=2 ttl=59 time=16.8 ms
64 bytes from 99.236.194.239: icmp_req=3 ttl=59 time=20.7 ms
64 bytes from 99.236.194.239: icmp_req=4 ttl=59 time=18.7 ms
64 bytes from 99.236.194.239: icmp_req=5 ttl=59 time=23.6 ms

 This is from the working household.. I'm over wireless so high response times.. 

Unfortuanately I just tried to ping again and get rejections.. Ridiculous.. I can't traceroute currently from either connection.. As you can imagine this is causing alot of headaches..

[Gdkitty]

On your 99. IP, i am able to tracert to it completely fine, from my rogers connection
(again, i am in a very different area).

The 173, i am not, it is not able to go past the 2nd hop, just the same as yours.. allthough a different 3rd node IP.

173... that an ODD ip range though.. never seen one in that range normally in my experiences..

[Yatti420]

Hi GDKitty, 

I forced a new IP last night.. I can also ping to the 99 and tracert fine.. 

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

ping 99.236.194.239

Pinging 99.236.194.239 with 32 bytes of data:
Reply from 99.236.194.239: bytes=32 time=18ms TTL=60
Reply from 99.236.194.239: bytes=32 time=15ms TTL=60
Reply from 99.236.194.239: bytes=32 time=15ms TTL=60
Reply from 99.236.194.239: bytes=32 time=18ms TTL=60

Ping statistics for 99.236.194.239:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 18ms, Average = 16ms

ping 99.236.194.239

Pinging 99.236.194.239 with 32 bytes of data:
Reply from 99.236.194.239: bytes=32 time=15ms TTL=60
Reply from 99.236.194.239: bytes=32 time=18ms TTL=60
Reply from 99.236.194.239: bytes=32 time=14ms TTL=60
Reply from 99.236.194.239: bytes=32 time=16ms TTL=60

Ping statistics for 99.236.194.239:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 18ms, Average = 15ms

tracert 99.236.194.239

Tracing route to CPE68b6fcd02783-CM68b6fcd02780.cpe.net.cable.rogers.com [99.236
.194.239]
over a maximum of 30 hops:

  1     8 ms     6 ms     8 ms  7.9.172.1
  2    11 ms    10 ms    11 ms  24.156.149.209
  3    11 ms    10 ms    10 ms  69.63.249.213
  4     8 ms     8 ms     9 ms  69.63.254.230
  5    17 ms    15 ms    14 ms  CPE68b6fcd02783-CM68b6fcd02780.cpe.net.cable.rog
ers.com [99.236.194.239]

Trace complete.

 I just debridged everything and disabled the wan ping block on the Cisco..

Oddly egnough Rogers must think we have a Hitron now as we got billed for a $7 rental versus the cisco $3-4? Wow.. 

[Yatti420]

173.32.79.179 is the IP we have currently for the bridged house.. Hopefully this shakeup without the D-Link in place will help.. 

So current setup

House 1 - Cisco DPC3825  (rogers DNS for testing) {WAN Ping Allowed} 173.32.79.179

House 2 - Hitron CGN2-ROG Gateway/Router (rogers DNS for testing) {WAN Ping Allowed} 99.236.194.239

I can go from House  1 to 2 no issues.. Just not backwards.. I agree it's a weird block of ips I've never seen it in use before.. 

[Gdkitty]

Did a little diging..

173, was a range that was not INITIALLY open to PUBLIC IP addressing, till a number of  years ago.

I wonder, if its that its not being routable, as something thinking its still NOT a public one?

Might be worth a call in, and see if you can have them CYCLE your IP address and get a new one, hopefully in a different range.

[Yatti420]

Can you ping/tracert both connections?

[Gdkitty]

ping/tracrt is FINE to your 99, fails on to the 173 from my rogers connection.

Am able to ping/tracert BOTH from my bell work connection.

[Yatti420]

I'm at a loss to what it could be.. Hopefully Rogers fixes this soon.. Express connection.. Billed for Hitron @ $7?

Model:	Cisco DPC3825
Vendor:	Cisco
Hardware Revision:	1.0
Serial Number:	
MAC Address:	
Bootloader Revision:	2.3.0_R3
Current Software Revision:	dpc3825-v302r125533-111108a-ROG
Firmware Name:	dpc3825-v302r125533-111108a-ROG.bin
Firmware Build Time:	 Nov 8 18:12:42 2011
Cable Modem Status:	Operational
Wireless Network:	Enable
 	Cisco Logo
 		
Cable Modem State	 
DOCSIS Downstream Scanning:	Completed
DOCSIS Ranging:	Completed
DOCSIS DHCP:	Completed
DOCSIS TFTP:	Completed
DOCSIS Data Reg Complete:	Completed
DOCSIS Privacy:	Enabled
 		
Downstream Channels	 
 	Power Level:	Signal to Noise Ratio:
Channel 1:	 -7.2 dBmV	37.9 dB
Channel 2:	 -6.9 dBmV	38.3 dB
Channel 3:	 -7.2 dBmV	38.1 dB
Channel 4:	 -7.5 dBmV	37.8 dB
Channel 5:	 -7.6 dBmV	37.1 dB
Channel 6:	 -7.6 dBmV	37.9 dB
Channel 7:	 -8.8 dBmV	37.2 dB
Channel 8:	 -9.2 dBmV	36.9 dB
 		
Upstream Channels	 
 	Power Level:
Channel 1:	39.0 dBmV
Channel 2:	39.2 dBmV
Channel 3:	40.7 dBmV
Channel 4:	 0.0 dBmV

**Edited for content**

[Gdkitty]

Signal levels look within norms there..

only thing i can think is the hitron is blocking something.. many people have found issues with port forwarding on it, etc..

Any of the rogers near you, have anything other than the hitron that you could use instead? (like the cisco, smc, etc)

[Yatti420]

Looks like routing from 173 to 99 isn't the problem.. But 99 block to 173 block is.. I'm not sure if it's been fixed yet I haven't tried anything in a few days.. The cisco doesn't seem to like port forwarding or triggering on its own..  I will look into bridging the hitron aswell..

[Gdkitty]

The port forwarding on the Cisco used to work but a few others have commented lately about issues with it. Maybe upgraded the firmware and broke it.
I am holding onto my smc for dear life as I know it works. 😛

[Yatti420]

That is not surprising with the Cisco.. I rebridged and can still ping to 99 block.. Now to see if 99x can go to 173x..

[Yatti420]

Still same issue.. Can go one way but not the other.. 99x to 173x is returning destination host unreachable.. Yet from anywhere else I can ping both.. 😞

[Gdkitty]

Only thing I can think is if you can swap the hardware to another different gateway at the the 173 side.

[Yatti420]

Oddly my setup started working.. Im not sure if its intermittent however.. So pinging isn't working but my logging is from 99x to 173x.. Hopefully backups aswell.. We will see in a bit.

Can somebody confirm the rental price for the DPC3825 Cisco? We were charged 7$ this month?

[TeDD13]

Cisco DPC 3825 is in the same category as Hitron CGN2, so it should be $8/month