SOLVED Issues with connecting to the TrueNAS update server

[satrajitdas]

I am new to TrueNAS and having issues with connecting to the TrueNAS update server (update-master.ixsystems.com) and wanted to see if anyone has encountered this and found a resolution.

This has been observed in my homelab (a TerraMaster T9-423 box) in both Bluefin (22.12.3.1 through 22.12.4.2) and Cobia (23.10).

From the Linux shell I can do a nslookup for "update-master.ixsystems.com" and it returns IPv4 "136.0.77.2" and IPv6 "2a10:c640:dead::5".

However, ping to "update-master.ixsystems.com" does not reach the server. Traceroute to "update-master.ixsystems.com" does not complete after step 30.

Trying to update through the TrueNAS GUI errors out saying the server is not reachable.

I can ping/traceroute other addresses (google.com, cloudflare.com) from the Linux shell.

The only way I could make it work was by clearing out the IPv6 gateway (a FE80 address), so that only a IPv4 gateway remained. Then the GUI update check worked.

Any help is appreciated.

 

[morganL]

Are you trying to update via IPv6?
Sounds like your IPv6 gateway is advertising reachability to something it cannot reach?

 

[satrajitdas]

My ISP supports IPv6 and I get IPv6 addresses for google.com and cloudflare.com and can ping them from the TreueNAS shell. So IPv6 by itself does not seem to be the problem.

 

[morganL]

My ISP supports IPv6 and I get IPv6 addresses for google.com and cloudflare.com and can ping them from the TreueNAS shell. So IPv6 by itself does not seem to be the problem.

Sure, but does the ISP offer global connectivity?
Do you need IPv6?

 

[satrajitdas]

If by global connectivity you mean if I can connect to other IPv6 websites, I can connect to other IPv6 sites like ipv6.google.com.

I would certainly like to be able to use IPv6 in my homelab environments.

 

[morganL]

If by global connectivity you mean if I can connect to other IPv6 websites, I can connect to other IPv6 sites like ipv6.google.com.

I would certainly like to be able to use IPv6 in my homelab environments.

google is not really a global test.. it has presence in every country.

.... can you get to others sites in other countries?

 

[morganL]

FYI.. I found that there is an issue with IPv6 routing to the specific CDN update servers we use.
The issue is being worked... in the meantime, disable IPv6 as a workaround.

 

[morganL]

If by global connectivity you mean if I can connect to other IPv6 websites, I can connect to other IPv6 sites like ipv6.google.com.

I would certainly like to be able to use IPv6 in my homelab environments.

I think it is now working with IPv6... can you verify?

 

[satrajitdas]

Right now the nslookup of "update-master.ixsystems.com" is returning only an IPv4 (185.244.226.4) and no IPv6. Therefore, the update check has no issues.

 

[morganL]

Right now the nslookup of "update-master.ixsystems.com" is returning only an IPv4 (185.244.226.4) and no IPv6. Therefore, the update check has no issues.

It looks like we fixed the problem in two ways:
1. By disabling IPv6 in DNS lookup
2. By fixing the Ipv6 routing

So, #2 is not really being tested.

 

[un1xl0ser]

I'm on IPv4 and dying well after my ISP in traceroutes. System was powered off, then did an update and wasn't able to "double check" updates after the update. Not sure if timing was a coincidence.

Trying the IP address that my host naturally responds to:
6 bundle-ether307.amstr1.amsterdam.opentransit.net (193.251.241.222)
7 * * *

Trying the 226.4 address above.
9 be3529.rcr51.b054249-0.yyz02.atlas.cogentco.com (154.54.24.194)

be3528.rcr51.b054249-0.yyz02.atlas.cogentco.com (66.28.4.246)

10 * * *

The host knows nothing of IPv6. Simple curl of Google and other hosts works fine. So it may be an issue with a CDN network, but I'm not 100% that it is only with IPv6.

Sorry this is my first post.

 

[morganL]

I'm on IPv4 and dying well after my ISP in traceroutes. System was powered off, then did an update and wasn't able to "double check" updates after the update. Not sure if timing was a coincidence.

Trying the IP address that my host naturally responds to:
6 bundle-ether307.amstr1.amsterdam.opentransit.net (193.251.241.222)
7 * * *

Trying the 226.4 address above.
9 be3529.rcr51.b054249-0.yyz02.atlas.cogentco.com (154.54.24.194)

be3528.rcr51.b054249-0.yyz02.atlas.cogentco.com (66.28.4.246)

10 * * *

The host knows nothing of IPv6. Simple curl of Google and other hosts works fine. So it may be an issue with a CDN network, but I'm not 100% that it is only with IPv6.

Sorry this is my first post.

Try again ... if Internet connectivity is fine, but update server is not available, let us know location and ISP.

 

[un1xl0ser]

Try again ... if Internet connectivity is fine, but update server is not available, let us know location and ISP.

Looks good now, as expected, no updates.

 

[listhor]

I’m not sure if it is just only me, but my instance of Cobia can’t reach update servers through ip6 network. ip4 works fine.
Can somebody confirm that?