Skip to content

Commit

Permalink
clarify wording for unique hostnames (#219)
Browse files Browse the repository at this point in the history
  • Loading branch information
ab7pa committed Nov 18, 2022
1 parent 25b003d commit 9473084
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion arednGettingStarted/advanced_config.rst
Original file line number Diff line number Diff line change
Expand Up @@ -190,7 +190,7 @@ In ``Direct`` mode the LAN hosts are directly accessible from the mesh since no
DHCP Address Reservations
If your node has its DHCP server enabled, it will automatically provide IP addresses to connected hosts. Look under the **Current DHCP Leases** heading to see the existing hosts and their assigned IP addresses.

.. attention:: The hostnames of computers connected to the mesh at large must be unique. Typically you should prefix your amateur radio callsign to the computer's hostname in order to have the best chance of it being unique on the mesh network.
.. attention:: The hostnames of every device connected to the mesh at large must be unique. It is best practice to prefix your Amateur Radio callsign to the hostname of each of your devices in order to have the best chance of it being unique on the mesh network.

Since DHCP leases are dynamic and can change over time, there may be a reason why a host's assigned IP address should be made permanent. This is especially useful if that host will provide an application, program, or service through your node to the mesh network at large. You can permanently reserve that host's DHCP address by clicking the *Add* button at the right of the row in the *Current DHCP Leases* list. You will see that host now appears in the list under the **DHCP Address Reservations** heading above the list of leases.

Expand Down

0 comments on commit 9473084

Please sign in to comment.