Skip to content

packages.broadcom.com has no AAAA record / IPv6 support #67051

Closed as not planned

Description

@chrisnew

Description of Issue/Question

After discovering the sudden and fun breaking change (salt-bootstrap:#2027) of deprecating repo.saltstack.io recently, we tried to follow the community’s effort to patch the install script and to install salt manually. However, some of our infrastructure is IPv6-only.

Setup

IPv6-only deployment.

Steps to Reproduce Issue

Try to install salt-minion from packages.broadcom.com in an IPv6-only network.

The core issue can be reproduced as shown below:

$ dig -t aaaa packages.broadcom.com

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> -t aaaa packages.broadcom.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52388
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;packages.broadcom.com.		IN	AAAA

;; ANSWER SECTION:
packages.broadcom.com.	56	IN	CNAME	broadcom.jfrog.io.
broadcom.jfrog.io.	60	IN	CNAME	endpointdns-prod-usw2-lb.jfrog.io.
endpointdns-prod-usw2-lb.jfrog.io. 60 IN CNAME	k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com.

Versions and Systems

not applicable

Activity

  1. ScriptAutomate commented on Nov 12, 2024

    @ScriptAutomate
    Contributor

    We've reached out to the Broadcom team that manages this, and will update this issue when more information is made available.

  2. changed the title [-]packages.broadcom.com has no AAAA record[/-] [+]packages.broadcom.com has no AAAA record / IPv6 support[/+] on Nov 13, 2024
  3. deleted a comment from welcome on Nov 13, 2024
  4. chrisnew commented on Nov 25, 2024

    @chrisnew
    Author

    @ScriptAutomate thanks! Do you have already feedback from them? One of my clients has severe issues right now and we are duct taping the fun out of these sites 😕 The reason being Cannot initiate the connection to packages.broadcom.com:443 (100.21.156.46). - connect (101: Network is unreachable) completely breaks the ability to upgrade and install things on Debian

  5. AxisNL commented on Nov 25, 2024

    @AxisNL

    Same here, I manage dozens of ipv6-only machines, got a problem connecting those. Disabled the repo for now.

  6. ScriptAutomate commented on Nov 26, 2024

    @ScriptAutomate
    Contributor

    @chrisnew @AxisNL The team owning this started engaging with JFrog last week. No new updates on our end.

  7. pk-lms-dev commented on Dec 4, 2024

    @pk-lms-dev

    Oh yes, IPv6 for the repo please!

  8. ichilton commented on Dec 12, 2024

    @ichilton

    Any update on this? - I too have v6 only machines which are unable to access the repo.

  9. MEschenbacher commented on Dec 29, 2024

    @MEschenbacher
    Contributor

    I'd like to chime in, please support the current internet protocol version.

  10. ScriptAutomate commented on Jan 15, 2025

    @ScriptAutomate
    Contributor

    Updates:

    • No changes have been made to packages.broadcom.com
    • Internal teams at Broadcom are aware of this issue: they have no estimated date upon when they'd have changes implemented
    • Expect that any new updates may take several months

    The Salt Project team is unable to assist further at this time. I will only update this issue when we get more relevant updates from Broadcom teams internally in regard to this issue.

    For those that are Broadcom / VMware by Broadcom customers: we recommend opening a ticket with support about this issue, as that will help raise further awareness and priority internally as they track impacted customers.

  11. ScriptAutomate commented on Jan 30, 2025

    @ScriptAutomate
    Contributor

    Updates:

    • After further investigation, found that JFrog SaaS infra is not configured to support IPv6 - leaving Broadcom dependent on changes via JFrog
    • Confirmed with JFrog, through support contact, that they indeed do not currently support IPv6 as an option but are aware of the need (already had an internal backlog item for it). Though, they have no ETA on implementation and will be providing no estimate
    • Best recommendation for users would be to see whether able to create a reachable mirror in the IPv6-only environments, after pulling/pushing mirrors of the repo from an IPv4-capable host: https://docs.saltproject.io/salt/install-guide/en/latest/topics/other-install-types/air-gap-install.html
    • For those that are Broadcom / VMware by Broadcom customers: we recommend opening a ticket with Broadcom support about this issue, as that will help raise further awareness as they track impacted customers

    Since the Salt Project Team is unable to take further action at this time, we are going to close this ticket as not planned / won't fix.

  12. ScriptAutomate commented on Feb 14, 2025

    @ScriptAutomate
    Contributor

    Speaking of IPv6 support: I'm sharing here in this issue thread a link to a feature request I've submitted for GitHub since there have been users reporting problems using some services/endpoints/features of GitHub. Sharing for awareness.

  13. mattgroves commented on Jun 19, 2025

    @mattgroves

    Still an issue - how difficult can it be to assign an IPv6 address in AWS?

    packages.broadcom.com is an alias for broadcom.jfrog.io.
    broadcom.jfrog.io is an alias for endpointdns-prod-usw2-lb.jfrog.io.
    endpointdns-prod-usw2-lb.jfrog.io is an alias for k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com.
    k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com has address 54.185.186.5
    k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com has address 100.21.156.46
    k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com has address 44.226.59.123
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions