Handbook:Parts/Installation/Networking
Otomatik ağ tanıma
Belki kendiliğinden çalışır?
Sisteminiz eğer DHCP sunucu olan bir ethernet ağına bağlı ise, herhangi bir ayar yapmanıza gerek olmayabilir. Eğer bağlanırsanız kurulum CD'sinde internetten kurulum yapmanızı sağlayacak ssh, scp, ping, irssi, wget ve links gibi komutlar anında işe yarar hale gelecektir.
DHCP kullanmak
DHCP (Dynamic Host Configuration Protocol), ağ yapılandırmasına ait bilgileri (IP adresi, ağ maskesi, yayın/broadcast adresi, isim sunucuları vb.) otomatik olarak dağıtmayı sağlayan bir protokoldür. Bu, bağlı olduğunuz ağda DHCP sunucu bulunuyorsa mümkündür. Ağınızdan bunu talep etmek için dhcpcd kullanabilirsiniz:
DHCP requires that a server be running on the same Layer 2 (Ethernet) segment as the client requesting a lease. DHCP is often used on RFC1918 (private) networks, but is also used to acquire public IP information from ISPs.
Official Gentoo boot media runs dhcpcd automatically at startup. This behavior can be disabled by adding the
nodhcp argument to the boot media kernel commandline.If it is not already running, dhcpcd can be started on enp1s0 with:
root #dhcpcd eth0Bazı ağ yöneticileri sistemlerde DHCP sunucudan verilen makine isimlerinin kullanılmasını isteyebilir, bu durumda:
root #dhcpcd -HD eth0To stop dhcpcd, -x can be used:
root #dhcpcd -xsending signal Term to pid 10831 waiting for pid 10831 to exit
Dhcpcd usage
Bağlantıyı test etmek
A properly configured default route is a critical component of Internet connectivity, route configuration can be checked with:
root #ip routedefault via 192.168.0.1 dev enp1s0
If no default route is defined, Internet connectivity is unavailable, and additional configuration is required.
Basic internet connectivity can be confirmed with a ping:
root #ping -c 3 1.1.1.1It's helpful to start by pinging a known IP address instead of a hostname. This can isolate DNS issues from basic Internet connectivity issues.
Outbound HTTPS access and DNS resolution can be confirmed with:
root #curl --location gentoo.org --output /dev/nullEğer bağlanabildiyseniz, bu makaleyi geçip sonraki adım olan diskleri hazırlama'ya geçebilirsiniz.
If curl reports an error, but Internet-bound pings work, DNS may need configuration.
If Internet connectivity has not been established, first interface information should be verified, then:
- net-setup can be used to assist in network configuration.
- Application specific configuration may be required.
- Manual network configuration can be attempted.
Obtaining interface info
If networking doesn't work out of the box, additional steps must be taken to enable Internet connectivity. Generally, the first step is to enumerate host network interfaces.
The ip command, part of the sys-apps/iproute2 package, can be used to query and configure system networking.
The link argument can be used to display network interface links:
root #ip link1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
4: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether e8:40:f2:ac:25:7a brd ff:ff:ff:ff:ff:ffThe address argument can be used to query device address information:
root #ip address2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000<pre>
link/ether e8:40:f2:ac:25:7a brd ff:ff:ff:ff:ff:ff
inet 10.0.20.77/22 brd 10.0.23.255 scope global enp1s0
valid_lft forever preferred_lft forever
inet6 fe80::ea40:f2ff:feac:257a/64 scope link
valid_lft forever preferred_lft foreverThe output of this command contains information for each network interface on the system. Entries begin with the device index, followed by the device name: enp1s0.
Biz dökümanımızda örnek bağlantı ismi olarak eth0 kullanacağız.
Arayüz ismi eth0'dan farklı olabilir. Güncel kurulum ortamlarında donanıma bağlı olarak bu isim eno0, ens1 veya enp5s0 şeklinde de görülebilmekte. Sadece ifconfig çıktısında yerel ağınızla ilişkili bir IP alan ağ bağlantısını arayın.
Optional: Application specific configuration
The following methods are not generally required, but may be helpful in situations where additional configuration is required for Internet connectivity.
Seçime bağlı: Proxy (ağ geçidi) ayarlama
Eğer internete ağ geçidi kullanarak bağlanıyorsanız, doğru olarak yapılandırmanız gerekmektedir. Bu yapılandırma kolaydır, sadece bir değişken tanımlamanız gerektiği anlamına gelir.
Certain text-mode web browsers such as links can also make use of environment variables that define web proxy settings; in particular for the HTTPS access it also will require the https_proxy environment variable to be defined. While Portage will be influenced without passing extra run time parameters during invocation, links will require proxy settings to be set.
Çoğu durumda sunucunuzun adını veya IP adresini kullanarak bir değişken tanımı yetmektedir. Örnek olarak ağ geçidimizin proxy.gentoo.org ve kullandığı portun 8080 olduğunu varsayalım.
The
# symbol in the following commands is a comment. It has been added for clarity only and does not need to be typed when entering the commands.Şimdi (HTTP ve HTTPS trafik için) bir HTTP ağ geçidi yapılandırması yapalım:
root #export http_proxy="http://proxy.gentoo.org:8080"Eğer bu geçitler bir kullanıcı adı ve parola istiyor ise, değişkenleri aşağıdaki şekilde tanımlayabilirsiniz:
http://kullanıcıadı:parola@proxy.gentoo.org:8080
Start links using the following parameters for proxy support:
user $links -http-proxy ${http_proxy} -https-proxy ${https_proxy} FTP ağ geçidi tanımı yapmak için de:
root #export ftp_proxy="ftp://proxy.gentoo.org:8080"Start links using the following parameter for a FTP proxy:
user $links -ftp-proxy ${ftp_proxy} RSYNC ağ geçidi yapılandırması:
root #export RSYNC_PROXY="proxy.gentoo.org:8080"Alternatif: PPP kullanmak
If PPPoE is required for Internet access, the Gentoo boot media includes the pppoe-setup script to simplify ppp configuration.
During setup, pppoe-setup will ask for:
- The name of the Ethernet interface connected to the ADSL modem.
- The PPPoE username and password.
- DNS server IPs.
- Whether or not a firewall is needed.
root #pppoe-setup
root #pppoe-startIn the event of failure, credentials in /etc/ppp/pap-secrets or /etc/ppp/chap-secrets should be verified. If credentials are correct, PPPoE Ethernet interface selection should be checked.
Alternatif: PPTP kullanmak
PPTP desteği gerekliyse, kurulum CD'sinde sağlanan pptpclient komutunu kullanın. Ancak öncelikle yapılandırmanın doğru olduğuna emin olun. Bunun için /etc/ppp/pap-secrets veya /etc/ppp/chap-secrets dosyalarını kontrol edip doğru kullanıcı adı/parola girili olduğuna emin olun:
Edit /etc/ppp/pap-secrets or /etc/ppp/chap-secrets so it contains the correct username/password combination:
root #nano -w /etc/ppp/chap-secretsArdından gerekli ise /etc/ppp/options.pptp dosyasını düzenleyin:
root #nano -w /etc/ppp/options.pptpTamamladıysanız sunucuya bağlanmak için pptp komutunu çalıştırın:
root #pptp <sunucu ip'si>Kablosuz bağlantı için hazırlık
Do not use WEP unless it is the only option. WEP provides essentially no security over an open network.
iwconfig komutuna verilen destek mimariye göre değişebilir. Eğer kullandığınız mimaride bu komutu bulamazsanız, linux-wlan-ng projesindeki yönergeleri uygulayın.Kablosuz (802.11) bir ağ kartı kullanıyorsanız, ilerlemeden önce kablosuz yapılandırmasını düzenlemeniz gerekmekte. Mevcut durumu görmek için iwconfig kullanabilirsiniz. Çıktı şuna benzeyecektir:
root #iwconfig eth0eth0 IEEE 802.11-DS ESSID:"GentooNode"
Mode:Managed Frequency:2.442GHz Access Point: 00:09:5B:11:CC:F2
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:25/10 Signal level:-51 dBm Noise level:-102 dBm
Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx
excessive retries:237 Invalid misc:350282 Missed beacon:84
To check for a current connection:
root #iw dev wlp9s0 linkNot connected.
or
root #iw dev wlp9s0 linkConnected to 00:00:00:00:00:00 (on wlp9s0) SSID: GentooNode freq: 2462 RX: 3279 bytes (25 packets) TX: 1049 bytes (7 packets) signal: -23 dBm tx bitrate: 1.0 MBit/s
Bazı kablosuz ağ donanımları eth0 yerine wlan0 veya ra0 olarak görülebilir. Tüm tanınan donanımları görmek için parametre vermeden sadece
iwconfig çalıştırın.Çoğu kullanıcı için, değiştirilecek iki ayar yeterli olacaktır. ESSID (kablosuz ağ adı) ve WEP anahtarı. Eğer şifresiz bağlantı kullanıyorsanız ve erişim noktası adı komut çıktısında varsa, zaten bağlısınız demektir.
ESSID değiştirmek veya WEP anahtarı eklemek için aşağıdaki komutları kullanabilirsiniz.
- Bağlanacağınız ağın ismi EvAgiise:
root #iwconfig eth0 essid EvAgi- Hex WEP anahtarı atamak için:
root #iwconfig eth0 key 1234123412341234abcdWEP anahtarını ASCII vermek için kodun önüne s: ekleyebilirsiniz:
root #iwconfig eth0 key s:some-passwordroot #iw dev wlp9s0 connect -w GentooNode
- To connect with a hex WEP key, prefix the key with
d::
root #iw dev wlp9s0 connect -w GentooNode key 0:d:1234123412341234abcd
- To connect with an ASCII WEP key:
root #iw dev wlp9s0 connect -w GentooNode key 0:some-password
Eğer kablosuz ağda WPA veya WPA2 şifreleme varsa
wpa_supplicant kullanılmalıdır. Gentoo Linux üzerinde kablosuz ağ yapılandırması hakkında daha detaylı bilgi için lütfen rehberdeki kablosuz ağ bölümünü okuyun.iwconfig komutunu tekrar çalıştırarak değişiklikleri kontrol edin. Yapılandırma doğruysa, IP katmanındaki ağ ayarlarını yapılandırmak için (ağ terminolojisini anlamak) bölümünü okuyun veya önceden anlattığımız net-setup aracını kullanın.
Otomatik ağ yapılandırması
In cases where automatic network configuration is unsuccessful, the Gentoo boot media provides scripts to aid in network configuration. net-setup can be used to configure wireless network information and static IPs.
root #net-setup eth0net-setup komutu bağlantı ortamıyla ilgili bazı sorular soracaktır. Tmamlandığında ağ bağlantısının başlaması beklenir. Önceki adımlarda anlatıldığı gibi, bağlantınızı test edin. Eğer bağlandıysanız, tebrikler! Sayfanın devamını es geçip, diskleri hazırlama adımına gidebilirsiniz.
Network status should be tested after any configuration steps are taken. In the event that configuration scripts do not work, manual network configuration is required.
Ağ terminolojisini anlamak
If all of the above fails, the network must be configured manually. This is not particularly difficult, but should be done with consideration. This section serves to clarify terminology and introduce users to basic networking concepts pertaining to manually configuring an Internet connection.
Some CPE (Carrier Provided Equipment) combines the functions of a router, access point, modem, DHCP server, and DNS server into one unit. It's important to differentiate the functions of a device from the physical appliance.
Interfaces and addresses
Network interfaces are logical representations of network devices. An interface needs an address to communicate with other devices on the network. While only a single address is required, multiple addresses can be assigned to a single interface. This is especially useful for dual stack (IPv4 + IPv6) configurations.
For consistency, this primer will assume the interface enp1s0 will be using the address 192.168.0.2.
IP addresses can be set arbitrarily. As a result, it's possible for multiple devices to use the same IP address, resulting in an address conflict. Address conflicts should be avoided by using DHCP or SLAAC.
IPv6 typically uses StateLess Address AutoConfiguration (SLAAC) for address configuration. In most cases, manually setting IPv6 addresses is a bad practice. If a specific address suffix is preferred, interface identification tokens can be used.
Networks and CIDR
Once an address is chosen, how does a device know how to talk to other devices?
IP addresses are associated with networks. IP networks are contiguous logical ranges of addresses.
Classless Inter-Domain Routing or CIDR notation is used to distinguish network sizes.
- The CIDR value, often notated starting with a /, represents the size of the network.
- The formula 2 ^ (32 - CIDR) can be used to calculate network size.
- Once network size is calculated, usable node count must be reduced by 2.
- The first IP in a network is the Network address, and the last is typically the Broadcast address. These addresses are special and cannot be used by normal hosts.
The most common CIDR values are /24, and /32, representing 254 nodes and a single node respectively.
A CIDR of /24 is the de-facto default network size. This corresponds to a subnet mask of 255.255.255.0, where the last 8 bits are reserved for IP addresses for nodes on a network.
The notation: 192.168.0.2/24 can be interpreted as:
- The address 192.168.0.2
- On the network 192.168.0.0
- With a size of 254 (2 ^ (32 - 24) - 2)
- Usable IPs are in the range 192.168.0.1 - 192.168.0.254
- With a broadcast address of 192.168.0.255
- In most cases, the last address on a network is used as the broadcast address, but this can be changed.
Using this configuration, a device should be able to communicate with any host on the same network (192.168.0.0).
The Internet
Once a device is on a network, how does it know how to talk to devices on the Internet?
To communicate with devices outside of local networks, routing must be used. A router is simply a network device that forwards traffic for other devices. The term default route or gateway typically refers to whatever device on the current network is used for external network access.
It's a standard practice to make the gateway the first or last IP on a network.
If an Internet-connected router is available at 192.168.0.1, it can be used as the default route, granting Internet access.
To summarize:
- Interfaces must be configured with an address and network information, such as the CIDR value.
- Local network access is used to access a router on the same network.
- The default route is configured, so traffic destined for external networks is forwarded to the gateway, providing Internet access.
The Domain Name System
Remembering IPs is hard. The Domain Name System was created to allow mapping between Domain Names and IP addresses.
Linux systems use /etc/resolv.conf to define nameservers to be used for DNS resolution.
Many routers can also function as a DNS server, and using a local DNS server can augment privacy and speed up queries through caching.
Many ISPs run a DNS server that is generally advertised to the gateway over DHCP. Using a local DNS server tends to improve query latency, but most public DNS servers will return the same results, so server usage is largely based on preference.
Elle ağ yapılandırma
Interface address configuration
When manually configuring IP addresses, the local network topology must be considered. IP addresses can be set arbitrarily; conflicts may cause network disruption.
To configure enp1s0 with the address 192.168.0.2 and CIDR /24:
root #ip address add 192.168.0.2/24 dev enp1s0The start of this command can be shortened to ip a.
Default route configuration
Configuring address and network information for an interface will configure link routes, allowing communication with that network segment:
root #ip route192.168.0.0/24 dev enp1s0 proto kernel scope link src 192.168.0.2
This command can be shortened to ip r.
The default route can be set to 192.168.0.1 with:
root #ip route add default via 192.168.0.1DNS configuration
Nameserver info is typically acquired using DHCP, but can be set manually by adding nameserver entries to /etc/resolv.conf.
If dhcpcd is running, changes to /etc/resolv.conf will not persist. Status can be checked with
ps x | grep dhcpcd.nano is included in Gentoo boot media and can be used to edit /etc/resolv.conf with:
root #nano -w /etc/resolv.confLines containing the keyword nameserver followed by a DNS server IP address are queried in order of definition:
/etc/resolv.confUse Quad9 DNS.nameserver 9.9.9.9
nameserver 149.112.112.112
/etc/resolv.confUse Cloudflare DNS.nameserver 1.1.1.1
nameserver 1.0.0.1
DNS status can be checked by pinging a domain name:
root #ping -c 3 gentoo.orgOnce connectivity has been verified, continue with Preparing the disks.