December 2, 2017


Amazon AWS's EC2 started supporting IPv6 earlier this year. When I spun up my new Debian 9 Stretch instance a few months ago it came with IPv6 support. It started out working just fine. However, after one week, consistently, my instance would always lose its IPv6 route. The host would keep its IP address but any attempt to use ping6 or a traceroute6 would return "network unreachable" and ip -6 route would show no gateway. (I even set accept_ra 1 in the network interfaces configuration, among other things that I tried.) Lots of changes to my configuration yielded no results. Since I can't get a console using EC2 the only way to test would be to make a configuration change, reboot, and then wait a week to see if IPv6 still works. So today I finally just removed my AAAA records.

Comments

Weren't we supposed to run out of ipv6 addresses a year or two ago?
posted at 6:08AM PST on December 5, 2017 by Erik
I meant ipv4 obv. I just got some coffee
posted at 6:09AM PST on December 5, 2017 by Erik

Post Comment

About

Location Seattle, WA
First post September 6, 2004
Total posts 5,958

Tags

  1. 1,798
  2. 694
  3. 632
  4. 585
  5. 553
  6. 497
  7. 268
  8. 193
  9. 192
  10. 139
  11. 131
  12. 106
  13. 104
  14. 86
  15. 78
  16. 70
  17. 58
  18. 57
  19. 41
  20. 26
  21. 1
Load the RSS feed for entries or for comments.