Networking weirdness after distupgrade => 4.4

[Pumpapa]

I just did a distupgrade to 4.4-13/7ea56165 which seems to work mostly OK except for this weirdness:

'apt-get update' got stuck (on two repositories) on a client, so I tried pinging the same servers from the host. Turns out, some (but not all) external servers are inaccessible some or all of the time.

I tried to ping the repositories from the host, but there, also every now and then one or more IP's are inaccessible from my server (tried them from my local PC but they are up and running).

Also, every now and then my server drops all network connections (broken pipe from my local machine, and proxmox web UI says: connection error every 15 minutes or so

I don't know where to begin to look for this, since at times some IP's and hosts (DNS works ok) are accessible and others are not.

For all clarity: I am unsure if this follows from the distupgrade; I just noticed it after the upgrade.

 

[Richard]

I just did a distupgrade to 4.4-13/7ea56165 which seems to work mostly OK except for this weirdness:

'apt-get update' got stuck (on two repositories) on a client, so I tried pinging the same servers from the host. Turns out, some (but not all) external servers are inaccessible some or all of the time.

I tried to ping the repositories from the host, but there, also every now and then one or more IP's are inaccessible from my server (tried them from my local PC but they are up and running).

Also, every now and then my server drops all network connections (broken pipe from my local machine, and proxmox web UI says: connection error every 15 minutes or so

I don't know where to begin to look for this, since at times some IP's and hosts (DNS works ok) are accessible and others are not.

For all clarity: I am unsure if this follows from the distupgrade; I just noticed it after the upgrade.

Sound simply like a network (configuration) problem. Check routing tables and ip configuration - if repositories (or any other server) cannot be reached despite correct ip settings follow the packets. Take also possibly existing firewall(s) in consideration.