Differences

This shows you the differences between two versions of the page.

--- basic-ipv6 [2024/11/06 23:56] – [IPv6 (Configuration)] -Condense, formatting hogwild
+++ basic-ipv6 [2025/01/28 12:39] (current) – pedro
@@ Line 46: / Line 46: @@
  \\
-Other options exist in this mode. If the prefix is smaller than 64, and bridges 1 through 3 exist, you can enable subnets for those bridges, as below.
+Other options exist in this mode. If the prefix is smaller than 64, and bridges 1 through 3 exist, you can enable subnets for those bridges.
- \\ {{::ft_basic_ipv6_dhcpv6_02-2020.7.jpg?731}}
+See the image below for details: \\ \\ \\ {{::ft_basic_ipv6_dhcpv6_02-2020.7.jpg?731}}
  \\
@@ Line 56: / Line 56: @@
 [Static IPv6]
-This mode is similar to Static IP mode in IPv4. With this service type, you enter the IP address and other settings into FreshTomato's menus. Your Internet provider gives you the settings.
+This mode is similar to Static IP mode in IPv4. You must enter the IP address and other settings into this menu. Your ISP provides these settings.
  \\
@@ Line 66: / Line 66: @@
 [6to4 Anycast Relay]
-to4 is a transitional protocol for migrating from IPv4 to IPv6.  6to4 acts as a transparent transport layer between IPv6 nodes. It allows IPv6 packets to be transmitted over an IPv4 network, such as the Internet, without requiring you to configure explicit tunnels. 6to4 hosts and networks communicate with native IPv6 networks via Special relay servers, known as "6to4 Anycast Relays".
+to4 is a transitional protocol for migrating from IPv4 to IPv6.  6to4 acts as a transparent transport layer between IPv6 nodes. It allows IPv6 packets to be transmitted over an IPv4 network, such as the Internet, without having to configure explicit tunnels. 6to4 hosts and networks communicate with native IPv6 networks via Special relay servers, known as "6to4 Anycast Relays".
 Note that 6to4 //does not support communication between IPv4-only hosts and IPv6-only hosts.//
@@ Line 94: / Line 94: @@
  \\
-Example Configuration through Tunnelbroker.net
+//Example Configuration through Tunnelbroker.net//
 This example uses tunnelbroker.net to create a standard tunnel.
-  - Login to tunnelbroker.net and click "Create a Regular Tunnel". \\
+ \\
-  - On the "Create New Tunnel" page, enter your router's current IPv4 WAN address \\ into the "IPv4 Endpoint (Your Side)" field. \\
+  - Login to tunnelbroker.net and click "Create a Regular Tunnel". \\  \\
+  - On the "Create New Tunnel" page, enter your router's current IPv4 WAN address \\ into the "IPv4 Endpoint (Your Side)" field. \\  \\
   - Tunnelbroker.net tries to detect your current IPv4 WAN address, and displays it\\ after the words: “You are viewing from:”. If it's correct, copy and paste it into the \\ “IPv4 Endpoint address” field. \\ \\ \\ {{::basic-ipv6-6in4_example-tunnelbroker.net-create_a_new_tunnel_2-redacted.png?467}} \\  \\
     - The bar under IPv4 endpoint should display: "Checking...", then turn green. \\ It should then display: "IP is a potential tunnel endpoint."  An ICMP reachability \\ test passed. If it doesn't, and reports ICMP is blocked to that address, you must \\ go to FreshTomato's Firewall menu, and enable //WAN interfaces respond to ping //\\ //and traceroute//. This will allow FreshTomato to respond to tunnelbroker.net's \\ ICMP test to check\\ its connection to your router.
@@ Line 123: / Line 125: @@
  \\
-  - Select the 6in4 Static Tunnel IPv6 Service Type.
+  - Select the 6in4 Static Tunnel IPv6 Service Type. \\  \\
-  - Copy the Routed /64 address from Tunnel details and paste it in the\\ FreshTomato Assigned/Routed Prefix field.
+  - Copy the Routed /64 address from Tunnel details and paste it in the\\ FreshTomato Assigned/Routed Prefix field. \\  \\
   - Select a Prefix Length of 64. You can sign up for other prefix lengths. \\ \\ \\ {{::basic-ipv6-6in4_example-tunnelbroker.net-tunnel_details-ipv6_tunnelpng-redacted.png?584}} \\  \\  \\
