GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installing GNU/Linux Basic Survival Wajig Applications AI, Machine Learning, Data Science Android - GNU/Linux Devices Audio Backup Booting CD Chinese ChRoot Clock Command Line Databases DIA Directories Disks EcoSysL Emacs Email Evolution Files File Systems Firewalls Floppy Disks FreedomBox Glade GNOME Graphics, Images, Photos Hardware Initialisations on Booting Installation Examples Internet IOT Java KDE Kernels Keyboard Konqueror KVM Switch LATEX Log System Login Magellan MATE Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks Nextcloud Network File System NFS NT File System Oracle Packages Partitions Passwords PDF Power Management PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Screens Security Spreadsheet SSH Swap Teradata Data Warehouse Themes TV Unity USB Version Control Video Virtualization Voice over IP WebCam WordPress Web Sites Word Processing and Printing X XML Troubleshooting Index

CLICK HERE TO VISIT THE UPDATED SURVIVAL GUIDE

Networking

During an install DHCP will be attempted to obtain your network information from a DHCP server. This (usually) requires that you identify your host as a host that your DHCP server knows or relies on the DHCP server allocating the next available IP address. Do so just to see if there is a DHCP server available to you.

If a DHCP server is not available then you will be prompted for alternative options, including manually setting up the appropriate network information.

Generally you need the following, where some sample addresses are supplied:

  IP       155.229.8.165
  Netmask  255.255.255.192
  Gateway  155.229.8.190
  Domain   togaware.com
  DNS      183.44.72.1

The information is recorded in /etc/network/interfaces and /etc/resolv.conf. Later on edit /etc/resolv.conf to add search togaware.com so that you can refer to your local machines by their name, without fully specifying the domain.

Some useful commands for trouble shooting are:

  # netstat -n
  # ifconfig -a