Differences

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

--- advanced-dhcpdns [2023/06/10 01:27] – [DHCP Client (WAN)] -formatting hogwild
+++ advanced-dhcpdns [2023/06/10 01:32] – [DHCP Client (WAN)] -condense hogwild
@@ Line 57: / Line 57: @@
   * No-Resolv - If Stubby fails or has issues, there will be no fallback to other DNS resolution methods anywhere.
   * None - This adds stubby as a resolution method for dnsmasq. This alone does not guarantee.
+ \\
 **Local Port:** This is the port number on which Stubby serves clients. Dnsmasq will be the only client for Stubby, \\ but it is dnsmasq that serves clients.
@@ Line 64: / Line 66: @@
 **Force TLS1.3:**  Enforces usage of the latest TLS version for encryption. This must be supported upstream.
-**WINS (for DHCP):** Here you specify the IP address of a WINS Server that will be given to DHCP clients. This does NOT \\ actually enable the WINS service. FreshTomato's WINS Server function is enabled on the //[[:nas-samba|File Sharing]]// menu.
+**WINS (for DHCP):** Here you specify the IP address of a WINS Server that will be given to DHCP clients. This does NOT actually enable the WINS service. FreshTomato's WINS Server function is enabled on the [[:nas-samba|File Sharing]] menu.
-Windows Internet Name Service (WINS) is a legacy name registration and resolution service that maps computer NetBIOS names to IP addresses. Officially, WINS is outdated and largely obsolete. DNS was supposed to have replaced WINS functionality. However, Microsoft has not officially deprecated WINS. WINS may still be necessary for some Windows LAN browsing functions, especially on old Windows versions.
+Windows Internet Name Service (WINS) is a legacy name resolution service that maps NetBIOS names to IP addresses. Officially, it's outdated and largely obsolete. DNS was supposed to replace WINS functionality. However, Microsoft has not officially deprecated WINS. WINS may still be necessary for some Windows LAN browsing functions on old Windows versions.
 **DHCPC Options:**  In this field you can enter custom configuration settings for the dhcp client.
-**Reduce Packet Size:** //udhcpc// (the DHCP client FreshTomato uses to obtain a WAN IP address) has a problem. It has a DHCP discovery packet size 590 bytes long. However, DHCP relay servers can only handle DHCP discovery packets up to 576 bytes. If there are DHCP relay servers between your FreshTomato router and your Internet provider's DHCP server, FreshTomato might fail to acquire a DHCP lease on the WAN interface.  The extra bytes appeared to be entirely padding, and not necessary.  FreshTomato developers eliminated the padding, which reduced udhcpc's DHCP discovery packet size to only 331 bytes. This 331 byte size eventually became FreshTomato's default setting. This way, udhcpc can successfully obtain a DHCP lease from a provider which might have DHCP relays. However, some users may not be able to obtain a WAN IP address unless they disable this feature. (Default: Enabled). <del>Please note this has now been removed from the FT GUI.</del>
+**Reduce Packet Size:** //udhcpc// (the DHCP client FreshTomato uses to obtain a WAN IP address) has a problem. It has a DHCP discovery packet size 590 bytes long. However, DHCP relay servers can only handle DHCP discovery packets up to 576 bytes. If there are DHCP relay servers between your FreshTomato router and your Internet provider's DHCP server, FreshTomato might fail to acquire a DHCP lease on the WAN interface.
+The extra bytes appeared to be entirely padding, and therefore unnecessary.  FreshTomato developers eliminated the padding, reducing udhcpc's DHCP discovery packet size to 331 bytes. This 331 byte size eventually became the default setting. As a result, udhcpc can successfully obtain a DHCP lease from an ISP with DHCP relays. However, some users may not be able to obtain a WAN IP address unless they disable this feature. (Default: Enabled).

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools