With the System Rescue CD, you will be able to use the network. Here is the most important information about the network.
Network configuration tools
If your system has supported hardware, the ethernet or wifi network adapter (NIC) should be automatically detected, and the driver loaded. The interface needs to be assigned an IP address and a default gateway.
SystemRescueCd-1.5.2 and more recent versions come with Network-Manager. It provides a very user friendly graphical interface to configure the network. It makes the configuration easier especially for wireless networks. For instance, wireless networks will be automatically detected and connecting to them is very easy. The Network-Manager is available as a small icon in the taskbar just next to the clock. The Network-Manager is only available in the graphical environment.
net-setup eth should be used on the command line.)
You can also configure the network with other tools such as the standard
ip commands. In that case you will have to stop the Network-Manager first, else it will conflict and you will loose your settings. You can do that either by running
/etc/init.d/NetworkManager stop in the shell or by booting SystemRescueCd with the
nonm boot option. Support for this option has been added in SystemRescueCd-1.5.5.
If you are booting SystemRescueCd from the network or if you are using boot options such as
dodhcp the Network-Manager service will automatically be stopped.
The following sections of this chapter explain how to use the network using linux commands. You don't have to read it if you prefer to use the Network-Manager.
Setting up the network by hand
To use dynamic configuration,
dhcpcd eth0. Use
ifconfig -a to display the IP address the DHCP server leased to the interface.
To assign a specific static IP address, enter something such as:
ifconfig eth0 192.168.10.17 . Next the default route is configured. For example, for an interface at address 192.168.10.17 connected to a gateway at 192.168.10.2 enter:
route add default gw 192.168.10.2.
SystemRescueCd provides network boot options such as
ethx, dns, gateway, dodhcp that allow you to automatically configure the network when SystemRescueCd starts. It's very useful if you want to boot SystemRescueCd from the network using PXE but it can be used in any case. It can be very useful if you plan to make customized versions of the CD.
Read the chapter about Basic IP configuration tools on Linux for details about how to configure TCP/IP from the command line on a machine running Linux.
See also the following FAQ: I cannot access other hosts on the network
Running an SSH Server
SSH allows you to use a shell on another computer (as telnet does), and you can copy files (with scp). If you want to run an SSH server, you have to change the root password. Just type
passwd and give a valid password. You can also use the
rootpass=xxx boot option before SystemRescueCd starts to define the root password.
The ssh server is automatically started but you can type the following command anyway:
/etc/init.d/sshd restart. You can stop it with
/etc/init.d/sshd stop Of course you can also use SystemRescueCd as an SSH client to connect to an SSH server: just use
ssh email@example.com or
scp source dest. Both source and dest may be local or remote. Use
firstname.lastname@example.org:/path/filename for remote files.
SystemRescueCd comes with the smbfs/cifs client package that allows you to connect to a Windows machine having shared drives. In recent kernels, support for
smbfs has been replaced with
cifs so you should try not to use
The mount-cifs package allows you to access a Windows computer on the network. Here is an example to explain how to access Windows shared folders. Let's consider the Windows box is on 192.168.10.3 and has a shared directory called mydata accessible by the user called
mkdir /mnt/windows mount -t cifs //192.168.10.3/mydata /mnt/windows -o username=robert,MyPaSsWoRd=root -o lfs cd /mnt/windows
Now you should be able to see files in
/mnt/windows. Don't forget to unmount the directory when you have finished what you are doing in the shared directory.
It's important not to forget the option "lfs" (Large File Support), because it allows you to handle files that are larger than 2 GB. Big files are often used when making a backup or an image file. Without this option, the copy would fail, with an error.
If you want to access files located on an FTP server, there is a new very powerful way to do this. The "Userland FileSystem" allows you to mount the share, and work on the remote files just as you would work on any local files. With all these file systems, you can umount the share with the standard umount command.
Here is an example showing how to mount an FTP file system in
/mnt/ftp as anonymous (read only)
mkdir /mnt/ftp lufis fs=ftpfs,host=ftp.kernel.org /mnt/ftp -s cd /mnt/ftp umount /mnt/ftp
Here is an example of how to mount an SSH file system in
/mnt/ssh as anonymous (read only)
mkdir /mnt/ssh passwd root sshfs email@example.com:/path/to/dir /mnt/ssh cd /mnt/ssh umount /mnt/ssh