These are all working fine from my eyeball networks on IPv6.

I put together the commands I ran to check, if others are interested. All
besides git and ssh I was able to do without hosts file modifications.

Great job, Kevin! The only thing I noticed was an inconsistency in the
headers served from the proxies vs from the download servers directly. The
former use lowercase headers (x-fedora-appserver) and the latter uppercase
(X-Fedora-AppServer). Definitely small and fairly inconsequential unless
you're grepping for stuff like I am here.

Anyways, my one liners:

---

# Test SSH to bastions (requires hosts file for completeness)

for s in bastion0{1..2}; do ssh -vv $s 'hostname -f' 2>&1 | grep -E
'(debug1: Connecting to|^bastion[0-9]+\.rdu3)'; done

# Test DNS resolution from NS01 and NS03

for s in 2620:52:6:1121:bead:cafe:feed:fed{3..4}; do dig +noall +answer @$s
SOA fedoraproject.org; done

# Test proxies

for host in fed{5..6}; do curl -6 https://koji.fedoraproject.org/koji/
--resolve koji.fedoraproject.org:443:[2620:52:6:1121:bead:cafe:feed:$host]
-svo /dev/null 2>&1 | grep -E '(Connected to|x-fedora)'; done

# Test RSYNC from download servers

for host in fe{d{7..9},{10..11}}; do rsync -vvv
[2620:52:6:1121:bead:cafe:feed:$host]:: 2>&1 | grep -iEo '(You have
)?Connected to.*'; done

# Test https from download servers

for host in fe{d{7..9},{10..11}}; do curl -X HEAD -svo /dev/null
https://download.fedoraproject.org/pub/fedora/fullfilelist --resolve
download.fedoraproject.org:443:[2620:52:6:1121:bead:cafe:feed:$host] 2>&1 |
grep -iE '(Connected to|x-fedora)'; done

# Test pkgs git (needs DNS, for completeness)

git clone git+ssh://$USER@pkgs01/forks/$USER/rpms/remind /tmp/remind
git -C /tmp/remind commit --allow-empty -m "testing"
git -C /tmp/remind push

# Test proxies (stg)

for host in fed{1..2}; do curl -6 https://koji.stg.fedoraproject.org/koji/
--resolve koji.stg.fedoraproject.org:443:[2620:52:6:1131:bead:cafe:feed:$host]
-svo /dev/null 2>&1 | grep -E '(Connected to|x-fedora)'; done

---

--Neil

On Wed, Jul 16, 2025 at 6:54 PM Kevin Fenzi via infrastructure <
infrastructure@lists.fedoraproject.org> wrote:

> Hey everyone.
>
> We have ipv6 turned up in the new datacenter, and I would love for some
> folks with ipv6 enabled to do a bit of testing before we add it into dns
> for everyone.
>
> The addresses and some notes about testing:
>
> In general, you will need to add a /etc/hosts entry locally and then
> test the services that thing provides.
>
> bastion01 - 2620:52:6:1121:bead:cafe:feed:fed1
> bastion02 - 2620:52:6:1121:bead:cafe:feed:fed2
>
> For these if you are in a sysadmin group, you should be able to ssh to
> them.
>
> ns01      - 2620:52:6:1121:bead:cafe:feed:fed3
> ns03      - 2620:52:6:1121:bead:cafe:feed:fed4
>
> For these you should be able to dig/host at them for fedoraproject.org
> domain and get a reply. (No /etc/hosts needed if you pass the address)
>
> proxy01   - 2620:52:6:1121:bead:cafe:feed:fed5
> proxy10   - 2620:52:6:1121:bead:cafe:feed:fed6
>
> For these, it's basically all of our proxy using services.
> So you would add a /etc/hosts entry for say 'koji.fedoraproject.org' and
> confirm that the site loads as expected, etc. This is a bunch of
> apps/sites, but if one works they all should.
>
> download01 -2620:52:6:1121:bead:cafe:feed:fed7
> download02 -2620:52:6:1121:bead:cafe:feed:fed8
> download03 -2620:52:6:1121:bead:cafe:feed:fed9
> download04 -2620:52:6:1121:bead:cafe:feed:fe10
> download05 -2620:52:6:1121:bead:cafe:feed:fe11
>
> For these you should be able to add a /etc/hosts entry and hit them via
> browser or rsync
>
> pkgs01 - 2620:52:6:1141:bead:cafe:feed:fed1
>
> This one needs you to be a packager and see that you can pull/push git
> via ssh.
>
> proxy01.stg - 2620:52:6:1131:bead:cafe:feed:fed1
> proxy02.stg - 2620:52:6:1131:bead:cafe:feed:fed2
>
> For these just like the prod proxies above, but sites are
> .stg.fedoraproject.org, ie, 'koji.stg.fedoraproject.org'.
>
> If any ipv6 enabled folks could test and let me know if there's things
> not working that would be great.
>
> Thanks in advance.
>
> kevin
> --
> _______________________________________________
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
-- 
_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to