Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
AWS re:Postre:Post

ALB, adding IPv6 support - no traffic arrives at target instances

0

TLDR; do xLB support IPv6-to-IPv4 NAT ? Or only forward incoming IPvX traffic to matching IPvX target IPs ?

I have a standard working, IPv4 setup with a bunch of EC2 behind a ALB that also terminates our TLS.

I'd like to accept incoming IPv6 traffic. I've added IPv6 to the subnets, migrated the LB to duel stack and updated the DNS with AAAA records, then updated the various security groups.

But when I use https://ready.chair6.net/ to send IPv6 only traffic, nothing arrives at the target EC2s.

So I am wondering if the ALB doesn't to 6-to-4 translation, and so I would need to add IPv6 IPs to all the target EC2s and then route to our app from there ?

Argomenti
ComputazionaliNetworking e distribuzione di contenuti
Tag
Amazon EC2Equilibratore di carico elasticoEquilibratore di carico applicazioniIPv6
Lingua
English
Tom
posta 10 mesi fa302 visualizzazioni
1 Risposta
1

Hello.
EC2 should have no problem with IPv4.
You should be able to confirm that the ALB health check and other checks are successful.

profile picture
ESPERTO
Riku_Kobayashi
con risposta 10 mesi fa
profile picture
ESPERTO
Gary Mclean
verificato 10 mesi fa
  • Riku_Kobayashi ESPERTO
    10 mesi fa

    Access was confirmed on EC2 with IPv6 disabled and duel stack in ALB.

    [root@ip-10-0-0-58 ~]# curl -v test-xxxxxxxx.ap-northeast-1.elb.amazonaws.com
*   Trying [2406:da14:77f:8a01:xxxx:xxxx:xxxx:xxxx]:80...
* Connected to test-xxxxxx.ap-northeast-1.elb.amazonaws.com (2406:da14:77f:8a01:xxxx:xxxx:xxxx:xxxx) port 80 (#0)
> GET / HTTP/1.1
> Host: test-xxxxxx.ap-northeast-1.elb.amazonaws.com
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Tue, 08 Aug 2023 08:44:45 GMT
< Content-Type: text/html; charset=UTF-8
< Content-Length: 5
< Connection: keep-alive
< Server: Apache/2.4.56 (Amazon Linux)
< Last-Modified: Tue, 08 Aug 2023 08:33:09 GMT
< ETag: "5-60265367eb799"
< Accept-Ranges: bytes
<
test
* Connection #0 to host test-xxxxxx.ap-northeast-1.elb.amazonaws.com left intact

    The access log confirms that communication between ALB and EC2 is over IPv4.

    [root@ip-10-0-0-239 ~]# tail -f /var/log/httpd/access_log
10.0.0.75 - - [08/Aug/2023:08:44:45 +0000] "GET / HTTP/1.1" 200 5 "-" "curl/8.0.1"
10.0.0.166 - - [08/Aug/2023:08:45:07 +0000] "GET / HTTP/1.1" 200 5 "-" "ELB-HealthChecker/2.0"
10.0.0.75 - - [08/Aug/2023:08:45:13 +0000] "GET / HTTP/1.1" 200 5 "-" "ELB-HealthChecker/2.0"
10.0.0.166 - - [08/Aug/2023:08:45:37 +0000] "GET / HTTP/1.1" 200 5 "-" "ELB-HealthChecker/2.0"
10.0.0.75 - - [08/Aug/2023:08:45:43 +0000] "GET / HTTP/1.1" 200 5 "-" "ELB-HealthChecker/2.0"

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente