Handbook:Parts/Networking/Modular/ko

네트워크 모듈
We now support modular networking scripts, which means we can easily add support for new interface types and configuration modules while keeping compatibility with existing ones.

Modules load by default if the package they need is installed. If users specify a module here that doesn't have its package installed then they get an error stating which package they need to install. Ideally, the modules setting is only used when two or more packages are installed that supply the same service and one needs to be preferred over the other.

인터페이스 핸들러
We provide two interface handlers presently: ifconfig and iproute2. Only one of these is needed to do any kind of network configuration.

ifconfig is installed by default (the net-tools package is part of the system profile). iproute2 is a more powerful and flexible package, but it's not included by default.

As both ifconfig and iproute2 do very similar things we allow their basic configuration to work with each other. For example both the below code snippet work regardless of which module the user is using.

DHCP
DHCP is a means of obtaining network information (IP address, DNS servers, Gateway, etc) from a DHCP server. This means that if there is a DHCP server running on the network, the user just has to tell each client to use DHCP and it sets up the network all by itself. Of course, the user will have to configure for other things like wireless, PPP or other things if required before he can use DHCP.

DHCP can be provided by dhclient, dhcpcd, or pump. Each DHCP module has its pros and cons - here's a quick run down.

If more than one DHCP client is installed, specify which one to use - otherwise we default to dhcpcd if available.

To send specific options to the DHCP module, use module_eth0="..." (change module to the DHCP module being used - i.e. dhcpcd_eth0).

We try and make DHCP relatively agnostic - as such we support the following commands using the dhcp_eth0 variable. The default is not to set any of them:
 * release - releases the IP address for re-use
 * nodns - don't overwrite
 * nontp - don't overwrite
 * nonis - don't overwrite

PPPoE/PPPoA로 ADSL 연결
우선 ADSL 프로그램을 설치해야합니다.

그 다음 PPP net 스크립트를 만들고 PPP에서 사용할 이더넷 인터페이스용 net 스크립트도 만드십시오:

에서 rc_depend_strict를 YES로 설정했는지 확인하십시오.

Now we need to configure.

It is also possible to set the password in.

If PPPoE is used with a USB modem then make sure to emerge br2684ctl. Please read for information on how to properly configure it.

APIPA(자동 개인 IP 주소 지정)
APIPA tries to find a free address in the range 169.254.0.0-169.254.255.255 by arping a random address in that range on the interface. If no reply is found then we assign that address to the interface.

This is only useful for LANs where there is no DHCP server and the system doesn't connect directly to the Internet and all other computers use APIPA.

For APIPA support, emerge or.

본딩
For link bonding/trunking emerge.

Bonding is used to increase network bandwidth or to improve resiliency in face of hardware failures. If a system has two network cards going to the same network, then the administrator can bond them together so the applications see just one interface but they really use both network cards.

There are many ways to configure bonding. Some of them, such as the 802.3ad LACP mode, require support and additional configuration of the network switch. For a reference of the individual options, please refer to the local copy of.

First, clear the configuration of the participating interfaces:

다음, 인터페이스간 본딩을 지정하십시오:

실행 레벨에서 net.eth* 서비스를 제거하고 net.bond0을 만들어 올바른 실행 레벨에 추가하십시오.

브릿징(802.1d 지원)
For bridging support emerge.

Bridging is used to join networks together. For example, a system may have a server that connects to the Internet via an ADSL modem and a wireless access card to enable other computers to connect to the Internet via the ADSL modem. It is possible to create a bridge to join the two interfaces together.

MAC 주소
네트워크 설정 파일을 통해서도 인터페이스 맥 주소를 바꿀 수 있습니다.

터널링
터널링은 인터페이스 핸들러가 처리할 수 있으므로 프로그램을 추가로 설치할 필요가 없습니다.

VLAN (802.1q 지원)
For VLAN support, make sure that is installed and ensure that iproute2 is used as configuration module rather than ifconfig.

Virtual LAN is a group of network devices that behave as if they were connected to a single network segment - even though they may not be. VLAN members can only see members of the same VLAN even though they may share the same physical network.

To configure VLANs, first specify the VLAN numbers in like so:

다음 각각 VLAN의 인터페이스를 설정하십시오:

VLAN별 설정은 다음과 같이 vconfig로 처리합니다: