Skip to content

About

IPv4 to IPv6 TCP gateway using Nginx TLS SNI passthrough. Allows IPv4-only clients to access IPv6-only services without terminating SSL.

Resources

Stars

1 star

Watchers

1 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

IPv4 to IPv6 Nginx Bridge

Purpose

This project provides an IPv4-to-IPv6 bridge using Nginx.

It allows IPv4-only clients to reach IPv6-only services.

  • IPv6 clients connect directly using the AAAA DNS record.
  • IPv4-only clients connect to this server using the A DNS record, and Nginx forwards the TLS connection to the IPv6 backend.

Nginx works as a TCP TLS passthrough proxy using SNI (ssl_preread).

Ports

Port Protocol Usage
443 TCP TLS passthrough proxy

Allowed domains

The list of domains allowed through the bridge is configured in:

nginx/conf.d/v4-frontend.conf

Edit this file to add or remove allowed domains.

Example:

.mirkohubtv.it       $ssl_preread_server_name;
.itzmirko.it         $ssl_preread_server_name;
.mrk.re              $ssl_preread_server_name;
.02012006.xyz        $ssl_preread_server_name;

After changing the domain list, restart Nginx:

docker compose restart frontend

Notes

  • Nginx does not terminate SSL/TLS.
  • Certificates are handled by the IPv6 backend server.
  • Only domains listed in v4-frontend.conf are forwarded.

About

IPv4 to IPv6 TCP gateway using Nginx TLS SNI passthrough. Allows IPv4-only clients to access IPv6-only services without terminating SSL.

Resources

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Contributors