| Before we discuss MAC addresses, IP addresses, and the like, it might be a good idea to ensure that basic IP capabilities have been compiled into the kernel. This may seem super-simplified because the default installation of HP-UX comes with networking enabled; this is just to make sure. Remember making assumptions is dangerous. " An assumption only makes an ass out of an umption ." Table 15-1 shows the basic drivers that we need to ensure basic IP functionality. Table 15-1. Basic Networking Drivers | Driver | Comment | | hpstreams | Required for streams connectivity | | dlpi | Required for access to MAC level diagnostics | | uipc | Required fro TCP/IP | | inet | Required fro TCP/IP | | nms | Required fro TCP/IP | | netdiag1 | Required for network diagnostics | | tun | Required for PPP |
As you can see from this system, all the required drivers are in place:
root@hpeos004[] kmsystem grep -e hpstreams -e dlpi -e uipc -e inet -e nms e netdiag1  e tun dlpi Y - hpstreams Y - hpstreamsqa N - inet Y - netdiag1 Y - nms Y - tun Y - uipc Y - root@hpeos004[]
It is worthwhile checking that we also have the necessary device file in place; again, these should have been created during the installation process. Without these device files, we won't be able to use commands like lanadmin : The device file are /dev/lan (for Ethernet frames ), /dev/snap (for 802.3 frames: Sub Network Access Protocol), and /dev/dlpi (interface to MAC level diagnostics: Data-Link Provider Interface). They are configured with the same major and minor number, so don't be surprised if some of them are symbolic links:
root@hpeos004[] ll /dev/lan /dev/snap /dev/dlpi crw-rw-rw- 1 root sys 72 0x000077 Aug 5 15:39 /dev/dlpi crw-r--r-- 1 root sys 72 0x000077 Aug 5 15:39 /dev/lan lrwxr-xr-x 1 root sys 9 Aug 5 15:36 /dev/snap -> /dev/dlpi root@hpeos004[]
If they are missing, we can simply recreate the /dev/dlpi device file using insf :
root@hpeos004[dev] insf -ve -d dlpi insf: Installing special files for pseudo driver dlpi root@hpeos004[dev]
We then recreate the other device files either with a symbolic link or mknod . Now we can consider configuring individual LAN interfaces. | 