-  - Leave the IPv6 Router LAN Address at the Default. \\
+  - Leave the IPv6 Router LAN Address at the Default. \\  \\
-  - In the first Static DNS field, enter the Anycast IPv6 Caching Nameserver address in Tunnel Details. \\
+  - In the first Static DNS field, enter the Anycast IPv6 Caching Nameserver address in Tunnel Details. \\  \\
-  - In the second Static DNS field, you can (optionally) enter an external DNS server address. \\
+  - In the second Static DNS field, you can (optionally) enter an external DNS server address. \\  \\
-  - If you want clients on your LAN to be able to autoconfigure IPv6 addresses, check that \\ IPv6 Router Advertisements are enabled in [[advanced-dhcpdns|DHCP/DNS/TFTP]]. \\ These configuration options only appear when IPv6 is enabled. \\
+  - If you want clients on your LAN to be able to autoconfigure IPv6 addresses, check that \\ IPv6 Router Advertisements are enabled in [[advanced-dhcpdns|DHCP/DNS/TFTP]]. \\ These configuration options only appear when IPv6 is enabled. \\  \\
-  - From Tunnel Details, copy the Server IP4 address and paste it the Tunnel Remote Endpoint field. \\
+  - From Tunnel Details, copy the Server IP4 address and paste it the Tunnel Remote Endpoint field. \\  \\
-  - From Tunnel Details, copy the Client IPv6 address and paste it the Tunnel Client IPv6 address field. \\
+  - From Tunnel Details, copy the Client IPv6 address and paste it the Tunnel Client IPv6 address field. \\  \\
-  - Leave Tunnel MTU and Tunnel TTL at their defaults. Click Save. \\
+  - Leave Tunnel MTU and Tunnel TTL at their defaults. Click Save. \\  \\
-  - If your IP address is dynamic, must use DDNS to update your "Client IPv4 Address" \\ value automatically when it changes. For an example, see this thread:\\ [[https://www.linksysinfo.org/index.php?threads/setting-up-ipv6-for-he-tunnelbroker.35297/]]
+  - If your IP address is dynamic, you must use DDNS to update the "Client IPv4 Address" automatically when it changes. For an example, see this thread: [[https://www.linksysinfo.org/index.php?threads/setting-up-ipv6-for-he-tunnelbroker.35297/]]
  \\
@@ Line 139: / Line 141: @@
 For more details, see tunnelbroker.net's tutorial for creating tunnels: [[https://ipv6.he.net/presentations.php]] \\   \\ [6rd Relay]
- \\ Fix Me  \\
+ \\ FIXME  \\
  \\   \\ [6rd from DHCPv4 (Option 212)]
-Fix Me.  \\
+ \\ FIXME  \\
  \\   \\ [Other (Manual Configuration) ]
@@ Line 155: / Line 157: @@
 **Debug**
-Checking this sets the Detail level in Logging to the Debug Level. This causes it to log all messages of debug level or higher.\\  \\
+Enabling this sets the Logging Detail level to to Debug Level. All messages of debug level or higher will be logged.\\  \\
  \\  \\ **IPv6 DUID Type**
-Every DHCP client/server has a DHCP Unique Identifier ("DUID"). The DHCP server uses it to identify clients for the selection of configuration parameters.
+Every DHCP client/server has a DHCP Unique Identifier. The DHCP server uses it to identify clients for selection of configuration parameters.
 Options:
@@ Line 166: / Line 168: @@
   * DUID-LLT - uses the LAN MAC address, but in addition, will include \\ time value, and will change on every reboot/reconnection of the WAN interface.
- \\ You can see the DUID type currently in use in the [[status-overview|Overview]] menu.
+ \\ You can see the DUID type currently used in the [[status-overview|Overview]] menu.
 Support for DUID Type started in release 2022.4. Fixed DUID types and custom DUIDS are not supported.
@@ Line 176: / Line 178: @@
  \\
-**Prefix Length**  \\ The network prefix is analogous to an IPv4 subnet mask. It represents the network portion (most significant bits) of the address. The leading bits are identical on all hosts on your assigned network.
+**Prefix Length**  \\ The network prefix is analogous to an IPv4 subnet mask. It represents the network portion (most significant bits) of the address. The leading bits are identical on all assigned network hosts.
 Other options commonly used include 56 bits. (Default: 64).
- \\ **Request PD Only**  \\ This setting should be enabled for ISPs that require only a Prefix Delegation. This is usually PPPoE-authenticated DSL or fiber connections.
+ \\ **Request PD Only**  \\ This setting should be enabled for ISPs that require only a Prefix Delegation. This is usually PPPoE-authenticated DSL/fiber connections.
  \\ **Do not allow PD/Address release**
-Enabling this prevents DHCP6 clients from sending a release message to the ISP when disconnecting. With this set, the client is more likely to receive the same allocation on subsequent requests.
+Enabling this prevents disconnecting DHCP6 clients disconnecting from the ISP from sending a release message. Enabling it makes the client more likely to receive the same allocation on subsequent requests. Support for this option started in release 2022.4.
-Support for this option started in release 2022.4.
  \\
@@ Line 194: / Line 194: @@
 See also [[https://www.linksysinfo.org/index.php?threads/ipv6-and-comcast.38006/|Linksysinfo.org: IPv6 and Comcast]]
- \\ **Static DNS**  \\ FreshTomato users can add/specify DNS server addresses. For example, if you are using DHCPv6 with PD on the ISP German Telekom, DHCP will automatically provide two IPv6 DNS server addresses. However, you can still manually add static DNS addresses if you wish.  \\  \\
+ \\ **Static DNS**  \\ FreshTomato users can specify DNS server addresses. For example, if you are using DHCPv6 with PD on the ISP German Telekom, DHCP will automatically provide two IPv6 DNS server addresses. However, you can still manually add static DNS addresses if you wish.  \\
 Examples:
@@ Line 207: / Line 207: @@
 Options:  \\
-  * WAN - Tomato will accept IPv6 router advertisements on the WAN interface.
+  * WAN - FreshTomato will accept IPv6 router advertisements \\ on the WAN interface.
-  * LAN - Tomato will accept IPv6 router advertisements on the LAN interface.
+  * LAN - FreshTomato will accept IPv6 router advertisements \\ on the LAN interface.
  \\

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools