I have this strange situation that since three days or so all sites under the ipfire.org domain are inaccessble from my home ISP connection.
They just time out and when I ping the domain it redirects to some odd double subdomain which responds to the ping, but doesn’t serve any websites.
Strangely enough on this mobile data connection it still works.
Previously I had similar issues when websites messed up their IPv6 routing, as my home ISP prefers IPv6.
The whole ipfire.org web site is working fine for me right now.
The response I got back to pinging ipfire.org just now was
ping -c4 ipfire.org
PING ipfire.org (81.3.27.38) 56(84) bytes of data.
64 bytes from fw01.ipfire.org (81.3.27.38): icmp_seq=1 ttl=57 time=26.0 ms
64 bytes from fw01.ipfire.org (81.3.27.38): icmp_seq=2 ttl=57 time=56.9 ms
64 bytes from fw01.ipfire.org (81.3.27.38): icmp_seq=3 ttl=57 time=26.2 ms
64 bytes from fw01.ipfire.org (81.3.27.38): icmp_seq=4 ttl=57 time=26.2 ms
--- ipfire.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 26.040/33.832/56.909/13.323 ms
Is 81.3.27.38 the IP you get provided back from running your ping command? If not, try running ping to the ip
ping -c4 81.3.27.38
PING 81.3.27.38 (81.3.27.38) 56(84) bytes of data.
64 bytes from 81.3.27.38: icmp_seq=1 ttl=57 time=26.6 ms
64 bytes from 81.3.27.38: icmp_seq=2 ttl=57 time=25.9 ms
64 bytes from 81.3.27.38: icmp_seq=3 ttl=57 time=27.3 ms
64 bytes from 81.3.27.38: icmp_seq=4 ttl=57 time=26.4 ms
--- 81.3.27.38 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 25.881/26.530/27.251/0.487 ms
What IP do you get from the ping command and what is the odd double subdomain that you are being redirected to?
Which ones are those?
Looks like there is some problem now. However it was all working fine for me 2 hours ago.
@ms will find what the problem is and get the webserver running again.
I just ran an upgrade of the PostgreSQL database that fires it… It is back now…
Yes it is back up and running.
Can the original poster, @povoq, of this thread indicate if this has solved their problem as they were mentioning having their problem for the last three days.
Not solved here.
I am pretty sure it is an IPv6 routing issue on your side.
Pinging ipfire.org or community.ipfire.org on my home ISP connections results in a response from:
fw01.haj.ipfire.org with an IPv6 claimed to be 2001:678:b28:: which looks a bit odd to me, but the ping response seems OK otherwise.
Still no websites at all though.
The site was unreachable to me for a few hours. I could read the forums but not log in and post. All seems to work as intended now.
Same problem with ipfire.org and its subdomains here since a few days, while on holiday in France in different Airbnb homes. Mobile works fine…
Ah, now it seems to be working again.
Only this forum though, the main ipfire.org site still fails.
Edit: and now it is broken again. Maybe I was accidently on mobile connection?
Could you explain more with what you mean by fails?
I can reach the website over IPv6 without any issues.
It times out.
And the above test with ping seems to show that IPv6 connection get redirected to a wrong server.
I would suggest one of those “Is it down or just me” sites to see if you can triangulate where the outage stems from.
That is of limited use if it is a specific IPv6 routing issue as these sites will always fall back on IPv4.
Anyways, something changed today and now it seems to intermittently work.
Maybe you could actually show the full result of the ping test.
Can’t type that off on my mobile, but there is nothing else relevant in a ping than what I wrote above. I assume you don’t need the ping time?
However, did you change something this morning or not? Because previously it didn’t work at all, and now it is working at least temporarily.
I haven’t changed anything as I am not involved at all in the IPFire infrastructure.
@ms needs to respond on that.
In one of the IPFire blogs the IPv6 IP you referenced
2001:678:b28::
is the one that www.ipfire.org resolves to.
At home with WiFI the sites www.ipfire.org and community.ipfire.org works OK on my phone, but when I use mobile data with my carrier the sites do not work (but other sites work OK, like CNN etc). I tried to ping community.ipfire.org from phone and do a traceroute on www.ipfire.org
Yes, but I suspect the reverse-proxy was routing IPv6 requests differently from IPv4 requests, resulting in a redirection to a non-functional sub domain.
But anyways at least here it is currently working again. Maybe some mess-up at the hosting company?
