I do not know if this the correct place to post this. Maybe the moderator can move it if it is in the wrong place.
I have over the last weeks started to see problems from one of my FreeBSD 12.2 server hosted at RamNode on their European location. When doing a "pkg upgrade” the terminal often hangs. Doing “pkg -4 upgrade” and it works well. This is something I have seen over the last weeks and not before that.
Looking into it I can se that pkg0.pkt.freebsd.org (2604:1380:2000:9501::50:2) is contacted on port 80. A netstat shows a “SYN_SENT” and no more.
And trying to contact it gives….
Sometimes it works though, but not always. Intermittent problem it is… My IPv6 /64 is within the network operator RouteLabel V.O.F.
My server have no problems whatsoever with IPv6 apart from this. Therefor I can conclude that it is either a routing/network issue between my node and the FreeBSD upgrade server, or maybe a problem in or near the FreeBSD update server. Before posting this, I logged a case at the VPS hosting provider RamNode asking them if they had any ongoing known problems. They have checked.. All green. And as I have no IPv6 problems against anything else, I think they are correct...
Have anyone seen anything similar when doing "pkg upgrade" lately?
Tnx
/Peo
I have over the last weeks started to see problems from one of my FreeBSD 12.2 server hosted at RamNode on their European location. When doing a "pkg upgrade” the terminal often hangs. Doing “pkg -4 upgrade” and it works well. This is something I have seen over the last weeks and not before that.
Looking into it I can se that pkg0.pkt.freebsd.org (2604:1380:2000:9501::50:2) is contacted on port 80. A netstat shows a “SYN_SENT” and no more.
And trying to contact it gives….
Code:
—snip—
19:17:35 huey:~ # telnet -6 2604:1380:2000:9501::50:2 80
Trying 2604:1380:2000:9501::50:2...
telnet: connect to address 2604:1380:2000:9501::50:2: Operation timed out
telnet: Unable to connect to remote host
—snip—
Sometimes it works though, but not always. Intermittent problem it is… My IPv6 /64 is within the network operator RouteLabel V.O.F.
My server have no problems whatsoever with IPv6 apart from this. Therefor I can conclude that it is either a routing/network issue between my node and the FreeBSD upgrade server, or maybe a problem in or near the FreeBSD update server. Before posting this, I logged a case at the VPS hosting provider RamNode asking them if they had any ongoing known problems. They have checked.. All green. And as I have no IPv6 problems against anything else, I think they are correct...
Have anyone seen anything similar when doing "pkg upgrade" lately?
Tnx
/Peo