Handbook:Parts/Installation/Networking/ta

தானியக்க வலையமைப்பு கண்டறிதல்
ஒருவேளை ஏற்கனவே வேளை செய்து கொண்டிருக்கலாம்?

If the system is plugged into an Ethernet network with a DHCP server, it is very likely that the networking configuration has already been set up automatically. If so, then the many included network-aware commands on the installation CD such as, , , , , and , among others, will work immediately.

ifconfig கட்டளை
வலையமைப்பு உள்ளமைக்கப்பட்டிருந்தால், கட்டளையை அளித்தவுடன் ஒன்று அல்லது பல வலையமைப்பு இடைமுகங்கள் ( விற்கு அடுத்து) பட்டியலிடப்பட்டிருக்கும். கீழுள்ள எடுத்துக்காட்டில் ஐ காணலாம்:

As a result of the shift towards predictable network interface names, the interface name on the system can be quite different from the old naming convention. Recent installation media might show regular network interfaces names like, , or. Look for the interface in the output that has an IP address related to the local network.

ip கட்டளை
கட்டளைக்கு மாற்றாக இடைமுக பெயர்களை அறிந்துகொள்ள கட்டளையையும் பயன்படுத்தலாம். எடுத்துக்காட்டாக என்னும் கட்டளையின் வெளியீட்டைப் பின்வருமாறு காணலாம் (இது மற்றொரு முறைமையிலிருந்து எடுக்கப்பட்ட வெளியீடு என்பதால் மேலுள்ள எடுத்துக்காட்டை விட மாறுபட்டதாக இருக்கலாம்):

மேலுள்ள வெளியீடு இதன் மாற்று கட்டளையின் வெளியீட்டை விட படிப்பதற்கு சற்று சிக்கலானதாக இருக்கலாம். இந்த எடுத்துக்காட்டில் இடைமுகத்தின் பெயரான தெளிவாக எண்ணை அடுத்து வருவதை காணலாம்.

இதைத் தொடர்ந்து வரும் பகுதிகளில், இயக்கத்தில் உள்ள இடைமுகத்தின் பெயர் என்னும் அனுமானத்தில் கையேடு நகரும்.

விரும்பினால்: ஏதாவது பதிலாளிகளை உள்ளமைத்தல்
If the Internet is accessed through a proxy, then it is necessary to set up proxy information during the installation. It is very easy to define a proxy: just define a variable which contains the proxy server information.

In most cases, it is sufficient to define the variables using the server hostname. As an example, we assume the proxy is called proxy.gentoo.org and the port is 8080.

HTTP பதிலாளியை அமைப்பதற்கு (HTTP மற்றும் HTTPS போக்குவரத்துகளுக்கு):

FTP பதிலாளியை அமைப்பதற்கு:

RSYNC பதிலாளியை அமைப்பதற்கு:

ஒருவேளை பதிலாளிக்கு பயனர்பெயர் மற்றும் கடவுச்சொல் தேவைப்பட்டால், மாறிக்கான பின்வரும் தொடரியலை பயன்படுத்தவும்:

வலையமைப்பை சோதித்தல்
உங்கள் இணையச் சேவையாளரின் DNS சேவையகம் ( இல் காணலாம்) மற்றும் நீங்கள் விரும்பும் ஒரு இணையப்பக்கத்தை பிங் செய்து முயலவும். இதன்மூலம் வலையமைப்பு நன்றாக வேளை செய்கிறது என்றும் வலையமைப்பு தொகுப்புகள் இணையத்தைச் சென்றடைகிறது என்றும் DNS பெயர் தீர்மானம் முறையாக வேலை செய்கிறது என்றும் உறுதிப்படுத்திக்கொள்ளலாம்.

இவையெல்லாம் சரியாக வேளை செய்தால், இப்பகுதியின் மீதமுள்ள வழிமுறைகளைத் தவிர்த்துவிட்டு நேரடியாக நிறுவல் வழிமுறைகளின் அடுத்த பகுதியான (தகடுகளை ஆயத்தப்படுத்துதல்) பகுதிக்குச் செல்லலாம்.

தானியக்க வலையமைப்பு உள்ளமைத்தல்
வலையமைப்பு உடனடியாக வேளை செய்யவில்லை என்றால், சில நிறுவல் ஊடகங்கள் (வழக்கமான அல்லது கம்பியில்லா வலையமைப்புகளுக்கு),  (ADSL பயனாளர்களுக்கு) அல்லது  (PPTP பயனாளர்களுக்கு) போன்ற கட்டளைகளைப் பயன்படுத்தப் பயனர்களை அனுமதிக்கிறது.

If the installation medium does not contain any of these tools, continue with the Manual network configuration.


 * Regular Ethernet users should continue with Default: Using net-setup
 * ADSL users should continue with Alternative: Using PPP
 * PPTP users should continue with Alternative: Using PPTP

Default: Using net-setup
The simplest way to set up networking if it didn't get configured automatically is to run the script:

will ask some questions about the network environment. When all is done, the network connection should work. Test the network connection as stated before. If the tests are positive, congratulations! Skip the rest of this section and continue with Preparing the disks.

If the network still doesn't work, continue with Manual network configuration.

Alternative: Using PPP
Assuming PPPoE is needed to connect to the Internet, the installation CD (any version) has made things easier by including ppp. Use the provided script to configure the connection. During the setup the Ethernet device that is connected to your ADSL modem, the username and password, the IPs of the DNS servers and if a basic firewall is needed or not will be asked.

If something goes wrong, double-check that the username and password are correct by looking at or  and make sure to use the right Ethernet device. If the Ethernet device does not exist, the appropriate network modules need to be loaded. In that case continue with Manual network configuration as it will explain how to load the appropriate network modules there.

