The default networking setup for Fedora 10 uses “NetworkManager”. The initial configuration of NetworkManager will generally use DHCP. This configuration may be quite accepted for many Access Grid installations and will work straight away.

Though it should be noted that NetworkManager has been designed to improve portable, especially wireless, network configurations/setups. Unfortunately, it is still an ongoing project and can be problematic for fixed IP configurations.

Additionally, there are a number of bugs within Fedora’s Networking which makes it difficult to get it working effectively.  Therefore, the following instructions provides step by step guide on how to configure a “DHCP” based network, or a “Fixed IP” based network.

DHCP

Information to be added soon!

Fixed IP

Generally speaking, for fixed IP network configurations, it is recommended to switch to using the old "network" service, rather than using "NetworkManager". By default, Fedora 10 disables the "network" service in preference to using "NetworkManager", therefore NetworkManager will need to be disabled before enabling and configuring the network service.

To disable NetworkManager, issue the following commands (as root or superuser):

• /etc/init.d/NetworkManager stop

• chkconfig NetworkManager off

Once NetworkManager has been turned off and disabled, you now have to configure the network. Unfortunately, to date (8th/Dec/2008) there is a bug with system-config-network (GUI Version) in which it incorrectly stores the network mask as the default gateway address. See bug https://bugzilla.redhat.com/show_bug.cgi?id=469434, therefore it is highly suggested to use the text base program (system-config-network-tui) for configuring the network settings.

To configure the network, simply do the following:

• As root or superuser, issue the command "system-config-network-tui"

• Select "Edit a device params" and hit Enter

• Select appropriate network device, generally it should be the device eth0 then hit enter

• The Network Configuration screen should now be displayed. If you do not know this or any of the below settings, it is recommended that your ask your network administration team:

• The device "Name" should generally be unchanged.

• The "Device" should also generally be unchanged.

• Unselect the "Use DHCP" property if selected.

• Enter the manual IP Address within the "Static IP" section.

• Enter the netmask within the "Netmask" section. Generally it will be 255.255.255.0

• Enter the gateway address within the "Default gateway IP" section.

• Once these settings have been added, select the "Ok" option, then the "Save" option.

• The "Edit DNS configuration" option should then be selected to modify the hostname and DSN server settings.

• Enter and/or modify the details for hostname, DNS and Search entries

• Selection Ok once correct details have been entered

• Simply select the "Save&Quit" option to save network settings and to quit.

To enable the network service, issue the following commands (as root or superuser):

• /etc/init.d/network start

• chkconfig network on

Hopefully the network should now be enabled and working.  If it is not working correctly, a reboot might be required. 

Hosts File

As part of the configuration of the network, where you may have selected to use Static Ip Address and entered the hostname manually, you will mostly likely have to edit your /etc/hosts file.

Note, you only have to edit this file if you are using a static ip address. If you are using DHCP (dynamically assigned IP address) you don't have to worry about editing this file.

It has been found that if you dont make the following changes to the hosts file, the multicast beacon and AGServiceManager will not work correctly.

To edit the file /etc/hosts, type vi /etc/hosts. Make sure you are the super-user while doing this.

If your hosts file looks similar to this:

login or register to post comments