Hi, I am using the routers built in tools, Linux CLI, an...

[Kod3]

Hi,

I am using the routers built in tools, Linux CLI, and windows CMD to ping and trace 

Here are the results from trace to Microsoft.com

IP 1 TRACE
traceroute to microsoft.com (40.113.200.201), 30 hops max, 38 byte packets
1 96.51.128.1 (96.51.128.1) 12.751 ms 9.315 ms 14.690 ms
2 rc3no-be109-1.cg.shawcable.net (64.59.134.101) 9.727 ms 9.500 ms 9.922 ms
3 rc1st-be11-1.vc.shawcable.net (66.163.72.70) 25.608 ms 23.378 ms 21.625 ms
4 ae61-0.ier01.yvr30.ntwk.msn.net (104.44.12.96) 21.384 ms 23.703 ms 20.810 ms
5 ae22-0.icr01.mwh01.ntwk.msn.net (104.44.40.37) 33.069 ms 29.672 ms 27.640 ms
6 be-160-0.ibr02.mwh01.ntwk.msn.net (104.44.21.149) 66.356 * * *
12 * * *
13 * * *
14 * * *

IP 2 TRACE
traceroute to microsoft.com (40.113.200.201), 30 hops max, 38 byte packets
1 * * *
2 rc3no-be109-1.cg.shawcable.net (64.59.134.101) 8.900 ms 9.040 ms 9.580 ms
3 rc1st-be11-1.vc.shawcable.net (66.163.72.70) 26.280 ms 16.120 ms 20.420 ms
4 ae61-0.ier01.yvr30.ntwk.msn.net (104.44.12.96) 18.700 ms 30.800 ms 21.720 ms
5 ae22-0.icr01.mwh01.ntwk.msn.net (104.44.40.37) 28.560 ms 29.020 ms 29.680 ms
6 be-141-0.ibr03.mwh01.ntwk.msn.net (104.44.21.157) 67.340 ms 67.460 ms 66.960 ms
7 104.44.29.21 (104.44.29.21) 68.300 ms 67.500 ms 72.580 ms
8 be-4-0.ibr03.dsm05.ntwk.msn.net (104.44.28.248) 66.700 ms 67.640 ms 66.860 ms
9 ae142-0.icr04.dsm05.ntwk.msn.net (104.44.22.200) 62.320 ms 65.840 ms 63.360 ms
10 * * *
11 * * *
12 * * *

[mdk]

@Four2zero -- interleaving your two traces:

1 192.168.1.1 - gateway on one of your routers
1 192.168.0.1 - gateway on your other router

2 96.48.96.1 - Shaw's router in your city
2 96.48.96.1

3 rc1bb-be122-1.vc.shawcable.net [64.59.147.185] - one Shaw router
3 rc1st-be122-1.vc.shawcable.net (64.59.147.189) - another Shaw router

4 rc1bb-be25.vc.shawcable.net (66.163.69.197) - other Shaw router, listed only in one trace

4 rc3ar-tge0-6-0-16.ed.shawcable.net [66.163.76.42]
5 rc3ar-tge0-6-0-16.ed.shawcable.net (66.163.76.42) 

5 a23-11-242-9.deploy.static.akamaitechnologies.com [23.11.242.9]

Vancouver is a big city. So, your packets from "96.48.96.1" found two different paths from Vancouver to Shaw's router in Edmonton: VAN1 -> VAN2 -> ED versus VAN3 -> ED.

Curious that one trace is not "successful". No idea why.

From your LINUX system, can you access the www.microsoft.com web-site?  Maybe, it's just PING packets to that site that either or not being responded to, or the response does not reach your system.

[mdk]

@Kod3 -- Here are the results from trace to Microsoft.com

Physically, are you in the Calgary area?

Microsoft has multiple web-servers.

In my reply to @Four2zero -- the traces (from YVR) went to a Microsoft computer in Edmonton.

In your reply, you traces to a Microsoft computer south of YVR, inside the USA.

