Handbook:Parts/Installation/Networking/ja

ネットワークの自動検出
動いているかも？

もしあなたのシステムが、DHCPサーバを持つEthernetネットワークに接続されているなら、おそらく既にネットワーク設定は自動的に完了しているでしょう. その場合には、、、、、、など、インストールCDに含まれるネットワーク接続が必要な多くのコマンドはすぐに使うことができるでしょう.

ネットワークが設定されているならば、コマンドで、loと並んでなどのネットワークインターフェースを一覧表示できるはずです：

インターフェース名はシステムによってとはかなり違うかもしれません. 最近のインストールメディアはややなど、命名規則に則ったネットワークインターフェース名を表示するかもれません. の出力から、あなたのローカルネットワーク上のIPアドレスが設定されたインターフェースを探してください.

以降、このドキュメントでは、インターフェース名はであると仮定します.

Optional: Configure any proxies
プロキシを経由してインターネットにつなぐ場合には、インストール作業の中でプロキシ情報を設定する必要があります. プロキシを設定するのはとても簡単です：プロキシサーバ情報を変数に設定するだけです.

ほとんどの場合、プロキシサーバのホスト名を設定するだけで十分です. 例えば、ホスト名はproxy.gentoo.org、ポート番号は8080であるとしましょう.

HTTPプロキシ（HTTPとHTTPS通信のため）を設定するには：

FTPプロキシを設定するには：

RSYNCプロキシを設定するには：

ユーザ名とパスワードが必要ならば、次の構文で変数を設定します：

ネットワークのテスト
あなたのISPのDNSサーバ（で見つかります）と、好きなウェブサイトへのpingを試してみましょう. これにより、ネットワークが正常に機能しているか、ネットワークパケットがインターネットに到達できるか、DNS名前解決が正常に機能しているか、等のことを確認できます.

これがすべてうまくいくのなら、この章の残りの部分を読み飛ばして、インストールマニュアルの次のステップ（ディスクの準備）へ進むことができます.

自動でのネットワーク設定
起動しただけではネットワークが使えない場合は、インストールメディアに（通常のネットワークや無線ネットワーク用）や、（ADSL用）や、 （PPTP用）などのツールが含まれているなら、それらを使って設定できます.

お使いのインストールメディアがこれらのツールを含んでいない場合は、へ進んでください.


 * 通常のEthernetユーザはDefault: Using net-setupへ
 * ADSLユーザはAlternative: Using PPPへ
 * PPTPユーザはAlternative: Using PPTPへ

Default: Using net-setup
ネットワークが自動で設定されなかった場合に、ネットワークを設定するための最も簡単な方法がスクリプトを実行することです：

はあなたのネットワーク環境について、いくつかの質問をします. すべてに答えると、ネットワーク接続が使えるようになるはずです. 上に書いた方法でネットワークをテストしてください. すべてのテストをパスできたなら、おめでとうございます！ この章の残りを飛ばしてディスクの準備へ進みましょう.

それでもネットワークが使えない場合は、へ進んでください.

Alternative: Using PPP
インターネットへの接続にPPPoEが必要なら、インストールCD（どのバージョンでも可）に含まれるpppが設定を楽にしてくれます. 提供されるスクリプトを使ってネットワークを設定しましょう. セットアップ中には、ADSLモデムに接続されたEthernetデバイスの名前、ユーザ名とパスワード、DNSサーバのIPアドレス、基本的なファイアウォールが必要かどうかが聞かれます.

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.

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 wlan0 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), 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:

For most users, there are only two settings that might be important to change, the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access Point address listed are already those of the environment's access point and the environment is not not using WEP, then the wireless configuration is already working.

To change the ESSID, or add a WEP key, issue the following commands.


 * To set the network name to GentooNode:




 * To set a hex WEP key:




 * To set an ASCII WEP key, prefix the key with :



Confirm the wireless settings again 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.

Understanding network terminology
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
Setting up the network consists of three steps:


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

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

Set up routing using. Substitute ${GATEWAY} with the right gateway IP address:

Now open :

Fill in the nameserver(s) using the following as a template. Make sure to substitute ${NAMESERVER1} and ${NAMESERVER2} with the appropriate nameserver addresses:

That's it. Now test the network by pinging some Internet server (like Google). If this works, congratulations then. Continue with Preparing the disks.