GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installation Basic Survival Wajig Audio AbiWord APM Backup Bash Booting Cameras CD Chinese ChRoot Clock Commercial Conference Management Configuration CRON CVS Databases DIA Directories Disks Documentation DVD Email Eye of Gnome Evolution File Systems Firewalls Floppy Disks Fonts Ghemical GIMP Glade Gnome GnuCash Gnumeric GQView Graphics Groups HTML Editors ImageMagick Initialisations on Booting Java KDE Kernels Keyboard Konqueror KVM Switch LaTeX Log System Login Magellan Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks NFS NT File System OpenOffice.org Oracle Packages Partitions Passwords PDF Photos PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Security SH File System Sketch Spell SPlus Spruce SSH SUDO Subversion Swap Themes USB Video Virtualization Web Word X XML Sample Installations Troubleshooting Index

Example Configurations

We present here some example network configurations. The numbers will only make sense for very specific locations and you will need to obtain your specific addresses from your System Administrator. We illustrate these through the contents of /etc/network/interfaces but it is advisable to use Applications-->System Tools-->Networking as discussed above to change the contents of this configuration file.

The simplest configuration uses DHCP to automatically obtain network information from a server that allocates addresses:

  auto eth0
  iface eth0 inet dhcp

Velox (104.33) was initially set up to allow DHCP allocation of the IP address. The DHCP server delivered the appropriate information as demonstrated in /var/log/installer.log:

  got dhcp offer 
  HOSTNAME: requesting velox
  ip: 183.44.70.122
  next server: 0.0.0.0
  netmask: 255.255.255.0
  gateway: 183.44.70.177
  dnsServers[0]: 183.44.72.1
  numDns: 1
  domain: togaware.com
  broadcast: 183.44.70.255
  network: 183.44.70.0
  configured interface eth0
  The network has been successfully configured using DHCP/BOOTP.

A manual configuration requires the information to be specified:

  auto eth0
  iface eth0 inet static
    address 105.229.8.151
    netmask 255.255.255.192
    broadcast 105.229.8.191
    gateway 105.229.8.190

A computer with a 3Com 3c905 ethernet card:

eth0: 3Com 3c905 Boomerang 100baseTx at 0xfc80,  00:c0:4f:f7:02:bf, IRQ 10
  8K word-wide RAM 3:5 Rx:Tx split, autoselect/MII interface. 
  MII transceiver found at address 24, status 7849. 
  Enabling bus-master transmits and whole-frame receives.

You can check that the eth0 interface is functioning:

# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:C0:4F:F7:02:BF  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:21
          collisions:0 txqueuelen:100 
          Interrupt:10 Base address:0xfc80

A computer with a SMC91C92 Ethernet network card. I had to configure the appropriate kernel module to have this card recognised. I used the modconf command to do this, select the Net modules and select the smc9194 module. Configuring this succeeded, returning the following message:

SMC9194: SMC91C90/91C92(r:3) at 0x300 IRQ:10 INTF:TP MEM:4608b ADDR: 00:c0:4f:df:25:55