If everything worked, continue with Preparing the disks.

Alternative: Using PPTP
If PPTP support is needed, use which is provided by the installation CDs. But first make sure that the configuration is correct. Edit or  so it contains the correct username/password combination:

Then adjust if necessary:

When all that is done, run (along with the options that couldn't be set in ) to connect the server:

Now continue with Preparing the disks.

Loading the appropriate network modules
When the Installation CD boots, it tries to detect all the hardware devices and loads the appropriate kernel modules (drivers) to support the hardware. In the vast majority of cases, it does a very good job. However, in some cases, it may not auto-load the kernel modules needed to communicate properly with the present network hardware.

If or  failed, then it is possible that the network card wasn't found immediately. This means users may have to load the appropriate kernel modules manually.

To find out what kernel modules are provided for networking, use the command:

If a driver is found for the network device, use to load the kernel module. For instance, to load the module:

To check if the network card is now detected, use. A detected network card would result in something like this (again, here is just an example):

If however the following error is shown, the network card is not detected:

The available network interface names on the system can be listed through the file system:

In the above example, 6 interfaces are found. The one is most likely the (wired) Ethernet adapter whereas  is the wireless one.

Assuming that the network card is now detected, retry or  again (which should work now), but for the hardcore people we explain how to configure the network manually as well.

Select one of the following sections based on your network setup:


 * Using DHCP for automatic IP retrieval
 * Preparing for wireless access if a wireless network is used
 * Understanding network terminology explains the basics about networking
 * Using ifconfig and route explains how to set up networking manually

Using DHCP
DHCP (Dynamic Host Configuration Protocol) makes it possible to automatically receive networking information (IP address, netmask, broadcast address, gateway, nameservers etc.). This only works if a DHCP server is in the network (or if the ISP provider provides a DHCP service). To have a network interface receive this information automatically, use :

Some network administrators require that the hostname and domainname provided by the DHCP server is used by the system. In that case, use:

If this works (try pinging some Internet server, like Google's 8.8.8.8 or Cloudflare's 1.1.1.1), then everything is set and ready to continue. Skip the rest of this section and continue with Preparing the disks.

Preparing for wireless access
When using a wireless (802.11) card, the wireless settings need to be configured before going any further. To see the current wireless settings on the card, one can use. Running might show something like:

To check for a current connection:

or

For most users, there are only two settings needed to connect, the ESSID (aka wireless network name) and, optionally, the WEP key.


 * First, ensure the interface is active:


 * To connect to an open network with the name GentooNode:




 * To connect with a hex WEP key, prefix the key with :




 * To connect with an ASCII WEP key:



Confirm the wireless settings by using. Once wireless is working, continue configuring the IP level networking options as described in the next section (Understanding network terminology) or use the tool as described previously.

வலையமைப்பு கலைச்சொற்களைப் புரிந்துகொள்ளுதல்
If all of the above fails, the network will need to be configured manually. This is not difficult at all. However, some knowledge of network terminology and basic concepts might be necessary. After reading this section, users will know what a gateway is, what a netmask serves for, how a broadcast address is formed and why systems need nameservers.

In a network, hosts are identified by their IP address (Internet Protocol address). Such an address is perceived as a combination of four numbers between 0 and 255. Well, at least when using IPv4 (IP version 4). In reality, such an IPv4 address consists of 32 bits (ones and zeros). Let's view an example:

Such an IP address is unique to a host as far as all accessible networks are concerned (i.e. every host that one wants to be able to reach must have a unique IP address). In order to distinguish between hosts inside and outside a network, the IP address is divided in two parts: the network part and the host part.

The separation is written down with the netmask, a collection of ones followed by a collection of zeros. The part of the IP that can be mapped on the ones is the network-part, the other one is the host-part. As usual, the netmask can be written down as an IP address.

In other words, 192.168.0.14 is part of the example network, but 192.168.1.2 is not.

The broadcast address is an IP address with the same network-part as the network, but with only ones as host-part. Every host on the network listens to this IP address. It is truly meant for broadcasting packets.

To be able to surf on the Internet, each computer in the network must know which host shares the Internet connection. This host is called the gateway. Since it is a regular host, it has a regular IP address (for instance 192.168.0.1).

Previously we stated that every host has its own IP address. To be able to reach this host by a name (instead of an IP address) we need a service that translates a name (such as dev.gentoo.org) to an IP address (such as 64.5.62.82). Such a service is called a name service. To use such a service, the necessary name servers need to be defined in.

In some cases, the gateway also serves as a nameserver. Otherwise the nameservers provided by the ISP need to be entered in this file.

To summarize, the following information is needed before continuing:

Using ifconfig and route
Employing tools from the package, setting up the network manually generally consists of three steps:


 * 1) Assign an IP address using the  command.
 * 2) Set up routing to the gateway using the  command.
 * 3) Finish up by placing valid nameserver IPs in the  file.

To assign an IP address, the IP address, broadcast address, and netmask are needed. Execute the following command, substituting ${IP_ADDR} with the target IP address, ${BROADCAST} with the target broadcast address, and ${NETMASK} with the target netmask:

To configure routing using, substitute the ${GATEWAY} value with the appropriate gateway IP address:

Now open the file using a text editor:

Fill in the nameserver(s) using the following as a template substituting ${NAMESERVER1} and ${NAMESERVER2} with nameserver IP addresses as necessary. More than one nameserver can be added:

Now test the network by pinging an Internet server (like Google's 8.8.8.8 or Cloudflare's 1.1.1.1). Once connected, continue with Preparing the disks.