This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
configuration:ipv6-wan-overview [2021/11/18 14:37] – [General] dodenhoeft | configuration:ipv6-support [2022/07/15 05:34] (current) – [Table] klueppel | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== IPv6 Support ====== | ====== IPv6 Support ====== | ||
+ | With Software version [[ftp:// | ||
==== General==== | ==== General==== | ||
- | <WRAP center round tip 75%> | ||
- | With Software version [[ftp:// | ||
- | </ | ||
- | One of the major difference in the IPv6 address concept is the fact it has fully developed address scopes. It's mainly divided into two actually sets of scope Unicast addresses and multicast addresses. Each main scopes are segemented into sub scopes. | ||
- | |||
- | == IPv6 Unitcast scopes == | ||
- | * **Global** (supported) | ||
- | * Site-Local | ||
- | * Link-Local | ||
- | * Interface-Local | ||
+ | Netmodule device only support global scope addresses, which basically means WAN/WWAN interfaces can connect to existing IPv6 infrastructure and are also useable in VPN Tunnel structures. | ||
- | Netmodule device only support global scope addresses, which basically means WAN/WWAN interfaces can connect to existing IPv6 infrastructure and are also useable in VPN Tunnel structures. | + | <WRAP center round important |
- | <WRAP center round important | + | Please notice as well as in IPv4, providers still blocking incoming connections on the boarder gateway in their IPv6 network. For this reason it not set and done to have a " |
- | Please notice as well as in ipv4, providers still blocking incoming connections on the boarder gateway in their network. For this reason it not set and done to have a " | + | |
</ | </ | ||
- | |||
+ | === DualStack Mode=== | ||
+ | The dualstack implementation provides complete ipv4 and ipv6 protocol stack and allows parallel operation on the same network interface. It has been integrated as " | ||
==== Provider knowledge ==== | ==== Provider knowledge ==== | ||
- | {{tablelayout? | + | {{tablelayout? |
- | ^ Telekom | + | ^ Telekom |
- | | **APN** | + | | **APN** |
- | | **Auth** | + | | **Auth** |
- | | **user** | + | | **user** |
- | | **Password** | + | | **Password** |
Telekom has no available ipv6 DNS server address, which will automatically be assigned to the ipv6 client. You need to define public [[https:// | Telekom has no available ipv6 DNS server address, which will automatically be assigned to the ipv6 client. You need to define public [[https:// | ||
- | == Recommonded IPv6 DNS server == | + | === Recommonded IPv6 DNS server |
- | * 2a05: | + | * 2a05: |
+ | * 2a05: | ||
+ | * 2620:fe::fe - Germany - quad9 - https:// | ||
+ | * 2620: | ||
* 2a01: | * 2a01: | ||
* 2001: | * 2001: | ||
Line 60: | Line 54: | ||
{{: | {{: | ||
===2. define ipv6 APN=== | ===2. define ipv6 APN=== | ||
- | In this example we are using are SIM Card by " | + | In this example we are using a SIM Card by " |
{{: | {{: | ||
- | It is possbile | + | After the setting has been applied the interface |