FreshTomato Wiki

User Tools

Site Tools

Trace:
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/10/05 00:06] – [IPT] -Change sentence order hogwildbasic-static [2024/11/27 00:14] (current) – [Static ARP] -formatting, condense hogwild
Line 33: Line 33:
  \\  \\
  
-{{::basic-dhcp_reservation-2024.1.png?909}}\\ \\  \\+{{::basic-dhcp_reservation-2024.1.png?833}}\\ \\  \\
  
  
Line 53: Line 53:
  \\  \\
  
-  * //"static DHCP assignment"// in DD-WRT,+  * //"static DHCP assignment"// in DD-WRT.
  
-  * "//fixed-address"// in the Linux dhcp daemon (dhcpd) documentation+  * "//fixed-address"// in the Linux dhcp daemon (dhcpd) documentation.
  
-  * //"Address Reservation"// by Netgear+  * //"Address Reservation"// by Netgear.
  
-  * Either// "DHCP Reservation" //or "//Static DHCP"// by Cisco/Linksys+  * //"DHCP Reservation" //or "//Static DHCP"// by Cisco/Linksys.
  
-  * //"IP address reservation"// or "//MAC/IP address binding"// by other router vendors.+  * //"IP address reservation"// or "//MAC/IP address binding"// \\ by other vendors.
  
  \\  \\
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 122: Line 128:
 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.
  
  \\  \\
Line 135: Line 141:
 **Ignore DHCP Requests from unknown devices:** **Ignore DHCP Requests from unknown devices:**
  
-Enabling this will ensure FreshTomato won't offer a DHCP lease to any DHCP requests from unlisted MAC addresses/Hostnames. A MAC address is considered unknown when there is no [[dhcp_reservation|DHCP Reservation]] for it. Again, this won't apply to a client device configured with a (true) Static IP. By default, it will still be allowed on the network, unless further measures are taken.+Enabling this ensures FreshTomato won't offer a DHCP lease to any requests from unlisted MAC addresses/Hostnames. A MAC address is considered unknown when there's no [[dhcp_reservation|DHCP Reservation]] for it. Again, this won't apply to a client configured with a (true) Static IP. By default, it will still be allowed on the network, unless further measures are taken.
  
 The //Ignore DHCP Requests from unknown devices// function only works for devices in subnets with netmask 255.255.255.0 (previously called “Class C” subnets). The //Ignore DHCP Requests from unknown devices// function only works for devices in subnets with netmask 255.255.255.0 (previously called “Class C” subnets).
  
- \\ {{::dhcp_reservation-options-2022.6.jpg?611}}\\+ \\ {{::dhcp_reservation-options-2022.6.jpg?529}}\\
  
  \\  \\
basic-static.1728083212.txt.gz · Last modified: by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki