Shaw BlueCurve 2 Ip's - cant connect between them

[Kod3]

hello,

I recently upgraded to Shaw blue curve and I have spent 10 hours trying to solve this issue, went a bought a new router and contacted chat support 5 times and no help what so ever.

i have broken the issue down now to what i believe is a issue within Shaw's systems.

The modem is in bridged mode, providing 2 ip's to two routers.
Home network IP1 (ip range 192.168.10.xx)
Server network IP2 (hosts a website) (ip range 192.168.1.xx)

I appears that when im connected to IP1 I am unable to access any Services running in IP2,
such as the webserver on port 80 
or my manager software on port 8006

when I disconnect from both networks and use an outside IP address IP3 everything loads just fine.

So What ive broken it down to is that the internal IP's 1 & 2 can not connect on any port.

IP1 + IP2 = dropped packets
IP1/IP2 + IP3 = Packets are sent

Hopefully there is a fix or a simple solution as this has caused me many hours of headache, $150 for a router that wasn't needed and it worked with standard cable internet.

[mdk]

@Kod3 -- The modem is in bridged mode, providing 2 ip's to two routers.

Presumably, the WAN port on each of the two routers has obtained a "public" IP-address from Shaw's DHCP-server.

> Home network IP1 (ip range 192.168.10.xx). Server network IP2 (hosts a website) (ip range 192.168.1.xx)

Note that the "192.168.xxx.yyy" network is "special" -- it is a range of IP-addresses that routers on Shaw network, and on the whole Internet, are programmed to *NOT* "route" to any other router.

So, any IP-packet that you send from any "192.168.10.xxx" to an IP-address not on the same network is sent to your first router. But, that router does not route any IP-packet that has a "destination" IP-address of "192.168.xxx.yyy".

If you use the IPCONFIG command, you'll get output like:

Ethernet adapter Local Area Connection:

   IPv4 Address. . . . . . . . . . . : 192.168.0.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

That "subnet mask" is used to decide if an outgoing IP-packet is addressed to an IP-address inside your local network, or if the outgoing IP-packet must be sent to the "gateway", for forwarding on to the next router.

Compare talking face-to-face to somebody inside your house, or needing to use a telephone to talk to somebody who is not inside your house. The latter person cannot hear your voice, because the walls of your house block your voice from exiting your house.

To do what you want, you have to send your outgoing IP-packet to the "public" IP-address of the second router. Also, that router must be programmed to "forward" your IP-packet to the correct computer on the "192.168.1.xxx" network, because there could be multiple computers connected to that second router. 

Compare to two side-by-side apartment blocks, with a renter in one block looking out the window to see a renter in the other block looking out their window.  The two renters cannot communicate by voice. One renter needs to leave their block, go outside to a public area, and then walk to the public entrance to the other block, and then try to determine the correct apartment-number of the second person -- which will be a difficult task.

> use an outside IP address IP3 everything loads just fine

This implies that sending to the public IP-address of the second router causes that router to "forward" the IP-packets to a computer "inside" that local network. That is good.

Can you PING the public IP-address of the second router from a computer connected to the network provided by the first router?

Can you PING the public IP-address of the first router from a computer connected to the network provided by the second router?

Both should work.

[Kod3]

Hello,

I am able to ping from IP1 to IP2
but 100% Loss IP2 to IP1

[mdk]

@Kod3 -- I am able to ping from IP1 to IP2, but 100% Loss IP2 to IP1

That is a little too terse to be useful.

An IP-address is four "octets", e.g., "8.8.4.4".

What are the first 3 "octets" of the public IP-address (the WAN port) on the first router?

What are the first 3 "octets" of the public IP-address (the WAN port) on the second router?

From a computer connected to a LAN port on the first router, try TRACERT to the public IP-address of the second router. What output do you get?

From a different computer connected to a LAN port on the second router, try TRACERT to the public IP-address of the first router. What output do you get?

[Kod3]

ips
IP1 - 70.73.166.XX

IP2 - 70.73.173.XX

both traces time out at 15 hops.
Response from shaw only on IP1
No response from shaw or anything on IP2


IP1 TRACE ROUTE
traceroute to 70.73.173.XX (70.73.173.XX), 30 hops max, 38 byte packets
1 96.51.128.1 (96.51.128.1) 17.472 ms 15.432 ms 8.536 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *

IP2 TRACE ROUTE

traceroute to 70.73.166.XX (70.73.166.XX), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *

[mdk]

@Kod3 --  IP1 TRACE ROUTE
traceroute to 70.73.173.XX (70.73.173.XX), 30 hops max, 38 byte packets
1 96.51.128.1 (96.51.128.1) 17.472 ms 15.432 ms 8.536 ms

Are you using a traceroute function via an app within the router's web-server, or are you launching TRACERT from a Windows command-line prompt?

The IP-address ending with ".1" is a Shaw router in Calgary.

Nearby computers:

Name:    S010610561191f97d.cg.shawcable.net -- Address:  96.51.128.2 -- Arris Group

Name:    S0106a84e3fe79cc3.cg.shawcable.net -- Address:  96.51.128.3 -- Hitron Technologies

I am surprised at the output: 17.472 ms 15.432 ms 8.536 ms

Those are quite-large numbers for going just two "hops" (your router -> your BlueCurve -> that ".1" Shaw router).

Do you get similarly-large numbers when tracing to www.microsoft.com ?  Try from both of your routers.

[Four2zero]

i am having the exact same problem and am actively catching up i will post if my results are different

[Four2zero]

2 9 ms 8 ms 7 ms 96.48.96.1   windows to linux

2 96.48.96.1 (96.48.96.1) 25.466 ms 20.237 ms 26.893 ms  linux to windows 

15+ dead hops after wards on both sides

[Four2zero]

My set up is a Older dlink 825 wrt with a kali linux box and a couple raspberry pi's ( linux network )

other side is Ubiquiti Edgerouter Lite, Wireless APLR few windows pc's a bunch of xbox ones, phones, tvs pretty much the house( windows network )

[Four2zero]

Windows Side

tracert www.microsoft.com

Tracing route to e13678.dscb.akamaiedge.net [23.11.242.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 8 ms 12 ms 96.48.96.1
3 14 ms 11 ms 11 ms rc1bb-be122-1.vc.shawcable.net [64.59.147.185]
4 85 ms 228 ms 18 ms rc3ar-tge0-6-0-16.ed.shawcable.net [66.163.76.42]
5 9 ms 8 ms 8 ms a23-11-242-9.deploy.static.akamaitechnologies.com [23.11.242.9]

Trace complete.

Linux Side

traceroute www.microsoft.com
traceroute to www.microsoft.com (23.11.242.9), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.185 ms  0.215 ms  0.264 ms
 2  96.48.96.1 (96.48.96.1)  10.046 ms  15.709 ms  15.715 ms
 3  rc1st-be122-1.vc.shawcable.net (64.59.147.189)  18.031 ms  18.056 ms  18.092 ms
 4  rc1bb-be25.vc.shawcable.net (66.163.69.197)  19.199 ms  17.642 ms  17.659 ms
 5  rc3ar-tge0-6-0-16.ed.shawcable.net (66.163.76.42)  20.619 ms  20.697 ms  20.686 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *