From 829d40731b8d6fc89548fb2605f5f8fd4b277281 Mon Sep 17 00:00:00 2001 From: Klaatu von Schlacker Date: Mon, 25 Jun 2012 09:28:49 -0400 Subject: Added netconfig and startup services section to ch02 Made minor changes to ch14 15 16 --- chapter_14.xml | 73 +++++++++++++++++++++++++++++++--------------------------- 1 file changed, 39 insertions(+), 34 deletions(-) (limited to 'chapter_14.xml') diff --git a/chapter_14.xml b/chapter_14.xml index b9e7e58..aeedd11 100644 --- a/chapter_14.xml +++ b/chapter_14.xml @@ -2,10 +2,10 @@ - + Networking -
+
<application>netconfig</application> @@ -43,24 +43,23 @@ book.
-
+
Manual Configuration Ok, so you've installed Slackware, you've setup a desktop, but you can't get it to connect to the Internet or your business's LAN (local -area network), what do you do? Fortunately, the answer to that question -is simple. Slackware includes a number of tools to configure your -network connection. The first we will look at today is the very -powerful ifconfig(8). -ifconfig is used to setup or modify the -configuration of a Network Interface Card (NIC or Ethernet Card), the -most common hardware for connecting to networks today. -ifconfig is an incredibly powerful tool -capable of doing much more than setting IP addresses. For a complete -introduction, you should read its man page. For now, we're just going -to use it to display and change the network addresses of some ethernet -controllers. +area network), what do you do? Fortunately, the answer to that +question is simple. Slackware includes a number of tools to configure +your network connection. The first we will look at is the very +powerful ifconfig(8), which is used to +setup or modify the configuration of the most common hardware for +connecting to networks: a Network Interface Card (NIC or +Ethernet Card). ifconfig is an incredibly powerful +tool capable of doing much more than setting IP addresses. For a +complete introduction, you should read its man page. For now, we're +just going to use it to display and change the network addresses of +some ethernet controllers. darkstar:~# ifconfig @@ -177,7 +176,8 @@ For now, let's take a look at our routing table immediately after setting up eth0. -darkstar:~# route + +darkstar:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 @@ -198,7 +198,8 @@ itself. In order to reach the rest of the world, we'll need to setup a default gateway. -darkstar:~# route add default gw 192.168.1.254 + +darkstar:~# route add default gw 192.168.1.254 darkstar:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface @@ -233,7 +234,7 @@ nameserver 192.168.1.254 -Most users won't need the search line. This is used to map hostnames +Many users won't need the search line. This is used to map hostnames to domain names. Basically, if I attempt to connect to "barnowl", the computer knows to look for "barnowl.lizella.net" thanks to this search line. We're mainly interested in the nameserver line. This tells @@ -305,7 +306,7 @@ clients, so use whichever you prefer.
-
+
Automatic Configuration with <filename>rc.inet1.conf</filename> @@ -357,14 +358,17 @@ Protocol Address for the n network interface card. Typically, n corrosponds to eth0, eth1, and so on, but this isn't always the case. You can specify these values to -pertain to a different network controller with the INFAME[n] -variable, but we will reserve that for the next chapter on wireless -networking, as it more commonly pertains to wireless network -controllers. Likewise, NETMASK[n] is the subnet mask to use -for the network controller. If these lines are left empty, then -static IP addresses will not be automatically assigned to this network -controller. The USE_DHCP[n] variable tells -Slackware (naturally) to use DHCP to configure the interface. +pertain to a different network controller with the IFNAME[n] +variable, but we will reserve that for , +as it more commonly pertains to wireless network controllers. + + + +Likewise, NETMASK[n] is the subnet mask to use for the network +controller. If these lines are left empty, then static IP addresses +will not be automatically assigned to this network controller. The +USE_DHCP[n] variable tells Slackware +(naturally) to use DHCP to configure the interface. DHCP_HOSTNAME[n] is rarely used, but some DHCP servers may require it. In that case, it must be set to a valid hostname. Finally, we come to the GATEWAY variable. It is actually @@ -379,13 +383,14 @@ interfaces are attached to it. If you need to use static IP addressing, you will have to obtain a -unique static IP address and the subnet mask for the interface, as well -as the default gateway address, and enter those here. There is no place -to enter DNS information in rc.inet1.conf, so DNS -servers will have to be manually placed into -resolv.conf as we discussed above. Of course, if -you use netconfig, this will be handled for -you by that program. Now let's take a look at another interface on my +unique static IP address and the subnet mask for the interface, as +well as the default gateway address, and enter those here. There is no +place to enter DNS information in rc.inet1.conf, +so DNS servers will have to be manually placed into +resolv.conf as discussed in . Of course, if you use +netconfig, this will be handled for you by +that program. Now let's take a look at another interface on my computer. -- cgit v1.2.3