Ah, the "fun" of dynamic routing tables, with different priorities for each network.

The IP-address depends on which DNS-server you ask:

$ nslookup www.microsoft.com 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Name:    e13678.dscb.akamaiedge.net
Addresses:  23.11.242.9
Aliases:  www.microsoft.com
          www.microsoft.com-c-3.edgekey.net
          www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net

$ nslookup www.microsoft.com 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Name:    e13678.dscb.akamaiedge.net
Addresses:  23.218.110.52
Aliases:  www.microsoft.com
          www.microsoft.com-c-3.edgekey.net
          www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net

Take your pick: 23.11.242.9 or 23.218.110.52 or 40.113.200.201

  🙂

[Kod3]

Hello Yes I am In the calgary area.

and I tested trace on 2 of the IPs above on both networks

IP 1

Test 1

traceroute to 23.218.110.52 (23.218.110.52), 30 hops max, 38 byte packets
1 96.51.128.1 (96.51.128.1) 193.766 ms 8.065 ms 8.537 ms
2 rc3no-be109-1.cg.shawcable.net (64.59.134.101) 12.180 ms 11.100 ms 9.122 ms
3 rc2wt-be100.wa.shawcable.net (66.163.75.233) 25.301 ms 25.570 ms 27.934 ms
4 rx0wt-korea-telecom.wa.shawcable.net (66.163.68.14) 24.760 ms 24.862 ms 24.707 ms
5 ae3.digfort-sea.netarch.akamai.com (23.203.145.151) 27.347 ms 27.295 ms 24.574 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *

Test 2

traceroute to 40.113.200.201 (40.113.200.201), 30 hops max, 38 byte packets
1 96.51.128.1 (96.51.128.1) 267.610 ms 8.005 ms 17.472 ms
2 rc3no-be109-1.cg.shawcable.net (64.59.134.101) 9.237 ms 8.881 ms 8.352 ms
3 rc1st-be11-1.vc.shawcable.net (66.163.72.70) 20.830 ms 20.846 ms 23.083 ms
4 ae61-0.ier01.yvr30.ntwk.msn.net (104.44.12.96) 20.621 ms 20.289 ms 25.334 ms
5 ae22-0.icr01.mwh01.ntwk.msn.net (104.44.40.37) 34.277 ms 29.447 ms 29.664 ms
6 be-100-0.ibr01.mwh01.ntwk.msn.net (104.44.21.141) 65.642 ms be-141-0.ibr03.mwh01.ntwk.msn.net (104.44.21.157) 68.276 ms be-161-0.ibr04.mwh01.ntwk.m * * *
7 * * *
8 * * *
9 * * *
10 * * *

IP 2

Test 1

traceroute to 23.218.110.52 (23.218.110.52), 30 hops max, 38 byte packets
1 * * *
2 rc3no-be109-1.cg.shawcable.net (64.59.134.101) 8.620 ms 8.920 ms 9.700 ms
3 rc2wt-be100.wa.shawcable.net (66.163.75.233) 24.680 ms 30.260 ms 20.680 ms
4 rx0wt-korea-telecom.wa.shawcable.net (66.163.68.14) 23.920 ms 23.300 ms 24.220 ms
5 ae3.digfort-sea.netarch.akamai.com (23.203.145.151) 27.240 ms 32.380 ms 27.900 ms
6 a23-218-110-52.deploy.static.akamaitechnologies.com (23.218.110.52) 26.500 ms 23.420
Trace complete

