IPv6 not working on Linux EC2 instance

0

New EC2 instance. IPv4 connectivity works fine. Added IPv6 to SecurityGroup, Subnet, and made sure it's enabled on eth0. Linux sees Global IPv6 address in ifconfig. IPv6 routing looks good. (netstat -nr6) ping6 resolves name to IPv6 address, but remote sites do not respond.

SG permits all ICMP ipv6 in, ssh ipv6 in, All ipv6 out inet6 2600:1f16:8cf:d105:2c0f:2059:d33c:c494 prefixlen 128 scopeid 0x0<global>

Thanks

1 Answer
1
Accepted Answer

Hi, when you said "but remote sites do not respond" do you mean ping is not successful? Can you clarity this part please. Do you have:

  1. an Egress Only Internet Gateway set up in your VPC?, and configured it as gateway for ::/0 in the route table?
  2. Any possible Network ACLs permit for incoming and outgoing IPv6 traffic? Within your instance, could you check that an IPv6 default route is set as per the "default via … proto ra": #ip -6 route show
profile pictureAWS
answered a year ago
profile pictureAWS
EXPERT
reviewed a year ago
  • Thanks! My VPC was missing a default IP6 route.

    [ec2-user@amber ~]$ ping6 google.com PING google.com(ord38s29-in-x0e.1e100.net (2607:f8b0:4009:818::200e)) 56 data bytes 64 bytes from ord38s29-in-x0e.1e100.net (2607:f8b0:4009:818::200e): icmp_seq=1 ttl=95 time=17.9 ms 64 bytes from ord38s29-in-x0e.1e100.net (2607:f8b0:4009:818::200e): icmp_seq=2 ttl=95 time=17.8 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 17.889/17.898/17.907/0.009 ms

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions