Hello,
My name is Jonás and I manage the servers of a university.
We are having problems with the fedora repositories from two servers: 193.145.120.40 and 193.145.120.80.
It appears that access has been closed.
nsa06:/home/adminstic# dnf repoinfo epel Última comprobación de caducidad de metadatos hecha hace 0:00:23, el vie 07 jun 2024 13:53:27. Id-Repositorio : epel Nombre-Repositorio : Extra Packages for 9 - x86_64 Estado-Repositorio : habilitado Versión-Repositorio : 1717633827 Repositorio-actualizado : jue 06 jun 2024 01:31:20 Paquetes-Repositorio : 21.557 Paquetes-disponibles-Repositorio: 21.557 Tamaño-Repositorio : 18 G Repositorios-espejos : https://mirrors.fedoraproject.org/mirrorlist?repo=epel-9&arch=x86_64 Repositorio-baseurl : http://mirrorrpm.stic.ull.es/mrepo/epel/9/ Finalización-Repostorio : 172.800 segundo(s) (último: vie 07 jun 2024 09:53:03) Nombre de fichero-Repositorio : /etc/yum.repos.d/epel.repo
nsa06:/home/adminstic# nslookup mirrors.fedoraproject.org Server: 127.0.0.1 Address: 127.0.0.1#53
Non-authoritative answer: mirrors.fedoraproject.org canonical name = wildcard.fedoraproject.org. Name: wildcard.fedoraproject.org Address: 38.145.60.21 Name: wildcard.fedoraproject.org Address: 152.19.134.142 Name: wildcard.fedoraproject.org Address: 185.141.165.254 Name: wildcard.fedoraproject.org Address: 18.159.254.57 Name: wildcard.fedoraproject.org Address: 85.236.55.6 Name: wildcard.fedoraproject.org Address: 18.133.140.134 Name: wildcard.fedoraproject.org Address: 152.19.134.198 Name: wildcard.fedoraproject.org Address: 18.192.40.85 Name: wildcard.fedoraproject.org Address: 38.145.60.20 Name: wildcard.fedoraproject.org Address: 2a05:d014:10:7803:f774:4d7c:e277:a457 Name: wildcard.fedoraproject.org Address: 2605:bc80:3010:600:dead:beef:cafe:fed9 Name: wildcard.fedoraproject.org Address: 2a05:d01c:c6a:cc01:269:da52:9ae1:43e6 Name: wildcard.fedoraproject.org Address: 2600:2701:4000:5211:dead:beef:fe:fed3 Name: wildcard.fedoraproject.org Address: 2604:1580:fe00:0:dead:beef:cafe:fed1 Name: wildcard.fedoraproject.org Address: 2001:4178:2:1269::fed2
(193.145.120.80):/home/adminstic# telnet 152.19.134.142 443 Trying 152.19.134.142...
(193.145.120.40):/home/adminstic# telnet 152.19.134.142 443 Trying 152.19.134.142...
From other servers we have no problems.
glpi01:/home/adminstic# telnet 152.19.134.142 443
Trying 152.19.134.142...
Connected to 152.19.134.142.
Escape character is '^]'.
Thanks in advance.
Metadata Update from @zlopez: - Issue tagged with: Needs investigation
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review)
It's indeed working from other places :
>/dev/tcp/152.19.134.142/443 && echo "working !" working !
Can that be a routing issue between your servers and these two servers ? (hosted by University of North Carolina a Chapel Hill (UNC-1)
In the past this is due to the network firewalls at UNC/Ibiblio getting upgraded and the traffic getting blocked. Normally this either passes in a day or two, or a ticket needs to be opened with Ibiblio to see if they can clear out the traffic block. A traceroute from the affected servers would be useful because it can show if you are getting blocked even further up the stream
traceroute 152.19.132.142 traceroute -P tcp -p 443 152.19.132.142
Also your above thing noted 152.19.132.142 twice, did you mean 152.19.134.198 for the second one?
and yeah, ping/traceroute might be helpful.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
It is ALREADY resolved. It was a misconfiguration in the firewall. The return of traffic was not enabled.
Thanks, the case could be closed.
Metadata Update from @jregueir: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.