1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Bearing in mind that the AWS services do not have access to your instance OS while it is running: So if the OS (Debian) is dropping the IPv6 configuration then the changes are that it is something in Debian that is doing this.
However, given that it doesn't recover until after a reboot there might be something on the AWS side to look at.
Best advice: Raise a support case and they can confirm whether there is an issue on the AWS side or not.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 ans
Could you expand a little on "...and then disappears". What do you mean by that? What disappears from where?
When I give the command ifconfig I don't see ipv6 anymore, I can't ping any ipv6 address anymore and I don't even receive ping. There are several solutions for this, but not debian 10 the ipv6 always after a few minutes or hours it just disappears from the ens5 interface.
aws folks might as well help! Thanks e regards