Test 2
traceroute to 40.113.200.201 (40.113.200.201), 30 hops max, 38 byte packets
1 * * *
2 rc3no-be109-1.cg.shawcable.net (64.59.134.101) 8.700 ms 9.160 ms 9.600 ms
3 rc1st-be11-1.vc.shawcable.net (66.163.72.70) 20.100 ms 20.980 ms 20.600 ms
4 ae61-0.ier01.yvr30.ntwk.msn.net (104.44.12.96) 19.580 ms 20.160 ms 19.660 ms
5 ae22-0.icr01.mwh01.ntwk.msn.net (104.44.40.37) 29.160 ms 28.000 ms 29.340 ms
6 be-160-0.ibr02.mwh01.ntwk.msn.net (104.44.21.149) 84.780 ms 67.780 ms 67.840 ms
7 be-7-0.ibr02.cys04.ntwk.msn.net (104.44.18.224) 63.460 ms 63.600 ms 63.680 ms
8 be-8-0.ibr02.dsm05.ntwk.msn.net (104.44.18.151) 171.200 ms 65.460 ms 60.220 ms
9 ae163-0.icr04.dsm05.ntwk.msn.net (104.44.22.192) 71.300 ms 80.100 ms 74.160 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *

I am able to access webpages and everything just fine on both networks, The only problem that exists still in IP1 cant connect with IP2, This is really quite frustrating. Could it be an issue with the IP's Assigned themselves, Should We reset them and get two new IP addresses?

[mdk]

@Kod3 -- frustrating

Indeed! Sigh.

> Should we reset them and get two new IP addresses?

Unfortunately for you, unless you can change the MAC-address of your router, sending a new DHCP-request to Shaw's DHCP-server will return the current IP-address. I suppose that you could convince your router to "clone" the MAC-address of one computer connected to the router.

> Could it be an issue with the IP's Assigned themselves,

Doubtful, given that your TRACERT outputs seem completely normal, and your HTTP-accesses are working fine.

Maybe, the routing-tables inside Shaw's routers could be "blocking" your traces.

Not being employed by Shaw, I cannot access those tables.

Also, without knowing the "public" IP-address of your router(s), I cannot do any TRACERT to see if I can reach your router.

[Four2zero]

**bleep** still no solution to this, i talked to shaw for sometime about this they just told me it's my problem

[mdk]

@Four2zero -- take a notebook computer running Windows to a "ShawOpen" or a "ShawGo" WiFi access-point (or even a "#TELUS" WiFi access-point), and connect.

Do a TRACERT to the public IP-address of your first router.

Do a TRACERT to the public IP-address of your second router.

Show us the results.

[cenobyte]

I have the same problem. Configuration was working fine with a legacy cable modem two ports, two public ips. Pfsense firewall on the main network, Microtik on the secondary network. Pings between the networks are answered, but no connection between the two are possible. Web requests time out, unable to ssh between the two.

I plugged straight into the modem with a laptop and tried to access the secondary network....same issue so it's not the pfsense firewall. Both setups work externally, they just can't talk to each other.

I suspect this is an issue either on the back end with Shaw's services/ routing or with the cable modem itself (modem is in bridge mode)
Their support staff won't touch this kind of configuration so don't bother wasting your time with them.

Unfortunately this is going in the unfixable bin for now 😞

[mdk]

@cenobyte -- Pings between the networks are answered, but no connection between the two are possible.

PING packets are handled by the TCP/IP software running inside the operating system's "kernel", not by any app running on the computer. HTTP packets must go "through" that TCP/IP software to connect to a HTTP-server app, and the response packets from the app must return "through" to the network to the computer that issued the HTTP request.

So, does the log-file on the HTTP-server app record the incoming HTTP-request?

Under Windows, are you using the "iptrace" system-tool to "sniff" all the traffic reaching the computer that is running the HTTP-server app?  Does its log-file show any traffic from the "source" computer?

[cenobyte]

I think you’re referring to traceroute which basically shows the route running from one public up to another with only one stop at shaw along the way. I don’t see an “iptrace” command either on my linux boxes or windows (windows 10 or otherwise).

Did check the logs on the web server on the second public network. Did not see any traffic from the first. My guess is there’s some kind of blocking of “hairpinning” done either on their network or the modem itself. (the modem doesn’t expect to see traffic from itself maybe?)

Either way, I managed to work around this by setting up a second virtual network card that lives on the second web server. Then I pointed the internal dns to that card.

Everything works now and the two devices can talk.

Might be a solution for the original poster (don’t know what’s happened since with them)