FreshTomato Wiki

User Tools

Site Tools

Trace: • wireless_filter • tools-qr • remote_upgrade_poc • forward-dmz • basic-ident • basic-static • admin-log • admin-sched • bwm-monthly • entware_installation_usage
basic-static

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
basic-static [2024/11/27 00:10] – [Inconsistent Terminology] -Formatting, condense hogwildbasic-static [2025/11/18 05:56] (current) – [Static ARP] -Remove monospace tag from MAC address example hogwild
Line 6: Line 6:
 ===== Basic Concepts ===== ===== Basic Concepts =====
  
-Since release 2020.8, what was called "Static DHCP" is now more accurately named "DHCP Reservation". Please see "Inconsistent Terminology" in this section for clarification and differentiation of terminology.+Since r2020.8, what was called "Static DHCP" is now more accurately named "DHCP Reservation". Please see "Inconsistent Terminology" in this section for clarification and differentiation of terminology.
  
 DHCP Reservation is a simple way to ensure that FreshTomato offers certain client devices the same IP address each time they request a lease. Simply enter the MAC address for a client device (found in [[status-devices|Device List]]), into the **MAC Address** field, enter the **IP Address** (and optionally, **Hostname**) you want to assign into the appropriate fields and click "Save". DHCP Reservation is a simple way to ensure that FreshTomato offers certain client devices the same IP address each time they request a lease. Simply enter the MAC address for a client device (found in [[status-devices|Device List]]), into the **MAC Address** field, enter the **IP Address** (and optionally, **Hostname**) you want to assign into the appropriate fields and click "Save".
Line 94: Line 94:
  \\  \\
  
-**MAC Address:  **Here, enter the MAC Address you wish to bind.+**MAC Address:  **here, enter the MAC Address you wish to bind.
  
  \\  \\
  
-**Bound To:  **Enables Static ARP binding for the IP - MAC mapping. It adds a Static ARP entry for it in FreshTomato's ARP table, using data found in the DHCP Reservation table. (Default: Disabled).+**Bound To:  **enables Static ARP binding for the IP - MAC mapping. 
 + 
 +This adds a Static ARP entry for it in FreshTomato's ARP table, using data found in the DHCP Reservation table. 
 + 
 +(Default: Disabled).
  
  \\  \\
  
-**IP Address:**  The (optional) address to bind to the MAC address entered. If you leave this empty, it will link only a Hostname to a MAC address, allowing normal DHCP operations. This "lack of IP" can be helpful for devices that don't automatically have a Hostname assigned, but for which you still prefer a dynamic IP allocation.+**IP Address:** the (optional) address to bind to the MAC address entered. 
 + 
 +Leaving this empty will link only a Hostname to a MAC address, allowing normal DHCP operations. This "lack of IP" can be helpful for devices that don't automatically have a Hostname assigned, but for which you still prefer a dynamic IP allocation.
  
  \\  \\
  
-**IP Traffic:** This enables IP Traffic Monitoring for the mapped MAC Address/IP/Hostname combination.+**IP Traffic:** enables IP Traffic Monitoring for the mapped MAC Address/IP/Hostname combination.
  
 (Default: Disabled). (Default: Disabled).
Line 112: Line 118:
  \\  \\
  
-**Hostname:**  This optional DHCP Client Identifier will be mapped to the client device.+**Hostname:**  an optional DHCP Client Identifier to be mapped to the client device.
  
-It is an arbitrary human-readable nickname to make it easier to identify the device on the network.+This is an arbitrary human-readable nickname to make it easier to identify the device on the network.
  
 Traditionally, devices were identified within DHCP by a //hardware type// code and //a client hardware (MAC) address//. Later, the optional Hostname field allowed more freedom when mapping device names in DHCP. Ironically, many people still used the //hardware type// followed by the //client hardware address// as a Hostname. Traditionally, devices were identified within DHCP by a //hardware type// code and //a client hardware (MAC) address//. Later, the optional Hostname field allowed more freedom when mapping device names in DHCP. Ironically, many people still used the //hardware type// followed by the //client hardware address// as a Hostname.
Line 120: Line 126:
  \\  \\
  
-For example: "''01 00 01 02 a0 bc d3''"). However, you can use whatever (valid) naming scheme you wish.+For example: "01 00 01 02 a0 bc d3". However, you can use whatever (valid) naming scheme you wish.
  
-Often, the client DNS/Netbios name is used as the Hostname. To avoid conflicts, every client must have a unique Hostname on the broadcast domain.+Often, the client DNS/Netbios name is used as the Hostname. Every client must have a unique Hostname on the broadcast domain to avoid conflicts.
  
  \\  \\
basic-static.1732666247.txt.gz · Last modified: by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki