[RndTbl] Problems with setting up off-site backup via Shaw (residential)

Kevin McGregor kevin.a.mcgregor at gmail.com
Mon Jan 1 17:05:07 CST 2024


I've been trying to set up off-site backups from my home (site A) to
another person's home (site B).

My home internet (i.e. site A) is provided by Shaw. Site B has internet
services provided by Telus, which is provided by Altima Telecom... which is
provided by Shaw (as near as I can tell).

Both sites have a server running TrueNAS. In the past I had this setup
working, although the internet providers were different at the time. It
involved forwarding a port by the router at site B to the destination
server within site B. I haven't been able to get this to work since the
change in providers. The destination simply doesn't respond no matter what
port-forwarding settings I use.

I ran a traceroute from site B to google.ca:
Tracing route to www.google.ca [142.251.211.227]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.home [192.168.1.1]
  2    10 ms     8 ms     8 ms  50.71.160.1
  3     *        *        *     Request timed out.
  4    10 ms     9 ms     9 ms  rc3sc-be2.wp.shawcable.net [24.244.58.169]
  5    35 ms    35 ms    36 ms  104.159.27.13
  6    37 ms    34 ms    34 ms  10.70.50.1
  7    37 ms    37 ms    36 ms  van-b1-link.ip.twelve99.net [62.115.145.124]
  8    38 ms    38 ms    40 ms  sea-b3-link.ip.twelve99.net [62.115.138.40]
  9    47 ms    41 ms    42 ms  sea-b1-link.ip.twelve99.net [62.115.132.157]
 10    40 ms    39 ms    38 ms  74.125.51.236
 11    41 ms    43 ms    42 ms  142.251.70.99
 12    40 ms    40 ms    40 ms  216.239.43.121
 13    43 ms    41 ms    41 ms  sea30s13-in-f3.1e100.net [142.251.211.227]

Trace complete.

>From site A to site B, the traceroute shows:
Tracing route to 104.159.x.y over a maximum of 30 hops

  1     3 ms     3 ms     2 ms  192.168.1.1
  2     7 ms     5 ms     6 ms  10.0.0.1       <site A is double-NATted :-(
>
  3    15 ms    16 ms    17 ms  50.71.160.1
  4    19 ms    14 ms    17 ms  rc3sc-be101-1.wp.shawcable.net
[64.59.179.233]
  5    18 ms    17 ms    17 ms  24.244.61.61
  6    20 ms    18 ms    21 ms  24.244.58.173
  7    18 ms    17 ms    22 ms  rc3sc-be2.wp.shawcable.net [24.244.58.169]
  8    34 ms    30 ms    28 ms  rc3so-be110-1.cg.shawcable.net
[66.163.76.61]
  9    41 ms    42 ms    45 ms  rc1bb-be6-1.vc.shawcable.net [66.163.78.38]
 10     *       42 ms    41 ms  rd3bb-tge0-3-0-14.vc.shawcable.net
[66.163.69.42]
 11    49 ms    49 ms    47 ms  altimatelecom-ic-369545.ip.twelve99-cust.net
[62.115.145.125]
 12    50 ms    46 ms    47 ms  <WAN IP of site B (104.159.x.y)>
 13    79 ms    78 ms    98 ms  <WAN IP of site B, again>
 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

Can anyone explain what I'm seeing here? E.g. Why does the site B IP
address appear twice? Why all the following request timeouts? I've used the
WAN IP address of site B as the destination and set up port forwarding from
that router to my remote NAS box, but as I said there is never any response.

Does anyone have any suggestions as to what to try next?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://muug.ca/pipermail/roundtable/attachments/20240101/3df24262/attachment.htm>


More information about the Roundtable mailing list