Repository :
http://git.fedorahosted.org/cgit/docs/fedora-cookbook.git
On branch : master
---------------------------------------------------------------
commit cdd653a70d6bc05f2c95a0c07152a0568bfad052
Author: Glen Rundblom <grundblom(a)fedoraproject.org>
Date: Tue Jul 21 22:12:59 2015 -0500
Brainstorming and creating networking page, more to follow but generating cobulk
content to edit later
---------------------------------------------------------------
en-US/Networking.xml | 18 +++++++++++++++---
1 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/en-US/Networking.xml b/en-US/Networking.xml
index 53e962b..b38cbff 100644
--- a/en-US/Networking.xml
+++ b/en-US/Networking.xml
@@ -4,6 +4,18 @@
%BOOK_ENTITIES;
]>
<chapter id="Networking">
-<title>Networking</title>
-
-<para /> </chapter>
+ <title>Networking</title>
+ <section id="DHCP_Static">
+ <title>DHCP VS Static IP assignment</title>
+ <para>
+ DHCP: Dynamic Host protocol: The DHCP server assigns an IP address to the computer.
This can be random within the DHCP server's address pool.
+ Or it can be a reservation. Having a reservation for a client can effectively mimic
a static IP. This will give the client the same IP address over and over, without having
to manually configure the IP manually on the host.
+ The advantage to this is less manual configuration on the host
+ </para>
+ <para>
+ Static: This way is when you manually assign an IP address into the computer. You
may need to do this on a network that has no DHCP server, or the DHCP server will not
allow you to have reservations for your computer.
+ Manually assigning a static IP address has the benifit of making some configurations
easier. Especially when configuring a server because in server configuration files
+ you can specify the IP address of the server, that you know will be the same every
time. An example if configuring MySQL to answer on a specific IP address you have
configured on the server.
+ </para>
+ </section>
+</chapter>