This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
advanced-dhcpdns [2023/06/10 01:32] – [DHCP Client (WAN)] -condense hogwild | advanced-dhcpdns [2023/08/05 19:13] (current) – [DHCP Client (WAN)] -condense hogwild | ||
---|---|---|---|
Line 50: | Line 50: | ||
\\ | \\ | ||
- | **Upstream resolvers: | + | **Upstream resolvers: |
**Priority: | **Priority: | ||
- | * Strict-Order - Stubby is tried first, but if it experiences | + | * Strict-Order - Stubby is tried first, but if issues |
- | * No-Resolv - If Stubby fails or has issues, there will be no fallback to other DNS resolution methods | + | * No-Resolv - If Stubby fails or has issues, there will be no fallback to other DNS resolution methods. |
- | * None - This adds stubby | + | * None - This adds Stubby |
\\ | \\ | ||
Line 66: | Line 66: | ||
**Force TLS1.3: | **Force TLS1.3: | ||
- | **WINS (for DHCP):** Here you specify the IP address of a WINS Server | + | **WINS (for DHCP):** Here, specify the IP address of a WINS Server |
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. | 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. | ||
Line 74: | Line 74: | ||
**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' | **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' | ||
- | The extra bytes appeared to be entirely padding, and therefore unnecessary. | + | The extra bytes were entirely padding, and therefore, unnecessary. |
Line 103: | Line 103: | ||
\\ | \\ | ||
- | **Solve .onion using Tor** This option | + | **Solve .onion using Tor:** If Tor is enabled, this option |
- | FreshTomato has a built-in Tor client. For more information about this, see the TOR | + | FreshTomato has a built-in Tor client. For more information about this, see the [[advanced-tor|TOR]] page. |
**Maximum active DHCP leases:** Sets the maximum allowed active DHCP leases at one time. (Default: 255). | **Maximum active DHCP leases:** Sets the maximum allowed active DHCP leases at one time. (Default: 255). | ||
Line 111: | Line 111: | ||
**Static lease time:** Sets the absolute maximum valid time for any DHCP lease. | **Static lease time:** Sets the absolute maximum valid time for any DHCP lease. | ||
- | * Same as Normal Lease Time\\ Static lease time remains | + | * Same as Normal Lease Time\\ Static lease time is the same as normal (1440 minute) lease time. (Default.) |
* Infinite\\ Static lease time is infinity | * Infinite\\ Static lease time is infinity | ||
* Custom\\ This setting allows you to enter a custom Static DHCP lease time. | * Custom\\ This setting allows you to enter a custom Static DHCP lease time. | ||
- | To retain leases after rebooting the router, please see this [[retain_dhcp_lease_info_after_a_reboot|HOWTO]] for additional information on non-volatile | + | To retain leases after rebooting the router, please see this [[retain_dhcp_lease_info_after_a_reboot|HOWTO]] for additional information on non-volatile |
- | **Announce IPv6 on LAN (SLAAC): **Enabling this turns on router advertisements for IPv6 //Stateless Address Autoconfiguration | + | **Announce IPv6 on LAN (SLAAC): **Enabling this turns on router advertisements for IPv6 // |
- The client sends out an RS (router solicitation) ICMP packet. | - The client sends out an RS (router solicitation) ICMP packet. | ||
- The nearest router responds with an RA (router advertisement) packet. | - The nearest router responds with an RA (router advertisement) packet. | ||
- | - The client uses the IPv6 prefix from the RA packet as the first 64 bits of its address. It then derives the last 64 bits of its address using the EUI-64 process or a randomization algorithm. | + | - The client uses the IPv6 prefix from the RA packet as the first 64 bits of its address. It then derives the last 64 bits \\ of its address using the EUI-64 process or a randomization algorithm. |
**Announce IPv6 on LAN (DHCP): | **Announce IPv6 on LAN (DHCP): | ||
Line 131: | Line 131: | ||
**Mute dhcpv4 logging: | **Mute dhcpv4 logging: | ||
- | **Mute dhcpv6 logging: **Enabling this stops FreshTomato from logging IPv6 dhcp activity. (Default: Disabled). | + | **Mute dhcpv6 logging: |
**Mute RA logging: | **Mute RA logging: | ||
Line 139: | Line 139: | ||
{{: | {{: | ||
- | **Prevent client auto DoH**: Modern browsers | + | **Prevent client auto DoH**: |
- | **Enable DNS Rebind protection**: DNS rebind | + | **Enable DNS Rebind protection:** DNS rebind is a type of malicious attack against domain resolution. |
- | **Forward local domain queries to the upstream DNS**: Enabling this forwards local domains to the router' | + | **Forward local domain queries to the upstream DNS:** Enabling this forwards local domains to the router' |
- | **Enable multicast DNS:** Checking this enables an implementation of Avahi mDNS. Avahi is system that enables programs to publish and discover services and hosts running on a LAN. It is a zero-configuration implementation which includes multicast service discovery via the mDNS/DNS-SD protocol suite. " | + | **Enable multicast DNS: |
+ | |||
+ | Avahi is system that enables programs to publish and discover services and hosts running on a LAN. It is a zero-configuration implementation which includes multicast service discovery via the mDNS/DNS-SD protocol suite. " | ||
**Enable reflector** FIXME | **Enable reflector** FIXME | ||
- | **Custom configuration: | + | **Custom configuration: |
Line 158: | Line 160: | ||
**TFTP root path**: Text entered here defines where TFTP root is located in the filesystem. | **TFTP root path**: Text entered here defines where TFTP root is located in the filesystem. | ||
- | **PXE on LANx (brx)**: Enbables PXE (Pre Boot eXecution Environment) on one or more bridges. PXE was designed for diskless clients. A PXE client can obtain an IP address via DHCP and, once obtained, download boot code via a TFTP location. Syslinux is a good example of these principles/ | + | **PXE on LANx (brx)**: Enbables PXE (Pre Boot eXecution Environment) on one or more bridges. PXE was designed for diskless clients. A PXE client can obtain an IP address via DHCP and, once obtained, download boot code via a TFTP location. Syslinux is a good example of this in action. |
- | ===== DHCP / DNS Notes ===== | + | ===== DHCP/DNS/TFTP Notes ===== |
* Do not use results from Cloudflare' | * Do not use results from Cloudflare' |