Escolar Documentos
Profissional Documentos
Cultura Documentos
Introduction
Each Linux distribution has its own tool or utility for configuring an ethernet card and network settings. However, learning how to do this using only an xterm session will allow you to configure the network on almost any Linux box.
The list of compiled ethernet card drivers that come with your system are usually located under /lib/modules/2.2.14-5.0/net where 2.2.14-5.0 is your kernel version. The source code for these drivers are usually located at /usr/src/linux-2.2.14/drivers/net again where 2.2.14 is the kernel version you are running. Sometimes the comments at the beginning of the source code file will tell you which ethernet cards the driver is for. Some distributions will find it during installation and automatically load the driver for you. To see if this is the case, view the file /etc/modules.conf or /etc/conf.modules depending on your distribution. If you see a line that looks similar to alias eth0 ne2k-pci, then the third item on the line is the module being used for your ethernet card. In this example, ne2k-pci, the NE2000 driver is being used. To verify the module has been loaded successfully, issue the command /sbin/lsmod. This will display all modules successfully loaded in the system. Once your module is loaded, you are ready to move to the next step. If the module is not loaded, but you know what module your network card uses, issue the following steps as root:
Make sure the network is stopped by issuing /etc/rc.d/init.d/network stop. Manually load the module by issuing /sbin/insmod ne2k-pci replacing ne2k-pci with whatever your module is. This module must be present in the /lib/modules/2.2.14-5.0/net directory for lsmod to find it. Verify it loaded successfully by issuing /sbin/lsmod. Activate the eth0 device by issuing /etc/rc.d/init.d/network start Configure your network settings with steps 2-6. You must still be root to perform these steps.
1. Set the IP address and network mask: /sbin/ifconfig -a eth0 192.168.1.5 netmask 255.255.255.0. This example gives the machine the IP address 192.168.1.5, but you can use any combination of IP/netmask that will work with your network. 2. Verify the settings with /sbin/ifconfig eth0. 3. Add the default gatway: /sbin/route add default gw 192.168.1.254 replacing 192.168.1.254 with your gateway. 4. Verify the gateway setting: /sbin/route. The line beginning with default should have your gateway under the gateway column. 5. Alternately, you can edit the file /etc/sysconfig/network-scripts/ifcfg-eth0 to look like (replace with your network numbers)
DEVICE=eth0 USERCTL=no ONBOOT=yes BOOTPROTO=none BROADCAST=192.168.1.255 NETWORK=192.168.1.0 NETMASK=255.255.255.0 IPADDR=192.168.1.5 and the file /etc/sysconfig/network to look like (replace with your network numbers and hostname) NETWORKING=yes HOSTNAME=name.host.net FORWARD_IPV4=yes GATEWAYDEV= GATEWAY=192.168.1.254
Ping the gateway and a few other computers on the network to verify your settings are correct.
The list of compiled ethernet card drivers that come with your system are usually located under /lib/modules/2.2.14-5.0/net where 2.2.14-5.0 is your kernel version. The source code for these drivers are usually located at /usr/src/linux-2.2.14/drivers/net again where 2.2.14 is the kernel version you are running. Sometimes the comments at the beginning of the source code file will tell you which ethernet cards the driver is for. Some distributions will find it during installation and automatically load the driver for you. To see if this is the case, view the file /etc/modules.conf or /etc/conf.modules depending on your distribution. If you see a line that looks similar to alias eth0 ne2k-pci, then the third item on the line is the module being used for your ethernet card. In this example, ne2k-pci, the NE2000 driver is being used. To verify the module has been loaded successfully, issue the command /sbin/lsmod. This will display all modules successfully loaded in the system. Once your module is loaded, you are ready to move to the next step.
If the module is not loaded, but you know what module your network card uses, issue the following steps as root:
Make sure the network is stopped by issuing /etc/rc.d/init.d/network stop. Manually load the module by issuing /sbin/insmod ne2k-pci replacing ne2k-pci with whatever your module is. This module must be present in the /lib/modules/2.2.14-5.0/net directory for lsmod to find it. Verify it loaded successfully by issuing /sbin/lsmod. Activate the eth0 device by issuing /etc/rc.d/init.d/network start Configure your network settings with steps 2-4. You must still be root to perform these steps. Edit/create the file /etc/sysconfig/network-scripts/ifcfg-eth0 to use DHCP.
Sample ifcfg-eth0 file: DEVICE=eth0 USERCTL=no ONBOOT=yes BOOTPROTO=dhcp BROADCAST= NETWORK= NETMASK= IPADDR=
Replace eth0 above with eth1 if it is the second network card in your system. Edit/create the file /etc/sysconfig/network to use DHCP.
Restart the network to probe the DHCP server for your network settings with the command /etc/rc.d/init.d/network restart. Verify your network settings with the command /sbin/ifconfig to make sure you have received an IP address from the DHCP server. Ping the gateway and a few other computers on the network to verify your connection.
What is Related
Network Configuration Using Red Hat linuxconf Network Configuration Using SuSE YaST squid Proxy Server Configuration Network Configuration Using Red Hat netcfg Samba Configuration Linux/Windows Connectivity Installation and Configuration: Internet Search Engine Print Sharing Dial-up Networking Configuration Using Red Hat netcfg Cable Modem Configuration ipchains Configuration Dial-up Networking Configuration Using KDEs Kppp
Description List DNS servers for internet domain name resolution. Manual page for: /etc/resolv.conf Lists hosts to be resolved locally (not by DNS). Manual page for: /etc/hosts List order of host name search. Typically look at local files, then NIS server, then DNS server. Manual page for: /etc/nsswitch.conf Specify network configuration. eg. Static IP, DHCP, NIS, etc. Specify TCP network information.
/etc/hosts
/etc/nsswitch.conf
Red Hat/Fedora/CentOS:
/etc/sysconfig/network
Red Hat/Fedora/CentOS:
/etc/sysconfig/network-scripts/ifcfgdevice
Ubuntu/Debian: /etc/network/interfaces Specify network configuration and devices. eg. Static IP and info, DHCP, etc.
This configures Linux so that it knows which DNS server will be resolving domain names into IP addresses. If using DHCP client, this will automatically be sent to you by the ISP and loaded into this file as part of the DHCP protocol. If using a static IP address, ask the ISP or check another machine on your network. Red Hat/Fedora GUI: /usr/sbin/system-config-network (select tab "DNS"). File: /etc/hosts - locally resolve node names to IP addresses
127.0.0.1 localhost XXX.XXX.XXX.XXX your-node-name.your-domain.com node-name localhost.localdomain
Note when adding hosts to this file, place the fully qualified name first. (It helps sendmail identify your server correctly) i.e.:
XXX.XXX.XXX.XXX superserver.yolinux.com superserver
This informs Linux of local systems on the network which are not handled by the DNS server. (or for all systems in your LAN if you are not using DNS or NIS) The file format for the hosts file is specified by RFC 952. Red Hat/Fedora configuration GUI: /usr/sbin/system-config-network (select tab "Hosts"). File: /etc/nsswitch.conf - System Databases and Name Service Switch configuration file
hosts: files dns nisplus nis
This example tells Linux to first resolve a host name by looking at the local hosts file(/etc/hosts), then if the name is not found look to your DNS server as defined by /etc/resolv.conf and if not found there look to your NIS server. In the past this file has had the following names: /etc/nsswitch.conf, /etc/svc.conf, /etc/netsvc.conf, ... depending on the distribution.
/etc/sysconfig/network Red Hat network configuration file used by the system during the boot process.
File: /etc/sysconfig/network-scripts/ifcfg-eth0 Configuration settings for your first ethernet port (0). Your second port is eth1.
File:
o o o /etc/modprobe.conf (kernel 2.6) /etc/modules.conf (kernel 2.4) (or for older systems: /etc/conf.modules)
Modules for other devices on the system will also be listed. This tells the kernel which device driver to use if configured as a loadable module. (default for Red Hat)
Network configuration:
/usr/sbin/systemconfig-network (FC-
(RH 9.0 - FC-1) Text console network configuration tool. First interface only -
eth0:
/usr/sbin/netconfig /usr/bin/netcfg (GUI)
(RH 9.0 - FC-3) Proxy configuration. Choose one of three options: 1. Direct internet connection 2. Manual proxy configuration (specify proxy and port) 3. Automatic proxy configuration (give URL)
Assigning an IP address:
Computers may be assiged a static IP address or assigned one dynamically. Typically a server will require a static IP while a workstation will use DHCP (dynamic IP assignment). The Linux server requires a static IP so that those who wish to use its resources can find the system. It is more easily found if the IP address does not change and is static. This is not important for the Linux client workstation and thus it is easier to use an automated Dynamic Host Configuration Protocol (DHCP) for IP address assignment.
Command Line:
/sbin/ifconfig eth0 192.168.10.12 netmask 255.255.255.0 broadcast 192.168.10.255
Network address by convention would be the lowest: 192.168.10.0 Broadcast address by convention would be the highest: 192.168.10.255 The gateway can be anything, but following convention: 192.168.10.1 Note: the highest and lowest addresses are based on the netmask. The previous example is based on a netmask of 255.255.255.0
Red Hat / Fedora GUI tools: o /usr/bin/neat Gnome GUI network administration tool. Handles all interfaces. Configure for Static IP or DHCP client. (First available with Red Hat 7.2.) o /usr/bin/netcfg (Handles all interfaces) (last available in Red Hat 7.1) Red Hat / Fedora Console tools: o /usr/sbin/system-config-network-tui (Text User Interface) o /usr/sbin/netconfig (Only seems to work for the first network interface eth0 but not eth1,...) Directly edit configuration files/scripts. See format below.
The ifconfig command does NOT store this information permanently. Upon reboot this information is lost. Manually add the network configuration to /etc/sysconfig/networkscripts/ifcfg-eth0 (Red Hat/Fedora/CentOS) for the first NIC, ifcfg-eth1 for the second, etc, or /etc/network/interfaces (Ubuntu) as shown below. Any other commands you may want to add to the system boot sequence can be added to the end of the file /etc/rc.d/rc.local. The commands netcfg and netconfig make permanent changes to system network configuration files located in /etc/sysconfig/networkscripts/, so that this information is retained and used upon system boot. The IANA has allocated IP addresses in the range of 192.168.0.0 to 192.168.255.255 for private networks. Helpful tools:
Network Calculators: Subnet mask calculator, node calculator, mask inverter, ... IP subnet calculator
where:
interface: eth0, eth1, eth2 represent the computer ethernet interfaces aftype: inet (TCP/IP, default), inet6 (IPv6), ax25 (AMPR Packet Radio), ddp (Appletalk Phase 2), ipx (Novell IPX) or netrom (AMPR Packet radio)
Options: Option up down arp -arp promisc -promisc mtu ## broadcast XXX.XXX.XXX.XXX netmask XXX.XXX.XXX.XXX Man page: ifconfig Shut down interface Enable ARP protocol on this interface. Allow ARP to detect the addresses of computer hosts attached to the network. Disable ARP protocol on this interface Enable promiscuous mode. Receive all packets on the network not just those destined for this interface. Disable promiscuous mode. Specify the Maximum Transfer Unit (MTU) of the interface. The MTU is the maximum number of octets the interface is able to handle in a single transaction. Defaults: Ethernet: 1500 SLIP: 296 Set the network broadcast address for this interface. Set the IP network mask for this interface. Description Activate the interface. Implied if IP addresses are specified.
auto eth1 iface eth1 inet dhcp auto eth2 iface eth2 inet dhcp auto ath0 iface ath0 inet dhcp auto wlan0 iface wlan0 inet dhcp
Interfaces:
lo: Loopback interface (network within your system without slowing down for the real ethernet based network) eth0: First ethernet interface card wlan0: First wireless network interface
- Hostname is defined here and by command hostname - True for NAT firewall gateways and linux routers. False for everyone else - desktops and servers. GATEWAY="XXX.XXX.XXX.YYY" - Used if your network is connected to another network or the internet. Static IP configuration. Gateway not defined here for DHCP client.
NETWORKING=yes HOSTNAME=my-hostname
File (Red Hat/Fedora): /etc/sysconfig/network-scripts/ifcfg-eth0 (S.u.s.e.: /etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX) This file used by the command scripts ifup and ifdown Static IP address configuration:
DEVICE=eth0 BOOTPROTO=static BROADCAST=XXX.XXX.XXX.255 IPADDR=XXX.XXX.XXX.XXX NETMASK=255.255.255.0 NETWORK=XXX.XXX.XXX.0 ONBOOT=yes
RHEL4/FC3 additions:
o o o
RHEL4/FC3 additions:
o o o o o
(Used by script /etc/sysconfig/network-scripts/ifup to bring the various network interfaces on-line) To disable DHCP change BOOTPROTO=dhcp to BOOTPROTO=none In order for updated information in any of these files to take effect, one must issue the command: service network restart (or: /etc/init.d/network restart)
Network IP aliasing:
Assign more than one IP address to one ethernet card:
ifconfig eth0 XXX.XXX.XXX.XXX netmask 255.255.255.0 broadcast XXX.XXX.XXX.255 ifconfig eth0:0 192.168.10.12 netmask 255.255.255.0 broadcast 192.168.10.255 ifconfig eth0:1 192.168.10.14 netmask 255.255.255.0 broadcast 192.168.10.255 route add -host XXX.XXX.XXX.XXX dev eth0 route add -host 192.168.10.12 dev eth0 route add -host 192.168.10.14 dev eth0
In this example 0 and 1 are aliases in addition to the regular eth0. The result of the ifconfig command:
eth0 Link encap:Ethernet HWaddr 00:10:4C:25:7A:3F inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14218 errors:0 dropped:0 overruns:0 frame:0 TX packets:1362 errors:0 dropped:0 overruns:0 carrier:0 collisions:1 txqueuelen:100 Interrupt:5 Base address:0xe400 eth0:0 Link encap:Ethernet HWaddr 00:10:4C:25:7A:3F inet addr:192.168.10.12 Bcast:192.168.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:5 Base address:0xe400 Link encap:Ethernet HWaddr 00:10:4C:25:7A:3F inet addr:192.168.10.14 Bcast:192.168.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:5 Base address:0xe400
eth0:1
NETWORK=192.168.10.0 ONBOOT=yes
Aliases can also be shut down independently. i.e.: ifdown eth0:0 The option during kernel compile is: CONFIG_IP_ALIAS=y (Enabled by default in Redhat) Note: The Apache web server can be configured so that different IP addresses can be assigned to specific domains being hosted. See Apache configuration and "configuring an IP based virtual host" in the YoLinux Web site configuration tutorial.
DHCP Linux Client: get connection info: /sbin/pump -i eth0 --status (Red Hat Linux 7.1 and older)
Device eth0 IP: 4.XXX.XXX.XXX Netmask: 255.255.252.0 Broadcast: 4.XXX.XXX.255 Network: 4.XXX.XXX.0 Boot server 131.XXX.XXX.4 Next server 0.0.0.0 Gateway: 4.XXX.XXX.1 Domain: vz.dsl.genuity.net Nameservers: 4.XXX.XXX.1 4.XXX.XXX.2 4.XXX.XXX.3 Renewal time: Sat Aug 11 08:28:55 2001 Expiration time: Sat Aug 11 11:28:55 2001
Note that hostnames may only contain alphanumeric characters, minus signs ("-"), and periods ("."). They must begin with an alphabetic character and end with an alphanumeric character.
Change the host name using GUI tool: /usr/sbin/system-config-network (Red Hat / Fedora / CentOS) Hostname entries are made in two places:
Commands for starting and stopping TCP/IP network services on a Network Interface Card (NIC):
Activate:
/sbin/ifup eth0 (Also: ifconfig eth0 up - Note:
Core 2/3)
/usr/bin/redhat -controlnetwork (RH 9.0
- FC-1) Configure Ethernet, ISDN, modem, token Ring, Wireless or DSL network connection:
/usr/sbin/syste m-config-
network-druid
(FC2/3)
/usr/sbin/redha t-confignetwork-druid
(RH 9 - FC-1)
Subnets:
M # A OF Sla S SU sh K B Fm NE t TS 2 5 5 2 5 4 1 or /32 256 CLASS A HOSTS CLA CLA CLAS CLASS SS SS A S B B C MAS HOST MASK HOS K S TS CLASS C MASK CLAS SC SUB HOST S CLASS C SUB MASK
255.25 5.0.0
254
Invalid 255.255. 1 255.255.2 255.0 addre 55.255 ss Invalid 255.255. 2 255.255.2 254.0 addre 55.254 sses
128 /31
255.25 4.0.0
510
2 5 2
64
/30
255.25 2.0.0
2 hosts 1,02 255.255. 4 2 252.0 addre sses 6 hosts 2,04 255.255. 8 6 248.0 addre sses 14 hosts 4,09 255.255. 16 4 240.0 addre sses 30 8,19 255.255. hosts 0 224.0 32 addre
255.255.2 55.252
2 4 8
32
/29
255.24 8.0.0
255.255.2 55.248
2 4 0
16
/28
255.255.2 55.240
2 2 4
/27
255.255.2 55.224
sses 1 9 2 62 hosts 16,3 255.255. 64 82 192.0 addre sses 126 hosts 32,7 255.255. 128 66 128.0 addre sses
/26
255.255.2 55.192
1 2 8
/25
255.255.2 55.128
7 6 5 4321 1 0 0 0000
128 64 32 16 8 4 2 1
Example 192=128+64 Some addresses are reserved and outside this scope. Loopback (127.0.0.1), reserved class C 192.168.XXX.XXX, reserved class B 172.31.XXX.XXX and reserved class A 10.XXX.XXX.XXX. Subnet Example: Your ISP assigns you a subnet mask of 255.255.255.248 for your office.
208.88.34.104 Network Base address 208.88.34.105 Computer 1 208.88.34.106 Computer 2 208.88.34.107 Computer 3 208.88.34.108 Computer 4 208.88.34.109 Computer 5 208.88.34.110 DSL router/Gateway 208.88.34.111 Broadcast address
Of the eight addresses, there are six assigned to hardware systems and ultimately only five usable addresses. Links:
Subnet calculator Table of subnets IP Subnetting, Variable Subnetting, and CIDR (Supernetting) CISCO.com: Subnet Masking and Addressing
Network Classes:
The concept of network classes is a little obsolete as subnets are now used to define smaller networks using CIDR (Classless Inter-Domain Routing) as detailed above. These subnets may be part of a class A, B, C, etc network. For historical reference the network classes are defined as follows:
Class A: Defined by the first 8 bits with a range of 0 - 127. First number (8 bits) is defined by Internic i.e. 77.XXX.XXX.XXX One class A network can define 16,777,214 hosts. Range: 0.0.0.0 - 127.255.255.255 Class B: Defined by the first 8 bits with a range from 128 - 191 First two numbers (16 bits) are defined by Internic i.e. 182.56.XXX.XXX One class B network can define 65,534 hosts. Range: 128.0.0.0 - 191.255.255.255 Class C: Defined by the first 8 bits with a range from 192 - 223 First three numbers (24 bits) are defined by Internic i.e. 220.56.222.XXX One class B network can define 254 hosts. Range: 192.0.0.0 - 223.255.255.255 Class D: Defined by the first 8 bits with a range from 224 - 239 This is reserved for multicast networks (RFC988) Range: 224.0.0.0 - 239.255.255.255 Class E: Defined by the first 8 bits with a range from 240 - 255 This is reserved for experimental use. Range: 240.0.0.0 - 247.255.255.255
Enable Forwarding:
Forwarding allows the network packets on one network interface (i.e. eth0) to be forwarded to another network interface (i.e. eth1). This will allow the Linux computer to conect ("ethernet bridge") or route network traffic. The bridge configuration will merge two (or several) networks into one single network topology. IpTables firewall rules can be used to filter traffic. A router configuration can support multicast and basic IP routing using the " route" command. IP masquerading (NAT) can be used to connect private local area networks (LAN) to the internet or load balance servers.
Default is 0. One can add firewall rules by using ipchains. Another method is to alter the Linux kernel config file: /etc/sysctl.conf Set the following value:
net.ipv4.ip_forward = 1
Change the default "false" to "true". All methods will result in a proc file value of "1". Test: cat
/proc/sys/net/ipv4/ip_forward
The TCP Man page - Linux Programmer's Manual and /usr/src/linux/Documentation/proc.txt (Kernel 2.2 RH 7.0-) cover /proc/sys/net/ipv4/* file descriptions. Also see: (YoLinux tutorials)
Configure Linux as an internet gateway router: Using Linux and iptables/ipchains to set up an internet gateway for home or office (iptables) Load balancing servers using LVS (Linux Virtual Server) (ipvsadm)
example uses 2.2.5-15 (Fedora Core 3: /lib/modules/2.6.12-1.1381_FC3/kernel/net/) Here you will find the modules supported by your system. It can be permanently added to: o /etc/modprobe.conf (kernel 2.6) o /etc/modules.conf (kernel 2.4) o (or for older systems: /etc/conf.modules) Example:
alias eth0 3c59x
/sbin/insmod 3c59x (For a 3Com ethernet card) This inserts the specified module into the kernel.
/sbin/modprobe 3c59x This also loads a module into the system kernel. Modprobe command line options: o -r : to unload the module. o /sbin/modprobe -l \* : list all modules. o /sbin/modprobe -lt net \* : List only network modules o /sbin/modprobe -t net \* : Try loading all network modules and see what sticks. (act of desperation) ifconfig ...
The easy way: Red Hat versions 6.2 and later, ship with Kudzu, a device detection program which runs during system initialization. (/etc/rc.d/init.d/kudzu) This can detect a newly installed NIC and load the appropriate driver. Then use /usr/sbin/netconfig to configure the IP address and network settings. The configuration will be stored so that it will be utilized upon system boot. Systems with two NIC cards: Typically two cards are used when connecting to two networks. In this case the device must be defined using one of three methods: 1. Use the Red Hat GUI tool /usr/bin/netcfg OR 2. Define network parameters in configuration files: Define new device in file (Red Hat/Fedora) /etc/sysconfig/networkscripts/ifcfg-eth1 (S.u.s.e 9.2: /etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX) DEVICE=eth1 BOOTPROTO=static IPADDR=192.168.10.12 NETMASK=255.255.255.0 GATEWAY=XXX.XXX.XXX.XXX HOSTNAME=node-name.name-of-domain.com DOMAIN=name-of-domain.com
Special routing information may be specified, if necessary, in the file (Red Hat/Fedora): /etc/sysconfig/static-routes (S.u.s.e. 9.2: /etc/sysconfig/network/routes) Example:
eth1 net XXX.XXX.XXX.0 netmask 255.255.255.0 gw XXX.XXX.XXX.XXX
OR 3. Define network parameters using Unix command line interface: Define IP address:
ifconfig eth0 XXX.XXX.XXX.255 ifconfig eth1 192.168.10.255 XXX.XXX.XXX.XXX netmask 255.255.255.0 broadcast 192.168.10.12 netmask 255.255.255.0 broadcast
Where XXX.XXX.XXX.XXX is the gateway to the internet as defined by your ISP or network operator. If a mistake is made just repeat the route command substituting "del" in place of "add".
Option -F
Parameters 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD 100baseT4 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
-A
Description Queries ethernet device for rx/tx ring parameter information. Queries ethernet device for pause parameter information. Queries ethernet device for coalescing information. Queries ethernet device for associated driver information. Prints a register dump for the specified ethernet device. Queries ethernet device for offload information. Queries ethernet device for NIC and driver statistics.
Man Pages:
mii-tool - view, manipulate media-independent interface status ethtool - Display or change ethernet card settings
Route:
Static routes: IP (Internet Protocol) uses a routing table to determine where packets should be sent. First the packet is examined to see if its' destination is for the local or remote network. If it is to be sent to a remote network, the routing table is consulted to determine the path. If there is no information in the routing table then the packet is sent to the default gateway. Static routes are set with the route command and with the configuration file (Red Hat/Fedora): /etc/sysconfig/network-scripts/route-eth0 or (Red Hat 7: /etc/sysconfig/static-routes) (S.u.s.e. 9.2: /etc/sysconfig/network/routes):
See command: /etc/sysconfig/network-scripts/ifup-routes eth0 Dynamic routes: RIP (Routing Information Protocol) is used to define dynamic routes. If multiple routes are possible, RIP will choose the shortest route. (Fewest hops between routers not physical distance.) Routers use RIP to broadcast the routing table over UDP port 520. The routers would then add new or improved routes to their routing tables. Man pages:
route - show / manipulate the IP routing table (Static route) Show routes: Option -n -e -v
Description
display IP addresses. Do not resolve host names for faster results. Print more extensive information about routes. Verbose.
--help Route command information. Manipulate routes: Option add or del or neither
Description
Add or delete route information. If not specified then print route table information. Add a network identified by the network address, to the route. Specify the network gateway. Specify the network netmask. Of all the routes specified, identify one as the default network route. (typically the gateway is specified as the default route)
-host XXX.XXX.XXX.XXX Add a single computer host identified by the IP address. -net XXX.XXX.XXX.XXX gw XXX.XXX.XXX.XXX netmask XXX.XXX.XXX.XXX default
Examples:
o o o
Show routing table: route -e Access individual computer host specified via network interface card eth1:
route add -host 123.213.221.231 eth1
Access ISP network identified by the network address and netmask using network interface card eth0:
route add -net 10.13.21.0 netmask 255.255.255.0 gw 192.168.10.254 eth0
Specify default gateway to use to access remote network via network interface card eth0:
route add default gw 201.51.31.1 eth0 (Gateway can also be defined in /etc/sysconfig/network)
Specify two gateways for two network destinations: (i.e. one external, one internal private network. Two routers/gateways will be specified.) Add internet gateway as before: route add default gw 201.51.31.1 eth0 Add second private network: route add -net 10.0.0.0 netmask
255.0.0.0 gw 192.168.10.254 eth0
routed - network routing daemon. Uses RIP protocol to update routing table. ipx_route - show / manipulate the IPX routing table - IPX is the Novell networking protocol (Not typically used unless your office has Novell servers) ifuser - Identify destinations routed to a particular network interface.
VPN, Tunneling:
Commercial VPN Linux software solutions - YoLinux OpenSWAN.org - IPSec VPN for Linux FreeSWAN.org - IPSec VPN for Linux FreeSWAN tutorial - howto OpenVPN - SSL VPN solution for site to site, WiFi security, and enterprise-scale remote access with load balancing, failover, and fine-grained access-controls. SSL-Explorer - Java SLL based VPN Quagga dynamic routing suite VLAN n2n pier to pier within a private fabric CIPE: Crypto IP Encapsulation (Easiest way to configure two Linux gateways connecting two private networks over the internet with encryption.) o CIPE Home page - CIPE is a simple encapsulation system that securely connects two subnets. GRE Tunneling - Generic Routing Encapsulation - Hugo Samayoa VPN HowTo - Matthew D. Wilson Installing and Running PPTP on Linux L2TP Extensions (l2tpext) Internet Drafts.
o o o
-u: Show UDP -t: Show TCP -n: Show IP addresses only. Don't resolve host names -g: Show multi-cast group membership info -c: Continuous mode - update info every second -v: Verbose -e: Extended information -o: show network timer information List all connected processes: netstat -nap Show network statistics: netstat -s Display routing table info: netstat -rn
$ netstat -nr Kernel IP routing table Destination Gateway Iface 192.168.1.0 0.0.0.0 169.254.0.0 0.0.0.0 0.0.0.0 192.168.1.1
Flags U U UG
MSS Window 0 0 0 0 0 0
Flags: G: route uses gateway U: Interface is "up" H: Only a single host is accessible (eg. loopback) D: Entry generated by ICMP redirect message M: Modified by ICMP redirect message Display interface statistics: netstat -i
$ netstat -i Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR OVR Flg eth0 1500 0 2224 0 0 0 0 BMRU lo 16436 0 1428 0 0 0 0 LRU
Where: RX-OK/TX-OK: number of packets transmitted/received error free RX-ERR/TX-ERR: number of dammaged/error packets transmitted/received RX-DRP/TX-DRP: number of dropped packets RX-OVR/TX-OVR: number of packets dropped because of a buffer overrun Flags:
L: This interface is a loopback device M: All packets are received (promiscuous mode) N: Trailers are avoided O: ARP is turned off for this interface P: Point-to-point connection R: Interface is running U: Interface is up ping - send ICMP ECHO_REQUEST packets to network hosts. Use Cntl-C to stop ping. traceroute - print the route packets take to network host. (Ubuntu Note: Typically Ubuntu installs tracepath for IPv4 and traceroute6 for IPv6. One can install traceroute: apt-get install traceroute)
o o traceroute IP-address-of-server traceroute domain-name-of-server
mtr - a network diagnostic tool introduced in Fedora - Like traceroute except it gives more network quality and network diagnostic info. Leave running to get real time stats. Reports best and worst round trip times in milliseconds.
o o mtr IP-address-of-server mtr domain-name-of-server
whois - Lookup a domain name in the internic whois database. finger - Display information on a system user. i.e. finger user@host Uses $HOME/.plan and $HOME/.project user files. iptables - IP firewall administration (Linux kernel 2.6/2.4) See YoLinux firewall/gateway configuration. ipchains - IP firewall administration (Linux kernel 2.2) See YoLinux firewall/gateway configuration. socklist - Display list of open sockets, type, port, process id and the name of the process. Kill with fuser or kill. host - Give a host name and the command will return IP address. Unlike nslookup, the host command will use both /etc/hosts as well as DNS. Example: host domain-name-of-server nslookup - Give a host name and the command will return IP address. Also see Testing your DNS (YoLinux Tutorial) Note that nslookup does not use the /etc/hosts file.
inetd: Red Hat 6.x and older xinetd: Red Hat 7.0-9.0, Fedora Core
inetd:
Configuration file: /etc/inetd.conf Entries in this file consist of a single line made up of the following fields:
service socket-type protocol wait user server cmdline
service: The name assigned to the service. Matches the name given in the file /etc/services socket-type: o stream: connection protocols (TCP) o dgram: datagram protocols (UDP) o raw o rdm o seqpacket protocol: Transport protocol name which matches a name in the file /etc/protocols. i.e. udp, icmp, tcp, rpc/udp, rpc/tcp, ip, ipv6 wait: Applies only to datagram protocols (UDP). o wait[.max]: One server for the specified port at any time (RPC) o nowait[.max]: Continue to listen and launch new services if a new connection is made. (multi-threaded) Max refers to the maximum number of server instances spawned in 60 seconds. (default=40)
user[.group]: login id of the user the process is executed under. Often nobody, root or a special restricted id for that service. server: Full path name of the server program to be executed. cmdline: Command line to be passed to the server. This includes argument 0 (argv[0]), that is the command name. This field is empty for internal services. Example of internal TCP services: echo, discard, chargen (character generator), daytime (human readable time), and time (machine readable time). (see RFC)
A line may be commented out by using a '#' as the first character in the line. This will turn the service off. The maximum length of a line is 1022 characters.
The inet daemon must be restarted to pick up the changes made to the file:
/etc/rc.d/init.d/inetd restart
For more information see the man pages "inetd" and "inetd.conf".
disable = yes
or
disable = no
SIGUSR1 (kill -SIGUSR1 process-id) - Soft reconfiguration does not terminate existing connections. (Important if you are connected remotely) SIGUSR2 - Hard reconfiguration stops and restarts the xinetd process.
This command will also restart the xinetd process to pick up the new configuration. The file contains entries of the form:
service service-name { attribute assignment-operator value value ... ... {
Where:
attribute: o disable: yes no o type: RPC INTERNAL: UNLISTED: Not found in /etc/rpc or /etc/services o id: By default the service id is the same as the service name. o socket_type: stream: TCP dgram: UDP raw: Direct IP access seqpacket: service that requires reliable sequential datagram transmission o flags: Combination of: REUSE, INTERCEPT, NORETRY, IDONLY, NAMEINARGS, NODELAY, DISABLE, KEEPALIVE, NOLIBWRAP. See the xinetd man page for details. o protocol: Transport protocol name which matches a name in the file /etc/protocols. o wait: no: multi-threaded yes: single-threaded - One server for the specified port at any time (RPC) o user: See file : /etc/passwd o group: See file : /etc/group o server: Program to execute and recieve data stream from socket. (Fully qualified name - full pathe name of program) o server_args: Unlike inetd, arg[0] or the name of the service is not passed. o only_from: IP address, factorized address, netmask range, hostname or network name from file /etc/networks. o no_access: Deny from ... (inverse of only_from) o access_times
Also: log_type, log_on_success, log_on_failure (Log options: += PID,HOST,USERID,EXIT,DURATION,ATTEMPT and RECORD), rpc_version, rpc_number, env, passenv, redirect, bind, interface, banner, banner_success, banner_fail, per_source, cps, max_load, groups, enabled, include, includedir, rlimit_as, rlimit_cpu, rlimit_data, rlimit_rss, rlimit_stack. The best source of information is the man page and its many examples.
assignment-operator: o = o +=: add a value to the set of values o -=: delete a value from the set of values
Then restart the daemon: /etc/rc.d/init.d/xinetd restart Example from man page: Limit telnet sessions to 8 Mbytes of memory and a total 20 CPU seconds for child processes.
service telnet { socket_type wait nice user server rlimit_as rlimit_cpu }
= = = = = = =
[Pitfall] Red Hat 7.1 with updates as of 07/06/2001 required that I restart the xinetd services before FTP would work properly even though xinetd had started without failure during the boot sequence. I have no explanation as to why this occurs or how to fix it other than to restart xinetd: /etc/rc.d/init.d/xinetd restart. Man Pages:
RedHat.com: Controlling Access to Services http://www.xinetd.org See RFC's: 862, 863, 864, 867, 868, 1413. man page xinetd, xinetd.conf, xinetd.log
telnet - user interface to the TELNET protocol rlogin - remote login rsh - remote shell to execute a command and return results uux - Remote command execution over UUCP rcp - remote file copy uucp - Unix to Unix copy uuxqt - UUCP execution daemon uucico - UUCP file transfer daemon cu - Call up another system (cu is an old legacy command which is reported to not work very well)
See the YoLinux.com secure shell tutorial for use of ssh, rssh, scp and sftp
Set service to start with system boot: chkconfig --level 345 rwhod on Start rwhod service: service rwhod start (or: service rwhod restart)
Man pages:
rwho: who is logged in on local network machines rwhod: system status server who: show who is logged on to the same system
Core)
Man Pages:
portmap - DARPA port to RPC program number mapper rpcinfo - report RPC information pmap_dump - print a list of all registered RPC programs pmap_set - set the list of registered RPC programs /etc/rpc - rpc program number data base
This specifically allows the given IP address to ftp to your system. One can also specify an entire domain. i.e. .name-of-domain.com Note the beginning ".".
File: /etc/hosts.deny
ALL:ALL
This generally denies any access. See the pam man page. File: /etc/inetd.conf
ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd -l -a
The inet daemon accepts the incoming network stream and assigns it to the PAM TCP wrapper, /usr/sbin/tcpd, which accepts or denies the network connection as defined by /etc/hosts.allow and /etc/hosts.deny and then passes it along to ftp. This is logged to /var/log/secure
Advanced PAM: More specific access can be assigned and controlled by controlling the level of authentication required for access. Files reflect the inet service name. Rules and modules are stacked to achieve the level of security desired. See the files in /etc/pam.d/... (some systems use /etc/pam.conf) The format: service type control module-path module-arguments
auth - (type) Password is required for the user o nullok - Null or non-existatant password is acceptable o shadow - encrypted passwords kept in /etc/shadow account - (type) Verifies password. Can track and force password changes. password - (type) Controls password update o retry=3 - Sets the number of login attempts o minlen=8 - Set minimum length of password session - (type) Controls monitoring
Modules:
/lib/security/pam_pwdb.so - password database module /lib/security/pam_shells.so /lib/security/pam_cracklib.so - checks is password is crackable /lib/security/pam_listfile.so
Wietse's Papers Pluggable Authentication Modules for Linux (PAM) Home Page
ICMP:
ICMP is the network protocol used by the ping and traceroute commands. ICMP redirect packets are sent from the router to the host to inform the host of a better route. To enable ICMP redirect, add the following line to /etc/sysctl.conf :
net.ipv4.conf.all.accept_redirects = 1
Command to view Kernel IP routing cache: /sbin/route -Cn NOTE: This may leave you vulnerable to hackers as attackers may alter your routes.
Ipchains:
ipchains -A output -p icmp -d 0/0 -j DENY
This is sometimes necessary to look invisible to DOS (Denial Of Service) attackers who use ping to watch your machine and launch an attack when it's pressence is detected
Description Exit after receiving count packets. Specify size of output dump files. Specify interface if multiple exist. Lowest used by default. i.e. eth0 Write the raw packets to file rather than parsing and printing them out. They can later be printed with the -r option. Improve speed by not performing DNS lookups. Report IP addresses. Don't print a timestamp on each dump line.
-n -t
Filter expressions: primitive host host-name net network-number port port-number tcp udp icmp
Description If host has multiple IP's, all will be checked. Network number. Port number specified. Sniff TCP packets. Sniff UDP packets. Sniff icmp packets.
Examples:
o o tcpdump tcp port 80 and host server-1 tcpdump ip host server-1 and not server-2
iptraf - Interactive Colorful IP LAN Monitor nmap - Network exploration tool and security scanner o List pingable nodes on network: nmap -sP 192.168.0.0/24 Scans network for IP addresses 192.168.0.0 to 192.168.0.255 using ping. Ethereal - Network protocol analyzer. Examine data from a live network. RPM's required:
o o o o
ethereal-0.8.15-2.i386.rpm - Red Hat 7.1 Powertools CD RPM ucd-snmp-4.2-12.i386.rpm - Red Hat 7.1 binary CD 1 ucd-snmp-utils-4.2-12.i386.rpm - Red Hat 7.1 binary CD 1 Also: gtk+, glib, glibc, XFree86-libs-4.0.3-5 (base install)
There is an error in the ethereal package because it does not show the snmp libraries as a dependancies, but you can deduce this from the errors that you get if the ucd-snmp libraries are not installed.
EtherApe - Graphical network monitor for Unix modeled after etherman. This is a great network discovery program with cool graphics. (Red Hat Powertools CD 7.1) Gkrellm - Network and system monitor. Good for monitoring your workstation. (Red Hat Powertools CD) IPTraf - ncurses-based IP LAN monitor. (Red Hat Powertools CD) Cheops - Network discovery, location, diagnosis and management. Cheops can identify all of the computers that are on your network, their IP address, their DNS name, the operating system they are running. Cheops can run a port scan on any system on your network. (Red Hat Powertools CD) ntop - Shows network usage in a way similar to what top does for processes. Monitors how much data is being sent and received on your network. (Red Hat Powertools CD) MRTG - Multi Router Traffic Grapher - Monitor network traffic load using SNMP and generate an HTML/GIF report. (See sample output) dnsad - IP traffic capture. Export to Cisco Netflow for network analysis reporting. Big Brother - Monitoring ans services availablility. OpenNMS.org - Network Management using SNMP. Nagios - host, service and network monitoring Angel network monitor
Ethernet hosts use the Address Resolution Protocol (ARP) to convert a 32-bit internet IP addresses into a 48-bit Ethernet MAC address used by network hardware. (See: RFC 826) ARP broadcasts are sent to all hosts on the subnet by the data transmitting host to see who replies. The broadcast is ignored by all except the intended receiver which recognizes the IP address as its own. The MAC addresses are remembered (APR cache) for future network communications. Computers on the subnet typically keep a cache of ARP responses. ARP broadcasts are passed on by hubs and switches but are blocked by routers. Reverse ARP (See: RFC 903) is a bootstrap protocol which allows a client to broadcast requesting a server to reply with its IP address. View ARP tables:
Show ARP table Linux style: /sbin/arp -e List ARP table: cat /proc/net/arp
Note that the use of a switch instead of a hub will limit your view of other hosts. Typically all you will see in the arp table is your router or gateway. Set/Configure ARP tables:
Add a host's IP address: /sbin/arp -s hostname XX:XX:XX:XX:XX:XX pub Delete a host from the table: /sbin/arp -d hostname This can be used to remove a duplicate IP or force a new interface to provide info.
Man pages:
arp (8) man page - manipulate the system ARP cache arpwatch (8) man page - keep track of ethernet/ip address pairings arpsnmp (8) man page - keep track of ethernet/ip address pairings. Reads information generated by snmpwalk arping (8) man page - send ARP REQUEST to a neighbor host Print ARP reply (similar to arp -a): arping 192.168.10.99 ip (8) man page - show / manipulate routing, devices, policy routing and tunnels View ARP table: ip neighbor
ARP is something that simply works. No Linux system configuration is necessary. It's all part of the ethernet and IP protocol. The aforementioned information is just part of the Linux culture of full visibility into what is going on.
Regular network exchanges of data are peer to peer unicast transactions. An HTTP request to a web server (TCP/IP), email SNMP (TCP/IP), DNS (UDP), FTP (TCP/IP), ... are all peer to peer unicast transactions. If one wants to transmit a video, audio or data stream to multiple nodes with one transmission stream instead of multiple individual peer to peer connections, one for each node, one may use multicasting to reduce network load. Note that multicast and a network broadcast are different. Multicast messages are only "heard" by the nodes on the network that have "joined the multicast group" which are those that are interested in the information. The Linux kernel is Level-2 Multicast-Compliant. It meets all requirements to send, receive and act as a router for multicast datagrams. For a process to receive multicast datagrams it has to request the kernel to join the multicast group and bind the port receiving the datagrams. When a process is no longer interested in the multicast group, a request is made to the kernel to leave the group. It is the kernel/host which joins the multicast group and not the process. Kernel configuration requires "CONFIG_IP_MULTICAST=y". In order for the Linux kernel to support multicast routing, set the following in the kernel config:
CONFIG_IP_MULTICAST=y CONFIG_IP_ROUTER=y CONFIG_IP_MROUTE=y CONFIG_NET_IPIP=y
The default Red Hat / Fedora kernels are compiled to support multicast. See the YoLinux tutorial on optimization and rebuilding the Linux kernal. Note that on multihomed systems (more than one IP address/network card), only one device can be configured to handle multicast. Class D networks with a range of IP addresses from 224.0.0.0 to 239.255.255.255 (See Network Classes above) have typically been reserved for multicast. Usefull commands: Command
cat /proc/net/igmp cat /proc/net/dev_mcast ping 224.0.0.1 ping 224.0.0.2
Description List multicast group to which the host is subscribed. Use "Internet Group Management Protocol". (See /usr/src/linux/net/core/igmp.c) List multicast interfaces. (See /usr/src/linux/net/core/dev_mcast.c) All hosts configured for multicast will respond with their IP addresses All routers configured for multicast will respond
All PIM routers configured for multicast will respond All DVMRP routers configured for multicast will respond All OSPF routers configured for multicast will respond
Multicast transmissions are achieved through proper routing, router configuration (if communicating through subnets) and programatically with the use of the following "C" function library calls: Function Call setsockopt() Description Pass information to the Kernel.
getsockopt() Retrieve information broadcast using multicast. For more on multicast programming see: Multicast Howto. The multicast application will specify the multicast loopback interface, TTL (network time to live), network interface and the multicast group to add or drop. Add route to support multicast:
route add 224.0.0.0 netmask 240.0.0.0 dev eth0
Note that if adding a route to forward packets through a router, that the router MUST be configured to forward multicast packets. Many routers do not support forwarding of multicast packets or have a default configuration which does not. The internet by default does not forward multicast packets.
YoLinux Tutorial: Configuring PPP dial up connections to an ISP YoLinux Tutorial: Dialing Compuserve YoLinux Tutorial: Dialing AOL YoLinux Tutorial: Configuring PPP dial-in connections
RFC 2637: Point-to-Point Tunneling Protocol (PPTP). PPTP-Linux Client - A PPTP Linux client that allows a linux system to connect to a PPTP server. Developed by C. S. Ananian. Counterpane Systems FAQ on Microsoft's PPTP Implementation - FAQ on the security flaws in Microsoft's PPTP Implementation.
64 65 66 67 Interface minor numbers The command ls -l /dev/ttyS* /dev/cua* will show the device major and minor numbers. The major and minor numbers are used when creating a SPLIP interface: Example:
mknod -m 666 /dev/cua1 c 5 65 chown root.uucp /dev/cua1
SLIP configuration:
Configure /etc/resolve.conf (See notes above in this tutorial) Attach network interface to serial line on COM2: /sbin/slattach -p slip -s
19200 /dev/ttyS1 &
Assign local IP (192.168.1.10) and connect to remote server (192.168.1.40) Alternate example: /sbin/route add plip1 192.168.1.10 pointopoint
192.168.1.40 Add route: /sbin/route add default dev sl0 &
Specify remote host as the gateway. On the remote host at the other end of the cable, the opposite must be specified:
ifconfig plip1 192.168.1.40 pointopoint 192.168.1.10 route add 192.168.1.10 gw 192.168.1.40
setserial - get/set Linux serial port information Typical configuration: o Interrupt detection: /sbin/setserial -W /dev/cua* o Configuration: /sbin/setserial /dev/cua1 auto_irq skip_test
autoconfig or /sbin/setserial /dev/cua1 auto_irq skip_test autoconfig uart 16550 Display Configuration: /sbin/setserial -bg /dev/cua* Enable hardware handshake: stty crtscts < /dev/cua1 (verify: stty -s < /dev/cua1)
o o
stty - change and print terminal line settings tty - print the file name of the terminal connected to standard input pppd - Point-to-Point Protocol Daemon slattach - attach a network interface to a serial line
SMB4k: My favorite MS/Windows file share browser. In Nautilus use the URL "smb:" to view MS/Windows servers. [tutorial] LinNeighborhood: Linux workstation gui tool. Make your life simple and use the GUI/File Manager LinNeighborhood. It uses smbmount, samba and smbclient to give you access to MS/Windows servers and printers.
o o
Network Definitions:
IPv4: Most of the Internet servers and personal computers use Internet Protocol version 4 (IPv4). This uses 32 bits to assign a network address as defined by the four octets of an IP address up to 255.255.255.255. Which is the representation of four 8 bit numbers thus totaling 32 bits. IPv6: Internet Protocol version 6 (IPv6) uses a 128 bit address and thus billions and billions of potential addresses. The protocol has also been upgraded to include new quality of service features and security. Currently Linux supports IPv6 but IPv4 is used when connecting your computer to the internet. TCP/IP: (Transmission Control Protocol/Internet Protocol) uses a client - server model for communications. The protocol defines the data packets transmitted (packet header, data section), data integrity verification (error detection bytes), connection and acknowledgement protocol, and re-transmission. TCP/IP time to live (TTL): This is a counting mechanism to determine how long a packet is valid before it reaches its destination. Each time a TCP/IP packet passes through a router it will decrement its TTL count. When the count reaches zero the packet is dropped by the router. This ensures that errant routing and looping aimless packets will not flood the network. MAC Address: (media access control) is the network card address used for communication between other network devices on the subnet. This info is not routable. The ARP table maps TCP/IP address (global internet) to the local hardware on the local network. Use the command /sbin/ifconfig to view both the IP address and the MAC address. The MAC address uniquely identifies each node of a network and is used by the Ethernet protocol. Full Duplex: Allows the simultaneous sending and receiving of packets. Most modern modems support full duplex.
Half Duplex: Allows the sending and receiving of packets in one direction at a time only. OSI 7 Layer Model: The ISO (International Standards Organization) has defined the OSI (Open Systems Interconnection) model for current networking protocols. OSI Layer 7 Description Application Layer. The top layer for communications applications like email and the web. Presentation Layer. Syntax and format of data transfer. Session Layer. Transport Layer. TCP Connection, acknowledgement and data packet UDP transmission. Network Layer. Data Link Layer. Error control, timing Physical Layer. Electrical characteristics of signal and NIC IP ARP Ethernet Ethernet Linux Networking Use telnet, web browser, sendmail SMTP, http
6 5 4
3 2 1
Network Hub: Hardware to connect network devices together. The devices will all be on the same network and/or subnet. All network traffic is shared and can be sniffed by any other node connected to the same hub. Network Switch: Like a hub but creates a private link between any two connected nodes when a network connection is established. This reduces the amount of network collisions and thus improves speed. Broadcast messages are still sent to all nodes.
Related Links:
Cable modem HowTo - Vladimir Vuksan Ethernet HowTo - Paul Gortmaker YoLinux Tutorial: Setting up an internet gateway for home or office using iptables or ipchains Firewall HowTo - Mark Grennan YoLinux networking tutorial Networking Overview HowTo - Daniel Lopez Ridruejo Networking Howto - Joshua Drake NFS Howto - Nicolai Langfeldt
SNMP: Simple Network Management Protocol (Uses ports 161,162,391,1993) o SNMP - Intro tutorials o Linux SNMP Network Management Tools o SNMP FAQ o net-snmp - tools and libraries News/Usenet Group: comp.os.linux.networking - Deja MARS-nwe - Netware emulator Linux 2.4 Advanced Routing HOWTO - iproute2, traffic shaping and a bit of netfilter ISDN: o ISDN4LINUX FAQ - Matthias Hessler o ISDN4 Linux Home Page o Dan Kegel's ISDN Page DHCP: (Dynamic Host Configuration Protocol) o YoLinux DHCP Tutorial - How to set up a DHCP server. o ISC Dynamic Host Configuration Protocol - DHCP home page Multicast: o YoLinux Tutorial: Configuring Linux for multicast - this tutorial in section above o Multicast over TCP/IP HOWTO ISP's: (National/Global) o TheList.com - Comprehensive list of ISP's o Concentric NIS: (NFS infrastructure) o YoLinux NIS tutorial - NIS configuration and use o NIS howto Ethernet cables: o Making CAT 3, 5, 5E RJ45 Ethernet Cables Gigabit Ethernet VIX: Vienna Internet eXchange - European traffic exchange for ISP's