https://wiki.archlinux.org/api.php?action=feedcontributions&user=SteamedFish&feedformat=atomArchWiki - User contributions [en]2024-03-28T10:07:18ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=User:SteamedFish&diff=695590User:SteamedFish2021-09-13T09:09:07Z<p>SteamedFish: Blanked the page</p>
<hr />
<div></div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271818BIND (简体中文)2013-08-20T09:31:45Z<p>SteamedFish: 增加一些配置的解释</p>
<hr />
<div>{{TranslationStatus (简体中文)|BIND|2013-08-20|271792}}<br />
<br />
[[Category:Domain Name System]]<br />
[[en:BIND]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
{{translateme (简体中文)|由[[User:SteamedFish|SteamedFish]]翻译中,尚未完成翻译}}<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
<br />
[[Pacman (简体中文)|安装]][[Official Repositories (简体中文)|官方源]]中的 {{Pkg|bind}}。<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== 缓存 DNS 服务器 ==<br />
<br />
BIND 的默认配置即为缓存 DNS 服务器,可以直接使用。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 并且在 ''options'' 中加上下面的这一行,来只允许来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
如果你想开放外网的查询,你需要编译 {{ic|/etc/named.conf}} 并且将<br />
allow-recursion { 127.0.0.1; };<br />
修改为<br />
allow-recursion { any; };<br />
<br />
你可以编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|重启]] '''named''' 守护进程。<br />
<br />
== 权威 DNS 服务器 ==<br />
<br />
下面是一个如何设置自己的权威域的简单教程,假设我们要用的权威域为 "domain.tld" (请替换成自己真实的域)<br />
<br />
更详尽的教程参见 [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. 设置一个 zone 文件 ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL 定义了这个文件里面的记录在未指定情况下默认的 TTL, 单位是秒。在这个例子中,默认 TTL 为2小时<br />
<br />
每次修改 zone 文件的时候,都需要将 Serial 加一,然后再重启 named, 否则 BIND 主服务器不会将 zone 文件的变更发送给从服务器。让主服务器将变更发送给从服务器的条件是主服务器上的 zone 文件的 Serial 比从服务器的大。<br />
<br />
<br />
=== 2. 配置主服务器 ===<br />
<br />
将你的 zone 文件加到 {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
如果你想让 BIND 仅仅作为权威服务器使用,不做递归查询,你可以在 {{ic|/etc/named.conf}} 的 "options" 中关掉递归查询:<br />
recursion no;<br />
<br />
重启 "named"<br />
<br />
=== 3. 配置从服务器 ===<br />
<br />
TODO<br />
<br />
== 仅转发 DNS 服务器 ==<br />
<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271815BIND (简体中文)2013-08-20T09:00:54Z<p>SteamedFish: 增加 TranslationStatus 模板和 en:BIND</p>
<hr />
<div>{{TranslationStatus (简体中文)|BIND|2013-08-20|271792}}<br />
<br />
[[Category:Domain Name System]]<br />
[[en:BIND]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
{{translateme (简体中文)|由[[User:SteamedFish|SteamedFish]]翻译中,尚未完成翻译}}<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
<br />
[[Pacman (简体中文)|安装]][[Official Repositories (简体中文)|官方源]]中的 {{Pkg|bind}}。<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== 缓存 DNS 服务器 ==<br />
<br />
BIND 的默认配置即为缓存 DNS 服务器,可以直接使用。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 并且在 ''options'' 中加上下面的这一行,来只允许来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
如果你想开放给外网查询,建议在 {{ic|/etc/named.conf}} 的 "options" 中加上下面的几行,来防止其他人查询到你的系统信息<br />
version none;<br />
hostname none;<br />
server-id none;<br />
<br />
你可以编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|重启]] '''named''' 守护进程。<br />
<br />
== 权威 DNS 服务器 ==<br />
<br />
下面是一个如何设置自己的权威域的简单教程,假设我们要用的权威域为 "domain.tld" (请替换成自己真实的域)<br />
<br />
更详尽的教程参见 [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. 设置一个 zone 文件 ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL 定义了这个文件里面的记录在未指定情况下默认的 TTL, 单位是秒。在这个例子中,默认 TTL 为2小时<br />
<br />
每次修改 zone 文件的时候,都需要将 Serial 加一,然后再重启 named, 否则 BIND 主服务器不会将 zone 文件的变更发送给从服务器。让主服务器将变更发送给从服务器的条件是主服务器上的 zone 文件的 Serial 比从服务器的大。<br />
<br />
<br />
=== 2. 配置主服务器 ===<br />
<br />
将你的 zone 文件加到 {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
如果你想让 BIND 仅仅作为权威服务器使用,不做递归查询,你可以在 {{ic|/etc/named.conf}} 的 "options" 中关掉递归查询:<br />
recursion no;<br />
<br />
重启 "named"<br />
<br />
=== 3. 配置从服务器 ===<br />
<br />
TODO<br />
<br />
== 仅转发 DNS 服务器 ==<br />
<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271811BIND (简体中文)2013-08-20T08:38:52Z<p>SteamedFish: /* 缓存 DNS 服务器 */ 修改解释</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
{{translateme (简体中文)|由[[User:SteamedFish|SteamedFish]]翻译中,尚未完成翻译}}<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
<br />
[[Pacman (简体中文)|安装]][[Official Repositories (简体中文)|官方源]]中的 {{Pkg|bind}}。<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== 缓存 DNS 服务器 ==<br />
<br />
BIND 的默认配置即为缓存 DNS 服务器,可以直接使用。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 并且在 ''options'' 中加上下面的这一行,来只允许来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
如果你想开放给外网查询,建议在 {{ic|/etc/named.conf}} 的 "options" 中加上下面的几行,来防止其他人查询到你的系统信息<br />
version none;<br />
hostname none;<br />
server-id none;<br />
<br />
你可以编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|重启]] '''named''' 守护进程。<br />
<br />
== 权威 DNS 服务器 ==<br />
<br />
下面是一个如何设置自己的权威域的简单教程,假设我们要用的权威域为 "domain.tld" (请替换成自己真实的域)<br />
<br />
更详尽的教程参见 [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. 设置一个 zone 文件 ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL 定义了这个文件里面的记录在未指定情况下默认的 TTL, 单位是秒。在这个例子中,默认 TTL 为2小时<br />
<br />
每次修改 zone 文件的时候,都需要将 Serial 加一,然后再重启 named, 否则 BIND 主服务器不会将 zone 文件的变更发送给从服务器。让主服务器将变更发送给从服务器的条件是主服务器上的 zone 文件的 Serial 比从服务器的大。<br />
<br />
<br />
=== 2. 配置主服务器 ===<br />
<br />
将你的 zone 文件加到 {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
如果你想让 BIND 仅仅作为权威服务器使用,不做递归查询,你可以在 {{ic|/etc/named.conf}} 的 "options" 中关掉递归查询:<br />
recursion no;<br />
<br />
重启 "named"<br />
<br />
=== 3. 配置从服务器 ===<br />
<br />
TODO<br />
<br />
== 仅转发 DNS 服务器 ==<br />
<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271810BIND (简体中文)2013-08-20T08:37:15Z<p>SteamedFish: 改进已经翻译的内容</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
{{translateme (简体中文)|由[[User:SteamedFish|SteamedFish]]翻译中,尚未完成翻译}}<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
<br />
[[Pacman (简体中文)|安装]][[Official Repositories (简体中文)|官方源]]中的 {{Pkg|bind}}。<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== 缓存 DNS 服务器 ==<br />
<br />
下面的过程将 BIND 配置成仅供本地使用的缓存 DNS 服务器。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 并且在 ''options'' 中加上下面的这一行,来只允许来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
如果你想开放给外网查询,建议在 {{ic|/etc/named.conf}} 的 "options" 中加上下面的几行,来防止其他人查询到你的系统信息<br />
version none;<br />
hostname none;<br />
server-id none;<br />
<br />
编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|重启]] '''named''' 守护进程。<br />
<br />
== 权威 DNS 服务器 ==<br />
<br />
下面是一个如何设置自己的权威域的简单教程,假设我们要用的权威域为 "domain.tld" (请替换成自己真实的域)<br />
<br />
更详尽的教程参见 [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. 设置一个 zone 文件 ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL 定义了这个文件里面的记录在未指定情况下默认的 TTL, 单位是秒。在这个例子中,默认 TTL 为2小时<br />
<br />
每次修改 zone 文件的时候,都需要将 Serial 加一,然后再重启 named, 否则 BIND 主服务器不会将 zone 文件的变更发送给从服务器。让主服务器将变更发送给从服务器的条件是主服务器上的 zone 文件的 Serial 比从服务器的大。<br />
<br />
<br />
=== 2. 配置主服务器 ===<br />
<br />
将你的 zone 文件加到 {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
如果你想让 BIND 仅仅作为权威服务器使用,不做递归查询,你可以在 {{ic|/etc/named.conf}} 的 "options" 中关掉递归查询:<br />
recursion no;<br />
<br />
重启 "named"<br />
<br />
=== 3. 配置从服务器 ===<br />
<br />
TODO<br />
<br />
== 仅转发 DNS 服务器 ==<br />
<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271809BIND (简体中文)2013-08-20T08:22:05Z<p>SteamedFish: 继续部分翻译</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
{{translateme (简体中文)|由[[User:SteamedFish|SteamedFish]]翻译中,尚未完成翻译}}<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
下面的过程是简单的安装 BIND 并且将其配置成仅供本地使用的缓存 DNS 服务器。<br />
<br />
[[Pacman (简体中文)|安装]][[Official Repositories (简体中文)|官方源]]中的 {{Pkg|bind}}。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 加上下面的这一行,来只允许来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== 一个权威域的配置模板 ==<br />
<br />
下面是一个如何设置自己的权威域的简单教程,假设我们要用的权威域为 "domain.tld" (请替换成自己真实的域)<br />
<br />
更详尽的教程参见 [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. 设置一个 zone 文件 ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL 定义了这个文件里面的记录在未指定情况下默认的 TTL, 单位是秒。在这个例子中,默认 TTL 为2小时<br />
<br />
每次修改 zone 文件的时候,都需要将 Serial 加一,然后再重启 named, 否则 BIND 主服务器不会将 zone 文件的变更发送给从服务器。让主服务器将变更发送给从服务器的条件是主服务器上的 zone 文件的 Serial 比从服务器的大。<br />
<br />
<br />
=== 2. 配置主服务器 ===<br />
将你的 zone 文件加到 {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
重启 "named"<br />
<br />
== BIND as simple DNS forwarder ==<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271806BIND (简体中文)2013-08-20T08:11:29Z<p>SteamedFish: add template to notice that this page is being translating from English page</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
{{translateme (简体中文)|由[[User:SteamedFish|SteamedFish]]翻译中,尚未完成翻译}}<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
These few steps show you how to install BIND and set it up as a local caching-only server.<br />
<br />
[[Pacman (简体中文)|安装]][[Official Repositories (简体中文)|官方源]]中的 {{Pkg|bind}}。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 加上下面的这一行,来只允许来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== A configuration template for running a domain ==<br />
This is a simple tutorial in howto setup a simple home network DNS-server with bind. In our example we use "domain.tld" as our domain.<br />
<br />
For a more elaborate example see [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. Creating a zonefile ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL defines the default time-to-live in seconds for all record types. In this example it is 2 hours.<br />
<br />
Serial must be incremented manually before restarting named every time you change a resource record for the zone. If you forget to do it slaves will not re-transfer the zone: they only do it if the serial is greater than that of the last time they transferred the zone.<br />
<br />
=== 2. Configuring master server ===<br />
Add your zone to {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
Restart the daemon and you are done.<br />
<br />
== BIND as simple DNS forwarder ==<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=User:SteamedFish&diff=271803User:SteamedFish2013-08-20T08:04:35Z<p>SteamedFish: Change My Information</p>
<hr />
<div>NetEase.com, Inc</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271802ArchWiki:Translation Team (简体中文)2013-08-20T08:02:57Z<p>SteamedFish: /* 贡献列表 */ 增加 SteamedFish</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[en:ArchWiki Translation Team]]<br />
[[es:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[tr:ArchWiki_Çeviri_Ekibi]]<br />
Arch Wiki 上有许多中文页面,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果希望进行翻译和维护,只需要编辑下面的[[#页面维护列表]],将自己加为页面的维护者。如果列表中还没有要认领翻译的页面,请自行添加。如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{注意|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin |登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表 | 页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接 (参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-CN}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,即时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[https://wiki.archlinux.org/index.php/Special:WhatLinksHere/Template:TranslationStatus_(简体中文) 模板的反向链接]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
需要优先翻译的页面:<br />
* [[Systemd/User]]<br />
* [[netctl]]<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
| <br />
|-<br />
| [[ACPI modules (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Activating Numlock on Bootup (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Ad-hoc networking (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 部分未翻译<br />
|-<br />
| [[AHCI (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Allow Users to Shutdown (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[aMule (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Android (简体中文)]]<br />
| 完成<br />
| Stlt1sean<br />
| 无<br />
|-<br />
| [[Apache, suEXEC and Virtual Hosts (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Arch Based Distributions (Active) (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[Arch Build System (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[ArchWiki:About (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 过期<br />
| 无<br />
| 请优先翻译此文<br />
|-<br />
| [[AUR Helpers (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Avant Window Navigator (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[Bash (简体中文)]]<br />
| 完成<br />
| Jaurung<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 翻译中<br />
| SteamedFish<br />
| 无<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[Common Applications (简体中文)]]<br />
| 翻译中<br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Configuring Network (简体中文)]]<br />
| 完成<br />
| Stlt1sean<br />
| 无<br />
|-<br />
| [[Core Utilities (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[CPU Frequency Scaling (简体中文)]]<br />
| 完成<br />
| Flockyrocky<br />
| <br />
|-<br />
| [[Creating Packages (简体中文)]]<br />
| 完成<br />
| Cael<br />
| 无<br />
|-<br />
| [[Disabling IPv6 (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Downgrading Packages (简体中文)]]<br />
| 完成<br />
| Cael<br />
| 无<br />
|-<br />
| [[E17 (简体中文)]]<br />
| 完成<br />
| Aaron_chen<br />
| 同步翻译至2012年12月24日18:00英文页面<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
|-<br />
| [[Font Configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Fstab (简体中文)]]<br />
| 完成<br />
| Fengchao<br />
| 无<br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 翻译中<br />
| 无<br />
| 无<br />
|-<br />
| [[Help:Style (简体中文)]]<br />
| 完成<br />
| Fengchao<br />
| 无<br />
|-<br />
| [[i3 (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[IBus (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 请优先翻译此文<br />
|-<br />
| [[Improve_Pacman_Performance_(简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Intel Graphics (简体中文)]]<br />
| 完成<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 完成<br />
| Stlt1sean<br />
| 无<br />
|-<br />
| [[Kernel Compilation (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Kernel Compilation/Arch Build System (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[Laptop Mode Tools (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Lenovo ThinkPad T420 (简体中文)]]<br />
| 完成<br />
| Flockyrocky<br />
| 无<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Makepkg (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[mkinitcpio (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[NetworkManager (简体中文)]] || 部分翻译 || 无 || 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 部分未翻译<br />
|-<br />
| [[Official Repositories (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Openbox (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pacman (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[pacman Tips (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|- <br />
| [[Plasma (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|- <br />
| [[Polipo (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无 <br />
|-<br />
| [[Python (简体中文)]]<br />
| 完成<br />
| Fengchao<br />
| 无 <br />
|-<br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Reporting_Bug_Guidelines_(简体中文)]]<br />
| 翻译中<br />
| Jason Zhang<br />
| <br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 部分未翻译<br />
|-<br />
| [[Systemd (简体中文)]]<br />
| 完成<br />
| cuihao<br />
| 无<br />
|-<br />
| [[TeXLive (简体中文)]]<br />
| 完成<br />
| reverland<br />
| 无<br />
|-<br />
| [[USB Installation Media (简体中文)]]<br />
| 完成<br />
| Stlt1sean <br />
| 无<br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| yukirock<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译中<br />
| Carl X. Su<br />
| 请优先翻译此文<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 翻译中<br />
| Jason Zhang<br />
| 无<br />
|-<br />
| [[Wine (简体中文)]]<br />
| 完成<br />
| cuihao<br />
| 无<br />
|- <br />
| [[Xfce (简体中文)]] || 翻译中 || ZaticWu || 请优先翻译<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 未翻译<br />
| Rns<br />
| 翻译中<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[Xscreensaver (简体中文)]]<br />
| 完成<br />
| liuyix<br />
| 无<br />
|-<br />
| [[LXDE (简体中文)]]<br />
| 翻译中<br />
| Tuxzz<br />
| 无<br />
|}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
== 贡献列表 ==<br />
为翻译做出贡献的用户请加入列表,感谢所有人做出的贡献。<br />
* [[User:Fengchao|Fengchao]] &ndash; [[Special:Contributions/Fengchao|贡献]] &ndash; [[Special:EmailUser/Fengchao|Send Email]] &ndash; [[ArchWiki:Administrators|ArchWiki Administrators]]<br />
* [[User:Skydiver|Skydiver]] &ndash; [[Special:Contributions/Skydiver|贡献]] &ndash; [[Special:EmailUser/Skydiver|Send Email]] &ndash; [[ArchWiki:Maintainers|ArchWiki Maintainers]]<br />
* [[User:Alswl|Alswl]] &ndash; [[Special:Contributions/Alswl|贡献]] &ndash; [[Special:EmailUser/Alswl|Send Email]]<br />
* [[User:Reverland|Reverland]] &ndash; [[Special:Contributions/Reverland|贡献]] &ndash; [[Special:EmailUser/Reverland|Send Email]]<br />
* [[User:Cuihao|cuihao]] &ndash; [[Special:Contributions/Cuihao|贡献]] &ndash; [[Special:EmailUser/Cuihao|Send Email]]<br />
* [[User:Cael|Cael]] &ndash; [[Special:Contributions/Cael|贡献]] &ndash; [[Special:EmailUser/Cael|Send Email]]<br />
* [[User:Flockyrocky|Flockyrocky]] &ndash; [[Special:Contributions/Flockyrocky|贡献]] &ndash; [[Special:EmailUser/Flockyrocky|Send Email]]<br />
* [[User:Tuxzz|Tuxzz]] &ndash; [[Special:Contributions/Tuxzz|贡献]] &ndash; [[Special:EmailUser/Tuxzz|Send Email]]<br />
* [[User:Aaron_chen|Aaron_chen]] &ndash; [[Special:Contributions/Aaron_chen|贡献]] &ndash; [[Special:E17/Aaron_chen|Send Email]]<br />
* [[User:Shibao Zhao|Shibao Zhao]] &ndash; [[Special:Contributions/Shibao Zhao|贡献]] &ndash; [[Special:EmailUser/Shibao Zhao|Send Email]] &ndash;<br />
* [[User:Radflum|Yk]] &ndash; [[Special:Contributions/Radflum|贡献]] &ndash; [[Special:EmailUser/Radflum|Send Email]]<br />
* [[User:Hang yan|Hang yan]] &ndash; [[Special:Contributions/Hang yan|贡献]] &ndash; [[Special:EmailUser/Hang yan|Send Email]]<br />
* [[User:Acgtyrant|Acgtyrant]] &ndash; [[Special:Contributions/Acgtyrant|贡献]] &ndash; [[Special:EmailUser/Acgtyrant|Send Email]]<br />
* [[User:Xuchunyang|Xuchunyang]] &ndash; [[Special:Contributions/Acgtyrant|贡献]] &ndash; [[Special:EmailUser/Acgtyrant|Send Email]]<br />
* [[User:Stlt1sean|Stlt1sean]] &ndash; [[Special:Contributions/Stlt1sean|贡献]] &ndash; [[Special:EmailUser/Stlt1sean|Send Email]]<br />
* [[User:Carl_tw|Carl X. Su]] &ndash; [[Special:Contributions/Carl_tw|贡献]] &ndash; [[Special:EmailUser/Carl_tw|Send Email]]<br />
* [[User:SteamedFish|SteamedFish]] &ndash; [[Special:Contributions/SteamedFish|贡献]] &ndash; [[Special:EmailUser/SteamedFish|Send Email]]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271801ArchWiki:Translation Team (简体中文)2013-08-20T08:01:41Z<p>SteamedFish: /* 页面维护列表 */ 增加 BIND (简体中文)</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[en:ArchWiki Translation Team]]<br />
[[es:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[tr:ArchWiki_Çeviri_Ekibi]]<br />
Arch Wiki 上有许多中文页面,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果希望进行翻译和维护,只需要编辑下面的[[#页面维护列表]],将自己加为页面的维护者。如果列表中还没有要认领翻译的页面,请自行添加。如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{注意|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin |登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表 | 页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接 (参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-CN}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,即时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[https://wiki.archlinux.org/index.php/Special:WhatLinksHere/Template:TranslationStatus_(简体中文) 模板的反向链接]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
需要优先翻译的页面:<br />
* [[Systemd/User]]<br />
* [[netctl]]<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
| <br />
|-<br />
| [[ACPI modules (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Activating Numlock on Bootup (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Ad-hoc networking (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 部分未翻译<br />
|-<br />
| [[AHCI (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Allow Users to Shutdown (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[aMule (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Android (简体中文)]]<br />
| 完成<br />
| Stlt1sean<br />
| 无<br />
|-<br />
| [[Apache, suEXEC and Virtual Hosts (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Arch Based Distributions (Active) (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[Arch Build System (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[ArchWiki:About (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 过期<br />
| 无<br />
| 请优先翻译此文<br />
|-<br />
| [[AUR Helpers (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Avant Window Navigator (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[Bash (简体中文)]]<br />
| 完成<br />
| Jaurung<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 翻译中<br />
| SteamedFish<br />
| 无<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[Common Applications (简体中文)]]<br />
| 翻译中<br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Configuring Network (简体中文)]]<br />
| 完成<br />
| Stlt1sean<br />
| 无<br />
|-<br />
| [[Core Utilities (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[CPU Frequency Scaling (简体中文)]]<br />
| 完成<br />
| Flockyrocky<br />
| <br />
|-<br />
| [[Creating Packages (简体中文)]]<br />
| 完成<br />
| Cael<br />
| 无<br />
|-<br />
| [[Disabling IPv6 (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Downgrading Packages (简体中文)]]<br />
| 完成<br />
| Cael<br />
| 无<br />
|-<br />
| [[E17 (简体中文)]]<br />
| 完成<br />
| Aaron_chen<br />
| 同步翻译至2012年12月24日18:00英文页面<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
|-<br />
| [[Font Configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Fstab (简体中文)]]<br />
| 完成<br />
| Fengchao<br />
| 无<br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 翻译中<br />
| 无<br />
| 无<br />
|-<br />
| [[Help:Style (简体中文)]]<br />
| 完成<br />
| Fengchao<br />
| 无<br />
|-<br />
| [[i3 (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[IBus (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 请优先翻译此文<br />
|-<br />
| [[Improve_Pacman_Performance_(简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Intel Graphics (简体中文)]]<br />
| 完成<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 完成<br />
| Stlt1sean<br />
| 无<br />
|-<br />
| [[Kernel Compilation (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Kernel Compilation/Arch Build System (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[Laptop Mode Tools (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[Lenovo ThinkPad T420 (简体中文)]]<br />
| 完成<br />
| Flockyrocky<br />
| 无<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Makepkg (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[mkinitcpio (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[NetworkManager (简体中文)]] || 部分翻译 || 无 || 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 部分未翻译<br />
|-<br />
| [[Official Repositories (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Openbox (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pacman (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|-<br />
| [[pacman Tips (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|- <br />
| [[Plasma (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 无<br />
|- <br />
| [[Polipo (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无 <br />
|-<br />
| [[Python (简体中文)]]<br />
| 完成<br />
| Fengchao<br />
| 无 <br />
|-<br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Reporting_Bug_Guidelines_(简体中文)]]<br />
| 翻译中<br />
| Jason Zhang<br />
| <br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 未翻译<br />
| 无<br />
| 部分未翻译<br />
|-<br />
| [[Systemd (简体中文)]]<br />
| 完成<br />
| cuihao<br />
| 无<br />
|-<br />
| [[TeXLive (简体中文)]]<br />
| 完成<br />
| reverland<br />
| 无<br />
|-<br />
| [[USB Installation Media (简体中文)]]<br />
| 完成<br />
| Stlt1sean <br />
| 无<br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| yukirock<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译中<br />
| Carl X. Su<br />
| 请优先翻译此文<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 翻译中<br />
| Jason Zhang<br />
| 无<br />
|-<br />
| [[Wine (简体中文)]]<br />
| 完成<br />
| cuihao<br />
| 无<br />
|- <br />
| [[Xfce (简体中文)]] || 翻译中 || ZaticWu || 请优先翻译<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 未翻译<br />
| Rns<br />
| 翻译中<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 完成<br />
| acgtyrant<br />
| 无<br />
|-<br />
| [[Xscreensaver (简体中文)]]<br />
| 完成<br />
| liuyix<br />
| 无<br />
|-<br />
| [[LXDE (简体中文)]]<br />
| 翻译中<br />
| Tuxzz<br />
| 无<br />
|}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
== 贡献列表 ==<br />
为翻译做出贡献的用户请加入列表,感谢所有人做出的贡献。<br />
* [[User:Fengchao|Fengchao]] &ndash; [[Special:Contributions/Fengchao|贡献]] &ndash; [[Special:EmailUser/Fengchao|Send Email]] &ndash; [[ArchWiki:Administrators|ArchWiki Administrators]]<br />
* [[User:Skydiver|Skydiver]] &ndash; [[Special:Contributions/Skydiver|贡献]] &ndash; [[Special:EmailUser/Skydiver|Send Email]] &ndash; [[ArchWiki:Maintainers|ArchWiki Maintainers]]<br />
* [[User:Alswl|Alswl]] &ndash; [[Special:Contributions/Alswl|贡献]] &ndash; [[Special:EmailUser/Alswl|Send Email]]<br />
* [[User:Reverland|Reverland]] &ndash; [[Special:Contributions/Reverland|贡献]] &ndash; [[Special:EmailUser/Reverland|Send Email]]<br />
* [[User:Cuihao|cuihao]] &ndash; [[Special:Contributions/Cuihao|贡献]] &ndash; [[Special:EmailUser/Cuihao|Send Email]]<br />
* [[User:Cael|Cael]] &ndash; [[Special:Contributions/Cael|贡献]] &ndash; [[Special:EmailUser/Cael|Send Email]]<br />
* [[User:Flockyrocky|Flockyrocky]] &ndash; [[Special:Contributions/Flockyrocky|贡献]] &ndash; [[Special:EmailUser/Flockyrocky|Send Email]]<br />
* [[User:Tuxzz|Tuxzz]] &ndash; [[Special:Contributions/Tuxzz|贡献]] &ndash; [[Special:EmailUser/Tuxzz|Send Email]]<br />
* [[User:Aaron_chen|Aaron_chen]] &ndash; [[Special:Contributions/Aaron_chen|贡献]] &ndash; [[Special:E17/Aaron_chen|Send Email]]<br />
* [[User:Shibao Zhao|Shibao Zhao]] &ndash; [[Special:Contributions/Shibao Zhao|贡献]] &ndash; [[Special:EmailUser/Shibao Zhao|Send Email]] &ndash;<br />
* [[User:Radflum|Yk]] &ndash; [[Special:Contributions/Radflum|贡献]] &ndash; [[Special:EmailUser/Radflum|Send Email]]<br />
* [[User:Hang yan|Hang yan]] &ndash; [[Special:Contributions/Hang yan|贡献]] &ndash; [[Special:EmailUser/Hang yan|Send Email]]<br />
* [[User:Acgtyrant|Acgtyrant]] &ndash; [[Special:Contributions/Acgtyrant|贡献]] &ndash; [[Special:EmailUser/Acgtyrant|Send Email]]<br />
* [[User:Xuchunyang|Xuchunyang]] &ndash; [[Special:Contributions/Acgtyrant|贡献]] &ndash; [[Special:EmailUser/Acgtyrant|Send Email]]<br />
* [[User:Stlt1sean|Stlt1sean]] &ndash; [[Special:Contributions/Stlt1sean|贡献]] &ndash; [[Special:EmailUser/Stlt1sean|Send Email]]<br />
* [[User:Carl_tw|Carl X. Su]] &ndash; [[Special:Contributions/Carl_tw|贡献]] &ndash; [[Special:EmailUser/Carl_tw|Send Email]]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271800BIND (简体中文)2013-08-20T07:58:11Z<p>SteamedFish: fix typos</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
These few steps show you how to install BIND and set it up as a local caching-only server.<br />
<br />
[[Pacman (简体中文)|安装]][[Official Repositories (简体中文)|官方源]]中的 {{Pkg|bind}}。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 加上下面的这一行,来只允许来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== A configuration template for running a domain ==<br />
This is a simple tutorial in howto setup a simple home network DNS-server with bind. In our example we use "domain.tld" as our domain.<br />
<br />
For a more elaborate example see [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. Creating a zonefile ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL defines the default time-to-live in seconds for all record types. In this example it is 2 hours.<br />
<br />
Serial must be incremented manually before restarting named every time you change a resource record for the zone. If you forget to do it slaves will not re-transfer the zone: they only do it if the serial is greater than that of the last time they transferred the zone.<br />
<br />
=== 2. Configuring master server ===<br />
Add your zone to {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
Restart the daemon and you are done.<br />
<br />
== BIND as simple DNS forwarder ==<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271798BIND (简体中文)2013-08-20T07:57:08Z<p>SteamedFish: fix typo: an extra 's'</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
These few steps show you how to install BIND and set it up as a local caching-only server.<br />
<br />
[[Pacman (简体中文)|安装]] [[Official Repositories (简体中文)|官方源]] 中的 {{Pkg|bind}}。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 加上下面的这一行,来只运行来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== A configuration template for running a domain ==<br />
This is a simple tutorial in howto setup a simple home network DNS-server with bind. In our example we use "domain.tld" as our domain.<br />
<br />
For a more elaborate example see [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. Creating a zonefile ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL defines the default time-to-live in seconds for all record types. In this example it is 2 hours.<br />
<br />
Serial must be incremented manually before restarting named every time you change a resource record for the zone. If you forget to do it slaves will not re-transfer the zone: they only do it if the serial is greater than that of the last time they transferred the zone.<br />
<br />
=== 2. Configuring master server ===<br />
Add your zone to {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
Restart the daemon and you are done.<br />
<br />
== BIND as simple DNS forwarder ==<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271797BIND (简体中文)2013-08-20T07:56:08Z<p>SteamedFish: new page, translate from english, unfinished</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
<br />
伯克利互联网名称服务 Berkeley Internet Name Daemon (BIND) 是 DNS 协议的一个参考实现。<br />
<br />
== 安装 ==<br />
These few steps show you how to install BIND and set it up as a local caching-only server.<br />
<br />
[[Pacman (简体中文)|安装]] [[Official Repositories (简体中文)|官方源s]] 中的 {{Pkg|bind}}。<br />
<br />
你可以编辑 {{ic|/etc/named.conf}} 加上下面的这一行,来只运行来自 localhost 的查询。<br />
listen-on { 127.0.0.1; };<br />
<br />
编辑 {{ic|/etc/resolv.conf}} 让其使用本机作为 DNS 服务器。<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon (简体中文)#管理守护进程|启动]] '''named''' 守护进程。<br />
<br />
== A configuration template for running a domain ==<br />
This is a simple tutorial in howto setup a simple home network DNS-server with bind. In our example we use "domain.tld" as our domain.<br />
<br />
For a more elaborate example see [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. Creating a zonefile ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL defines the default time-to-live in seconds for all record types. In this example it is 2 hours.<br />
<br />
Serial must be incremented manually before restarting named every time you change a resource record for the zone. If you forget to do it slaves will not re-transfer the zone: they only do it if the serial is greater than that of the last time they transferred the zone.<br />
<br />
=== 2. Configuring master server ===<br />
Add your zone to {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
Restart the daemon and you are done.<br />
<br />
== BIND as simple DNS forwarder ==<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=BIND&diff=271792BIND2013-08-20T07:27:42Z<p>SteamedFish: add zh-CN language</p>
<hr />
<div>[[Category:Domain Name System]]<br />
[[de:BIND]]<br />
[[ja:BIND]]<br />
[[zh-CN:BIND]]<br />
Berkeley Internet Name Daemon (BIND) is the reference implementation of the Domain Name System (DNS) protocols.<br />
<br />
== Installation ==<br />
These few steps show you how to install BIND and set it up as a local caching-only server.<br />
<br />
[[pacman|Install]] the {{Pkg|bind}} package which can be found in the [[Official Repositories|official repositories]].<br />
<br />
Optionally edit {{ic|/etc/named.conf}} and add this under the options section, to only allow connections from the localhost:<br />
listen-on { 127.0.0.1; };<br />
<br />
Edit {{ic|/etc/resolv.conf}} to use the local DNS server:<br />
nameserver 127.0.0.1<br />
<br />
[[Daemon#Managing daemons|Start]] the '''named''' daemon.<br />
<br />
== A configuration template for running a domain ==<br />
This is a simple tutorial in howto setup a simple home network DNS-server with bind. In our example we use "domain.tld" as our domain.<br />
<br />
For a more elaborate example see [http://www.howtoforge.com/two_in_one_dns_bind9_views Two-in-one DNS server with BIND9].<br />
<br />
=== 1. Creating a zonefile ===<br />
# nano /var/named/domain.tld.zone<br />
<br />
$TTL 7200<br />
; domain.tld<br />
@ IN SOA ns01.domain.tld. postmaster.domain.tld. (<br />
2007011601 ; Serial<br />
28800 ; Refresh<br />
1800 ; Retry<br />
604800 ; Expire - 1 week<br />
86400 ) ; Minimum<br />
IN NS ns01<br />
IN NS ns02<br />
ns01 IN A 0.0.0.0<br />
ns02 IN A 0.0.0.0<br />
localhost IN A 127.0.0.1<br />
@ IN MX 10 mail<br />
imap IN CNAME mail<br />
smtp IN CNAME mail<br />
@ IN A 0.0.0.0<br />
www IN A 0.0.0.0<br />
mail IN A 0.0.0.0<br />
@ IN TXT "v=spf1 mx"<br />
<br />
$TTL defines the default time-to-live in seconds for all record types. In this example it is 2 hours.<br />
<br />
Serial must be incremented manually before restarting named every time you change a resource record for the zone. If you forget to do it slaves will not re-transfer the zone: they only do it if the serial is greater than that of the last time they transferred the zone.<br />
<br />
=== 2. Configuring master server ===<br />
Add your zone to {{ic|/etc/named.conf}}:<br />
zone "domain.tld" IN {<br />
type master;<br />
file "domain.tld.zone";<br />
allow-update { none; };<br />
notify no;<br />
};<br />
<br />
Restart the daemon and you are done.<br />
<br />
== BIND as simple DNS forwarder ==<br />
If you have problems with, for example, VPN connections, they can sometimes be solved by setting-up a forwarding DNS server. This is very simple with BIND. Add these lines to {{ic|/etc/named.conf}}, and change IP address according to your setup.<br />
listen-on { 192.168.66.1; };<br />
forwarders { 8.8.8.8; 8.8.4.4; };<br />
Don't forget to restart the service!<br />
<br />
== Running BIND in a chrooted environment ==<br />
Running in a [[chroot]] environment is not required but improves security. See [[BIND (chroot)]] for how to do this.<br />
<br />
== Configuring BIND to serve DNSSEC signed zones ==<br />
See [[DNSSEC#BIND (serving signed DNS zones)]]<br />
<br />
== Automatically listen on new interfaces without chroot and root privileges ==<br />
{{Out of date|initscripts have been replaced by systemd}}<br />
Add<br />
interface-interval <rescan-timeout-in-minutes>;<br />
parameter into {{ic|named.conf}} options. Then you should modify rc-script:<br />
<pre><br />
stat_busy "Starting DNS"<br />
- [ -z "$PID" ] && /usr/sbin/named ${NAMED_ARGS}<br />
+ setcap cap_net_bind_service=eip /usr/sbin/named<br />
+ NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
+ [ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
So your {{ic|/etc/rc.d/named}} should look like this:<br />
<pre><br />
stat_busy "Starting DNS"<br />
setcap cap_net_bind_service=eip /usr/sbin/named<br />
NAMED_ARGS=`echo ${NAMED_ARGS} | sed 's#-u [[:alnum:]]*##'`<br />
[ -z "$PID" ] && sudo -u named /usr/sbin/named ${NAMED_ARGS}<br />
</pre><br />
<br />
Change user name in last line (with "... sudo -u named ...") if your named user is not 'named'.<br />
<br />
==See also==<br />
*[[BIND (chroot)]]<br />
<br />
== BIND Resources ==<br />
* [http://www.reedmedia.net/books/bind-dns/ BIND 9 DNS Administration Reference Book]<br />
* [http://www.netwidget.net/books/apress/dns/intro.html Pro DNS and BIND]<br />
* [http://www.isc.org/ Internet Systems Consortium, Inc. (ISC)]<br />
* [http://www.menandmice.com/knowledgehub/dnsglossary DNS Glossary]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Plasma_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=271791Plasma (简体中文)2013-08-20T07:16:45Z<p>SteamedFish: /* 获取新的 plasmoids 组件 */ 翻译</p>
<hr />
<div>[[Category:Desktop environments (简体中文)]]<br />
[[Category:Eye candy (简体中文)]]<br />
[[en:Plasma]]<br />
[[it:Plasma]]<br />
Plasma 是 [[KDE]] 的项目的一个组成部分, actually displays the desktop (i.e. wallpapers, panels, etc) using 'containments'. The containments are capable of containing other widgets called plasmoids.<br />
<br />
==获取新的 plasmoids 组件==<br />
你可以从 [http://www.kde-look.org/index.php?xsortmode=new&logpage=0&xcontentmode=70x77x78&page=0 kde-look.org] 上取得新的 plasmoids 组件。<br />
AUR 中也有很多 plasmoids 组件, 包括 [https://aur.archlinux.org/packages.php?ID=21084 kde-extragear-plasmoids] 。 这个包是从 [http://www.kde-look.org/index.php?xsortmode=new&logpage=0&xcontentmode=70x77x78&page=0 kde-look.org] 获取流行的 plasmoid 并且将它们打成一个包。<br />
<br />
==提示与技巧==<br />
<br />
===Decoupling the Dashboard from the Desktop - the plasma way===<br />
click on top right cashew - zoom out - (new screen, look at new menu top left) configure plasma - use a separate dashboard<br />
===Adding an OSX style or so-called "fancy" panel===<br />
Right click on the desktop - add panel - fancy panel<br />
{{Warning|At the time of writing it is possible to edit a fancy panel extensively but it won't remember any settings.}}<br />
===Having different wallpapers for each side of your cube===<br />
click on top right cashew - zoom out - (new screen, look at new menu top left) configure plasma - different activity for each desktop<br />
===Mixing desktop and folder view activities in one cube===<br />
click on top right cashew - zoom out - (new screen, look at new menu top left) configure plasma - different activity for each desktop</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Talk:Super_Quick_Git_Guide&diff=46962Talk:Super Quick Git Guide2008-08-04T02:07:38Z<p>SteamedFish: forgot to add a signature</p>
<hr />
<div>To switch back to the master branch use:<br />
<br />
git branch master<br />
<br />
<br />
Should it be this?<br />
<br />
git checkout master<br />
<br />
I'm not quite sure. I'm just learning git.<br />
<br />
--[[User:SteamedFish|SteamedFish]] 22:07, 3 August 2008 (EDT)</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Talk:Super_Quick_Git_Guide&diff=46961Talk:Super Quick Git Guide2008-08-04T02:06:38Z<p>SteamedFish: New page: To switch back to the master branch use: git branch master Should it be this? git checkout master I'm not quite sure. I'm just learning git.</p>
<hr />
<div>To switch back to the master branch use:<br />
<br />
git branch master<br />
<br />
<br />
Should it be this?<br />
<br />
git checkout master<br />
<br />
I'm not quite sure. I'm just learning git.</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Pacman_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=35147Pacman (简体中文)2008-01-17T00:45:59Z<p>SteamedFish: Add {{translateme}} for part of it has left untranslated.</p>
<hr />
<div>[[Category:Package Management]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Pacman (Česky)}}<br />
{{i18n_entry|Deutsch|:Pacman (Deutsch)}}<br />
{{i18n_entry|English|:Pacman}}<br />
{{i18n_entry|Español|:Pacman (Español)}}<br />
{{i18n_entry|Français|:Pacman (Français)}}<br />
{{i18n_entry|Italiano|:Pacman (Italiano)}}<br />
{{i18n_entry|Nederlands|:Pacman (Nederlands)}}<br />
{{i18n_entry|Polski|:Pacman (Polski)}}<br />
{{i18n_entry|Português de Portugal|:Pacman (Portugues)}}<br />
{{i18n_entry|Romanian|:Pacman (română)}}<br />
{{i18n_entry|Русский|:Pacman (Русский)}}<br />
{{i18n_entry|简体中文|:Pacman (简体中文)}}<br />
{{i18n_entry|한국어|:Pacman (한국어)}}<br />
{{i18n_links_end}}<br />
<br />
{{translateme}}<br />
==概览==<br />
<br />
'''Pacman'''包管理器是Arch Linux的一大亮点。它将一个简单的二进制包格式和易用的构建系统结合了起来(see [[ABS]])。'''Pacman'''使得简单的管理与自定义软件包成为了可能,而不论他们来自于官方的Arch软件库或是用户自己创建的。软件库系统允许用户构建和维护他们自己的软件包仓库,这样可以鼓励社区的成长与贡献(see [[AUR]])。<br />
<br />
'''Pacman''' can keep a system up to date by synchronizing package lists with the master server, making it a breeze for the security-conscious system administrator to maintain. This server/client model also allows you to download/install packages with a simple command, complete with all required dependencies (similar to Debian's apt-get).<br />
<br />
'''Pacman''' <br />
NB: '''Pacman''' was written and is being maintained by [http://distrowatch.com/dwres.php?resource=interview-arch Judd Vinet], the creator of [[ArchLinux|Arch Linux]]. <br />
But it is used as a package management tool by other distros as well, such as<br />
[http://frugalware.org FrugalWare] (see also [[http://wiki.frugalware.org/FwPacman]]),<br />
[http://www.rubixlinux.org Rubix], [http://www.ufficiozero.org UfficioZero] (in Italian, based on Ubuntu!!), and of course ArchLinux-derivatives such as [http://archie.dotsrc.org Archie] and [http://arch-egis.berlios.de/content.php?article.1 AEGIS].<br />
<br />
==Usage==<br />
'''Pacman''' is both a binary and source package manager. It combines several ideas from FreeBSD, Debian and Slackware to form one of the most extensive yet easy to use package managers available for GNU/Linux. '''Pacman''' is able to download, install and upgrade packages from both remote and local repositories with full dependency handling, and has easy to understand tools for crafting your own packages too.<br />
<br />
'''Pacman''' 包管理器能够管理二进制包和源码包。它吸取了FreeBSD、Debian和Slackware的经验,成为了GNU/Linux最具扩展性,容易使用的包管理器之一。'''Pacman'''能够远程或本地的软件仓库中下载、安装和升级软件包,并且完美地处理包依赖关系,同时拥有容易理解的制作包制作工具。<br />
<br />
===Installing and Removing Packages===<br />
Before installing and upgrading packages, it is a good idea to synchronize the local packages database with the remote repositories.<br />
<br />
安装和升级软件包前,先让本地的包数据库和远程的软件仓库同步是个好习惯。<br />
<br />
pacman -Sy<br />
<br />
To install or upgrade a single package or list of packages (including dependencies), issue the following command:<br />
<br />
安装或者升级单个软件包,或者一列软件包,使用如下命令:<br />
<br />
<br />
pacman -S package_name1 package_name2<br />
<br />
Sometimes there are more versions of a package in different repositories (e.g. extra and testing). You can specify which one to install:<br />
<br />
有时候在不同的软件仓库中,一个软件包有多个版本(比如extra和testing)。你可以选择一个来安装:<br />
<br />
pacman -S extra/package_name<br />
pacman -S testing/package_name<br />
<br />
You can also combine parameters at once, for example this will both synchronize the package database and install a package:<br />
<br />
你也可以组合参数,比如这样将同步包数据库并且安装一个软件包:<br />
<br />
pacman -Sy package_name<br />
<br />
To remove a single package, leaving all of its dependencies installed:<br />
<br />
删除单个软件包,保留其全部已经安装的依赖关系<br />
<br />
pacman -R package_name<br />
<br />
To also remove all of the packages dependencies which aren't used by any other installed package:<br />
<br />
删除指定软件包,及其所有没有被其他已安装软件包使用的依赖关系:<br />
<br />
pacman -Rs package_name<br />
<br />
===Upgrading the System===<br />
===升级系统===<br />
<br />
'''Pacman''' can update all packages on the system with just one command. This could take quite a while depending on how up-to-date your system is.<br />
<br />
'''Pacman'''能够只用一个指令来升级系统中所有已安装的包。升级的时间取决于你的系统有多新。<br />
<br />
pacman -Su<br />
<br />
NB: you can synchronise the repository databases AND update your system in one go with<br />
<br />
NB: 你也可以将升级系统和同步仓库数据合成为一条指令<br />
pacman -Syu<br />
It is actually good practice to run the above command every few days.<br />
<br />
每几天运行一下上面的这条指令确实是一个好习惯。<br />
<br />
===Querying the Package Database===<br />
<br />
'''Pacman''' can search the package database for a list of packages, you can enter part of the package name to search for all packages matching the string.<br />
<br />
pacman -Ss package<br />
<br />
To just search installed packages:<br />
<br />
pacman -Qs package<br />
<br />
Once you know the name of the package you are looking for, you can display some information on the package.<br />
<br />
pacman -Si package <br />
pacman -Qi package<br />
<br />
For a list of files contained in a package:<br />
<br />
pacman -Ql package<br />
<br />
You can also query what package a file on your system belongs to.<br />
<br />
pacman -Qo /path/to/a/file<br />
<br />
===Simultaneously Searching Repositories and Installed Packages===<br />
<br />
You can use the following bash script to do the equivalent of simultaneously calling '''pacman -Ss foo''' and '''pacman -Qs foo''', in order to see which of the packages listed are actually installed on your system. The latter will be flagged with an asterisk.<br />
<br />
#!/bin/bash<br />
<br />
if [ -z "$1" ]; then<br />
echo "usage: pacsearch [regex pattern]"<br />
echo "usage: pacsearch -h|--help"<br />
exit 0<br />
fi<br />
<br />
if [ "$1" = "-h" -o "$1" = "--help" ]; then<br />
echo "usage: pacsearch [regex pattern]"<br />
echo " Like pacman -Ss [regex pattern] but installed packages are flagged with a *"<br />
echo "usage: pacsearch -h|--help"<br />
echo " Prints this message. No other options allowed"<br />
exit 0<br />
fi<br />
<br />
firstchar=`echo "$1" | cut -c1`<br />
if [ $firstchar = "-" ]; then<br />
echo "Sorry, $1 is not a valid option!"<br />
echo "usage: pacsearch [regex pattern]"<br />
echo "usage: pacsearch -h|--help"<br />
exit 0<br />
fi<br />
<br />
instpkg=`pacman -Qs $1 | egrep '^[^ ]' | sed 's|^local/||' | sed 's/ .\+$//'` <br />
syncdump=`mktemp`<br />
pacman -Ss $1 > $syncdump<br />
<br />
for pkg in $instpkg; do<br />
sed -i "s@^\(.\+/$pkg\) @\*\1 @" $syncdump<br />
done<br />
<br />
cat $syncdump<br />
<br />
Save the script somewhere in your path (e.g. ~/bin/) and name it '''pacsearch'''. Make it executable with <br />
chmod a+x pacsearch<br />
<br />
Now if you type for example<br />
pacsearch ^qt<br />
the output could look like this:<br />
extra/qca 1.0-1<br />
QT Cryptography Architecture<br />
extra/qsynth 0.2.5-1<br />
Qt GUI for fluidsynth<br />
*extra/qt 3.3.5-8<br />
The QT gui toolkit.<br />
extra/qt-doc 3.3.5-1<br />
The QT gui toolkit documentation.<br />
extra/qtella 0.6.5-1<br />
Qtella is a Gnutella client for Linux using QT<br />
extra/qtiplot 0.7.7-1<br />
Data analysis and scientific plotting - free clone of Origin<br />
extra/qtparted 0.4.5-3<br />
A Partition Magic clone written in C++ using the Qt toolkit<br />
extra/qwt 4.2.0-3<br />
Qt Widgets for Technical Applications<br />
extra/qwtplot3d 0.2.6-2<br />
Qt/OpenGL-based C++ programming library containing 3d-widgets<br />
<br />
So in this case you would know that none of the above packages are installed on your system except '''qt''' itself.<br />
<br />
'''NB1:''' ''a request has been filed on flyspray to integrate the above functionality in pacman itself, so the 'dirty' bash trick might become superfluous with a future version of pacman.''<br />
<br />
'''NB2:''' ''you can modify the above bash script on the basis of [[Colored_Pacman_output|this wiki]] to have installed packages colored differently in the output.''<br />
<br />
===Other Usage===<br />
<br />
'''Pacman''' is quite an extensive package management tool, below are some other features.<br />
<br />
* Downloading a package without installing it:<br />
pacman -Sw package_name<br />
<br />
* Installing a local package (not from repository):<br />
pacman -A /path/to/package/package_name-version.pkg.tar.gz<br />
<br />
* Cleaning pacman's cache (/var/cache/pacman/pkg):<br />
pacman -Scc<br />
<br />
For a more detailed list of switches please refer to '''pacman --help''' or '''man pacman'''.<br />
<br />
==Configuration==<br />
Pacman configuration is located in <code>/etc/pacman.conf</code>. There are two main sections in the file:<br />
<br />
===General options===<br />
General options are in [options] section.<br />
You can specify here which files should not be upgraded. This is useful for important system files. The syntax is very simple:<br />
<br />
<pre><br />
NoUpgrade = etc/passwd etc/group etc/shadow etc/sudoers<br />
NoUpgrade = etc/fstab etc/raidtab etc/ld.so.conf<br />
NoUpgrade = etc/rc.conf etc/rc.local<br />
NoUpgrade = etc/modprobe.conf etc/modules.conf<br />
NoUpgrade = etc/lilo.conf boot/grub/menu.lst<br />
</pre><br />
<br />
Another useful option is '''IgnorePkg'''. For example if you have modified or patched a certain package, adding it to the IgnorePkg line will prevent pacman from upgrading it when a new version becomes available. But pacman will still warn you about the newest available version, so you can eventually decide to update your customized version. <br />
This option is also useful for LARGE packages like openoffice-base if you want to avoid downloading and updating the whole lot every time there is a minor update in the repository. Since pacman warns you about the latest version anyway, you can decide to upgrade manually if you wish.<br />
<br />
===Repositories===<br />
In this section you define which repositories to use. They can be defined directly there or you can include them from another file. The latter is useful for the official repositories which have a lot of mirrors.<br />
<br />
<pre><br />
[repository-name]<br />
Server = ftp://server.net/repo<br />
</pre><br />
<br />
<pre><br />
[current]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/current<br />
</pre><br />
<br />
For more information please refer to '''man pacman'''.<br />
<br />
==Related links==<br />
[[Boost Pacman]]<br><br />
[[Colored Pacman output]]<br><br />
[[Downgrade packages]]<br><br />
[[Redownloading all installed packages]]<br><br />
[[Server_configuration|Server configuration in pacman.conf]]<br><br />
[[ArchLinux User-community Repository (AUR)]]<br><br />
[[Local repository HOW-TO]]<br><br />
[[Custom local repository with ABS and gensync]]<br><br />
[[Howto Upgrade via Home Network]]<br><br />
[[rucksack]]<br><br />
[[Pacman GUI Frontends]]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Network_configuration_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=35145Network configuration (简体中文)2008-01-16T22:42:20Z<p>SteamedFish: </p>
<hr />
<div>[[Category:Networking (简体中文)|WLPZ]]<br />
[[Category:Getting and installing Arch (简体中文)|WLPZ]]<br />
[[Category:HOWTOs (简体中文)|WLPZ]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Configuring_network}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Статический IP и DHCP}}<br />
{{i18n_entry|Česky|Statická IP a DHCP czech}}<br />
{{i18n_entry|简体中文|网络配置}}<br />
{{i18n_links_end}}<br />
<br />
{{translateme}}<br />
<br />
== 概览 ==<br />
<br />
一个简单的让你的网络工作的指导。<br />
<br />
A simple guide to get your network running.<br />
<br />
<br />
== 加载设备模块 ==<br />
<br />
如果你使用 [[hwdetect]] ,它应该可以检测你的网卡( NIC )模块并在开机时自动加载。<br />
否则的话,你需要根据你的硬件情况,判断哪些模块是需要加载的。<br />
<br />
在网上搜索你的网卡型号,或者尝试着用 Linux LiveCD 来寻找需要的模块的名字──在启动后运行 lsmod 来查看当前加载的所有模块。<br />
<br />
当你知道应该使用哪些模块之后,你可以加载它:<br />
<br />
# modprobe <模块名><br />
<br />
如果你不想/不能使用像 [[hwdetect]] 这样的自动加载工具,你可以把这些模块添加到 <code>/etc/rc.conf</code> 中去,这样你就不用每次开机之后手动加载它。例如,如果 tg3 是你需要的网络模块:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
其他常见的模块是: 8139too ( Realtek 芯片); sis900 ( SiS 卡)。<br />
<br />
If you use [[hwdetect]] it should detect your network card (NIC) module and load it automatically at startup. Otherwise, you will need to know which module is needed for your particular model.<br />
<br />
Search the Web for your card model, or try using a Linux LiveCD to find out the name of the needed module - run [[Linux And Hardware|lsmod]] to show you all currently loaded modules after booting.<br />
<br />
Now when you know which module to use you can load it:<br />
<br />
# modprobe <modulename><br />
<br />
If you don't want / can't use some auto-loader like [[hwdetect]] you can add it into the modules array in <code>/etc/rc.conf</code>, so you don't need to modprobe it everytime you boot. For example, if tg3 is the network module:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
Other common modules are 8139too for cards with the Realtek chipset or sis900 for SiS cards.<br />
<br />
== 配置 IP ==<br />
<br />
=== DHCP (自动获取) IP ===<br />
<br />
在这种情况下,你需要安装 dhcpd 包(绝大多数情况下都是默认安装好的)。这样编辑 <code>/etc/rc.conf</code> :<br />
<br />
eth0="dhcp"<br />
INTERFACES=(eth0)<br />
ROUTES=(!gateway)<br />
<br />
For this, you need the dhcpcd package (usually already available on most installation). Edit <code>/etc/rc.conf</code> like this:<br />
<br />
eth0="dhcp"<br />
INTERFACES=(eth0)<br />
ROUTES=(!gateway)<br />
<br />
=== 静态 IP ===<br />
<br />
如果你需要在不使用路由器的情况下,和一台安装 Windows 的电脑分享你的网络连接,确保两台电脑都使用静态 IP ,否则你的局域网将会有问题。<br />
<br />
你需要:<br />
<br />
* 你的静态IP地址;<br />
* 子网掩码;<br />
* 广播地址;<br />
* 你的网关;<br />
* DNS 服务器(域名服务器)的 IP 地址;<br />
* 你的域名。<br />
<br />
如果你想配置一个内部网络,可以将你的 IP设置成 192.168.*.* ,子网掩码设置成 255.255.0.0 ,广播地址设置成 192.168.255.255 。除非你的网络拥有路由器,否则网关地址不重要。参考下面的例子编辑你的<code>/etc/rc.conf</code> ,使用你自己的 IP ,掩码,广播地址和网关:<br />
<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
<br />
上面这个例子中, IP 为 82.137.129.29 ,掩码为 255.255.255.0 ,广播地址为 82.137.129.255 ,网关为 82.137.129.1<br />
<br />
参考下面的例子编辑 <code>/etc/resolv.conf</code> ,使用你自己的域名服务器的 IP 和你的域名:<br />
<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
<br />
上面的例子中,两个域名服务器分别为 61.23.173.5 、 61.95.849.8 。<br />
<br />
你可以添加任意多个域名服务器。<br />
<br />
如果你使用 DHCP 自动获取 IP 地址,但是不想每次启动网络的时候让 DHCP 更改你的 DNS 服务器(域名服务器),在 <code>/etc/conf.d/dhcpcd</code> 中的 <code>DHCPCD_ARGS</code> 中添加 -R 选项。这样会阻止 DHCP 在每次网络启动的时候改写你的 <code>/etc/resolv.conf</code> :<br />
<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
If you share your internet connection from a Windows box without a router, be sure to use static IPs on both computers. Otherwise you will have LAN issues.<br />
<br />
You need:<br />
<br />
* Your static IP address,<br />
* The netmask,<br />
* The broadcast address,<br />
* Your gateway,<br />
* Your nameservers' IP addresses,<br />
* Your domain name.<br />
<br />
If you are running a private network, it is safe to use IP addresses in 192.168.*.'* for your IPs, with a netmask of 255.255.0.0 and broadcast address of 192.168.255.255. Unless your network has a router, the gateway address does not matter. Edit <code>/etc/rc.conf</code> like this, substituting your own values for the IP, netmask, broadcast, and gateway:<br />
<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
<br />
and your <code>/etc/resolv.conf</code> like this, substituting your nameservers' IPs and your domain name:<br />
<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
<br />
You may include as many nameserver lines as you wish.<br />
<br />
If you use DHCP and you don't want your DNS servers to change every time you start your network, be sure to add the "-R" option to <code>DHCPCD_ARGS</code> in <code>/etc/conf.d/dhcpcd</code> (used by in <code>/etc/rc.d/network</code>). This prevents DHCP from rewriting your <code>/etc/resolv.conf</code> every time:<br />
<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
==其他选项==<br />
<br />
如果因为某些原因, 使用 DHCP 自动获取( dhcpd eth0 )失败,安装 dhclient ( pacman -Sy dhclient ),使用 '<code>dhclient eth0</code>' 代替。<br />
<br />
<br />
If for some reason dhcpcd eth0 fails, install dhclient (pacman -Sy dhclient)<br />
and use '<code>dhclient eth0</code>' instead.<br />
<br />
== 设置计算机名 ==<br />
<br />
编辑 <code>/etc/rc.conf</code> ,将 HOSTNAME 设置成你想要的计算机名称:<br />
<br />
HOSTNAME="banana"<br />
<br />
Edit <code>/etc/rc.conf</code> and set HOSTNAME to your desired computer name:<br />
HOSTNAME="banana"<br />
<br />
<br />
== 设置本机域名/ IP ==<br />
<br />
编辑 <code>/etc/hosts</code> ,添加你在 <code>/etc/rc.conf</code> 的 HOSTNAME 选项中填写的东西,按照这样的格式:<br />
<br />
127.0.0.1 banana.domain.org localhost.localdomain localhost banana<br />
<br />
那些带有 localhost 的项是很多程序所需要的<br />
<br />
Edit <code>/etc/hosts</code> and add the same HOSTNAME you entered in <code>/etc/rc.conf</code> :<br />
127.0.0.1 banana.domain.org localhost.localdomain localhost banana<br />
<br />
This format, including the localhost entries is required for program compatibility.<br />
<br />
== 导入设置 ==<br />
<br />
想测试你的设置,可以重启计算机,或者在 root (超级用户)下运行 <code>/etc/rc.d/network restart</code> 。<br />
试着按照这个顺序 ping 一些网络地址:你的网关, DNS 服务器(域名服务器), ISP 服务提供商,以及其他的网络地址。这样可以检查你的网络连接在哪里出了问题。<br />
<br />
To test your settings either reboot the computer, or as root, run <code>/etc/rc.d/network restart</code>.<br />
Try pinging your gateway, DNS server, ISP provider and other Internet sites, in that order, to detect any connection problems along the way.<br />
<br />
<br />
== 更多的设置==<br />
<br />
=== 无线网络配置 ===<br />
<br />
无线网络( wlan )配置在 [[Wireless Setup |另外一个wiki页面]] 中。<br />
<br />
The wireless (wlan) configuration is the topic of [[Wireless Setup|another wiki page]].<br />
<br />
=== 防火墙 ===<br />
<br />
你可以安装和配置 [[Firewalls |防火墙]] 来让你感到更安全。<br />
<br />
You can install and configure a [[Firewalls|firewall]] to feel more secure. ;-)<br />
<br />
=== 即插即用( Ifplugd ) ===<br />
<br />
你可以安装这个服务( Ifplugd ),使得当网络接入的时候自动配置网络,当网络断开的时候自动取消配置。这对于笔记本电脑这样的使用移动式的网络适配器的情况很有用,因为他只会在网络实际接入的时候才会配置网络接口。另外一个可能会用得着它的情况是,你需要重启你的网络,可是你既不想重启电脑也不想在 shell (终端)中配置。<br />
<br />
它在 [extra] 中,因此安装非常简单:<br />
<br />
# pacman -S ifplugd<br />
<br />
在默认情况下,它会检查 eth0 设备。更改这个设置(以及更改其他设置,比如等待时间),可以编辑 <code>/etc/ifplugd/ifplugd.conf</code> 。<br />
<br />
运行这个命令来启动它:<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
或者将它加入<code>/etc/rc.conf</code> 的 DAEMONS 列表,这样它就能开机自动启动了。<br />
<br />
<br />
You can install a daemon which will automatically configure your Ethernet device when a cable is plugged in and automatically unconfigure it if the cable is pulled. This is useful on laptops with onboard network adapters, since it will only configure the interface when a cable is really connected. Another use is when you just need to restart the network but don't want to restart the computer or do it from the shell.<br />
<br />
Installation is very simple since it's in [extra]:<br />
<br />
# pacman -S ifplugd<br />
<br />
By default it is configured to work for eth0 device. This and other settings like delays can be configured in <code>/etc/ifplugd/ifplugd.conf</code>.<br />
<br />
Start it with<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
or add it into DAEMONS array in <code>/etc/rc.conf</code>.<br />
<br />
=== 绑定 ===<br />
<br />
你可以安装 'ifenslave' 来让你的两块真实网卡绑定同一个 IP 地址。<br />
<br />
/etc/conf.d/bonding<br />
bond_bond0="eth0 eth1"<br />
BOND_INTERFACES=(bond0)<br />
<br />
/etc/rc.conf<br />
MODULES=(... bonding ...)<br />
bond0="bond0 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"<br />
INTERFACES=(bond0)<br />
使用<br />
#/etc/rc.d/network restart<br />
重启网络<br />
<br />
You can install 'ifenslave' to bind two real Ethernet cables with one IP address.<br />
/etc/conf.d/bonding<br />
bond_bond0="eth0 eth1"<br />
BOND_INTERFACES=(bond0)<br />
/etc/rc.conf<br />
MODULES=(... bonding ...)<br />
bond0="bond0 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"<br />
INTERFACES=(bond0)<br />
restart network by<br />
/etc/rc.d/network restart<br />
<br />
== Troubleshooting ==<br />
<br />
=== Swapping computers on the cable modem ===<br />
<br />
Most domestic cable ISPs (videotron for example) have the cable modem configured to recognise only one client PC, by the MAC address of its network interface. Once the cable modem has learnt the MAC address of the first PC that talks to it, it will not respond to another MAC address in any way. Thus if you swap one PC for another (or for a router), the new PC (or router) will not work with the cable modem, because the new PC (or router) has a different MAC address to the old one. To reset the cable modem so that it will recognise the new PC, you must power the cable modem off and on again. Once the cable modem has rebooted and gone fully online again (indicator lights settled down), reboot the newly connected PC so that it makes a DHCP request, or manually make it request a new DHCP lease.<br />
<br />
=== The TCP Window Scaling Issue ===<br />
<br />
TCP packets contain a "window" value in their headers indicating how much data the other host may send in return. This value is represented with only 16 bits, hence the window size is at most 64Kb. TCP packets are cached for a while (they have to be reordered), and as memory is (or used to be) limited, one host could easily run out of it.<br />
<br />
Back in 1992, as more and more memory became available, [http://www.faqs.org/rfcs/rfc1323.html RFC 1323] was written to improve the situation: Window Scaling. The "window" value, provided in all packets, will be modified by a Scale Factor defined once, at the very beginning of the connection.<br />
<br />
That 8-bit Scale Factor allows the Window to be up to 32 times higher than the initial 64Kb.<br />
<br />
It appears that some broken routers and firewalls on the Internet are rewriting the Scale Factor to 0 which causes misunderstandings between hosts.<br />
<br />
The Linux kernel 2.6.17 introduced a new calculation scheme generating higher Scale Factors, virtually making the aftermaths of the broken routers and firewalls more visible. <br />
<br />
The resulting connection is at best very slow or broken.<br />
<br />
==== How To Diagnose The Problem? ====<br />
<br />
First of all, let's make it clear: this problem is odd. In some cases, you will not be able to use TCP connections (HTTP, FTP, ...) at all and in others, you will be able to communicate with some hosts (very few).<br />
<br />
'''Warning''': <code>dmesg</code>'s output is OK, logs are clean and <code>ifconfig</code> will report normal status &mdash; and actually everything is normal.<br />
<br />
If you can't browse any website, but you can ping some rare hosts, chances are great that you're experiencing this issue: ping uses the ICMP protocol and is not affected by TCP issues.<br />
<br />
You can try to use WireShark. You might see successful UDP and ICMP communications but unsuccessful TCP communications (only to foreign hosts).<br />
<br />
==== How To Fix It? (The bad way) ====<br />
<br />
To fix it the bad way, you can change the tcp_rmem value, on which Scale Factor calculation is based. Although it should work for most hosts, it's not guaranteed, especially for very distant ones.<br />
<br />
echo "4096 87380 174760" > /proc/sys/net/ipv4/tcp_rmem<br />
<br />
Or you can try to remove one of your RAM sticks (yes, sir).<br />
<br />
==== How To Fix It? (The good way) ====<br />
<br />
Simply disable Window Scaling. Even if Window Scaling is a nice TCP feature, it may be uncomfortable especially if you can't fix the broken router. There are several ways to disable Window Scaling, and it seems that the most bulletproof (which will work with most kernels) is to add the following lines to your <code>/etc/rc.local</code>:<br />
<br />
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling<br />
<br />
==== How To Fix It? (The best way) ====<br />
<br />
This issue is caused by broken routers/firewalls, so let's change them. Some users have reported that the broken router was their very own DSL router.<br />
<br />
==== More about it? ====<br />
<br />
This section is based on the LWN article [http://lwn.net/Articles/92727/ TCP window scaling and broken routers] and a Kernel Trap article: [http://kerneltrap.org/node/6723 Window Scaling on the Internet].<br />
<br />
And more recently, some Archers have been hit by this issue:<br />
<br />
* [http://www.archlinux.org/pipermail/arch/2006-June/011250.html Odd network issue]<br />
* [http://www.archlinux.org/pipermail/arch/2006-September/011943.html Kernel 2.6.17 and TCP window scaling] &mdash; the topic which initiated this article<br />
<br />
There are also several relevant threads on the LKML.<br />
<br />
<br />
=== Realtek No Link / WOL issue ===<br />
<br />
Users with Realtek 8168 8169 8101 8111 based NICs (cards / and on board) may notice an issue where the NIC seems to be disabled on boot and has no Link light. This can usually be found on a dual boot system where Windows is also installed. It seems that using the offical realtek drivers (dated anything after May 2007) under windows is the cause. These newer drivers disable the Wake-On-Lan feature by disabling the NIC at Windows shutdown time, where it will remain disabled until the next time Windows boots. You will be able to spot if this is issue is affecting you because the Link light will remain off only until Windows boots, during Windows shutdown it will revert back to the Link light being off. Normal operation should be that the link light is always on as long as the system is on, even during POST. This issue will also affect other OS's without newer drivers (eg. Live CD's). Here's a couple of fixes for this issue.<br />
<br />
==== Method 1 - Rollback/Change Win driver ====<br />
<br />
You can rollback your Windows NIC driver to the Microsoft provided one (if available), or rollback/install to an official Realtek driver pre-dated May 2007 (maybe on the CD that came with your hardware).<br />
<br />
==== Method 2 - Enable WOL in Win driver ====<br />
<br />
Probably the best and fastest fix is to change this setting in the Windows driver. This way it should be fixed system wide and not only under Arch (eg. live CD's, other OSes). In Windows under device manager, find your Realtek Network adapter and double click it. Under the advanced tab change "wake-on-lan after shutdown" to enable.<br />
<br />
In Windows XP (example)<br />
Right click my computer --> Hardware tab --> Device Manager --> Network Adapters --> "double click" Realtek ... --> Advanced tab --> Wake-On-Lan After Shutdown --> Enable.<br />
<br />
==== Method 3 - Newer Realtek Linux driver ====<br />
<br />
Any newer driver for these Realtek cards can be found for Linux on the realtek site. (untested but believed to also solve the problem).</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=User:SteamedFish&diff=35143User:SteamedFish2008-01-16T22:22:21Z<p>SteamedFish: New page: A student from Nanjing University, China.</p>
<hr />
<div>A student from Nanjing University, China.</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Network_configuration_(%C4%8Ce%C5%A1tina)&diff=35142Network configuration (Čeština)2008-01-16T22:19:49Z<p>SteamedFish: Add i18n entry: 简体中文</p>
<hr />
<div>[[Category:Network]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Static IP and DHCP}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Статический IP и DHCP}}<br />
{{i18n_entry|Česky|Statická IP a DHCP czech}}<br />
{{i18n_entry|简体中文|网络配置}}<br />
{{i18n_links_end}}<br />
<br />
==Shrnutí==<br />
Jednoduchý průvodce zprovozněním sítě.<br />
<br />
==Nahrání ovladače (modulu) zařízeni==<br />
Jestliže používáte hwdetect, měl by být schopen rozpoznat vaši síťovou kartu a automaticky po startu zavést odpovídající moduly. V opačném případě potřebujete vědět název modulu potřebného pro chod vaší karty. Hledejte na webu výrobce výrobce vaší karty, ve vyhledávačích nebo zkuste některou z Live distribucí a podívejte se jaký modul používa - spusťte příkaz lsmod, který zobrazí všechny aktuálně načtené moduly.<br />
<br />
Nyní předpokládejme, že znáte název potřebného modulu. Můžete ho do jádra zavést následujícím příkazem:<br />
<br />
modprobe jmenomodulu<br />
<br />
Jestliže nechcete nebo nemůžete použít auto-loader jako například hwdetect, můžete přidat názvy potřebných modulů do /etc/rc.conf, potom už nebude potřeba zavádět moduly příkazem modprobe po každém startu počítače. Např. pokud se modul jemenuje tg3:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
Další běžné moduly jsou 8139too pro karty s čipy od RealTek nebo sis900 pro SiS karty.<br />
<br />
==Nastavení IP adresy==<br />
<br />
===DHCP===<br />
<br />
DCHP je služba, která dokáže dynamicky na požádání přidělovat klientům IP adresu (a nejen ji). Pokud dhcp používáte, upravte [[rc.conf]] následovně:<br />
<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
INTERFACES=(lo eth0)<br />
ROUTES=(!gateway)<br />
<br />
Pokud z nějákého důvodu dchpdc eth0 selhává, nainstalujte dhclienta (pacman -Sy dhclient) a použijte příkaz dhclient eth0 (samozřejmě pokud vaše síťová karta je označena jako eth0).<br />
<br />
===Statická IP===<br />
<br />
Jestliže sdílíte internetové připojeni z windowsovského boxu bez routeru, použijte na statickou IP adresu jinak můžete mít problémy se sítí.<br />
<br />
Pro konfiguraci statické IP potřebujete znát:<br />
<br />
* svou statickou IP<br />
* masku sítě<br />
* adresu broadcastu (poslední možná IP v rozsahu vaší sítě)<br />
* bránu (gateway)<br />
* IP adresy jmenných serverů<br />
* jméno vaší domény<br />
<br />
Pokud pracujete v soukromé síti, je bezpečné používat IP adresy v rozsahu 192.168.*.* , s maskou 255.255.0.0 a adresou všesměrového vysílání (broadcast) 192.168.255.255. Dokud vaše síť nemá router, na adrese brány nezáleží. Upravte [[rc.conf]] následovně, avšak nahraďte IP, masku sítě, broadcast a bránu svými vlastními hodnotami:<br />
<br />
lo="lo 127.0.0.1"<br />
eth0="eth0 192.168.10.1 netmask 255.255.0.0 broadcast 192.168.255.255"<br />
INTERFACES=(lo eth0)<br />
gateway="default gw 192.168.10.20"<br />
ROUTES=(gateway)<br />
<br />
V souboru /etc/resolv.conf potom nahraďte IP nameserveru a jméno domény vašimi vlastními. Jméno domény pro vzhledávání není vždy podmínkou:<br />
<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
<br />
Můžete zadat tolik nameserverů, kolik chcete.<br />
<br />
Pokud používáte DHCP a nechcete, aby se váš DNS server měnil při každém spuštění sítě, přidejte volbu <code>-R</code> do <code>DHCPCD_ARGS</code> v souboru /etc/conf.d/dhcpcd (používaném v /etc/rc.d/network). Tímto se zabrání, aby za každým spuštěním DHCP přepisoval váš /etc/resolv.conf:<br />
<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
==Nastavení jména počítače==<br />
Upravte [[rc.conf]] a nastavte HOSTNAME na vámi požadované jméno počítače:<br />
<br />
HOSTNAME="banana"<br />
<br />
==Nastavení lokálního překladu názvů hostitelů na IP adresy==<br />
<br />
Upravte /etc/hosts a přidejte podobný řádek se stejným HOSTNAME, jaké jste zadali v [[rc.conf]]:<br />
<br />
127.0.0.1 banana.localdomain banana<br />
<br />
Obdobně můžete přidávat i další záznamy.<br />
<br />
== Aktualizace konfigurace ==<br />
K otestování konfigurace nemusíte restartovat počítač, stačí jako root spustit <code>/etc/rc.d/network restart</code>. Nyní zkuste příkazem ping otestovat spojení na vaši bránu, DNS servery, ISP a jiné internetové servery.<br />
<br />
== Některá další nastavení ==<br />
<br />
=== Bezdrátové sítě ===<br />
<br />
Konfigurace bezdrátových sítí je probírána v [[Wireless Setup]].<br />
<br />
=== Firewall ===<br />
<br />
Aby jste se cítily bezpečněji, nainstalujte a nakonfigurujte si [[Firewalls|firewall]].<br />
<br />
=== Ifplugd ===<br />
<br />
Ifplugd je služba, která automaticky konfiguruje vaše síťová rozhraní, když zapojíte kabel a poté i konfiguraci vynuluje, pokud kabel zase odpojíte. To je velmi použitelné na laptopech s integrovanou síťovou kartou, protože se bude síť konfigurovat až opravdu v okamžiku, kdy je připojen kabel.<br />
<br />
Instalace je velmi jednoduchá. Baliček se nachází v [extra]:<br />
<br />
# pacman -S ifplugd<br />
<br />
Ve výchozím stavu je služba nastavena pro spolupráci s eth0. Toto a jiné nastavení se konfiguruje v <code>/etc/ifplugd/ifplugd.conf</code>.<br />
<br />
Ifplugd spusťte příkazem:<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
nebo jej přidejte do výčtu DAEMONS v <code>/etc/rc.conf</code>.<br />
<br />
== Troubleshooting ==<br />
<br />
=== TCP Window Scaling ===<br />
<br />
TCP pakety obsahují v jejich hlavičce "window" hodnotu, které říká, jak mnoho dat může druhý počítač poslat nazpět. This value is represented with only 16 bits hence the window size is at most 64Kb. TCP packets are cached for a while (they have to be reordered) and as memory is (or used to be) limited one host could easily run out of it.<br />
<br />
Back in 1992, as more and more memory became available, [http://www.faqs.org/rfcs/rfc1323.html RFC 1323] was written to improve the situation: Window Scaling. The "window" value, provided in all packets will be modified by a Scale Factor defined once, at the very beginning of the connection.<br />
<br />
That 8 bits Scale Factor allows the Window to be up to 32 times higher than the initial 64Kb.<br />
<br />
It appears that some broken routers and firewalls on the Internet are rewriting the Scale Factor to 0 which causes misunderstandings between hosts.<br />
<br />
The Linux kernel 2.6.17 introduced a new calculation scheme generating higher Scale Factors virtually making the aftermaths of the broken routers and firewalls more visible. <br />
<br />
The resulting connection is at best very slow or broken.<br />
<br />
==== How To Diagnose The Problem? ====<br />
<br />
First of all, let's make it clear: this problem is odd. In some cases, you will not be able to use TCP connections (HTTP, FTP, ...) at all and in others, you will be able to communicate with some hosts (very few).<br />
<br />
'''Warning''': <code>dmesg</code>'s output is ok, logs are clean and <code>ifconfig</code> will report normal status &mdash; and actually everything is normal.<br />
<br />
If you can't browse any website, but you can ping some rare hosts, chances are great that you're experiencing this issue: ping uses the ICMP protocol and is not affected by TCP issues.<br />
<br />
You can try to use WireShark. You might see successful UDP and ICMP communications but unsuccessful TCP communications (only to foreign hosts).<br />
<br />
==== How To Fix It? (The bad way) ====<br />
<br />
To fix it the bad way, you can change the tcp_rmem value, on which Scale Factor calculation is based. Although it should work for most hosts, it's not guaranteed, especially for very distant ones.<br />
<br />
echo "4096 87380 174760" > /proc/sys/net/ipv4/tcp_rmem<br />
<br />
Or you can try to remove one of your RAM sticks (yes sir).<br />
<br />
==== How To Fix It? (The good way) ====<br />
<br />
Simply disable Window Scaling. Even if Window Scaling is a nice TCP feature, it may be uncomfortable especially if you can't fix the broken router. There are several ways to disable Window Scaling and it seems that the most bullet-proof (which will work with most kernels) is to add the following lines to your <code>/etc/rc.local</code>:<br />
<br />
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling<br />
<br />
==== How To Fix It? (The best way) ====<br />
<br />
This issue is caused by broken routers/firewalls, let's change them. Some users have reported that the broken router was their very own DSL router.<br />
<br />
==== More about it? ====<br />
<br />
This section is based on the LWN article [http://lwn.net/Articles/92727/ TCP window scaling and broken routers] and a Kernel Trap article: [http://kerneltrap.org/node/6723 Window Scaling on the Internet].<br />
<br />
And more recently, some Archers have been hit by this issue:<br />
<br />
* [http://www.archlinux.org/pipermail/arch/2006-June/011250.html Odd network issue]<br />
* [http://www.archlinux.org/pipermail/arch/2006-September/011943.html Kernel 2.6.17 and TCP window scaling] &mdash; The topic which initiated this article<br />
<br />
There are also several relevant threads on the LKML.</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Network_configuration_(%D0%A0%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B9)&diff=35141Network configuration (Русский)2008-01-16T22:19:15Z<p>SteamedFish: Add i18n entry: 简体中文</p>
<hr />
<div>[[Category:Сеть]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Configuring_network}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Настройка_сети}}<br />
{{i18n_entry|Česky|Statická IP a DHCP czech}}<br />
{{i18n_entry|简体中文|网络配置}}<br />
{{i18n_links_end}}<br />
<br />
== Обзор ==<br />
Это простое руководство по настройке сети.<br />
<br />
== Загрузка модуля устройства ==<br />
Если вы используете [[hwdetect]] или [[Replacing Hotplug with LSHWD|lshwd]], они должны обнаружить модуль для вашей сетевой карты (NIC) и загрузить его автоматически при старте системы. В другом случае вы должны знать, какой модуль требуется для вашей сетевой карты.<br />
<br />
Поищите эту информацию в сети или попробуйте LiveCD, чтобы найти имя требуемого модуля запустите [[Linux And Hardware|lsmod]], выведет все загруженные модули.<br />
<br />
Теперь когда вы знаете, какой модуль использовать, можно его загрузить:<br />
<br />
# modprobe <имя_модуля><br />
<br />
Если вы не хотите использовать какой-либо автозагрузчик (например, [[hwdetect]]) , вы можете добавить его в список MODULES в <code>/etc/rc.conf</code>, чтобы не подгружать его каждый раз. Например, если tg3 является требуемым модулем:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
== Настройка ==<br />
=== Для DHCP ===<br />
Отредактируйте <code>/etc/rc.conf</code> следующим образом: <br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
INTERFACES=(lo eth0)<br />
ROUTES=(!gateway)<br />
</pre><br />
<br />
=== Для статического IP ===<br />
Если вы используете интернет с windows машины без роутера, необходимо использовать статические ip адреса на обоих машинах. В противном случае возникнут проблемы в локальной сети.<br />
<br />
Вам понадобится:<br />
<br />
* Ваш статический ip адрес<br />
* Маска сети<br />
* Широковещательный адрес<br />
* Ваш шлюз<br />
* Адреса ваших DNS серверов<br />
* Доменное имя<br />
<br />
Если вы находитесь в частной сети, то можете использовать ip адреса диапазона 192.168.*.* с маской сети 255.255.0.0 и широковещательным адресом 192.168.255.255. Если в вашей сети нет роутера - адрес гейта значения не имеет. Исправьте <code>/etc/rc.conf</code>, подставляя свои значения для IP, маски сети, широковещательного адреса и гейта:<br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(lo eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
</pre><br />
и <code>/etc/resolv.conf</code>, заменив адреса ваших DNS серверов и доменное имя:<br />
<pre><br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
</pre><br />
<br />
Количество DNS серверов не ограничено.<br />
<br />
Если вы используете DHCP и не хотите, чтобы DNS сервера менялись каждый раз при запуске сети, добавьте параметр <code>-R</code> к <code>DHCPCD_ARGS</code> в вашем <code>/etc/conf.d/dhcpcd</code> ( используется <code>/etc/rc.d/network</code>). Это предотвратит перезапись <code>/etc/resolv.conf</code> DHCP:<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
== Заключительное решение ==<br />
Возможно, вам придётся добавить параметр "-S" в аргументы dhcpcd, чтобы ваша сеть работала:<br />
<code>DHCPCD_ARGS="-S -t 30 -h $HOSTNAME"</code><br />
<br />
== Установка имени компьютера ==<br />
Отредактируйте <code>/etc/rc.conf</code> и установите HOSTNAME в соответствие с желаемым именем компьютера :<br />
HOSTNAME="banana"<br />
<br />
== Установка имени хоста/ip ==<br />
Отредактируйте <code>/etc/hosts</code> и добавьте похожую строку с тем же HOSTNAME, который вы ввели в <code>/etc/rc.conf</code> :<br />
127.0.0.1 banana.localdomain banana<br />
<br />
== Загрузка настроек ==<br />
Чтобы проверить ваши настройки, либо перезагрузите компьютер, либо запустите <code>#/etc/rc.d/network restart</code><br />
Попробйте пинговать ваш шлюз, DNS сервер, ISP провайдера и другие интернет сайт в этом порядке, чтобы установить какие-либо проблемы.<br />
<br />
== Дополнительные настройки ==<br />
<br />
=== Настройка беспроводной сети ===<br />
<br />
Настройка беспроводной сети (wlan) объяснена [[Wireless Setup|на другой странице]].<br />
<br />
=== Firewall ===<br />
<br />
Вы можете установить и настроить [[Firewalls|firewall]], чтобы быть более защищённым ;-)<br />
<br />
=== Ifplugd ===<br />
<br />
Вы можете установить демон, который будет автоматически настраивать вашу сеть, когда воткнут кабель, и возвращать её в исходное состояние, когда кабель выдернут. Это полезно для лаптопов с внутренними сетевыми адаптерами, так как демон настроит интерфейс только тогда, когда кабель действительно подключён. Также можно его использовать, когда надо перезапустить сеть, но вы не хотите перезапускать компьютер или делать это из оболочки.<br />
<br />
Установка очень проста, так как пакет находится в [extra]:<br />
<br />
# pacman -S ifplugd<br />
<br />
По умолчанию он настроен на работу с интрфейсом eth0. Эта другие настройки, например задержка, могут быть настроены в <code>/etc/ifplugd/ifplugd.conf</code>.<br />
<br />
Запустите его:<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
или добавьте в список DAEMONS в <code>/etc/rc.conf</code><br />
<br />
== Возможные проблемы ==<br />
<br />
=== Проблема расширения TCP-окна ===<br />
TCP-пакеты содержат значение "окна" в своих заголовках, которое показывает, сколько данных другой хост может послать в ответе. Это значение представлено 16-ю битами. Следовательно, размер окна ограничен 64 килобайтами. Для более эффективного использования широкополосного соединения этого мало.<br />
<br />
В 1992 году, когда стало доступно больше памяти, был описан прием (см. [http://www.faqs.org/rfcs/rfc1323.html RFC 1323]), призванный улучшить ситуацию: расширение окна (Window Scaling). Значение "окна", предоставляемое всеми пакетами, модифицируется с помощью опредяемого в момент установки соединения коэффициента (Scale Factor).<br />
Коэффициент представлен восемью битами и позволяет увеличить значение окна в 32 раза.<br />
<br />
Но в интернете появилось множество роутеров и межсетевых экранов, которые переписывали значение окна на 0, создавая недоразумения.<br />
<br />
В ядре 2.6.17 была введена новая схема генерации коэффициента, с которой последствия прохождения пакетов через подобные роутеры стали более заметны.<br />
<br />
В результате соединение в лучшем случае очень медленно или падает.<br />
<br />
==== Как диагностировать проблему? ====<br />
<br />
Во-первых, давайте уясним: эта проблема проявляется не всегда. В некоторых случаях, вы сможете использовать TCP-соединения и соединяться с некоторыми хостами (очень немногими).<br />
<br />
'''Внимание''': вывод <code>dmesg</code> не выявит ничего необычного, логи будут чисты и <code>ifconfig</code> сообщит, что все нормально; в действительности все в норме.<br />
<br />
Если же вы не можете просмотреть любой веб-сайт, однако можете пинговать некоторые хосты, велики шансы, что вы столкнулись с этой проблемой: pig использует ICMP-протокол, которого не касаются проблемы TCP.<br />
<br />
Можете попробовать воспользоваться WireShark. Вы можете увидеть удачные UDP- и ICMP-соединения и неудачные TCP.<br />
<br />
==== Как это исправить? (Плохой способ) ====<br />
<br />
Для исправления плохим способом, вы можете изменить значение tcp_rmem, на котором базируется алгоритм вычисления коэффициента. Несмотря на то, что это может сработать с большинством хостов, нет гарантии, что это сработает с очень удаленными.<br />
<br />
echo "4096 87380 174760" > /proc/sys/net/ipv4/tcp_rmem<br />
<br />
Еще вы можете попробовать удалить один из модулей оперативной памяти (да, сэр).<br />
<br />
==== Как это исправить? (Хороший способ) ====<br />
<br />
Просто отключить злополучное расширение окна. Даже если это и хорошая функция, она может не работать, если вы не сможете разобраться с некорректной работой роутеров. Есть несколько способов отключить расширение окна, и похоже, что самым надежным будет добавить следующую строку в файл <code>/etc/rc.local</code>:<br />
<br />
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling<br />
<br />
==== Как это исправить? (Действительно хороший способ) ====<br />
<br />
Если это происходит по вине роутеров и межсетевых экранов, замените их. Некоторые пользователи сообщали, что проблема была в их собственных DSL-роутерах.<br />
<br />
==== Хотите больше информации об этом? ====<br />
<br />
Эта секция основана на статьях [http://lwn.net/Articles/92727/ TCP window scaling and broken routers] и [http://kerneltrap.org/node/6723 Window Scaling on the Internet].<br />
<br />
Позднее, некоторые пользователи Arch столкнулись с этим:<br />
<br />
* [http://www.archlinux.org/pipermail/arch/2006-June/011250.html Odd network issue]<br />
* [http://www.archlinux.org/pipermail/arch/2006-September/011943.html Kernel 2.6.17 and TCP window scaling] &mdash; Тема, с которой началась эта статья<br />
<br />
Также есть несколько обсуждений в LKML.<br />
<br />
[[Category:Русский]]</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Network_configuration_(Slovensk%C3%BD)&diff=35140Network configuration (Slovenský)2008-01-16T22:18:03Z<p>SteamedFish: Add i18n entry: 简体中文</p>
<hr />
<div>[[Category:Network]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Static IP and DHCP}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Статический IP и DHCP}}<br />
{{i18n_entry|Česky|Statická IP a DHCP czech}}<br />
{{i18n_entry|简体中文|网络配置}}<br />
{{i18n_links_end}}<br />
<br />
==Zhrnutie==<br />
Jednoduchý sprievodca ako spojazdniť vašu sieť.<br />
<br />
==Nahrať modul zariadenia==<br />
Pridajte váš modul eth0 do poľa modulov v súbore <code>/etc/rc.conf</code>, napr. tg3, (8139too pre karty, ktoré používajú RealTek chipset)<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
==Konfigurovať IP==<br />
<br />
===Pre DHCP IP===<br />
<br />
Upravte <code>/etc/rc.conf</code> nasledovne:<br />
<br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
INTERFACES=(lo eth0)<br />
ROUTES=(!gateway)<br />
</pre><br />
<br />
===Pre statickú IP===<br />
<br />
Ak zdieľate vaše internetové pripojenie z Windowsovského boxu bez rútra, použite na oboch počítačoch statické IP adresy. V opačnom prípade budete mať problémy s LAN.<br />
<br />
Potrebujete:<br />
<br />
* Vašu statickú IP adresu,<br />
* Masku siete,<br />
* Adresu vysielania,<br />
* Vašu bránu,<br />
* IP adresy vašich nameserverov,<br />
* Meno vašej domény.<br />
<br />
<br />
Ak bežíte pod súkromnou sieťou, je bezpečné používať IP adresy v škále 192.168.*.* pre vaše IP, s maskou 255.255.0.0 a adresou vysielania 192.168.255.255. Pokiaľ vaša sieť nemá rúter, na adrese brány nezáleží. Upravte <code >/etc/rc.conf</code > nasledovne, avšak nahradte IP, masku siete, vysielanie a bránu vašimi vlastnými hodnotami:<br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(lo eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
</pre><br />
a váš súbor <code >/etc/resolv.conf</code > nasledovne, nahradte IP nameserverov a meno domény vašimi vlastnými:<br />
<br />
<pre><br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
</pre><br />
<br />
Môžete uviesť toľko riadkov nameserverov koľko len chcete.<br />
<br />
Ak používate DHCP a nechcete, aby sa vaše DNS servre menili pri každom spustení vašej siete, pridajte voľbu <code >-R</code > do <code >DHCPCD_ARGS</code > v súbore <code >/etc/conf.d/dhcpcd</code > (používanom v <code >/etc/rc.d/network</code >). Týmto sa zabráni, aby zakaždým DHCP prepisovalo váš <code >/etc/resolv.conf</code > :<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
==Nastaviť meno počítača==<br />
Upravte <code >/etc/rc.conf</code > a nastavte HOSTNAME na vami požadované meno počítača:<br />
HOSTNAME="banana"<br />
<br />
==Nastaviť meno hostiteľa/ip==<br />
<br />
Upravte <code >/etc/hosts</code > a pridajte podobný riadok s rovnakým HOSTNAME aké ste zadali v <code >/etc/rc.conf</code > :<br />
127.0.0.1 banana.localdomain banana</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Network_configuration&diff=35139Network configuration2008-01-16T22:17:13Z<p>SteamedFish: Add i18n entry: 简体中文</p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Configuring_network}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Статический IP и DHCP}}<br />
{{i18n_entry|Česky|Statická IP a DHCP czech}}<br />
{{i18n_entry|简体中文|网络配置}}<br />
{{i18n_links_end}}<br />
<br />
== Summary ==<br />
<br />
A simple guide to get your network running.<br />
<br />
<br />
== Load the device module ==<br />
<br />
If you use [[hwdetect]] it should detect your network card (NIC) module and load it automatically at startup. Otherwise, you will need to know which module is needed for your particular model.<br />
<br />
Search the Web for your card model, or try using a Linux LiveCD to find out the name of the needed module - run [[Linux And Hardware|lsmod]] to show you all currently loaded modules after booting.<br />
<br />
Now when you know which module to use you can load it:<br />
<br />
# modprobe <modulename><br />
<br />
If you don't want / can't use some auto-loader like [[hwdetect]] you can add it into the modules array in <code>/etc/rc.conf</code>, so you don't need to modprobe it everytime you boot. For example, if tg3 is the network module:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
Other common modules are 8139too for cards with the Realtek chipset or sis900 for SiS cards.<br />
<br />
== Configure IP ==<br />
<br />
=== For DHCP IP ===<br />
<br />
For this, you need the dhcpcd package (usually already available on most installation). Edit <code>/etc/rc.conf</code> like this:<br />
<br />
eth0="dhcp"<br />
INTERFACES=(eth0)<br />
ROUTES=(!gateway)<br />
<br />
=== For Static IP ===<br />
<br />
If you share your internet connection from a Windows box without a router, be sure to use static IPs on both computers. Otherwise you will have LAN issues.<br />
<br />
You need:<br />
<br />
* Your static IP address,<br />
* The netmask,<br />
* The broadcast address,<br />
* Your gateway,<br />
* Your nameservers' IP addresses,<br />
* Your domain name.<br />
<br />
If you are running a private network, it is safe to use IP addresses in 192.168.*.'* for your IPs, with a netmask of 255.255.0.0 and broadcast address of 192.168.255.255. Unless your network has a router, the gateway address does not matter. Edit <code>/etc/rc.conf</code> like this, substituting your own values for the IP, netmask, broadcast, and gateway:<br />
<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
<br />
and your <code>/etc/resolv.conf</code> like this, substituting your nameservers' IPs and your domain name:<br />
<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
<br />
You may include as many nameserver lines as you wish.<br />
<br />
If you use DHCP and you don't want your DNS servers to change every time you start your network, be sure to add the "-R" option to <code>DHCPCD_ARGS</code> in <code>/etc/conf.d/dhcpcd</code> (used by in <code>/etc/rc.d/network</code>). This prevents DHCP from rewriting your <code>/etc/resolv.conf</code> every time:<br />
<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
==Other option==<br />
If for some reason dhcpcd eth0 fails, install dhclient (pacman -Sy dhclient)<br />
and use '<code>dhclient eth0</code>' instead.<br />
<br />
== Set computer name ==<br />
<br />
Edit <code>/etc/rc.conf</code> and set HOSTNAME to your desired computer name:<br />
HOSTNAME="banana"<br />
<br />
<br />
== Set host name/IP ==<br />
<br />
Edit <code>/etc/hosts</code> and add the same HOSTNAME you entered in <code>/etc/rc.conf</code> :<br />
127.0.0.1 banana.domain.org localhost.localdomain localhost banana<br />
<br />
This format, including the localhost entries is required for program compatibility.<br />
<br />
== Load configuration ==<br />
To test your settings either reboot the computer, or as root, run <code>/etc/rc.d/network restart</code>.<br />
Try pinging your gateway, DNS server, ISP provider and other Internet sites, in that order, to detect any connection problems along the way.<br />
<br />
<br />
== Some more settings ==<br />
<br />
=== Wireless Setup ===<br />
<br />
The wireless (wlan) configuration is the topic of [[Wireless Setup|another wiki page]].<br />
<br />
=== Firewall ===<br />
<br />
You can install and configure a [[Firewalls|firewall]] to feel more secure. ;-)<br />
<br />
=== Ifplugd ===<br />
<br />
You can install a daemon which will automatically configure your Ethernet device when a cable is plugged in and automatically unconfigure it if the cable is pulled. This is useful on laptops with onboard network adapters, since it will only configure the interface when a cable is really connected. Another use is when you just need to restart the network but don't want to restart the computer or do it from the shell.<br />
<br />
Installation is very simple since it's in [extra]:<br />
<br />
# pacman -S ifplugd<br />
<br />
By default it is configured to work for eth0 device. This and other settings like delays can be configured in <code>/etc/ifplugd/ifplugd.conf</code>.<br />
<br />
Start it with<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
or add it into DAEMONS array in <code>/etc/rc.conf</code>.<br />
<br />
=== bonding ===<br />
You can install 'ifenslave' to bind two real Ethernet cables with one IP address.<br />
/etc/conf.d/bonding<br />
bond_bond0="eth0 eth1"<br />
BOND_INTERFACES=(bond0)<br />
/etc/rc.conf<br />
MODULES=(... bonding ...)<br />
bond0="bond0 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"<br />
INTERFACES=(bond0)<br />
restart network by<br />
/etc/rc.d/network restart<br />
<br />
== Troubleshooting ==<br />
<br />
=== Swapping computers on the cable modem ===<br />
<br />
Most domestic cable ISPs (videotron for example) have the cable modem configured to recognise only one client PC, by the MAC address of its network interface. Once the cable modem has learnt the MAC address of the first PC that talks to it, it will not respond to another MAC address in any way. Thus if you swap one PC for another (or for a router), the new PC (or router) will not work with the cable modem, because the new PC (or router) has a different MAC address to the old one. To reset the cable modem so that it will recognise the new PC, you must power the cable modem off and on again. Once the cable modem has rebooted and gone fully online again (indicator lights settled down), reboot the newly connected PC so that it makes a DHCP request, or manually make it request a new DHCP lease.<br />
<br />
=== The TCP Window Scaling Issue ===<br />
<br />
TCP packets contain a "window" value in their headers indicating how much data the other host may send in return. This value is represented with only 16 bits, hence the window size is at most 64Kb. TCP packets are cached for a while (they have to be reordered), and as memory is (or used to be) limited, one host could easily run out of it.<br />
<br />
Back in 1992, as more and more memory became available, [http://www.faqs.org/rfcs/rfc1323.html RFC 1323] was written to improve the situation: Window Scaling. The "window" value, provided in all packets, will be modified by a Scale Factor defined once, at the very beginning of the connection.<br />
<br />
That 8-bit Scale Factor allows the Window to be up to 32 times higher than the initial 64Kb.<br />
<br />
It appears that some broken routers and firewalls on the Internet are rewriting the Scale Factor to 0 which causes misunderstandings between hosts.<br />
<br />
The Linux kernel 2.6.17 introduced a new calculation scheme generating higher Scale Factors, virtually making the aftermaths of the broken routers and firewalls more visible. <br />
<br />
The resulting connection is at best very slow or broken.<br />
<br />
==== How To Diagnose The Problem? ====<br />
<br />
First of all, let's make it clear: this problem is odd. In some cases, you will not be able to use TCP connections (HTTP, FTP, ...) at all and in others, you will be able to communicate with some hosts (very few).<br />
<br />
'''Warning''': <code>dmesg</code>'s output is OK, logs are clean and <code>ifconfig</code> will report normal status &mdash; and actually everything is normal.<br />
<br />
If you can't browse any website, but you can ping some rare hosts, chances are great that you're experiencing this issue: ping uses the ICMP protocol and is not affected by TCP issues.<br />
<br />
You can try to use WireShark. You might see successful UDP and ICMP communications but unsuccessful TCP communications (only to foreign hosts).<br />
<br />
==== How To Fix It? (The bad way) ====<br />
<br />
To fix it the bad way, you can change the tcp_rmem value, on which Scale Factor calculation is based. Although it should work for most hosts, it's not guaranteed, especially for very distant ones.<br />
<br />
echo "4096 87380 174760" > /proc/sys/net/ipv4/tcp_rmem<br />
<br />
Or you can try to remove one of your RAM sticks (yes, sir).<br />
<br />
==== How To Fix It? (The good way) ====<br />
<br />
Simply disable Window Scaling. Even if Window Scaling is a nice TCP feature, it may be uncomfortable especially if you can't fix the broken router. There are several ways to disable Window Scaling, and it seems that the most bulletproof (which will work with most kernels) is to add the following lines to your <code>/etc/rc.local</code>:<br />
<br />
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling<br />
<br />
==== How To Fix It? (The best way) ====<br />
<br />
This issue is caused by broken routers/firewalls, so let's change them. Some users have reported that the broken router was their very own DSL router.<br />
<br />
==== More about it? ====<br />
<br />
This section is based on the LWN article [http://lwn.net/Articles/92727/ TCP window scaling and broken routers] and a Kernel Trap article: [http://kerneltrap.org/node/6723 Window Scaling on the Internet].<br />
<br />
And more recently, some Archers have been hit by this issue:<br />
<br />
* [http://www.archlinux.org/pipermail/arch/2006-June/011250.html Odd network issue]<br />
* [http://www.archlinux.org/pipermail/arch/2006-September/011943.html Kernel 2.6.17 and TCP window scaling] &mdash; the topic which initiated this article<br />
<br />
There are also several relevant threads on the LKML.<br />
<br />
<br />
=== Realtek No Link / WOL issue ===<br />
<br />
Users with Realtek 8168 8169 8101 8111 based NICs (cards / and on board) may notice an issue where the NIC seems to be disabled on boot and has no Link light. This can usually be found on a dual boot system where Windows is also installed. It seems that using the offical realtek drivers (dated anything after May 2007) under windows is the cause. These newer drivers disable the Wake-On-Lan feature by disabling the NIC at Windows shutdown time, where it will remain disabled until the next time Windows boots. You will be able to spot if this is issue is affecting you because the Link light will remain off only until Windows boots, during Windows shutdown it will revert back to the Link light being off. Normal operation should be that the link light is always on as long as the system is on, even during POST. This issue will also affect other OS's without newer drivers (eg. Live CD's). Here's a couple of fixes for this issue.<br />
<br />
==== Method 1 - Rollback/Change Win driver ====<br />
<br />
You can rollback your Windows NIC driver to the Microsoft provided one (if available), or rollback/install to an official Realtek driver pre-dated May 2007 (maybe on the CD that came with your hardware).<br />
<br />
==== Method 2 - Enable WOL in Win driver ====<br />
<br />
Probably the best and fastest fix is to change this setting in the Windows driver. This way it should be fixed system wide and not only under Arch (eg. live CD's, other OSes). In Windows under device manager, find your Realtek Network adapter and double click it. Under the advanced tab change "wake-on-lan after shutdown" to enable.<br />
<br />
In Windows XP (example)<br />
Right click my computer --> Hardware tab --> Device Manager --> Network Adapters --> "double click" Realtek ... --> Advanced tab --> Wake-On-Lan After Shutdown --> Enable.<br />
<br />
==== Method 3 - Newer Realtek Linux driver ====<br />
<br />
Any newer driver for these Realtek cards can be found for Linux on the realtek site. (untested but believed to also solve the problem).</div>SteamedFishhttps://wiki.archlinux.org/index.php?title=Network_configuration_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=35138Network configuration (简体中文)2008-01-16T22:15:36Z<p>SteamedFish: Translate from original English document. Not finished.</p>
<hr />
<div>[[Category:Networking (简体中文)]]<br />
[[Category:Getting and installing Arch (简体中文)]]<br />
[[Category:HOWTOs (简体中文)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Configuring_network}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Статический IP и DHCP}}<br />
{{i18n_entry|Česky|Statická IP a DHCP czech}}<br />
{{i18n_entry|简体中文|网络配置}}<br />
{{i18n_links_end}}<br />
<br />
{{translateme}}<br />
<br />
== 概览 ==<br />
<br />
一个简单的让你的网络工作的指导。<br />
<br />
A simple guide to get your network running.<br />
<br />
<br />
== 加载设备模块 ==<br />
<br />
如果你使用 [[hwdetect]] ,它应该可以检测你的网卡( NIC )模块并在开机时自动加载。<br />
否则的话,你需要根据你的硬件情况,判断哪些模块是需要加载的。<br />
<br />
在网上搜索你的网卡型号,或者尝试着用 Linux LiveCD 来寻找需要的模块的名字──在启动后运行 lsmod 来查看当前加载的所有模块。<br />
<br />
当你知道应该使用哪些模块之后,你可以加载它:<br />
<br />
# modprobe <模块名><br />
<br />
如果你不想/不能使用像 [[hwdetect]] 这样的自动加载工具,你可以把这些模块添加到 <code>/etc/rc.conf</code> 中去,这样你就不用每次开机之后手动加载它。例如,如果 tg3 是你需要的网络模块:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
其他常见的模块是: 8139too ( Realtek 芯片); sis900 ( SiS 卡)。<br />
<br />
If you use [[hwdetect]] it should detect your network card (NIC) module and load it automatically at startup. Otherwise, you will need to know which module is needed for your particular model.<br />
<br />
Search the Web for your card model, or try using a Linux LiveCD to find out the name of the needed module - run [[Linux And Hardware|lsmod]] to show you all currently loaded modules after booting.<br />
<br />
Now when you know which module to use you can load it:<br />
<br />
# modprobe <modulename><br />
<br />
If you don't want / can't use some auto-loader like [[hwdetect]] you can add it into the modules array in <code>/etc/rc.conf</code>, so you don't need to modprobe it everytime you boot. For example, if tg3 is the network module:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
Other common modules are 8139too for cards with the Realtek chipset or sis900 for SiS cards.<br />
<br />
== 配置 IP ==<br />
<br />
=== DHCP (自动获取) IP ===<br />
<br />
在这种情况下,你需要安装 dhcpd 包(绝大多数情况下都是默认安装好的)。这样编辑 <code>/etc/rc.conf</code> :<br />
<br />
eth0="dhcp"<br />
INTERFACES=(eth0)<br />
ROUTES=(!gateway)<br />
<br />
For this, you need the dhcpcd package (usually already available on most installation). Edit <code>/etc/rc.conf</code> like this:<br />
<br />
eth0="dhcp"<br />
INTERFACES=(eth0)<br />
ROUTES=(!gateway)<br />
<br />
=== 静态 IP ===<br />
<br />
如果你需要在不使用路由器的情况下,和一台安装 Windows 的电脑分享你的网络连接,确保两台电脑都使用静态 IP ,否则你的局域网将会有问题。<br />
<br />
你需要:<br />
<br />
* 你的静态IP地址;<br />
* 子网掩码;<br />
* 广播地址;<br />
* 你的网关;<br />
* DNS 服务器(域名服务器)的 IP 地址;<br />
* 你的域名。<br />
<br />
如果你想配置一个内部网络,可以将你的 IP设置成 192.168.*.* ,子网掩码设置成 255.255.0.0 ,广播地址设置成 192.168.255.255 。除非你的网络拥有路由器,否则网关地址不重要。参考下面的例子编辑你的<code>/etc/rc.conf</code> ,使用你自己的 IP ,掩码,广播地址和网关:<br />
<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
<br />
上面这个例子中, IP 为 82.137.129.29 ,掩码为 255.255.255.0 ,广播地址为 82.137.129.255 ,网关为 82.137.129.1<br />
<br />
参考下面的例子编辑 <code>/etc/resolv.conf</code> ,使用你自己的域名服务器的 IP 和你的域名:<br />
<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
<br />
上面的例子中,两个域名服务器分别为 61.23.173.5 、 61.95.849.8 。<br />
<br />
你可以添加任意多个域名服务器。<br />
<br />
如果你使用 DHCP 自动获取 IP 地址,但是不想每次启动网络的时候让 DHCP 更改你的 DNS 服务器(域名服务器),在 <code>/etc/conf.d/dhcpcd</code> 中的 <code>DHCPCD_ARGS</code> 中添加 -R 选项。这样会阻止 DHCP 在每次网络启动的时候改写你的 <code>/etc/resolv.conf</code> :<br />
<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
If you share your internet connection from a Windows box without a router, be sure to use static IPs on both computers. Otherwise you will have LAN issues.<br />
<br />
You need:<br />
<br />
* Your static IP address,<br />
* The netmask,<br />
* The broadcast address,<br />
* Your gateway,<br />
* Your nameservers' IP addresses,<br />
* Your domain name.<br />
<br />
If you are running a private network, it is safe to use IP addresses in 192.168.*.'* for your IPs, with a netmask of 255.255.0.0 and broadcast address of 192.168.255.255. Unless your network has a router, the gateway address does not matter. Edit <code>/etc/rc.conf</code> like this, substituting your own values for the IP, netmask, broadcast, and gateway:<br />
<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
<br />
and your <code>/etc/resolv.conf</code> like this, substituting your nameservers' IPs and your domain name:<br />
<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
<br />
You may include as many nameserver lines as you wish.<br />
<br />
If you use DHCP and you don't want your DNS servers to change every time you start your network, be sure to add the "-R" option to <code>DHCPCD_ARGS</code> in <code>/etc/conf.d/dhcpcd</code> (used by in <code>/etc/rc.d/network</code>). This prevents DHCP from rewriting your <code>/etc/resolv.conf</code> every time:<br />
<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
==其他选项==<br />
<br />
如果因为某些原因, 使用 DHCP 自动获取( dhcpd eth0 )失败,安装 dhclient ( pacman -Sy dhclient ),使用 '<code>dhclient eth0</code>' 代替。<br />
<br />
<br />
If for some reason dhcpcd eth0 fails, install dhclient (pacman -Sy dhclient)<br />
and use '<code>dhclient eth0</code>' instead.<br />
<br />
== 设置计算机名 ==<br />
<br />
编辑 <code>/etc/rc.conf</code> ,将 HOSTNAME 设置成你想要的计算机名称:<br />
<br />
HOSTNAME="banana"<br />
<br />
Edit <code>/etc/rc.conf</code> and set HOSTNAME to your desired computer name:<br />
HOSTNAME="banana"<br />
<br />
<br />
== 设置本机域名/ IP ==<br />
<br />
编辑 <code>/etc/hosts</code> ,添加你在 <code>/etc/rc.conf</code> 的 HOSTNAME 选项中填写的东西,按照这样的格式:<br />
<br />
127.0.0.1 banana.domain.org localhost.localdomain localhost banana<br />
<br />
那些带有 localhost 的项是很多程序所需要的<br />
<br />
Edit <code>/etc/hosts</code> and add the same HOSTNAME you entered in <code>/etc/rc.conf</code> :<br />
127.0.0.1 banana.domain.org localhost.localdomain localhost banana<br />
<br />
This format, including the localhost entries is required for program compatibility.<br />
<br />
== 导入设置 ==<br />
<br />
想测试你的设置,可以重启计算机,或者在 root (超级用户)下运行 <code>/etc/rc.d/network restart</code> 。<br />
试着按照这个顺序 ping 一些网络地址:你的网关, DNS 服务器(域名服务器), ISP 服务提供商,以及其他的网络地址。这样可以检查你的网络连接在哪里出了问题。<br />
<br />
To test your settings either reboot the computer, or as root, run <code>/etc/rc.d/network restart</code>.<br />
Try pinging your gateway, DNS server, ISP provider and other Internet sites, in that order, to detect any connection problems along the way.<br />
<br />
<br />
== 更多的设置==<br />
<br />
=== 无线网络配置 ===<br />
<br />
无线网络( wlan )配置在 [[Wireless Setup |另外一个wiki页面]] 中。<br />
<br />
The wireless (wlan) configuration is the topic of [[Wireless Setup|another wiki page]].<br />
<br />
=== 防火墙 ===<br />
<br />
你可以安装和配置 [[Firewalls |防火墙]] 来让你感到更安全。<br />
<br />
You can install and configure a [[Firewalls|firewall]] to feel more secure. ;-)<br />
<br />
=== 即插即用( Ifplugd ) ===<br />
<br />
你可以安装这个服务( Ifplugd ),使得当网络接入的时候自动配置网络,当网络断开的时候自动取消配置。这对于笔记本电脑这样的使用移动式的网络适配器的情况很有用,因为他只会在网络实际接入的时候才会配置网络接口。另外一个可能会用得着它的情况是,你需要重启你的网络,可是你既不想重启电脑也不想在 shell (终端)中配置。<br />
<br />
它在 [extra] 中,因此安装非常简单:<br />
<br />
# pacman -S ifplugd<br />
<br />
在默认情况下,它会检查 eth0 设备。更改这个设置(以及更改其他设置,比如等待时间),可以编辑 <code>/etc/ifplugd/ifplugd.conf</code> 。<br />
<br />
运行这个命令来启动它:<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
或者将它加入<code>/etc/rc.conf</code> 的 DAEMONS 列表,这样它就能开机自动启动了。<br />
<br />
<br />
You can install a daemon which will automatically configure your Ethernet device when a cable is plugged in and automatically unconfigure it if the cable is pulled. This is useful on laptops with onboard network adapters, since it will only configure the interface when a cable is really connected. Another use is when you just need to restart the network but don't want to restart the computer or do it from the shell.<br />
<br />
Installation is very simple since it's in [extra]:<br />
<br />
# pacman -S ifplugd<br />
<br />
By default it is configured to work for eth0 device. This and other settings like delays can be configured in <code>/etc/ifplugd/ifplugd.conf</code>.<br />
<br />
Start it with<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
or add it into DAEMONS array in <code>/etc/rc.conf</code>.<br />
<br />
=== 绑定 ===<br />
<br />
你可以安装 'ifenslave' 来让你的两块真实网卡绑定同一个 IP 地址。<br />
<br />
/etc/conf.d/bonding<br />
bond_bond0="eth0 eth1"<br />
BOND_INTERFACES=(bond0)<br />
<br />
/etc/rc.conf<br />
MODULES=(... bonding ...)<br />
bond0="bond0 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"<br />
INTERFACES=(bond0)<br />
使用<br />
#/etc/rc.d/network restart<br />
重启网络<br />
<br />
You can install 'ifenslave' to bind two real Ethernet cables with one IP address.<br />
/etc/conf.d/bonding<br />
bond_bond0="eth0 eth1"<br />
BOND_INTERFACES=(bond0)<br />
/etc/rc.conf<br />
MODULES=(... bonding ...)<br />
bond0="bond0 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"<br />
INTERFACES=(bond0)<br />
restart network by<br />
/etc/rc.d/network restart<br />
<br />
== Troubleshooting ==<br />
<br />
=== Swapping computers on the cable modem ===<br />
<br />
Most domestic cable ISPs (videotron for example) have the cable modem configured to recognise only one client PC, by the MAC address of its network interface. Once the cable modem has learnt the MAC address of the first PC that talks to it, it will not respond to another MAC address in any way. Thus if you swap one PC for another (or for a router), the new PC (or router) will not work with the cable modem, because the new PC (or router) has a different MAC address to the old one. To reset the cable modem so that it will recognise the new PC, you must power the cable modem off and on again. Once the cable modem has rebooted and gone fully online again (indicator lights settled down), reboot the newly connected PC so that it makes a DHCP request, or manually make it request a new DHCP lease.<br />
<br />
=== The TCP Window Scaling Issue ===<br />
<br />
TCP packets contain a "window" value in their headers indicating how much data the other host may send in return. This value is represented with only 16 bits, hence the window size is at most 64Kb. TCP packets are cached for a while (they have to be reordered), and as memory is (or used to be) limited, one host could easily run out of it.<br />
<br />
Back in 1992, as more and more memory became available, [http://www.faqs.org/rfcs/rfc1323.html RFC 1323] was written to improve the situation: Window Scaling. The "window" value, provided in all packets, will be modified by a Scale Factor defined once, at the very beginning of the connection.<br />
<br />
That 8-bit Scale Factor allows the Window to be up to 32 times higher than the initial 64Kb.<br />
<br />
It appears that some broken routers and firewalls on the Internet are rewriting the Scale Factor to 0 which causes misunderstandings between hosts.<br />
<br />
The Linux kernel 2.6.17 introduced a new calculation scheme generating higher Scale Factors, virtually making the aftermaths of the broken routers and firewalls more visible. <br />
<br />
The resulting connection is at best very slow or broken.<br />
<br />
==== How To Diagnose The Problem? ====<br />
<br />
First of all, let's make it clear: this problem is odd. In some cases, you will not be able to use TCP connections (HTTP, FTP, ...) at all and in others, you will be able to communicate with some hosts (very few).<br />
<br />
'''Warning''': <code>dmesg</code>'s output is OK, logs are clean and <code>ifconfig</code> will report normal status &mdash; and actually everything is normal.<br />
<br />
If you can't browse any website, but you can ping some rare hosts, chances are great that you're experiencing this issue: ping uses the ICMP protocol and is not affected by TCP issues.<br />
<br />
You can try to use WireShark. You might see successful UDP and ICMP communications but unsuccessful TCP communications (only to foreign hosts).<br />
<br />
==== How To Fix It? (The bad way) ====<br />
<br />
To fix it the bad way, you can change the tcp_rmem value, on which Scale Factor calculation is based. Although it should work for most hosts, it's not guaranteed, especially for very distant ones.<br />
<br />
echo "4096 87380 174760" > /proc/sys/net/ipv4/tcp_rmem<br />
<br />
Or you can try to remove one of your RAM sticks (yes, sir).<br />
<br />
==== How To Fix It? (The good way) ====<br />
<br />
Simply disable Window Scaling. Even if Window Scaling is a nice TCP feature, it may be uncomfortable especially if you can't fix the broken router. There are several ways to disable Window Scaling, and it seems that the most bulletproof (which will work with most kernels) is to add the following lines to your <code>/etc/rc.local</code>:<br />
<br />
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling<br />
<br />
==== How To Fix It? (The best way) ====<br />
<br />
This issue is caused by broken routers/firewalls, so let's change them. Some users have reported that the broken router was their very own DSL router.<br />
<br />
==== More about it? ====<br />
<br />
This section is based on the LWN article [http://lwn.net/Articles/92727/ TCP window scaling and broken routers] and a Kernel Trap article: [http://kerneltrap.org/node/6723 Window Scaling on the Internet].<br />
<br />
And more recently, some Archers have been hit by this issue:<br />
<br />
* [http://www.archlinux.org/pipermail/arch/2006-June/011250.html Odd network issue]<br />
* [http://www.archlinux.org/pipermail/arch/2006-September/011943.html Kernel 2.6.17 and TCP window scaling] &mdash; the topic which initiated this article<br />
<br />
There are also several relevant threads on the LKML.<br />
<br />
<br />
=== Realtek No Link / WOL issue ===<br />
<br />
Users with Realtek 8168 8169 8101 8111 based NICs (cards / and on board) may notice an issue where the NIC seems to be disabled on boot and has no Link light. This can usually be found on a dual boot system where Windows is also installed. It seems that using the offical realtek drivers (dated anything after May 2007) under windows is the cause. These newer drivers disable the Wake-On-Lan feature by disabling the NIC at Windows shutdown time, where it will remain disabled until the next time Windows boots. You will be able to spot if this is issue is affecting you because the Link light will remain off only until Windows boots, during Windows shutdown it will revert back to the Link light being off. Normal operation should be that the link light is always on as long as the system is on, even during POST. This issue will also affect other OS's without newer drivers (eg. Live CD's). Here's a couple of fixes for this issue.<br />
<br />
==== Method 1 - Rollback/Change Win driver ====<br />
<br />
You can rollback your Windows NIC driver to the Microsoft provided one (if available), or rollback/install to an official Realtek driver pre-dated May 2007 (maybe on the CD that came with your hardware).<br />
<br />
==== Method 2 - Enable WOL in Win driver ====<br />
<br />
Probably the best and fastest fix is to change this setting in the Windows driver. This way it should be fixed system wide and not only under Arch (eg. live CD's, other OSes). In Windows under device manager, find your Realtek Network adapter and double click it. Under the advanced tab change "wake-on-lan after shutdown" to enable.<br />
<br />
In Windows XP (example)<br />
Right click my computer --> Hardware tab --> Device Manager --> Network Adapters --> "double click" Realtek ... --> Advanced tab --> Wake-On-Lan After Shutdown --> Enable.<br />
<br />
==== Method 3 - Newer Realtek Linux driver ====<br />
<br />
Any newer driver for these Realtek cards can be found for Linux on the realtek site. (untested but believed to also solve the problem).</div>SteamedFish