| 1 |
# |
| 2 |
# AUTHOR <EMAIL@ADDRESS>, YEAR. |
| 3 |
# Ryuunosuke Ayanokouzi <[email protected]>, 2015-2019. |
| 4 |
# Kenshi Muto <[email protected]>, 2015. |
| 5 |
# Yoichi Chonan <[email protected]>, 2015. |
| 6 |
# YABUKI Youichi <[email protected]>, 2015. |
| 7 |
# |
| 8 |
msgid "" |
| 9 |
msgstr "" |
| 10 |
"Project-Id-Version: 0\n" |
| 11 |
"POT-Creation-Date: 2022-07-30 18:23+0200\n" |
| 12 |
"PO-Revision-Date: 2019-02-03 09:00+0900\n" |
| 13 |
"Last-Translator: AYANOKOUZI, Ryuunosuke <[email protected]>\n" |
| 14 |
"Language-Team: Japanese <https://github.com/l/debian-handbook/tree/master/translation/ja_JP/push>\n" |
| 15 |
"Language: ja\n" |
| 16 |
"MIME-Version: 1.0\n" |
| 17 |
"Content-Type: application/x-publican; charset=UTF-8\n" |
| 18 |
"Content-Transfer-Encoding: 8bit\n" |
| 19 |
|
| 20 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 21 |
msgid "Network" |
| 22 |
msgstr "ネットワーク" |
| 23 |
|
| 24 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 25 |
msgid "Gateway" |
| 26 |
msgstr "ゲートウェイ" |
| 27 |
|
| 28 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 29 |
msgid "TCP/IP" |
| 30 |
msgstr "TCP/IP" |
| 31 |
|
| 32 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 33 |
msgid "IPv6" |
| 34 |
msgstr "IPv6" |
| 35 |
|
| 36 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 37 |
msgid "DNS" |
| 38 |
msgstr "DNS" |
| 39 |
|
| 40 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 41 |
msgid "Bind" |
| 42 |
msgstr "Bind" |
| 43 |
|
| 44 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 45 |
msgid "DHCP" |
| 46 |
msgstr "DHCP" |
| 47 |
|
| 48 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 49 |
msgid "QoS" |
| 50 |
msgstr "QoS" |
| 51 |
|
| 52 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 53 |
msgid "Network Infrastructure" |
| 54 |
msgstr "ネットワークインフラ" |
| 55 |
|
| 56 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 57 |
msgid "Linux sports the whole Unix heritage for networking, and Debian provides a full set of tools to create and manage them. This chapter reviews these tools." |
| 58 |
msgstr "Linux はネットワークに関する Unix の財産すべてを受け継ぎ、Debian はネットワークを作成および管理する完全なツールセットを提供します。この章では、これらのツールを説明します。" |
| 59 |
|
| 60 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 61 |
msgid "<primary>gateway</primary>" |
| 62 |
msgstr "<primary>ゲートウェイ</primary>" |
| 63 |
|
| 64 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 65 |
msgid "<primary>network</primary><secondary>gateway</secondary>" |
| 66 |
msgstr "<primary>ネットワーク</primary><secondary>ゲートウェイ</secondary>" |
| 67 |
|
| 68 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 69 |
msgid "<primary>router</primary>" |
| 70 |
msgstr "<primary>ルータ</primary>" |
| 71 |
|
| 72 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 73 |
msgid "A gateway is a system linking several networks. This term often refers to a local network's “exit point” on the mandatory path to all external IP addresses. The gateway is connected to each of the networks it links together, and acts as a router to convey IP packets between its various interfaces." |
| 74 |
msgstr "ゲートウェイは複数のネットワークを連結するシステムです。ゲートウェイという用語は外部 IP アドレスに向かう経路に出るために必須のローカルネットワークの「出口」を意味する場合が多いです。ゲートウェイは相互に連結する各ネットワークに接続されており、複数のインターフェース間で IP パケットを相互に伝送するためのルータとして振る舞います。" |
| 75 |
|
| 76 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 77 |
msgid "<emphasis>BACK TO BASICS</emphasis> IP packet" |
| 78 |
msgstr "<emphasis>BACK TO BASICS</emphasis> IP パケット" |
| 79 |
|
| 80 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 81 |
msgid "<primary>packet</primary><secondary>IP</secondary>" |
| 82 |
msgstr "<primary>パケット</primary><secondary>IP パケット</secondary>" |
| 83 |
|
| 84 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 85 |
#, fuzzy |
| 86 |
#| msgid "<primary>DNS</primary><secondary>automated updates</secondary>" |
| 87 |
msgid "<primary>IP</primary><seealso>Internet Protocol</seealso>" |
| 88 |
msgstr "<primary>DNS</primary><secondary sortas=\"ジドウコウシン\">自動更新</secondary>" |
| 89 |
|
| 90 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 91 |
#, fuzzy |
| 92 |
#| msgid "<primary>AH, protocol</primary>" |
| 93 |
msgid "<primary>Internet Protocol</primary>" |
| 94 |
msgstr "<primary>AH、プロトコル</primary>" |
| 95 |
|
| 96 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 97 |
msgid "Most networks nowadays use the IP protocol (<emphasis>Internet Protocol</emphasis>). This protocol segments the transmitted data into limited-size packets. Each packet contains, in addition to its payload data, a number of details required for its proper routing." |
| 98 |
msgstr "今日、多くのネットワークは IP プロトコル (<emphasis>インターネットプロトコル</emphasis>) を使います。IP プロトコルは転送するデータを適当なサイズのパケットに分割します。それぞれのパケットには、実データ本体に加えて、適切な経路選択に必要な数々のデータが含まれます。" |
| 99 |
|
| 100 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 101 |
msgid "<emphasis>BACK TO BASICS</emphasis> TCP/UDP" |
| 102 |
msgstr "<emphasis>BACK TO BASICS</emphasis> TCP/UDP" |
| 103 |
|
| 104 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 105 |
#, fuzzy |
| 106 |
#| msgid "<primary>protocol</primary><secondary>ESP</secondary>" |
| 107 |
msgid "<primary>protocol</primary><secondary>TCP</secondary>" |
| 108 |
msgstr "<primary>プロトコル</primary><secondary>ESP</secondary>" |
| 109 |
|
| 110 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 111 |
#, fuzzy |
| 112 |
#| msgid "<primary>protocol</primary><secondary>ESP</secondary>" |
| 113 |
msgid "<primary>protocol</primary><secondary>UDP</secondary>" |
| 114 |
msgstr "<primary>プロトコル</primary><secondary>ESP</secondary>" |
| 115 |
|
| 116 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 117 |
msgid "<primary>port</primary><secondary>TCP</secondary>" |
| 118 |
msgstr "<primary>ポート</primary><secondary>TCP</secondary>" |
| 119 |
|
| 120 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 121 |
msgid "<primary>port</primary><secondary>UDP</secondary>" |
| 122 |
msgstr "<primary>ポート</primary><secondary>UDP</secondary>" |
| 123 |
|
| 124 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 125 |
#, fuzzy |
| 126 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 127 |
msgid "<primary>TCP</primary><secondary>port</secondary>" |
| 128 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 129 |
|
| 130 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 131 |
#, fuzzy |
| 132 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 133 |
msgid "<primary>UDP</primary><secondary>port</secondary>" |
| 134 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 135 |
|
| 136 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 137 |
#, fuzzy |
| 138 |
#| msgid "<primary>Dynamic Host Configuration Protocol</primary>" |
| 139 |
msgid "<primary>Transmission Control Protocol</primary><seealso></seealso>" |
| 140 |
msgstr "<primary>Dynamic Host Configuration Protocol</primary>" |
| 141 |
|
| 142 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 143 |
#, fuzzy |
| 144 |
#| msgid "<primary>protocol</primary><secondary>ESP</secondary>" |
| 145 |
msgid "<primary>User Datagram Protocol</primary><seealso>UDP</seealso>" |
| 146 |
msgstr "<primary>プロトコル</primary><secondary>ESP</secondary>" |
| 147 |
|
| 148 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 149 |
msgid "Many programs do not handle the individual packets themselves, even though the data they transmit does travel over IP; they often use TCP (<emphasis>Transmission Control Protocol</emphasis>). TCP is a layer over IP allowing the establishment of connections dedicated to data streams between two points. The programs then only see an entry point into which data can be fed with the guarantee that the same data exits without loss (and in the same sequence) at the exit point at the other end of the connection. Although many kinds of errors can happen in the lower layers, they are compensated by TCP: lost packets are retransmitted, and packets arriving out of order (for example, if they used different paths) are re-ordered appropriately." |
| 150 |
msgstr "IP を使ってデータを送信する場合であっても、プログラムが個々のパケットそれ自体を処理することはほとんどありません。多くのプログラムは TCP (<emphasis>Transmission Control Protocol</emphasis>) を使います。TCP は IP 上のレイヤで、2 点間にデータストリーム専用の接続を確立することが可能です。TCP を使うプログラムはデータを送り込むための入口を考慮するだけです。この入口から送信されたデータは接続の別の側にある出口から損失なく同じデータが (同じ順番で) 出てくると保証されます。TCP よりも下層のレイヤで起きるさまざまなエラーは TCP によって補正されます。具体的に言えば、損失したパケットはもう一度転送され、順番が狂って到着したパケット (たとえば、異なる経路で到着したために) は適切な順番にそろえられます。" |
| 151 |
|
| 152 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 153 |
# Tag: PTAL; |
| 154 |
msgid "Another protocol relying on IP is UDP (<emphasis>User Datagram Protocol</emphasis>). In contrast to TCP, it is packet-oriented. Its goals are different: the purpose of UDP is only to transmit one packet from an application to another. The protocol does not try to compensate for possible packet loss on the way, nor does it ensure that packets are received in the same order as were sent. The main advantage to this protocol is that the latency is greatly improved, since the loss of a single packet does not delay the receiving of all following packets until the lost one is retransmitted." |
| 155 |
msgstr "IP に依存するもう 1 つのプロトコルが UDP (<emphasis>User Datagram Protocol</emphasis>) です。TCP と対照的に、UDP はパケット重視です。UDP の目標は TCP と異なります。すなわち、UDP の目標は 1 個のパケットをあるアプリケーションから別のアプリケーションに転送するだけです。UDP を使った場合、転送中のパケット損失は補償されませんし、パケットが送信順と同じ順番で受信されることも保証されません。UDP の主な利点は遅延が大きく改善される点です。なぜなら、1 パケットを損失しても、損失したパケットの再転送要求を出さないかぎり、損失したパケット以降に続くパケットの受信は遅延しないからです。" |
| 156 |
|
| 157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 158 |
msgid "TCP and UDP both involve ports, which are “extension numbers” for establishing communication with a given application on a machine. This concept allows keeping several different communications in parallel with the same correspondent, since these communications can be distinguished by the port number." |
| 159 |
msgstr "TCP と UDP はどちらもポート番号を使います。ポート番号とは、マシン上で動くあるアプリケーションと通信を確立するための「内線番号」と言えます。この概念を使うことで、同一のマシンに対して複数の異なる通信を並列して保つことが可能になります。なぜなら、通信はポート番号で区別されるからです。" |
| 160 |
|
| 161 |
msgid "<primary>Internet Assigned Numbers Authority</primary><seealso>IANA</seealso>" |
| 162 |
msgstr "" |
| 163 |
|
| 164 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 165 |
#, fuzzy |
| 166 |
#| msgid "<primary>NAT</primary>" |
| 167 |
msgid "<primary>IANA</primary>" |
| 168 |
msgstr "<primary>NAT</primary>" |
| 169 |
|
| 170 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 171 |
#, fuzzy |
| 172 |
#| msgid "<primary>quality</primary><secondary>of service</secondary>" |
| 173 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/services</filename></secondary>" |
| 174 |
msgstr "<primary sortas=\"ヒンシツ\">品質</primary><secondary sortas=\"サービスノヒンシツ\">サービスの品質</secondary>" |
| 175 |
|
| 176 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 177 |
#, fuzzy |
| 178 |
#| msgid "Some of these port numbers — standardized by the IANA (<emphasis>Internet Assigned Numbers Authority</emphasis>) — are “well-known” for being associated with network services. For instance, TCP port 25 is generally used by the email server. <ulink type=\"block\" url=\"http://www.iana.org/assignments/port-numbers\" />" |
| 179 |
msgid "Some of these port numbers — standardized by the IANA (<emphasis>Internet Assigned Numbers Authority</emphasis>) — are “well-known” for being associated with network services. For instance, TCP port 25 is generally used by the email server. The list of services associated with port numbers can be found in the <filename>/etc/services</filename> file, also explained in <citerefentry><refentrytitle>services</refentrytitle> <manvolnum>5</manvolnum></citerefentry>, as well as in: <ulink type=\"block\" url=\"https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml\" />" |
| 180 |
msgstr "IANA (<emphasis>Internet Assigned Numbers Authority</emphasis>) が標準化したいくつかのポート番号は「well-known」とされ、ネットワークサービスに関連付けられています。たとえば、TCP ポート 25 番は一般に電子メールサーバが使うポート番号として標準化されています。<ulink type=\"block\" url=\"http://www.iana.org/assignments/port-numbers\" />" |
| 181 |
|
| 182 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 183 |
#, fuzzy |
| 184 |
#| msgid "<primary>service</primary><secondary>quality</secondary>" |
| 185 |
msgid "<primary>IP</primary><secondary>masquerading</secondary>" |
| 186 |
msgstr "<primary sortas=\"サービスノヒンシツ\">サービスの品質</primary>" |
| 187 |
|
| 188 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 189 |
#, fuzzy |
| 190 |
#| msgid "<primary>network</primary><secondary>gateway</secondary>" |
| 191 |
msgid "<primary>network</primary><secondary>masquerading</secondary>" |
| 192 |
msgstr "<primary>ネットワーク</primary><secondary>ゲートウェイ</secondary>" |
| 193 |
|
| 194 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 195 |
msgid "When a local network uses a private address range (not routable on the Internet), the gateway needs to implement <emphasis>address masquerading</emphasis> so that the machines on the network can communicate with the outside world. The masquerading operation is a kind of proxy operating on the network level: each outgoing connection from an internal machine is replaced with a connection from the gateway itself (since the gateway does have an external, routable address), the data going through the masqueraded connection is sent to the new one, and the data coming back in reply is sent through to the masqueraded connection to the internal machine. The gateway uses a range of dedicated TCP ports for this purpose, usually with very high numbers (over 60000). Each connection coming from an internal machine then appears to the outside world as a connection coming from one of these reserved ports." |
| 196 |
msgstr "ローカルネットワークがプライベートアドレス (インターネットにルーティングされないアドレス) 範囲を使う場合、ゲートウェイは<emphasis>アドレスマスカレード</emphasis>を実行する必要があります。<emphasis>アドレスマスカレード</emphasis>を使うことで、ローカルネットワーク上のマシンが外部と通信することが可能になります。マスカレード動作とはネットワークレベルのプロキシ動作のようなものです。すなわち、内部のマシンからの外部宛接続はゲートウェイ自身からの接続に置き替えられます (なぜなら、ゲートウェイは外部にルーティングできるアドレスを持っているからです)。マスカレード接続を通過するデータは外部に送信され、応答として戻ってくるデータはマスカレード接続を通過して内部のマシンに送信されます。ゲートウェイはこの目的に専用の TCP ポート範囲を使います。この範囲は通常とても大きな番号 (60000 番より大きい番号) です。内部マシンからの接続はこれらの予約されたポート番号の 1 つから送信された接続として外部に送信されます。" |
| 197 |
|
| 198 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 199 |
msgid "<primary>masquerading</primary>" |
| 200 |
msgstr "<primary>マスカレード</primary>" |
| 201 |
|
| 202 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 203 |
msgid "<emphasis>CULTURE</emphasis> Private address range" |
| 204 |
msgstr "<emphasis>CULTURE</emphasis> プライベートアドレス範囲" |
| 205 |
|
| 206 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 207 |
#, fuzzy |
| 208 |
#| msgid "<primary>IP address</primary><secondary>private</secondary>" |
| 209 |
msgid "<primary>IP</primary><secondary>private address</secondary>" |
| 210 |
msgstr "<primary>IP アドレス</primary><secondary>プライベート</secondary>" |
| 211 |
|
| 212 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 213 |
msgid "<primary>private IP address</primary>" |
| 214 |
msgstr "<primary>プライベート IP アドレス</primary>" |
| 215 |
|
| 216 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 217 |
# Ref: https://tools.ietf.org/html/rfc1918; |
| 218 |
# Ref: https://tools.ietf.org/html/rfc1466; |
| 219 |
msgid "RFC 1918 defines three ranges of IPv4 addresses not meant to be routed on the Internet but only used in local networks. The first one, <literal>10.0.0.0/8</literal> (see sidebar <xref linkend=\"sidebar.networking-basics\" />), is a class-A range (with 2<superscript>24</superscript> IP addresses). The second one, <literal>172.16.0.0/12</literal>, gathers 16 class-B ranges (<literal>172.16.0.0/16</literal> to <literal>172.31.0.0/16</literal>), each containing 2<superscript>16</superscript> IP addresses. Finally, <literal>192.168.0.0/16</literal> is a class-B range (grouping 256 class-C ranges, <literal>192.168.0.0/24</literal> to <literal>192.168.255.0/24</literal>, with 256 IP addresses each). <ulink type=\"block\" url=\"http://www.faqs.org/rfcs/rfc1918.html\" />" |
| 220 |
msgstr "RFC 1918 では、インターネットにルーティングされずローカルネットワークにのみ使うことができる、IPv4 アドレスの範囲が定義されています。1 番目の <literal>10.0.0.0/8</literal> (補注<xref linkend=\"sidebar.networking-basics\" />を参照してください) は 1 個のクラス A 範囲です (クラス A には 2<superscript>24</superscript> 個の IP アドレスが含まれます)。2 番目の <literal>172.16.0.0/12</literal> は 16 個のクラス B 範囲です (<literal>172.16.0.0/16</literal> から <literal>172.31.0.0/16</literal> まで)。クラス B には 2<superscript>16</superscript> 個の IP アドレスが含まれます。3 番目の <literal>192.168.0.0/16</literal> は 1 個のクラス B 範囲です (<literal>192.168.0.0/24</literal> から <literal>192.168.255.0/24</literal> までの 256 個のクラス C 範囲とも考えられます)。クラス C には 256 個の IP アドレスが含まれます。<ulink type=\"block\" url=\"http://www.faqs.org/rfcs/rfc1918.html\" />" |
| 221 |
|
| 222 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 223 |
msgid "The gateway can also perform two kinds of <emphasis>network address translation</emphasis> (or NAT for short). The first kind, <emphasis>Destination NAT</emphasis> (DNAT) is a technique to alter the destination IP address (and/or the TCP or UDP port) for a (generally) incoming connection. The connection tracking mechanism also alters the following packets in the same connection to ensure continuity in the communication. The second kind of NAT is <emphasis>Source NAT</emphasis> (SNAT), of which <emphasis>masquerading</emphasis> is a particular case; SNAT alters the source IP address (and/or the TCP or UDP port) of a (generally) outgoing connection. As for DNAT, all the packets in the connection are appropriately handled by the connection tracking mechanism. Note that NAT is only relevant for IPv4 and its limited address space; in IPv6, the wide availability of addresses greatly reduces the usefulness of NAT by allowing all “internal” addresses to be directly routable on the Internet (this does not imply that internal machines are accessible, since intermediary firewalls can filter traffic)." |
| 224 |
msgstr "ゲートウェイでは 2 種類の<emphasis>ネットワークアドレス変換</emphasis> (略して NAT) が実行されます。1 種類目は <emphasis>Destination NAT</emphasis> (DNAT) で、(通常は) 到着した接続の宛先 IP アドレス (および TCP や UDP ポート) を書き換える手法です。接続追跡メカニズムによって、通信の継続性を保証するために同じ接続でそれ以降に使われるパケットの宛先が書き換えられます。NAT の 2 種類目は <emphasis>Source NAT</emphasis> (SNAT) で、<emphasis>マスカレード</emphasis>は SNAT の特別な場合です。SNAT は (通常は) 出て行く接続のソース IP アドレス (および TCP や UDP ポート) を書き換えます。DNAT に関して言えば、出て行く接続の全パケットが接続追跡メカニズムによって適切に取り扱われます。NAT は IPv4 と IPv4 の制限されたアドレス空間だけに関連します。一方で IPv6 では、アドレス空間が広くなったことにより、すべての「内部」アドレスは直接インターネットにルーティングできるようになるため、NAT の有用性が減ります (これは内部マシンにアクセスできるようになることを意味しているのではありません。なぜなら、中間ファイアウォールがトラフィックをフィルタするからです)。" |
| 225 |
|
| 226 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 227 |
#, fuzzy |
| 228 |
#| msgid "<primary>Network</primary><secondary>Address Translation</secondary>" |
| 229 |
msgid "<primary>NAT</primary><seealso>Network Address Translation</seealso>" |
| 230 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"アドレスヘンカン\">アドレス変換</secondary>" |
| 231 |
|
| 232 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 233 |
#, fuzzy |
| 234 |
#| msgid "<primary>Network</primary><secondary>Address Translation</secondary>" |
| 235 |
msgid "<primary>Network Address Translation</primary><seealso>NAT</seealso>" |
| 236 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"アドレスヘンカン\">アドレス変換</secondary>" |
| 237 |
|
| 238 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 239 |
#, fuzzy |
| 240 |
#| msgid "<primary>Network</primary><secondary>Address Translation</secondary>" |
| 241 |
msgid "<primary>network</primary><secondary>address translation</secondary><seealso>NAT</seealso>" |
| 242 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"アドレスヘンカン\">アドレス変換</secondary>" |
| 243 |
|
| 244 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 245 |
#, fuzzy |
| 246 |
#| msgid "<primary>network</primary><secondary>gateway</secondary>" |
| 247 |
msgid "<primary>network</primary><secondary>NAT</secondary>" |
| 248 |
msgstr "<primary>ネットワーク</primary><secondary>ゲートウェイ</secondary>" |
| 249 |
|
| 250 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 251 |
#, fuzzy |
| 252 |
#| msgid "<primary>DNS</primary><secondary>automated updates</secondary>" |
| 253 |
msgid "<primary>SNAT</primary><seealso>Source NAT</seealso>" |
| 254 |
msgstr "<primary>DNS</primary><secondary sortas=\"ジドウコウシン\">自動更新</secondary>" |
| 255 |
|
| 256 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 257 |
#, fuzzy |
| 258 |
#| msgid "<primary>Source NAT</primary>" |
| 259 |
msgid "<primary>Source NAT</primary><seealso>SNAT</seealso>" |
| 260 |
msgstr "<primary>Source NAT</primary>" |
| 261 |
|
| 262 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 263 |
#, fuzzy |
| 264 |
#| msgid "<primary>DNS</primary><secondary>automated updates</secondary>" |
| 265 |
msgid "<primary>DNAT</primary><seealso>Destination NAT</seealso>" |
| 266 |
msgstr "<primary>DNS</primary><secondary sortas=\"ジドウコウシン\">自動更新</secondary>" |
| 267 |
|
| 268 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 269 |
#, fuzzy |
| 270 |
#| msgid "<primary>Destination NAT</primary>" |
| 271 |
msgid "<primary>Destination NAT</primary><seealso>DNAT</seealso>" |
| 272 |
msgstr "<primary>Destination NAT</primary>" |
| 273 |
|
| 274 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 275 |
msgid "<emphasis>BACK TO BASICS</emphasis> Port forwarding" |
| 276 |
msgstr "<emphasis>BACK TO BASICS</emphasis> ポート転送" |
| 277 |
|
| 278 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 279 |
msgid "<primary>port forwarding</primary>" |
| 280 |
msgstr "<primary sortas=\"ポートテンソウ\">ポート転送</primary>" |
| 281 |
|
| 282 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 283 |
#, fuzzy |
| 284 |
#| msgid "<primary>network</primary><secondary>gateway</secondary>" |
| 285 |
msgid "<primary>network</primary><secondary>port forwarding</secondary>" |
| 286 |
msgstr "<primary>ネットワーク</primary><secondary>ゲートウェイ</secondary>" |
| 287 |
|
| 288 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 289 |
#, fuzzy |
| 290 |
#| msgid "<primary><command>ripd</command></primary>" |
| 291 |
msgid "<primary><command>redir</command></primary>" |
| 292 |
msgstr "<primary><command>ripd</command></primary>" |
| 293 |
|
| 294 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 295 |
msgid "A concrete application of DNAT is <emphasis>port forwarding</emphasis>. Incoming connections to a given port of a machine are forwarded to a port on another machine. Other solutions may exist for achieving a similar effect, though, especially at the application level with <command>ssh</command> (see <xref linkend=\"sect.ssh-port-forwarding\" />) or <command>redir</command>." |
| 296 |
msgstr "DNAT の具体的な応用例が<emphasis>ポート転送</emphasis>です。マシンのあるポートに到着する接続が他のマシンのあるポートに転送されます。特にアプリケーションレベルでは <command>ssh</command> (<xref linkend=\"sect.ssh-port-forwarding\" />を参照してください) や <command>redir</command> などを使うことで、同じ効果を果たす別の解決策が存在するかもしれません。" |
| 297 |
|
| 298 |
msgid "<primary>filesystem</primary><secondary>virtual</secondary><tertiary><filename>/proc/</filename></tertiary>" |
| 299 |
msgstr "" |
| 300 |
|
| 301 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 302 |
msgid "Enough theory, let's get practical. Turning a Debian system into a gateway is a simple matter of enabling the appropriate option in the Linux kernel, by way of the <filename>/proc/</filename> virtual filesystem:" |
| 303 |
msgstr "理論はここまでにして、具体的な例を説明します。Debian システムをゲートウェイとして機能させるには、以下に示す通り <filename>/proc/</filename> 仮想ファイルシステムを使って、Linux カーネルの適切なオプションを有効化するだけです。" |
| 304 |
|
| 305 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 306 |
msgid "" |
| 307 |
"\n" |
| 308 |
"<computeroutput># </computeroutput><userinput>echo 1 > /proc/sys/net/ipv4/conf/default/forwarding</userinput>" |
| 309 |
msgstr "" |
| 310 |
"\n" |
| 311 |
"<computeroutput># </computeroutput><userinput>echo 1 > /proc/sys/net/ipv4/conf/default/forwarding</userinput>" |
| 312 |
|
| 313 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 314 |
#, fuzzy |
| 315 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 316 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/sysctl.conf</filename></secondary>" |
| 317 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 318 |
|
| 319 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 320 |
#, fuzzy |
| 321 |
#| msgid "<primary>traffic</primary><secondary>limitation</secondary>" |
| 322 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/sysctl.d/</filename></secondary>" |
| 323 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイゲン\">制限</secondary>" |
| 324 |
|
| 325 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 326 |
#, fuzzy |
| 327 |
#| msgid "This option can also be automatically enabled on boot if <filename>/etc/sysctl.conf</filename> sets the <literal>net.ipv4.conf.default.forwarding</literal> option to <literal>1</literal>." |
| 328 |
msgid "This option can also be automatically enabled on boot if <filename>/etc/sysctl.conf</filename> or a configuration file in <filename>/etc/sysctl.d/</filename> sets the <literal>net.ipv4.conf.default.forwarding</literal> option to <literal>1</literal>." |
| 329 |
msgstr "このオプションを起動時に自動的に有効化するには、<filename>/etc/sysctl.conf</filename> の <literal>net.ipv4.conf.default.forwarding</literal> オプションを <literal>1</literal> に設定してください。" |
| 330 |
|
| 331 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 332 |
msgid "The <filename>/etc/sysctl.conf</filename> file" |
| 333 |
msgstr "<filename>/etc/sysctl.conf</filename> ファイル" |
| 334 |
|
| 335 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 336 |
msgid "" |
| 337 |
"\n" |
| 338 |
"net.ipv4.conf.default.forwarding = 1\n" |
| 339 |
"net.ipv4.conf.default.rp_filter = 1\n" |
| 340 |
"net.ipv4.tcp_syncookies = 1" |
| 341 |
msgstr "" |
| 342 |
"\n" |
| 343 |
"net.ipv4.conf.default.forwarding = 1\n" |
| 344 |
"net.ipv4.conf.default.rp_filter = 1\n" |
| 345 |
"net.ipv4.tcp_syncookies = 1" |
| 346 |
|
| 347 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 348 |
msgid "The same effect can be obtained for IPv6 by simply replacing <literal>ipv4</literal> with <literal>ipv6</literal> in the manual command and using the <literal>net.ipv6.conf.all.forwarding</literal> line in <filename>/etc/sysctl.conf</filename>." |
| 349 |
msgstr "IPv6 に対して同様の効果を与えるには、IPv4 に対して手作業で行ったコマンドの <literal>ipv4</literal> を単純に <literal>ipv6</literal> へ置換して実行するか、<filename>/etc/sysctl.conf</filename> 中の <literal>net.ipv6.conf.all.forwarding</literal> オプションを <literal>1</literal> に設定してください。" |
| 350 |
|
| 351 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 352 |
msgid "Enabling IPv4 masquerading is a slightly more complex operation that involves configuring the <emphasis>netfilter</emphasis> firewall." |
| 353 |
msgstr "IPv4 マスカレードを設定するには少し複雑な作業が必要です。すなわち <emphasis>netfilter</emphasis> ファイアウォールを設定する必要があります。" |
| 354 |
|
| 355 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 356 |
msgid "Similarly, using NAT (for IPv4) requires configuring <emphasis>netfilter</emphasis>. Since the primary purpose of this component is packet filtering, the details are listed in <xref linkend=\"security\" xrefstyle=\"select: label quotedtitle nopage\" /> (see <xref linkend=\"sect.firewall-packet-filtering\" />)." |
| 357 |
msgstr "同様に、(IPv4 で) NAT を使うには <emphasis>netfilter</emphasis> の設定が必要です。<emphasis>netfilter</emphasis> の基本目的はパケットフィルタリングですから、詳細は<xref linkend=\"security\" xrefstyle=\"select: label quotedtitle nopage\" />に書かれています (<xref linkend=\"sect.firewall-packet-filtering\" />を参照してください)。" |
| 358 |
|
| 359 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 360 |
#, fuzzy |
| 361 |
#| msgid "<primary>X.509, certificate</primary>" |
| 362 |
msgid "X.509 certificates" |
| 363 |
msgstr "<primary>X.509</primary><secondary sortas=\"ショウメイショ\">証明書</secondary>" |
| 364 |
|
| 365 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 366 |
msgid "<primary>certificate</primary><secondary>X.509</secondary>" |
| 367 |
msgstr "<primary sortas=\"ショウメイショ\">証明書</primary><secondary>X.509</secondary>" |
| 368 |
|
| 369 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 370 |
msgid "<primary>SSL</primary>" |
| 371 |
msgstr "<primary>SSL</primary>" |
| 372 |
|
| 373 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 374 |
#, fuzzy |
| 375 |
#| msgid "<primary>record</primary><secondary>DNS</secondary>" |
| 376 |
msgid "<primary>Secure Socket Layer</primary><seealso>SSL</seealso>" |
| 377 |
msgstr "<primary>レコード</primary><secondary>DNS</secondary>" |
| 378 |
|
| 379 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 380 |
msgid "<primary>TLS</primary>" |
| 381 |
msgstr "<primary>TLS</primary>" |
| 382 |
|
| 383 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 384 |
#, fuzzy |
| 385 |
#| msgid "<primary>port</primary><secondary>TCP</secondary>" |
| 386 |
msgid "<primary>Transport Layer Security</primary><seealso>TLS</seealso>" |
| 387 |
msgstr "<primary>ポート</primary><secondary>TCP</secondary>" |
| 388 |
|
| 389 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 390 |
#, fuzzy |
| 391 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 392 |
msgid "<primary>X.509</primary><secondary>certificates</secondary>" |
| 393 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 394 |
|
| 395 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 396 |
#, fuzzy |
| 397 |
#| msgid "<primary>DNS</primary><secondary>automated updates</secondary>" |
| 398 |
msgid "<primary>CA</primary><seealso>Certificate Authority</seealso>" |
| 399 |
msgstr "<primary>DNS</primary><secondary sortas=\"ジドウコウシン\">自動更新</secondary>" |
| 400 |
|
| 401 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 402 |
#, fuzzy |
| 403 |
#| msgid "<primary>X.509, certificate</primary>" |
| 404 |
msgid "<primary>Certificate Authority</primary>" |
| 405 |
msgstr "<primary>X.509</primary><secondary sortas=\"ショウメイショ\">証明書</secondary>" |
| 406 |
|
| 407 |
msgid "Certificates are an important building block of many network services built on cryptographic protocols, when they need some sort of central authentication." |
| 408 |
msgstr "" |
| 409 |
|
| 410 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 411 |
#, fuzzy |
| 412 |
#| msgid "<primary>IKE</primary>" |
| 413 |
msgid "<primary>IETF</primary>" |
| 414 |
msgstr "<primary>IKE</primary>" |
| 415 |
|
| 416 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 417 |
#, fuzzy |
| 418 |
#| msgid "The SSL protocol (<emphasis>Secure Socket Layer</emphasis>) was invented by Netscape to secure connections to web servers. It was later standardized by IETF under the acronym TLS (<emphasis>Transport Layer Security</emphasis>). Since then TLS continued to evolve and nowadays SSL is deprecated due to multiple design flaws that have been discovered." |
| 419 |
msgid "Among those protocols, SSL (<emphasis>Secure Socket Layer</emphasis>) was invented by Netscape to secure connections to web servers. It was later standardized by IETF under the acronym TLS (<emphasis>Transport Layer Security</emphasis>). Since then TLS continued to evolve, and nowadays SSL is deprecated due to multiple design flaws that have been discovered." |
| 420 |
msgstr "SSL (<emphasis>Secure Socket Layer</emphasis>) プロトコルはウェブサーバとの安全な接続を確立する目的で Netscape によって考案されました。SSL は後に TLS (<emphasis>Transport Layer Security</emphasis>) の下で IETF によって標準化されました。その後 TLS は進化を続けました。対して SSL は構造的欠陥を見つけられたため SSL を使うことは推奨されません。" |
| 421 |
|
| 422 |
msgid "The TLS protocol aims primarily to provide privacy and data integrity between two or more communicating computer applications. The most common case on the Internet is the communication between a client (e.g. a web browser) and a server." |
| 423 |
msgstr "" |
| 424 |
|
| 425 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 426 |
#, fuzzy |
| 427 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 428 |
msgid "<primary>certificate</primary><secondary>root certificate</secondary>" |
| 429 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 430 |
|
| 431 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 432 |
#, fuzzy |
| 433 |
#| msgid "However, anyone can create a key pair, store any identity on it, and pretend to be the identity of their choice. One solution involves the concept of a <emphasis>Certification Authority</emphasis> (CA), formalized by the X.509 standard. This term covers an entity that holds a trusted key pair known as a <emphasis>root certificate</emphasis>. This certificate is only used to sign other certificates (key pairs), after proper steps have been undertaken to check the identity stored on the key pair. Applications using X.509 can then check the certificates presented to them, if they know about the trusted root certificates." |
| 434 |
msgid "A key pair is needed for the exchange of information, which involves a public key that includes information about the identity of the owner and matches a private key. The private key must be kept secret, otherwise the security is compromised. However, anyone can create a key pair, store any identity on it, and pretend to be the identity of their choice. One solution involves the concept of a <emphasis>Certification Authority</emphasis> (CA), formalized by the X.509 standard. This term covers an entity that holds a trusted key pair known as a <emphasis>root certificate</emphasis>. This certificate is only used to sign other certificates (key pairs), after proper steps have been undertaken to check the identity stored on the key pair. Applications using X.509 can then check the certificates presented to them, if they know about the trusted root certificates." |
| 435 |
msgstr "しかしながら、鍵ペアを作り、鍵ペアに任意の識別情報を保存し、自由に識別情報を偽ることは誰でも可能です。これに対する 1 つの解決策が X.509 標準によって体系化された<emphasis>認証局</emphasis> (CA) の概念です。<emphasis>認証局</emphasis>という用語には、<emphasis>ルート証明書</emphasis>として知られる信頼された鍵ペアに保存された識別情報の実体の意味も含まれています。<emphasis>ルート証明書</emphasis>は他の証明書 (鍵ペア) を署名するためにのみ使われ、署名したい鍵ペアに保存される識別情報を確認するために適切な手順を経た後に署名が行われます。こうすることで X.509 を使うアプリケーションは自分に提示された証明書の識別情報を確認し、提示された証明書が信頼されたルート証明書によって署名されたかを判断できます。" |
| 436 |
|
| 437 |
msgid "You can implement a CA (as described in <xref linkend=\"sect.easy-rsa\" />), but if you intend to use the certificate for a website, you need to rely on a trusted CA. The prices vary significantly, but it is possible to implement great security spending little to no money." |
| 438 |
msgstr "" |
| 439 |
|
| 440 |
msgid "Creating gratis trusted certificates" |
| 441 |
msgstr "" |
| 442 |
|
| 443 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 444 |
#, fuzzy |
| 445 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 446 |
msgid "<primary>certificate</primary><secondary>trusted certificate</secondary>" |
| 447 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 448 |
|
| 449 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 450 |
#, fuzzy |
| 451 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 452 |
msgid "<primary>certificate</primary><secondary>snakeoil certificate</secondary>" |
| 453 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 454 |
|
| 455 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 456 |
#, fuzzy |
| 457 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 458 |
msgid "<primary>certificate</primary><secondary>letsencrypt</secondary><seealso><emphasis role=\"pkg\">certbot</emphasis></seealso>" |
| 459 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 460 |
|
| 461 |
msgid "Many programs create and use snakeoil certificates by default (see sidebar <xref linkend=\"sidebar.snakeoil-certs\" />). Fortunately the <emphasis role=\"pkg\">certbot</emphasis> package brings everything we need to create our own trusted certificates, provided by the \"Lets Encrypt\" initiative (see sidebar <xref linkend=\"sidebar.letsencrypt\" />), which can also be used for mail transport agents (Postfix), mail delivery agents (Dovecot, Cyrus, etc.), and other network services." |
| 462 |
msgstr "" |
| 463 |
|
| 464 |
msgid "The Falcot administrators just want to create a certificate for their website, which runs on Apache. There is a convenient Apache plugin for <emphasis role=\"pkg\">certbot</emphasis> that automatically edits the Apache configuration to serve the obtained certificate, so they make use of it:" |
| 465 |
msgstr "" |
| 466 |
|
| 467 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 468 |
#, fuzzy |
| 469 |
#| msgid "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>" |
| 470 |
msgid "<primary><emphasis role=\"pkg\">certbot</emphasis></primary>" |
| 471 |
msgstr "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>" |
| 472 |
|
| 473 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 474 |
#, fuzzy |
| 475 |
#| msgid "<primary><emphasis role=\"pkg\">iputils-tracepath</emphasis></primary>" |
| 476 |
msgid "<primary><emphasis role=\"pkg\">python3-certbot-apache</emphasis></primary>" |
| 477 |
msgstr "<primary><emphasis role=\"pkg\">iputils-tracepath</emphasis></primary>" |
| 478 |
|
| 479 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 480 |
#, fuzzy |
| 481 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 482 |
msgid "<primary>Apache</primary><secondary><emphasis role=\"pkg\">certbot</emphasis></secondary>" |
| 483 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 484 |
|
| 485 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 486 |
#, fuzzy |
| 487 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 488 |
msgid "<primary>Apache</primary><secondary><emphasis role=\"pkg\">python3-certbot-apache</emphasis></secondary>" |
| 489 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 490 |
|
| 491 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 492 |
#, fuzzy |
| 493 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 494 |
msgid "<primary>Apache</primary><secondary>trusted certificates</secondary>" |
| 495 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 496 |
|
| 497 |
msgid "" |
| 498 |
"\n" |
| 499 |
"<computeroutput># </computeroutput><userinput>apt install python3-certbot-apache\n" |
| 500 |
"</userinput><computeroutput>[...]\n" |
| 501 |
"# </computeroutput><userinput>certbot --apache\n" |
| 502 |
"</userinput><computeroutput>aving debug log to /var/log/letsencrypt/letsencrypt.log\n" |
| 503 |
"Plugins selected: Authenticator apache, Installer apache\n" |
| 504 |
"Enter email address (used for urgent renewal and security notices)\n" |
| 505 |
" (Enter 'c' to cancel): </computeroutput><userinput>[email protected]\n" |
| 506 |
"</userinput><computeroutput>\n" |
| 507 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 508 |
"Please read the Terms of Service at\n" |
| 509 |
"https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must\n" |
| 510 |
"agree in order to register with the ACME server. Do you agree?\n" |
| 511 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 512 |
"(Y)es/(N)o: </computeroutput><userinput>Y\n" |
| 513 |
"</userinput><computeroutput>\n" |
| 514 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 515 |
"Would you be willing, once your first certificate is successfully issued, to\n" |
| 516 |
"share your email address with the Electronic Frontier Foundation, a founding\n" |
| 517 |
"partner of the Let's Encrypt project and the non-profit organization that\n" |
| 518 |
"develops Certbot? We'd like to send you email about our work encrypting the web,\n" |
| 519 |
"EFF news, campaigns, and ways to support digital freedom.\n" |
| 520 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 521 |
"(Y)es/(N)o: </computeroutput><userinput> N\n" |
| 522 |
"</userinput><computeroutput>\n" |
| 523 |
"Account registered.\n" |
| 524 |
"\n" |
| 525 |
"No names were found in your configuration files. Please enter in your domain\n" |
| 526 |
"name(s) (comma and/or space separated) (Enter 'c' to cancel): </computeroutput><userinput>falcot.com\n" |
| 527 |
"</userinput><computeroutput>\n" |
| 528 |
"Requesting a certificate for falcot.com\n" |
| 529 |
"Performing the following challenges:\n" |
| 530 |
"http-01 challenge for falcot.com\n" |
| 531 |
"Enabled Apache rewrite module\n" |
| 532 |
"Waiting for verification...\n" |
| 533 |
"Cleaning up challenges\n" |
| 534 |
"Created an SSL vhost at /etc/apache2/sites-available/000-default-le-ssl.conf\n" |
| 535 |
"Enabled Apache socache_shmcb module\n" |
| 536 |
"Enabled Apache ssl module\n" |
| 537 |
"Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-le-ssl.conf\n" |
| 538 |
"Enabling available site: /etc/apache2/sites-available/000-default-le-ssl.conf\n" |
| 539 |
"\n" |
| 540 |
"Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.\n" |
| 541 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 542 |
"1: No redirect - Make no further changes to the webserver configuration.\n" |
| 543 |
"2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for\n" |
| 544 |
"new sites, or if you're confident your site works on HTTPS. You can undo this\n" |
| 545 |
"change by editing your web server's configuration.\n" |
| 546 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 547 |
"Select the appropriate number [1-2] then [enter] (press 'c' to cancel):</computeroutput> <userinput>2\n" |
| 548 |
"</userinput><computeroutput>\n" |
| 549 |
"Enabled Apache rewrite module\n" |
| 550 |
"Redirecting vhost in /etc/apache2/sites-enabled/000-default.conf to ssl vhost in /etc/apache2/sites-available/000-default-le-ssl.conf\n" |
| 551 |
"\n" |
| 552 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 553 |
"Congratulations! You have successfully enabled https://falcot.com\n" |
| 554 |
"\n" |
| 555 |
"You should test your configuration at:\n" |
| 556 |
"https://www.ssllabs.com/ssltest/analyze.html?d=falcot.com\n" |
| 557 |
"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" |
| 558 |
"\n" |
| 559 |
"IMPORTANT NOTES:\n" |
| 560 |
" - Congratulations! Your certificate and chain have been saved at:\n" |
| 561 |
" /etc/letsencrypt/live/falcot.com/fullchain.pem\n" |
| 562 |
" Your key file has been saved at:\n" |
| 563 |
" /etc/letsencrypt/live/falcot.com/privkey.pem\n" |
| 564 |
" Your cert will expire on 2022-06-04. To obtain a new or tweaked\n" |
| 565 |
" version of this certificate in the future, simply run certbot again\n" |
| 566 |
" with the \"certonly\" option. To non-interactively renew *all* of\n" |
| 567 |
" your certificates, run \"certbot renew\"\n" |
| 568 |
" - Your account credentials have been saved in your Certbot\n" |
| 569 |
" configuration directory at /etc/letsencrypt. You should make a\n" |
| 570 |
" secure backup of this folder now. This configuration directory will\n" |
| 571 |
" also contain certificates and private keys obtained by Certbot so\n" |
| 572 |
" making regular backups of this folder is ideal.\n" |
| 573 |
" - If you like Certbot, please consider supporting our work by:\n" |
| 574 |
"\n" |
| 575 |
" Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate\n" |
| 576 |
" Donating to EFF: https://eff.org/donate-le\n" |
| 577 |
"</computeroutput>" |
| 578 |
msgstr "" |
| 579 |
|
| 580 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 581 |
#, fuzzy |
| 582 |
#| msgid "<emphasis>CULTURE</emphasis> Private address range" |
| 583 |
msgid "<emphasis>CULTURE</emphasis> The Let's Encrypt Initiative" |
| 584 |
msgstr "<emphasis>CULTURE</emphasis> プライベートアドレス範囲" |
| 585 |
|
| 586 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 587 |
#, fuzzy |
| 588 |
#| msgid "<primary>IPsec</primary>" |
| 589 |
msgid "<primary>Let's Encrypt</primary>" |
| 590 |
msgstr "<primary>IPsec</primary>" |
| 591 |
|
| 592 |
msgid "The <ulink url=\"https://letsencrypt.org/\">Let's Encrypt</ulink> initiative is a joint effort to create a free, automated, and open certificate authority (CA), run for the public's benefit. It is supported by the <acronym>EFF</acronym> and the Linux Foundation. The initiative provides an automated tool for acquiring and renewing certificates. This reduces the amount of manual effort involved, especially if multiple sites and domains must be managed. The certificates can also be used for SIP, XMPP, WebSockets and TURN servers. Usage of the service requires control over the DNS information of the domain in question (domain validation). <ulink type=\"block\" url=\"https://letsencrypt.org/how-it-works/\" />" |
| 593 |
msgstr "" |
| 594 |
|
| 595 |
msgid "If you would rather keep the server running during the certificate creation, you can use the webroot plugin to get the certificate with the arguments <command>certonly</command> and <command>--webroot</command>. You would have to specify a <command>--webroot-path</command> (abbreviated <command>-w</command>), which should contain the files served. The command looks as follows:" |
| 596 |
msgstr "" |
| 597 |
|
| 598 |
msgid "<computeroutput># </computeroutput><userinput>certbot certonly --webroot -w <replaceable>/var/www/html</replaceable> -d www.<replaceable>DOMAIN</replaceable>.com -d <replaceable>DOMAIN</replaceable>.com</userinput>" |
| 599 |
msgstr "" |
| 600 |
|
| 601 |
msgid "You need to restart all services using the certificates that you have created." |
| 602 |
msgstr "" |
| 603 |
|
| 604 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 605 |
#, fuzzy |
| 606 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 607 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.d/certbot</filename></secondary>" |
| 608 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 609 |
|
| 610 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 611 |
#, fuzzy |
| 612 |
#| msgid "<primary><command>route</command></primary>" |
| 613 |
msgid "<primary><command>certbot</command></primary>" |
| 614 |
msgstr "<primary><command>route</command></primary>" |
| 615 |
|
| 616 |
msgid "The certificates created are so called short-life certificates, which are valid for 90 days and must therefor be renewed every once in three months using the <command>certbot renew</command> command. However, we shouldn't renew every certificate manually, but automatically. A basic cron job is included by <emphasis role=\"pkg\">certbot</emphasis> in <filename>/etc/cron.d/certbot</filename>. To ensure that certificates can be automatically renewed, you can execute <command>certbot renew --dry-run</command>." |
| 617 |
msgstr "" |
| 618 |
|
| 619 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 620 |
msgid "Public Key Infrastructure: <emphasis>easy-rsa</emphasis>" |
| 621 |
msgstr "公開鍵基盤、<emphasis>easy-rsa</emphasis>" |
| 622 |
|
| 623 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 624 |
#, fuzzy |
| 625 |
#| msgid "<primary>PKI (Public Key Infrastructure)</primary>" |
| 626 |
msgid "<primary>PKI</primary><seealso>Public Key Infrastructure</seealso>" |
| 627 |
msgstr "<primary sortas=\"PKI (コウカイカギキバン)\">PKI (公開鍵基盤)</primary>" |
| 628 |
|
| 629 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 630 |
msgid "<primary>Public Key Infrastructure</primary>" |
| 631 |
msgstr "<primary sortas=\"コウカイカギキバン\">公開鍵基盤</primary>" |
| 632 |
|
| 633 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 634 |
#, fuzzy |
| 635 |
#| msgid "<primary>NAT</primary>" |
| 636 |
msgid "<primary>X.509</primary>" |
| 637 |
msgstr "<primary>NAT</primary>" |
| 638 |
|
| 639 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 640 |
msgid "<primary><emphasis>easy-rsa</emphasis></primary>" |
| 641 |
msgstr "<primary><emphasis>easy-rsa</emphasis></primary>" |
| 642 |
|
| 643 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 644 |
msgid "<primary>RSA (algorithm)</primary>" |
| 645 |
msgstr "<primary>RSA (アルゴリズム)</primary>" |
| 646 |
|
| 647 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 648 |
#, fuzzy |
| 649 |
#| msgid "<primary>port</primary><secondary>TCP</secondary>" |
| 650 |
msgid "<primary>algorithm</primary><secondary>RSA</secondary>" |
| 651 |
msgstr "<primary>ポート</primary><secondary>TCP</secondary>" |
| 652 |
|
| 653 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 654 |
msgid "<primary>key pair</primary>" |
| 655 |
msgstr "<primary sortas=\"カギペア\">鍵ペア</primary>" |
| 656 |
|
| 657 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 658 |
# Tag: PTAL; |
| 659 |
#, fuzzy |
| 660 |
#| msgid "The RSA algorithm is widely used in public-key cryptography. It involves a “key pair”, comprised of a private and a public key. The two keys are closely linked to each other, and their mathematical properties are such that a message encrypted with the public key can only be decrypted by someone knowing the private key, which ensures confidentiality. In the opposite direction, a message encrypted with the private key can be decrypted by anyone knowing the public key, which allows authenticating the origin of a message since only someone with access to the private key could generate it. When associated with a digital hash function (MD5, SHA1, or a more recent variant), this leads to a signature mechanism that can be applied to any message." |
| 661 |
msgid "It is also possible to create our own CA, for that we will use the RSA algorithm, widely used in public-key cryptography. It involves a “key pair”, comprised of a private and a public key. The two keys are closely linked to each other, and their mathematical properties are such that a message encrypted with the public key can only be decrypted by someone knowing the private key, which ensures confidentiality. In the opposite direction, a message encrypted with the private key can be decrypted by anyone knowing the public key, which allows authenticating the origin of a message since only someone with access to the private key could generate it. When associated with a digital hash function (MD5, SHA1, or a more recent variant), this leads to a signature mechanism that can be applied to any message." |
| 662 |
msgstr "公開鍵暗号では RSA アルゴリズムが広く使われています。公開鍵暗号は秘密鍵と公開鍵からなる「鍵ペア」を使います。2 種類の鍵は互いに密接な関係を持っており、公開鍵で暗号化されたメッセージは秘密鍵を知っている人だけが復号化できるという数学的特徴によって機密性が保証されます。逆に、秘密鍵を使って暗号化されたメッセージは公開鍵を持っている人なら誰でも復号化できます。この特徴を使うことで、メッセージの出自が本物であることを確認することが可能です。なぜなら、秘密鍵を持つものだけがその暗号化メッセージを生成できるからです。デジタルハッシュ関数 (MD5、SHA1、最近の亜種など) を組み合わせることで、これはいかなるメッセージにも適用できる署名メカニズムになります。" |
| 663 |
|
| 664 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 665 |
#, fuzzy |
| 666 |
#| msgid "OpenVPN follows this rule. Since public CAs only emit certificates in exchange for a (hefty) fee, it is also possible to create a private certification authority within the company. The <emphasis role=\"pkg\">easy-rsa</emphasis> package provides tools to serve as an X.509 certification infrastructure, implemented as a set of scripts using the <command>openssl</command> command." |
| 667 |
msgid "Since public CAs only emit certificates in exchange for a (hefty) fee, it is also possible to create a private certification authority within the company. The <emphasis role=\"pkg\">easy-rsa</emphasis> package provides tools to serve as an X.509 certification infrastructure, implemented as a set of scripts using the <command>openssl</command> command." |
| 668 |
msgstr "OpenVPN はこの識別情報確認ルールに従います。パブリック認証局は (高額な) 料金と引き換えに証明書を発行しているに過ぎません。OpenVPN を使えば会社内のプライベート認証局を作成することが可能です。<emphasis role=\"pkg\">easy-rsa</emphasis> パッケージは X.509 証明書基盤としての機能を果たすツールを提供し、このツールは <command>openssl</command> コマンドを使うスクリプト群として実装されています。" |
| 669 |
|
| 670 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 671 |
#, fuzzy |
| 672 |
#| msgid "<emphasis>CULTURE</emphasis> SSL and TLS" |
| 673 |
msgid "<emphasis>ALTERNATIVE</emphasis> GnuTLS" |
| 674 |
msgstr "<emphasis>CULTURE</emphasis> SSL と TLS" |
| 675 |
|
| 676 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 677 |
#, fuzzy |
| 678 |
#| msgid "<primary>TLS</primary>" |
| 679 |
msgid "<primary>DTLS</primary>" |
| 680 |
msgstr "<primary>TLS</primary>" |
| 681 |
|
| 682 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 683 |
#, fuzzy |
| 684 |
#| msgid "<primary>TLS</primary>" |
| 685 |
msgid "<primary>GnuTLS</primary>" |
| 686 |
msgstr "<primary>TLS</primary>" |
| 687 |
|
| 688 |
msgid "GnuTLS can also be used to generate a CA, and deal with other technologies around the TLS, DTLS and SSL protocols." |
| 689 |
msgstr "" |
| 690 |
|
| 691 |
msgid "The package <emphasis role=\"pkg\">gnutls-bin</emphasis> contains the command-line utilities. It is also useful to install the <emphasis role=\"pkg\">gnutls-doc</emphasis> package, which includes extensive documentation." |
| 692 |
msgstr "" |
| 693 |
|
| 694 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 695 |
msgid "The Falcot Corp administrators use this tool to create the required certificates, both for the server and the clients. This allows the configuration of all clients to be similar since they will only have to be set up so as to trust certificates coming from Falcot's local CA. This CA is the first certificate to create; to this end, the administrators set up a directory with the files required for the CA in an appropriate location, preferably on a machine not connected to the network in order to mitigate the risk of the CA's private key being stolen." |
| 696 |
msgstr "Falcot Corp の管理者は <emphasis>easy-rsa</emphasis> ツールを使い、サーバおよびクライアントに必要な証明書を作ります。<emphasis>easy-rsa</emphasis> ツールを使うことで、すべてのクライアントの設定を同様にすることが可能です。クライアントは Falcot のプライベート認証局から発行された証明書を信頼するようにセットアップしなければいけません。最初に Falcot のプライベート認証局用の証明書を発行します。この目的を達成するために、管理者は認証局に必要なファイルを含むディレクトリを適切な場所にセットアップします。セットアップする場所は、認証局の秘密鍵が盗まれる危険性を和らげるために、ネットワークに接続されていないマシンが好ましいです。" |
| 697 |
|
| 698 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 699 |
msgid "" |
| 700 |
"\n" |
| 701 |
"<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n" |
| 702 |
"</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>" |
| 703 |
msgstr "" |
| 704 |
"\n" |
| 705 |
"<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n" |
| 706 |
"</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>" |
| 707 |
|
| 708 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 709 |
#, fuzzy |
| 710 |
#| msgid "They then store the required parameters into the <filename>vars</filename> file, especially those named with a <literal>KEY_</literal> prefix; these variables are then integrated into the environment:" |
| 711 |
msgid "They then store the required parameters into the <filename>vars</filename> file, which can be uncommented and edited:" |
| 712 |
msgstr "<emphasis>easy-rsa</emphasis> ツールは必要なパラメータを <filename>vars</filename> ファイルに保存します。パラメータには特に <literal>KEY_</literal> 接頭辞が付けられています。これらの変数は環境変数に組み込まれます。" |
| 713 |
|
| 714 |
msgid "" |
| 715 |
"\n" |
| 716 |
"<computeroutput>$ </computeroutput><userinput>grep EASYRSA vars\n" |
| 717 |
"</userinput><computeroutput><![CDATA[if [ -z \"$EASYRSA_CALLER\" ]; then\n" |
| 718 |
"# easyrsa. More specific variables for specific files (e.g., EASYRSA_SSL_CONF)\n" |
| 719 |
"#set_var EASYRSA\t\"${0%/*}\"\n" |
| 720 |
"#set_var EASYRSA_OPENSSL\t\"openssl\"\n" |
| 721 |
"#set_var EASYRSA_OPENSSL\t\"C:/Program Files/OpenSSL-Win32/bin/openssl.exe\"\n" |
| 722 |
"#set_var EASYRSA_PKI\t\t\"$PWD/pki\"\n" |
| 723 |
"#set_var EASYRSA_TEMP_DIR\t\"$EASYRSA_PKI\"\n" |
| 724 |
"#set_var EASYRSA_DN\t\"cn_only\"\n" |
| 725 |
"set_var EASYRSA_REQ_COUNTRY\t\"FR\"\n" |
| 726 |
"set_var EASYRSA_REQ_PROVINCE\t\"Loire\"\n" |
| 727 |
"set_var EASYRSA_REQ_CITY\t\"Saint-Étienne\"\n" |
| 728 |
"set_var EASYRSA_REQ_ORG\t\"Falcot Corp\"\n" |
| 729 |
"set_var EASYRSA_REQ_EMAIL\t\"[email protected]\"\n" |
| 730 |
"set_var EASYRSA_REQ_OU\t\t\"Certificate authority\"\n" |
| 731 |
"#set_var EASYRSA_KEY_SIZE\t2048\n" |
| 732 |
"#set_var EASYRSA_ALGO\t\trsa\n" |
| 733 |
"#set_var EASYRSA_CURVE\t\tsecp384r1\n" |
| 734 |
"#set_var EASYRSA_CA_EXPIRE\t3650\n" |
| 735 |
"#set_var EASYRSA_CERT_EXPIRE\t825\n" |
| 736 |
"#set_var EASYRSA_CRL_DAYS\t180\n" |
| 737 |
"#set_var EASYRSA_CERT_RENEW\t30\n" |
| 738 |
"#set_var EASYRSA_RAND_SN\t\"yes\"\n" |
| 739 |
"#set_var EASYRSA_NS_SUPPORT\t\"no\"\n" |
| 740 |
"#set_var EASYRSA_NS_COMMENT\t\"Easy-RSA Generated Certificate\"\n" |
| 741 |
"#set_var EASYRSA_TEMP_FILE\t\"$EASYRSA_PKI/extensions.temp\"\n" |
| 742 |
"# when undefined here, default behaviour is to look in $EASYRSA_PKI first, then\n" |
| 743 |
"# fallback to $EASYRSA for the 'x509-types' dir. You may override this\n" |
| 744 |
"#set_var EASYRSA_EXT_DIR\t\"$EASYRSA/x509-types\"\n" |
| 745 |
"#set_var EASYRSA_KDC_REALM \"CHANGEME.EXAMPLE.COM\"\n" |
| 746 |
"# EASYRSA_PKI or EASYRSA dir (in that order.) NOTE that this file is Easy-RSA\n" |
| 747 |
"#set_var EASYRSA_SSL_CONF\t\"$EASYRSA/openssl-easyrsa.cnf\"\n" |
| 748 |
"#set_var EASYRSA_REQ_CN\t\t\"ChangeMe\"\n" |
| 749 |
"#set_var EASYRSA_DIGEST\t\t\"sha256\"\n" |
| 750 |
"#set_var EASYRSA_BATCH\t\t\"\"\n" |
| 751 |
"]]>$ </computeroutput><userinput>vim vars\n" |
| 752 |
"</userinput><computeroutput>$ </computeroutput>" |
| 753 |
msgstr "" |
| 754 |
|
| 755 |
msgid "Now we prepare the public key infrastructure directory with the following command:" |
| 756 |
msgstr "" |
| 757 |
|
| 758 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 759 |
#, fuzzy |
| 760 |
#| msgid "" |
| 761 |
#| "\n" |
| 762 |
#| "<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n" |
| 763 |
#| "</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>" |
| 764 |
msgid "" |
| 765 |
"\n" |
| 766 |
"<computeroutput>$ </computeroutput><userinput>./easyrsa init-pki\n" |
| 767 |
"</userinput><computeroutput>\n" |
| 768 |
"\n" |
| 769 |
"init-pki complete; you may now create a CA or requests.\n" |
| 770 |
"Your newly created PKI dir is: /home/debian/pki-falcot/pki\n" |
| 771 |
"\n" |
| 772 |
"</computeroutput>" |
| 773 |
msgstr "" |
| 774 |
"\n" |
| 775 |
"<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n" |
| 776 |
"</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>" |
| 777 |
|
| 778 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 779 |
#, fuzzy |
| 780 |
#| msgid "The next step is the creation of the CA's key pair itself (the two parts of the key pair will be stored under <filename>keys/ca.crt</filename> and <filename>keys/ca.key</filename> during this step):" |
| 781 |
msgid "The next step is the creation of the CA's key pair itself (the two parts of the key pair will be stored under <filename>pki/ca.crt</filename> and <filename>pki/private/ca.key</filename> during this step). We can add the option <literal>nopass</literal> to avoid entering a password each time the private key is used:" |
| 782 |
msgstr "次にプライベート認証局の鍵ペアを作成します (この最中に、鍵ペアの 2 つの部分が <filename>keys/ca.crt</filename> と <filename>keys/ca.key</filename> に保存されます)。" |
| 783 |
|
| 784 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 785 |
#, fuzzy |
| 786 |
#| msgid "" |
| 787 |
#| "\n" |
| 788 |
#| "<computeroutput>$ </computeroutput><userinput>./build-ca</userinput>\n" |
| 789 |
#| "<computeroutput>Generating a 2048 bit RSA private key\n" |
| 790 |
#| "...................................................................+++\n" |
| 791 |
#| "...+++\n" |
| 792 |
#| "writing new private key to 'ca.key'\n" |
| 793 |
#| "-----\n" |
| 794 |
#| "You are about to be asked to enter information that will be incorporated\n" |
| 795 |
#| "into your certificate request.\n" |
| 796 |
#| "What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 797 |
#| "There are quite a few fields but you can leave some blank\n" |
| 798 |
#| "For some fields there will be a default value,\n" |
| 799 |
#| "If you enter '.', the field will be left blank.\n" |
| 800 |
#| "-----\n" |
| 801 |
#| "Country Name (2 letter code) [FR]:\n" |
| 802 |
#| "State or Province Name (full name) [Loire]:\n" |
| 803 |
#| "Locality Name (eg, city) [Saint-Étienne]:\n" |
| 804 |
#| "Organization Name (eg, company) [Falcot Corp]:\n" |
| 805 |
#| "Organizational Unit Name (eg, section) [Certificate authority]:\n" |
| 806 |
#| "Common Name (eg, your name or your server's hostname) [Falcot Corp CA]:\n" |
| 807 |
#| "Name [Certificate authority for Falcot Corp]:\n" |
| 808 |
#| "Email Address [[email protected]]:\n" |
| 809 |
#| "</computeroutput>" |
| 810 |
msgid "" |
| 811 |
"\n" |
| 812 |
"<computeroutput>$ </computeroutput><userinput>./easyrsa build-ca nopass</userinput>\n" |
| 813 |
"<computeroutput>\n" |
| 814 |
"Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" |
| 815 |
"Generating RSA private key, 2048 bit long modulus (2 primes)\n" |
| 816 |
"..................+++++\n" |
| 817 |
"...............................+++++\n" |
| 818 |
"e is 65537 (0x010001)\n" |
| 819 |
"You are about to be asked to enter information that will be incorporated\n" |
| 820 |
"into your certificate request.\n" |
| 821 |
"What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 822 |
"There are quite a few fields but you can leave some blank\n" |
| 823 |
"For some fields there will be a default value,\n" |
| 824 |
"If you enter '.', the field will be left blank.\n" |
| 825 |
"-----\n" |
| 826 |
"Common Name (eg: your user, host, or server name) [Easy-RSA CA]:\n" |
| 827 |
"\n" |
| 828 |
"CA creation complete and you may now import and sign cert requests.\n" |
| 829 |
"Your new CA certificate file for publishing is at:\n" |
| 830 |
"/home/debian/pki-falcot/pki/ca.crt\n" |
| 831 |
"\n" |
| 832 |
"</computeroutput>" |
| 833 |
msgstr "" |
| 834 |
"\n" |
| 835 |
"<computeroutput>$ </computeroutput><userinput>./build-ca</userinput>\n" |
| 836 |
"<computeroutput>Generating a 2048 bit RSA private key\n" |
| 837 |
"...................................................................+++\n" |
| 838 |
"...+++\n" |
| 839 |
"writing new private key to 'ca.key'\n" |
| 840 |
"-----\n" |
| 841 |
"You are about to be asked to enter information that will be incorporated\n" |
| 842 |
"into your certificate request.\n" |
| 843 |
"What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 844 |
"There are quite a few fields but you can leave some blank\n" |
| 845 |
"For some fields there will be a default value,\n" |
| 846 |
"If you enter '.', the field will be left blank.\n" |
| 847 |
"-----\n" |
| 848 |
"Country Name (2 letter code) [FR]:\n" |
| 849 |
"State or Province Name (full name) [Loire]:\n" |
| 850 |
"Locality Name (eg, city) [Saint-Étienne]:\n" |
| 851 |
"Organization Name (eg, company) [Falcot Corp]:\n" |
| 852 |
"Organizational Unit Name (eg, section) [Certificate authority]:\n" |
| 853 |
"Common Name (eg, your name or your server's hostname) [Falcot Corp CA]:\n" |
| 854 |
"Name [Certificate authority for Falcot Corp]:\n" |
| 855 |
"Email Address [[email protected]]:\n" |
| 856 |
"</computeroutput>" |
| 857 |
|
| 858 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 859 |
#, fuzzy |
| 860 |
#| msgid "<primary><filename>named.conf</filename></primary>" |
| 861 |
msgid "<primary><filename>dh.pem</filename></primary>" |
| 862 |
msgstr "<primary><filename>named.conf</filename></primary>" |
| 863 |
|
| 864 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 865 |
#, fuzzy |
| 866 |
#| msgid "The certificate for the VPN server can now be created, as well as the Diffie-Hellman parameters required for the server side of an SSL/TLS connection. The VPN server is identified by its DNS name <literal>vpn.falcot.com</literal>; this name is re-used for the generated key files (<filename>keys/vpn.falcot.com.crt</filename> for the public certificate, <filename>keys/vpn.falcot.com.key</filename> for the private key):" |
| 867 |
msgid "The certificate can now be created, as well as the Diffie-Hellman parameters required for the server side of an SSL/TLS connection. They want to use it for a VPN server (see section <xref linkend=\"sect.virtual-private-network\" />) that is identified by the DNS name <literal>vpn.falcot.com</literal>; this name is re-used for the generated key files (<filename>keys/vpn.falcot.com.crt</filename> for the public certificate, <filename>keys/vpn.falcot.com.key</filename> for the private key):" |
| 868 |
msgstr "これで VPN サーバの証明書および SSL/TLS 接続のサーバ側に必要な Diffie-Hellman パラメータを作ることが可能になりました。VPN サーバは DNS 名 <literal>vpn.falcot.com</literal> で識別されます。ここで指定した DNS 名は作成される鍵ファイルの名前としても使われます (<filename>keys/vpn.falcot.com.crt</filename> は公開鍵証明書、<filename>keys/vpn.falcot.com.key</filename> は秘密鍵です)。" |
| 869 |
|
| 870 |
msgid "" |
| 871 |
"\n" |
| 872 |
"<computeroutput>$ </computeroutput><userinput>./easyrsa gen-req vpn.falcot.com nopass\n" |
| 873 |
"</userinput><computeroutput>\n" |
| 874 |
"Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" |
| 875 |
"Generating a RSA private key\n" |
| 876 |
"......................................+++++\n" |
| 877 |
"..........................................................................+++++\n" |
| 878 |
"writing new private key to '/home/debian/pki-falcot/pki/easy-rsa-5515.0PwyXl/tmp.g1c6u6'\n" |
| 879 |
"-----\n" |
| 880 |
"You are about to be asked to enter information that will be incorporated\n" |
| 881 |
"into your certificate request.\n" |
| 882 |
"What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 883 |
"There are quite a few fields but you can leave some blank\n" |
| 884 |
"For some fields there will be a default value,\n" |
| 885 |
"If you enter '.', the field will be left blank.\n" |
| 886 |
"-----\n" |
| 887 |
"Common Name (eg: your user, host, or server name) [vpn.falcot.com]:\n" |
| 888 |
"\n" |
| 889 |
"Keypair and certificate request completed. Your files are:\n" |
| 890 |
"req: /home/debian/pki-falcot/pki/reqs/vpn.falcot.com.req\n" |
| 891 |
"key: /home/debian/pki-falcot/pki/private/vpn.falcot.com.key\n" |
| 892 |
"\n" |
| 893 |
"\n" |
| 894 |
"$ </computeroutput><userinput>./easyrsa sign-req server vpn.falcot.com\n" |
| 895 |
"</userinput><computeroutput>\n" |
| 896 |
"Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" |
| 897 |
"\n" |
| 898 |
"\n" |
| 899 |
"You are about to sign the following certificate.\n" |
| 900 |
"Please check over the details shown below for accuracy. Note that this request\n" |
| 901 |
"has not been cryptographically verified. Please be sure it came from a trusted\n" |
| 902 |
"source or that you have verified the request checksum with the sender.\n" |
| 903 |
"\n" |
| 904 |
"Request subject, to be signed as a server certificate for 825 days:\n" |
| 905 |
"\n" |
| 906 |
"subject=\n" |
| 907 |
" commonName = vpn.falcot.com\n" |
| 908 |
"\n" |
| 909 |
"\n" |
| 910 |
"Type the word 'yes' to continue, or any other input to abort.\n" |
| 911 |
" Confirm request details: <userinput>yes\n" |
| 912 |
"</userinput>Using configuration from /home/debian/pki-falcot/pki/easy-rsa-5603.87iCIa/tmp.u8r8Fj\n" |
| 913 |
"Check that the request matches the signature\n" |
| 914 |
"Signature ok\n" |
| 915 |
"The Subject's Distinguished Name is as follows\n" |
| 916 |
"commonName :ASN.1 12:'vpn.falcot.com'\n" |
| 917 |
"Certificate is to be certified until May 27 15:26:29 2024 GMT (825 days)\n" |
| 918 |
"\n" |
| 919 |
"Write out database with 1 new entries\n" |
| 920 |
"Data Base Updated\n" |
| 921 |
"\n" |
| 922 |
"Certificate created at: /home/debian/pki-falcot/pki/issued/vpn.falcot.com.crt\n" |
| 923 |
"\n" |
| 924 |
"\n" |
| 925 |
"$ </computeroutput><userinput>./easyrsa gen-dh\n" |
| 926 |
"</userinput><computeroutput>\n" |
| 927 |
"Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" |
| 928 |
"Generating DH parameters, 2048 bit long safe prime, generator 2\n" |
| 929 |
"This is going to take a long time\n" |
| 930 |
"[…]\n" |
| 931 |
"\n" |
| 932 |
"DH parameters of size 2048 created at /home/debian/pki-falcot/pki/dh.pem\n" |
| 933 |
"\n" |
| 934 |
"</computeroutput>" |
| 935 |
msgstr "" |
| 936 |
|
| 937 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 938 |
msgid "The following step creates certificates for the VPN clients; one certificate is required for each computer or person allowed to use the VPN:" |
| 939 |
msgstr "以下では、VPN クライアント用の証明書を作成します。VPN を利用するコンピュータ 1 台ごとおよび人間 1 人ずつに 1 つの証明書が必要です。" |
| 940 |
|
| 941 |
msgid "" |
| 942 |
"\n" |
| 943 |
"<computeroutput>$ </computeroutput><userinput>./easyrsa build-client-full JoeSmith nopass\n" |
| 944 |
"</userinput><computeroutput>\n" |
| 945 |
"Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" |
| 946 |
"Generating a RSA private key\n" |
| 947 |
"...................................+++++\n" |
| 948 |
".........................................................................................+++++\n" |
| 949 |
"writing new private key to '/home/debian/pki-falcot/pki/easy-rsa-5694.DOYwSn/tmp.RKlbOE'\n" |
| 950 |
"-----\n" |
| 951 |
"Using configuration from /home/debian/pki-falcot/pki/easy-rsa-5694.DOYwSn/tmp.d5QHAC\n" |
| 952 |
"Check that the request matches the signature\n" |
| 953 |
"Signature ok\n" |
| 954 |
"The Subject's Distinguished Name is as follows\n" |
| 955 |
"commonName :ASN.1 12:'JoeSmith'\n" |
| 956 |
"Certificate is to be certified until May 27 15:29:25 2024 GMT (825 days)\n" |
| 957 |
"\n" |
| 958 |
"Write out database with 1 new entries\n" |
| 959 |
"Data Base Updated\n" |
| 960 |
"\n" |
| 961 |
"</computeroutput>" |
| 962 |
msgstr "" |
| 963 |
|
| 964 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 965 |
msgid "Virtual Private Network" |
| 966 |
msgstr "仮想プライベートネットワーク" |
| 967 |
|
| 968 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 969 |
msgid "<primary>network</primary><secondary>virtual private</secondary>" |
| 970 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"カソウプライベート\">仮想プライベート</secondary>" |
| 971 |
|
| 972 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 973 |
msgid "<primary>VPN</primary>" |
| 974 |
msgstr "<primary>VPN</primary>" |
| 975 |
|
| 976 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 977 |
#, fuzzy |
| 978 |
#| msgid "<primary>virtual private network</primary>" |
| 979 |
msgid "<primary>virtual private network</primary><seealso>VPN</seealso>" |
| 980 |
msgstr "<primary sortas=\"カソウプライベートネットワーク\">仮想プライベートネットワーク</primary>" |
| 981 |
|
| 982 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 983 |
#, fuzzy |
| 984 |
#| msgid "<primary>packet</primary><secondary>IP</secondary>" |
| 985 |
msgid "<primary>IP</primary><secondary>IPsec</secondary>" |
| 986 |
msgstr "<primary>パケット</primary><secondary>IP パケット</secondary>" |
| 987 |
|
| 988 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 989 |
msgid "A <emphasis>Virtual Private Network</emphasis> (VPN for short) is a way to link two different local networks through the Internet by way of a tunnel; the tunnel is usually encrypted for confidentiality. VPNs are often used to integrate a remote machine within a company's local network." |
| 990 |
msgstr "<emphasis>仮想プライベートネットワーク</emphasis> (略して VPN) は 2 つの異なるローカルネットワークをインターネットに作ったトンネルを経由してつなげる方法です。さらに、トンネルは通常機密を守るために暗号化されます。VPN はリモートマシンを会社のローカルネットワークの中に参加させるために使われることが多いです。" |
| 991 |
|
| 992 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 993 |
#, fuzzy |
| 994 |
#| msgid "Several tools provide this. OpenVPN is an efficient solution, easy to deploy and maintain, based on SSL/TLS. Another possibility is using IPsec to encrypt IP traffic between two machines; this encryption is transparent, which means that applications running on these hosts need not be modified to take the VPN into account. SSH can also be used to provide a VPN, in addition to its more conventional features. Finally, a VPN can be established using Microsoft's PPTP protocol. Other solutions exist, but are beyond the focus of this book." |
| 995 |
msgid "Several tools provide this functionality. OpenVPN is an efficient solution, easy to deploy and maintain, based on SSL/TLS. Another possibility is using IPsec to encrypt IP traffic between two machines; this encryption is transparent, which means that applications running on these hosts need not be modified to take the VPN into account. SSH can also be used to provide a VPN, in addition to its more conventional features. Finally, a VPN can be established using Microsoft's PPTP protocol. Other solutions exist, but are beyond the focus of this book." |
| 996 |
msgstr "VPN 機能を提供するツールにはさまざまなものがあります。OpenVPN は効果的な解決策で、設置とメンテナンスが簡単で、SSL/TLS に基づいています。別の可能性は IPsec を使って 2 台のマシン間の IP トラフィックを暗号化することです。IPsec の暗号化は透過的で、ホスト上で実行されているアプリケーションは VPN の存在を気にする必要がありません。SSH は伝統的な機能に加えて、VPN を提供するために使われる場合もあります。最後に、Microsoft の PPTP プロトコルを使って VPN を作ることも可能です。他にも解決策は存在しますが、本書では解説しません。" |
| 997 |
|
| 998 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 999 |
msgid "OpenVPN" |
| 1000 |
msgstr "OpenVPN" |
| 1001 |
|
| 1002 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1003 |
msgid "<primary>OpenVPN</primary>" |
| 1004 |
msgstr "<primary>OpenVPN</primary>" |
| 1005 |
|
| 1006 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1007 |
#, fuzzy |
| 1008 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 1009 |
msgid "<primary>VPN</primary><secondary>OpenVPN</secondary>" |
| 1010 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 1011 |
|
| 1012 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1013 |
#, fuzzy |
| 1014 |
#| msgid "<primary>network</primary><secondary>virtual private</secondary>" |
| 1015 |
msgid "<primary>network</primary><secondary><literal>tun</literal> interface</secondary>" |
| 1016 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"カソウプライベート\">仮想プライベート</secondary>" |
| 1017 |
|
| 1018 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1019 |
#, fuzzy |
| 1020 |
#| msgid "<primary>network</primary><secondary>virtual private</secondary>" |
| 1021 |
msgid "<primary>network</primary><secondary><literal>tap</literal> interface</secondary>" |
| 1022 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"カソウプライベート\">仮想プライベート</secondary>" |
| 1023 |
|
| 1024 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1025 |
msgid "OpenVPN is a piece of software dedicated to creating virtual private networks. Its setup involves creating virtual network interfaces on the VPN server and on the client(s); both <literal>tun</literal> (for IP-level tunnels) and <literal>tap</literal> (for Ethernet-level tunnels) interfaces are supported. In practice, <literal>tun</literal> interfaces will most often be used except when the VPN clients are meant to be integrated into the server's local network by way of an Ethernet bridge." |
| 1026 |
msgstr "OpenVPN は仮想プライベートネットワーク作成専用ソフトウェアの一種です。OpenVPN をセットアップするには VPN サーバ上とクライアント上に仮想ネットワークインターフェースの作成が必要です。さらに、OpenVPN は <literal>tun</literal> (IP レベルトンネル用) と <literal>tap</literal> (イーサネットレベルトンネル用) インターフェースをサポートします。実際には、VPN クライアントをイーサネットブリッジ経由でサーバのローカルネットワークに参加させる場合を除いて、<literal>tun</literal> インターフェースが最もよく使われます。" |
| 1027 |
|
| 1028 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1029 |
msgid "OpenVPN relies on OpenSSL for all the SSL/TLS cryptography and associated features (confidentiality, authentication, integrity, non-repudiation). It can be configured either with a shared private key or using X.509 certificates based on a public key infrastructure. The latter configuration is strongly preferred since it allows greater flexibility when faced with a growing number of roaming users accessing the VPN." |
| 1030 |
msgstr "OpenVPN は SSL/TLS 暗号化と関連する機能 (機密性、認証、整合性、否認防止) を使うために OpenSSL に依存しています。OpenVPN は共有秘密鍵または公開鍵基盤に基づく X.509 証明書を使うように設定できます。公開鍵基盤に基づく X.509 証明書を使うよう設定することをお勧めします。なぜなら、公開鍵基盤に従えば VPN にアクセスするローミングユーザの数が増えた場合も大きな自由度を保つことが可能だからです。" |
| 1031 |
|
| 1032 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1033 |
msgid "Configuring the OpenVPN Server" |
| 1034 |
msgstr "OpenVPN サーバの設定" |
| 1035 |
|
| 1036 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1037 |
#, fuzzy |
| 1038 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 1039 |
msgid "<primary>OpenVPN</primary><secondary>server</secondary>" |
| 1040 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 1041 |
|
| 1042 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1043 |
#, fuzzy |
| 1044 |
#| msgid "Now all certificates have been created, they need to be copied where appropriate: the root certificate's public key (<filename>keys/ca.crt</filename>) will be stored on all machines (both server and clients) as <filename>/etc/ssl/certs/Falcot_CA.crt</filename>. The server's certificate is installed only on the server (<filename>keys/vpn.falcot.com.crt</filename> goes to <filename>/etc/ssl/vpn.falcot.com.crt</filename>, and <filename>keys/vpn.falcot.com.key</filename> goes to <filename>/etc/ssl/private/vpn.falcot.com.key</filename> with restricted permissions so that only the administrator can read it), with the corresponding Diffie-Hellman parameters (<filename>keys/dh2048.pem</filename>) installed to <filename>/etc/openvpn/dh2048.pem</filename>. Client certificates are installed on the corresponding VPN client in a similar fashion." |
| 1045 |
msgid "After all certificates have been created (follow the instructions from <xref linkend=\"sect.easy-rsa\" />), they need to be copied where appropriate: the root certificate's public key (<filename>pki/ca.crt</filename>) will be stored on all machines (both server and clients) as <filename>/etc/ssl/certs/Falcot_CA.crt</filename>. The server's certificate is installed only on the server (<filename>pki/issued/vpn.falcot.com.crt</filename> goes to <filename>/etc/ssl/certs/vpn.falcot.com.crt</filename>, and <filename>pki/private/vpn.falcot.com.key</filename> goes to <filename>/etc/ssl/private/vpn.falcot.com.key</filename> with restricted permissions so that only the administrator can read it), with the corresponding Diffie-Hellman parameters (<filename>pki/dh.pem</filename>) installed to <filename>/etc/openvpn/dh.pem</filename>. Client certificates are installed on the corresponding VPN client in a similar fashion." |
| 1046 |
msgstr "すべての証明書を作ったら、証明書を適切な場所にコピーする必要があります。すなわち、ルート証明書の公開鍵 (<filename>keys/ca.crt</filename>) はすべてのマシン (サーバもクライアントも) に <filename>/etc/ssl/certs/Falcot_CA.crt</filename> という名前で保存されます。サーバの証明書はサーバにだけインストールされます (<filename>keys/vpn.falcot.com.crt</filename> は <filename>/etc/ssl/vpn.falcot.com.crt</filename> へ、<filename>keys/vpn.falcot.com.key</filename> は管理者だけが読めるようなパーミッション制限を掛けるために <filename>/etc/ssl/private/vpn.falcot.com.key</filename> へインストールされます)。同時に、対応する Diffie-Hellman パラメータ (<filename>keys/dh2048.pem</filename>) は <filename>/etc/openvpn/dh2048.pem</filename> へインストールされます。クライアント証明書は対応する VPN クライアントに同様の方法でインストールされます。" |
| 1047 |
|
| 1048 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1049 |
#, fuzzy |
| 1050 |
#| msgid "<primary>firewall</primary><secondary>IPv6</secondary>" |
| 1051 |
msgid "<primary><filename>/etc</filename></primary><secondary>/etc/ssl/</secondary>" |
| 1052 |
msgstr "<primary>ファイアウォール</primary><secondary>IPv6</secondary>" |
| 1053 |
|
| 1054 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1055 |
#, fuzzy |
| 1056 |
#| msgid "<primary>firewall</primary><secondary>IPv6</secondary>" |
| 1057 |
msgid "<primary><filename>/etc</filename></primary><secondary>/etc/openvpn/dh.pem</secondary>" |
| 1058 |
msgstr "<primary>ファイアウォール</primary><secondary>IPv6</secondary>" |
| 1059 |
|
| 1060 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1061 |
#, fuzzy |
| 1062 |
#| msgid "<primary>traffic</primary><secondary>control</secondary>" |
| 1063 |
msgid "<primary><filename>/etc</filename></primary><secondary>/etc/openvpn/*.conf</secondary>" |
| 1064 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイギョ\">制御</secondary>" |
| 1065 |
|
| 1066 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1067 |
#, fuzzy |
| 1068 |
#| msgid "By default, the OpenVPN initialization script tries starting all virtual private networks defined in <filename>/etc/openvpn/*.conf</filename>. Setting up a VPN server is therefore a matter of storing a corresponding configuration file in this directory. A good starting point is <filename>/usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz</filename>, which leads to a rather standard server. Of course, some parameters need to be adapted: <literal>ca</literal>, <literal>cert</literal>, <literal>key</literal> and <literal>dh</literal> need to describe the selected locations (respectively, <literal>/etc/ssl/certs/Falcot_CA.crt</literal>, <literal>/etc/ssl/vpn.falcot.com.crt</literal>, <literal>/etc/ssl/private/vpn.falcot.com.key</literal> and <literal>/etc/openvpn/dh2048.pem</literal>). The <literal>server 10.8.0.0 255.255.255.0</literal> directive defines the subnet to be used by the VPN; the server uses the first IP address in that range (<literal>10.8.0.1</literal>) and the rest of the addresses are allocated to clients." |
| 1069 |
msgid "By default, the OpenVPN initialization script tries starting all virtual private networks defined in <filename>/etc/openvpn/*.conf</filename>. Setting up a VPN server is therefore a matter of storing a corresponding configuration file in this directory. A good starting point is <filename>/usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz</filename>, which leads to a rather standard server. Of course, some parameters need to be adapted: <literal>ca</literal>, <literal>cert</literal>, <literal>key</literal> and <literal>dh</literal> need to describe the selected locations (respectively, <literal>/etc/ssl/certs/Falcot_CA.crt</literal>, <literal>/etc/ssl/vpn.falcot.com.crt</literal>, <literal>/etc/ssl/private/vpn.falcot.com.key</literal> and <literal>/etc/openvpn/dh.pem</literal>). The <literal>server 10.8.0.0 255.255.255.0</literal> directive defines the subnet to be used by the VPN; the server uses the first IP address in that range (<literal>10.8.0.1</literal>) and the rest of the addresses are allocated to clients." |
| 1070 |
msgstr "デフォルトで、OpenVPN 初期化スクリプトは <filename>/etc/openvpn/*.conf</filename> で定義されたすべての仮想プライベートネットワークを開始します。このため、VPN サーバをセットアップする場合、このディレクトリ内に対応する設定ファイルを配置することになります。設定ファイルの良い足掛かりとして <filename>/usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz</filename> が用意されています。これはどちらかと言えば標準的なサーバを作るためのものです。もちろん、一部のパラメータを適切に設定しなければいけません。具体的に言えば、<literal>ca</literal>、<literal>cert</literal>、<literal>key</literal>、<literal>dh</literal> パラメータを対応するファイルが設置されている場所に設定する必要があります (それぞれ、<literal>/etc/ssl/certs/Falcot_CA.crt</literal>、<literal>/etc/ssl/vpn.falcot.com.crt</literal>、<literal>/etc/ssl/private/vpn.falcot.com.key</literal>、<literal>/etc/openvpn/dh2048.pem</literal> に設定します)。<literal>server 10.8.0.0 255.255.255.0</literal> 指示文は VPN によって使われるサブネットを定義します。サーバにはこの範囲に含まれる最初の IP アドレス (<literal>10.8.0.1</literal>) が割り当てられ、クライアントには残りの IP アドレスが割り当てられます。" |
| 1071 |
|
| 1072 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1073 |
#, fuzzy |
| 1074 |
#| msgid "<primary>traffic</primary><secondary>control</secondary>" |
| 1075 |
msgid "<primary><filename>/etc</filename></primary><secondary>/etc/network/interfaces</secondary>" |
| 1076 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイギョ\">制御</secondary>" |
| 1077 |
|
| 1078 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1079 |
#, fuzzy |
| 1080 |
#| msgid "<primary>network</primary><secondary>virtual private</secondary>" |
| 1081 |
msgid "<primary>network</primary><secondary>virtual interface</secondary>" |
| 1082 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"カソウプライベート\">仮想プライベート</secondary>" |
| 1083 |
|
| 1084 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1085 |
#, fuzzy |
| 1086 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 1087 |
msgid "<primary>OpenVPN</primary><secondary>network interface</secondary>" |
| 1088 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 1089 |
|
| 1090 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1091 |
# Ref: $ zcat /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz | grep -v -e '^#' -e '^;' -e '^$'; |
| 1092 |
#, fuzzy |
| 1093 |
#| msgid "With this configuration, starting OpenVPN creates the virtual network interface, usually under the <literal>tun0</literal> name. However, firewalls are often configured at the same time as the real network interfaces, which happens before OpenVPN starts. Good practice therefore recommends creating a persistent virtual network interface, and configuring OpenVPN to use this pre-existing interface. This further allows choosing the name for this interface. To this end, <command>openvpn --mktun --dev vpn --dev-type tun</command> creates a virtual network interface named <literal>vpn</literal> with type <literal>tun</literal>; this command can easily be integrated in the firewall configuration script, or in an <literal>up</literal> directive of the <filename>/etc/network/interfaces</filename> file. The OpenVPN configuration file must also be updated accordingly, with the <literal>dev vpn</literal> and <literal>dev-type tun</literal> directives." |
| 1094 |
msgid "With this configuration, starting OpenVPN creates the virtual network interface, usually under the <literal>tun0</literal> name. However, firewalls are often configured at the same time as the real network interfaces, which happens before OpenVPN starts. Good practice therefore recommends creating a persistent virtual network interface, and configuring OpenVPN to use this pre-existing interface. This further allows choosing the name for this interface. To this end, <command>openvpn --mktun --dev vpn --dev-type tun</command> creates a virtual network interface named <literal>vpn</literal> with type <literal>tun</literal>; this command can easily be integrated in the firewall configuration script, or in an <literal>up</literal> directive of the <filename>/etc/network/interfaces</filename> file, or a <emphasis role=\"package\">udev</emphasis> rule can be added to that end. The OpenVPN configuration file must also be updated accordingly, with the <literal>dev vpn</literal> and <literal>dev-type tun</literal> directives." |
| 1095 |
msgstr "この設定で OpenVPN を開始すると、通常 <literal>tun0</literal> という名前の仮想ネットワークインターフェースが作成されます。しかしながら、ファイアウォールは OpenVPN の開始前に実ネットワークインターフェースと同時に設定される場合が多いです。このため、永続的な仮想ネットワークインターフェースを作成し、OpenVPN が事前に作成された仮想インターフェースを使うように設定することを推奨します。この追加的設定により、インターフェースの名前を選ぶことが可能になります。この目的を達成するには、<command>openvpn --mktun --dev vpn --dev-type tun</command> を使って <literal>tun</literal> 型の <literal>vpn</literal> と名付けられた仮想ネットワークインターフェースを作成します。さらに、このコマンドをファイアウォール設定スクリプトの中で使えば、簡単に設定を統合できます。つまり <filename>/etc/network/interfaces</filename> ファイルの <literal>up</literal> 指示文を使います。OpenVPN 設定ファイルをファイアウォール設定に対応させるためには <literal>dev vpn</literal> と <literal>dev-type tun</literal> 指示文を使います。" |
| 1096 |
|
| 1097 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1098 |
#, fuzzy |
| 1099 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 1100 |
msgid "<primary>OpenVPN</primary><secondary>push route</secondary>" |
| 1101 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 1102 |
|
| 1103 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1104 |
msgid "Barring further action, VPN clients can only access the VPN server itself by way of the <literal>10.8.0.1</literal> address. Granting the clients access to the local network (192.168.0.0/24), requires adding a <literal>push route 192.168.0.0 255.255.255.0</literal> directive to the OpenVPN configuration so that VPN clients automatically get a network route telling them that this network is reachable by way of the VPN. Furthermore, machines on the local network also need to be informed that the route to the VPN goes through the VPN server (this automatically works when the VPN server is installed on the gateway). Alternatively, the VPN server can be configured to perform IP masquerading so that connections coming from VPN clients appear as if they are coming from the VPN server instead (see <xref linkend=\"sect.gateway\" />)." |
| 1105 |
msgstr "これ以上の設定を追加しなければ、VPN クライアントは <literal>10.8.0.1</literal> アドレスの VPN サーバにアクセスできるだけです。クライアントをローカルネットワーク (192.168.0.0/24) へアクセスできる状態にするには、<literal>push route 192.168.0.0 255.255.255.0</literal> 指示文を OpenVPN 設定に追加します。こうすることで、VPN クライアントは自動的にネットワーク経路を取得し、VPN 経由でローカルネットワークに到達できるようになります。さらに、ローカルネットワークにいるマシンに対して VPN サーバに通じる VPN への経路を知らせる必要もあります (VPN サーバがゲートウェイにインストールされている場合、これは自動的に動きます)。別の方法として、VPN サーバが IP マスカレードを動かすように設定する方法があります。そうすれば、VPN クライアントからの接続はあたかもクライアントが VPN サーバからアクセスしたかのように見えます (<xref linkend=\"sect.gateway\" />を参照してください)。" |
| 1106 |
|
| 1107 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1108 |
msgid "Configuring the OpenVPN Client" |
| 1109 |
msgstr "OpenVPN クライアントの設定" |
| 1110 |
|
| 1111 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1112 |
#, fuzzy |
| 1113 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 1114 |
msgid "<primary>OpenVPN</primary><secondary>client</secondary>" |
| 1115 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 1116 |
|
| 1117 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1118 |
msgid "Setting up an OpenVPN client also requires creating a configuration file in <filename>/etc/openvpn/</filename>. A standard configuration can be obtained by using <filename>/usr/share/doc/openvpn/examples/sample-config-files/client.conf</filename> as a starting point. The <literal>remote vpn.falcot.com 1194</literal> directive describes the address and port of the OpenVPN server; the <literal>ca</literal>, <literal>cert</literal> and <literal>key</literal> also need to be adapted to describe the locations of the key files." |
| 1119 |
msgstr "OpenVPN クライアントを設定する場合にも、<filename>/etc/openvpn/</filename> に設定ファイルを置きます。標準的な設定の良い足掛かりとして <filename>/usr/share/doc/openvpn/examples/sample-config-files/client.conf</filename> が用意されています。<literal>remote vpn.falcot.com 1194</literal> 指示文は OpenVPN サーバのアドレスとポート番号を表します。さらに <literal>ca</literal>、<literal>cert</literal>、<literal>key</literal> も鍵ファイルの場所に合わせて設定が必要です。" |
| 1120 |
|
| 1121 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1122 |
#, fuzzy |
| 1123 |
#| msgid "<primary>network</primary><secondary>virtual private</secondary>" |
| 1124 |
msgid "<primary>OpenVPN</primary><secondary><literal>AUTOSTART</literal></secondary>" |
| 1125 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"カソウプライベート\">仮想プライベート</secondary>" |
| 1126 |
|
| 1127 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1128 |
#, fuzzy |
| 1129 |
#| msgid "<primary>traffic</primary><secondary>limitation</secondary>" |
| 1130 |
msgid "<primary><filename>/etc</filename></primary><secondary>/etc/default/openvpn</secondary>" |
| 1131 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイゲン\">制限</secondary>" |
| 1132 |
|
| 1133 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1134 |
#, fuzzy |
| 1135 |
#| msgid "<primary>server</primary><secondary>name</secondary>" |
| 1136 |
msgid "<primary>service</primary><secondary><filename>[email protected]</filename></secondary>" |
| 1137 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 1138 |
|
| 1139 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1140 |
#, fuzzy |
| 1141 |
#| msgid "If the VPN should not be started automatically on boot, set the <literal>AUTOSTART</literal> directive to <literal>none</literal> in the <filename>/etc/default/openvpn</filename> file. Starting or stopping a given VPN connection is always possible with the commands <command>service openvpn@<replaceable>name</replaceable> start</command> and <command>service openvpn@<replaceable>name</replaceable> stop</command> (where the connection <replaceable>name</replaceable> matches the one defined in <filename>/etc/openvpn/<replaceable>name</replaceable>.conf</filename>)." |
| 1142 |
msgid "If the VPN should not be started automatically on boot, set the <literal>AUTOSTART</literal> directive to <literal>none</literal> in the <filename>/etc/default/openvpn</filename> file. Starting or stopping a given VPN connection is always possible with the commands <command>systemctl start openvpn@<replaceable>name</replaceable></command> and <command>systemctl stop openvpn@<replaceable>name</replaceable></command> (where the connection <replaceable>name</replaceable> matches the one defined in <filename>/etc/openvpn/<replaceable>name</replaceable>.conf</filename>)." |
| 1143 |
msgstr "起動時に VPN を自動的に開始したくない場合、<filename>/etc/default/openvpn</filename> ファイルの <literal>AUTOSTART</literal> 指示文に <literal>none</literal> を設定してください。VPN 接続の開始と停止は <command>service openvpn@<replaceable>name</replaceable> start</command> と <command>service openvpn@<replaceable>name</replaceable> stop</command> コマンドを使えばいつでも可能です (ここで、接続名 <replaceable>name</replaceable> は <filename>/etc/openvpn/<replaceable>name</replaceable>.conf</filename> で定義したものにマッチします)。" |
| 1144 |
|
| 1145 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1146 |
#, fuzzy |
| 1147 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 1148 |
msgid "<primary>OpenVPN</primary><secondary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></secondary>" |
| 1149 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 1150 |
|
| 1151 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1152 |
#, fuzzy |
| 1153 |
#| msgid "The <emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis> package contains an extension to Network Manager (see <xref linkend=\"sect.roaming-network-config\" />) that allows managing OpenVPN virtual private networks. This allows every user to configure OpenVPN connections graphically and to control them from the network management icon. <indexterm><primary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></primary></indexterm>" |
| 1154 |
msgid "The <emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis> package contains an extension to Network Manager (see <xref linkend=\"sect.roaming-network-config\" />) that allows managing OpenVPN virtual private networks. This allows every user to configure OpenVPN connections graphically and to control them from the network management icon." |
| 1155 |
msgstr "<emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis> パッケージには、NetworkManager (<xref linkend=\"sect.roaming-network-config\" />を参照してください) の拡張が含まれ、これを使うことで OpenVPN 仮想プライベートネットワークを管理することが可能です。誰もがグラフィカルに OpenVPN 接続を設定し、ネットワーク管理アイコンからこれを制御することが可能です。<indexterm><primary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></primary></indexterm>" |
| 1156 |
|
| 1157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1158 |
#, fuzzy |
| 1159 |
#| msgid "<primary><emphasis role=\"pkg\">iputils-ping</emphasis></primary>" |
| 1160 |
msgid "<primary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></primary>" |
| 1161 |
msgstr "<primary><emphasis role=\"pkg\">iputils-ping</emphasis></primary>" |
| 1162 |
|
| 1163 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1164 |
msgid "Virtual Private Network with SSH" |
| 1165 |
msgstr "SSH を使った仮想プライベートネットワーク" |
| 1166 |
|
| 1167 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1168 |
#, fuzzy |
| 1169 |
#| msgid "<primary>port</primary><secondary>TCP</secondary>" |
| 1170 |
msgid "<primary>SSH</primary><secondary>VPN</secondary>" |
| 1171 |
msgstr "<primary>ポート</primary><secondary>TCP</secondary>" |
| 1172 |
|
| 1173 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1174 |
msgid "<primary>PPP</primary>" |
| 1175 |
msgstr "<primary>PPP</primary>" |
| 1176 |
|
| 1177 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1178 |
#, fuzzy |
| 1179 |
#| msgid "There are actually two ways of creating a virtual private network with SSH. The historic one involves establishing a PPP layer over the SSH link. This method is described in a HOWTO document: <ulink type=\"block\" url=\"http://www.tldp.org/HOWTO/ppp-ssh/\" />" |
| 1180 |
msgid "There are actually two ways of creating a virtual private network with SSH. The historic one involves establishing a PPP layer over the SSH link. This method is described in a HOWTO document: <ulink type=\"block\" url=\"https://www.tldp.org/HOWTO/ppp-ssh/\" />" |
| 1181 |
msgstr "SSH を使った仮想プライベートネットワークの作成法には、2 種類の方法があります。歴史的に見て重要な方法が SSH リンクの上で PPP レイヤを確立する方法です。この方法は HOWTO 文書で説明されています。<ulink type=\"block\" url=\"http://www.tldp.org/HOWTO/ppp-ssh/\" />" |
| 1182 |
|
| 1183 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1184 |
#, fuzzy |
| 1185 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 1186 |
msgid "<primary>SSH</primary><secondary><literal>PermitTunnel</literal></secondary>" |
| 1187 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 1188 |
|
| 1189 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1190 |
#, fuzzy |
| 1191 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 1192 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ssh/sshd_config</filename></secondary>" |
| 1193 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 1194 |
|
| 1195 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1196 |
msgid "The second method is more recent, and was introduced with OpenSSH 4.3; it is now possible for OpenSSH to create virtual network interfaces (<literal>tun*</literal>) on both sides of an SSH connection, and these virtual interfaces can be configured exactly as if they were physical interfaces. The tunneling system must first be enabled by setting <literal>PermitTunnel</literal> to “yes” in the SSH server configuration file (<filename>/etc/ssh/sshd_config</filename>). When establishing the SSH connection, the creation of a tunnel must be explicitly requested with the <literal>-w any:any</literal> option (<literal>any</literal> can be replaced with the desired <literal>tun</literal> device number). This requires the user to have administrator privilege on both sides, so as to be able to create the network device (in other words, the connection must be established as root)." |
| 1197 |
msgstr "2 番目の方法はより最近の方法で、OpenSSH 4.3 で導入されました。その結果今や、OpenSSH は SSH 接続のサーバおよびクライアント側に仮想ネットワークインターフェース (<literal>tun*</literal>) を作り、仮想インターフェースをあたかも物理インターフェースのように設定することが可能です。このトンネルシステムを有効化するにはまず、SSH サーバの設定ファイル (<filename>/etc/ssh/sshd_config</filename>) の中で <literal>PermitTunnel</literal> を「yes」に設定しなければいけません。SSH 接続を確立する際には、<literal>-w any:any</literal> オプションを使って明示的にトンネルの作成を要求しなければいけません (ここで <literal>any</literal> は必要な <literal>tun</literal> デバイス番号で置き替えます)。トンネルを作成するには、サーバおよびクライアント側でそのユーザが管理者権限を持っていることが必要です。そうすればネットワークデバイスを作成することが可能です (言い換えれば、接続は root で確立されなければいけません)。" |
| 1198 |
|
| 1199 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1200 |
msgid "Both methods for creating a virtual private network over SSH are quite straightforward. However, the VPN they provide is not the most efficient available; in particular, it does not handle high levels of traffic very well." |
| 1201 |
msgstr "SSH を使って仮想プライベートネットワークを作成する方法は、どちらもかなり直接的なものです。しかしながら、SSH の提供する VPN は最も効率のよい方法ではありません。特に、高レベルのトラフィックをうまく取り扱うことができません。" |
| 1202 |
|
| 1203 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1204 |
# Tag: PTAL; |
| 1205 |
#, fuzzy |
| 1206 |
#| msgid "The explanation is that when a TCP/IP stack is encapsulated within a TCP/IP connection (for SSH), the TCP protocol is used twice, once for the SSH connection and once within the tunnel. This leads to problems, especially due to the way TCP adapts to network conditions by altering timeout delays. The following site describes the problem in more detail: <ulink type=\"block\" url=\"http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" /> VPNs over SSH should therefore be restricted to one-off tunnels with no performance constraints." |
| 1207 |
msgid "The explanation is that when a TCP/IP stack is encapsulated within a TCP/IP connection (for SSH), the TCP protocol is used twice, once for the SSH connection and once within the tunnel. This leads to problems, especially due to the way TCP adapts to network conditions by altering timeout delays. The following site describes the problem in more detail: <ulink type=\"block\" url=\"http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" />" |
| 1208 |
msgstr "つまり、TCP/IP スタックが TCP/IP 接続 (SSH) の中にカプセル化される場合、TCP プロトコルは 2 回使われるという点です。1 回は SSH 接続で、もう 1 回がトンネル内です。TCP はタイムアウト遅延を変更することでネットワークの状態に接続状態を適合させる機能があるため、これは特に問題になります。以下のサイトがこの問題についてより詳しく説明しています。<ulink type=\"block\" url=\"http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" />このため、VPN over SSH はパフォーマンスに制約のない単発のトンネルに留めるべきです。" |
| 1209 |
|
| 1210 |
msgid "VPNs over SSH should therefore be restricted to one-off tunnels with no performance constraints." |
| 1211 |
msgstr "" |
| 1212 |
|
| 1213 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1214 |
msgid "IPsec" |
| 1215 |
msgstr "IPsec" |
| 1216 |
|
| 1217 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1218 |
msgid "<primary>IPsec</primary>" |
| 1219 |
msgstr "<primary>IPsec</primary>" |
| 1220 |
|
| 1221 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1222 |
#, fuzzy |
| 1223 |
#| msgid "<primary>protocol</primary><secondary>ESP</secondary>" |
| 1224 |
msgid "<primary>Internet Protocol Security</primary><see>IPsec</see>" |
| 1225 |
msgstr "<primary>プロトコル</primary><secondary>ESP</secondary>" |
| 1226 |
|
| 1227 |
#, fuzzy |
| 1228 |
#| msgid "<primary><command>openswan</command></primary>" |
| 1229 |
msgid "<primary><command>libreswan</command></primary>" |
| 1230 |
msgstr "<primary><command>openswan</command></primary>" |
| 1231 |
|
| 1232 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1233 |
msgid "<primary><command>strongswan</command></primary>" |
| 1234 |
msgstr "<primary><command>strongswan</command></primary>" |
| 1235 |
|
| 1236 |
msgid "IPsec, despite being the standard in IP VPNs, is rather more involved in its implementation. The IPsec engine itself is integrated in the Linux kernel; the required user-space parts, the control and configuration tools, are provided by the <emphasis role=\"pkg\">libreswan</emphasis> package or the <emphasis role=\"pkg\">strongswan</emphasis> package. Here we describe briefly the first of these options." |
| 1237 |
msgstr "" |
| 1238 |
|
| 1239 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1240 |
#, fuzzy |
| 1241 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 1242 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ipsec.conf</filename></secondary>" |
| 1243 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 1244 |
|
| 1245 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1246 |
#, fuzzy |
| 1247 |
#| msgid "<primary>server</primary><secondary>name</secondary>" |
| 1248 |
msgid "<primary>IPsec</primary><secondary>tunnel</secondary>" |
| 1249 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 1250 |
|
| 1251 |
msgid "First, we install the <emphasis role=\"pkg\">libreswan</emphasis> package. In concrete terms, each host's <filename>/etc/ipsec.conf</filename> contains the parameters for <emphasis>IPsec tunnels</emphasis> (or <emphasis>Security Associations</emphasis>, in the IPsec terminology) that the host is concerned with. There are many configuration examples in <filename>/usr/share/doc/libreswan/</filename>, but Libreswan's online documentation has more examples with explanations: <ulink type=\"block\" url=\"https://libreswan.org/wiki/\" />" |
| 1252 |
msgstr "" |
| 1253 |
|
| 1254 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1255 |
#, fuzzy |
| 1256 |
#| msgid "<primary>server</primary><secondary>name</secondary>" |
| 1257 |
msgid "<primary>service</primary><secondary><filename>ipsec.service</filename></secondary>" |
| 1258 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 1259 |
|
| 1260 |
msgid "The IPsec service can be controlled with <command>systemctl</command>; for example, <command>systemctl start ipsec</command> will start the IPsec service." |
| 1261 |
msgstr "" |
| 1262 |
|
| 1263 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1264 |
msgid "<primary>IKE</primary>" |
| 1265 |
msgstr "<primary>IKE</primary>" |
| 1266 |
|
| 1267 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1268 |
#, fuzzy |
| 1269 |
#| msgid "<primary>IPsec</primary>" |
| 1270 |
msgid "<primary>IPsec Key Exchange</primary><see>IKE</see>" |
| 1271 |
msgstr "<primary>IPsec</primary>" |
| 1272 |
|
| 1273 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1274 |
#, fuzzy |
| 1275 |
#| msgid "<primary>IPsec</primary><secondary>IPsec Key Exchange</secondary>" |
| 1276 |
msgid "<primary>IPsec</primary><secondary>IPsec Key Exchange</secondary><seealso>IKE</seealso>" |
| 1277 |
msgstr "<primary>IPsec</primary><secondary>IPsec Key Exchange</secondary>" |
| 1278 |
|
| 1279 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1280 |
msgid "<primary><command>setkey</command></primary>" |
| 1281 |
msgstr "<primary><command>setkey</command></primary>" |
| 1282 |
|
| 1283 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1284 |
msgid "In spite of its status as the reference, the complexity of setting up IPsec restricts its usage in practice. OpenVPN-based solutions will generally be preferred when the required tunnels are neither too many nor too dynamic." |
| 1285 |
msgstr "IPsec は標準規格という地位があるにも関わらず、その設定が複雑なことが原因で実際にはあまり使われていません。必要なトンネルが少なくて静的な場合は、OpenVPN に基づく解決策が通常好まれます。" |
| 1286 |
|
| 1287 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1288 |
msgid "<emphasis>CAUTION</emphasis> IPsec and NAT" |
| 1289 |
msgstr "<emphasis>CAUTION</emphasis> IPsec と NAT" |
| 1290 |
|
| 1291 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1292 |
msgid "<primary>NAT</primary>" |
| 1293 |
msgstr "<primary>NAT</primary>" |
| 1294 |
|
| 1295 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1296 |
msgid "<primary>NAT-T</primary>" |
| 1297 |
msgstr "<primary>NAT-T</primary>" |
| 1298 |
|
| 1299 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1300 |
#, fuzzy |
| 1301 |
#| msgid "<primary>NAT Traversal</primary>" |
| 1302 |
msgid "<primary>NAT Traversal</primary><seealso>NAT-T</seealso>" |
| 1303 |
msgstr "<primary>NAT Traversal</primary>" |
| 1304 |
|
| 1305 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1306 |
msgid "NATing firewalls and IPsec do not work well together: since IPsec signs the packets, any change on these packets that the firewall might perform will void the signature, and the packets will be rejected at their destination. Various IPsec implementations now include the <emphasis>NAT-T</emphasis> technique (for <emphasis>NAT Traversal</emphasis>), which basically encapsulates the IPsec packet within a standard UDP packet." |
| 1307 |
msgstr "ファイアウォールの NAT は IPsec とうまく共存しません。なぜなら、IPsec はパケットを署名しますが、ファイアウォールがパケットを書き換えることで IPsec による署名は無効化され、無効な署名のパケットは受け取り側で拒否されるからです。今やさまざまな IPsec 実装が <emphasis>NAT-T</emphasis> (<emphasis>NAT Traversal</emphasis> の略語) 技術をサポートしています。これは基本的に IPsec パケットを標準的な UDP パケットにカプセル化するものです。" |
| 1308 |
|
| 1309 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1310 |
msgid "<emphasis>SECURITY</emphasis> IPsec and firewalls" |
| 1311 |
msgstr "<emphasis>SECURITY</emphasis> IPsec とファイアウォール" |
| 1312 |
|
| 1313 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1314 |
msgid "<primary>ESP, protocol</primary>" |
| 1315 |
msgstr "<primary>ESP、プロトコル</primary>" |
| 1316 |
|
| 1317 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1318 |
msgid "<primary>AH, protocol</primary>" |
| 1319 |
msgstr "<primary>AH、プロトコル</primary>" |
| 1320 |
|
| 1321 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1322 |
msgid "<primary>protocol</primary><secondary>AH</secondary>" |
| 1323 |
msgstr "<primary>プロトコル</primary><secondary>AH</secondary>" |
| 1324 |
|
| 1325 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1326 |
msgid "<primary>protocol</primary><secondary>ESP</secondary>" |
| 1327 |
msgstr "<primary>プロトコル</primary><secondary>ESP</secondary>" |
| 1328 |
|
| 1329 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1330 |
msgid "The standard mode of operation of IPsec involves data exchanges on UDP port 500 for key exchanges (also on UDP port 4500 in the case that NAT-T is in use). Moreover, IPsec packets use two dedicated IP protocols that the firewall must let through; reception of these packets is based on their protocol numbers, 50 (ESP) and 51 (AH)." |
| 1331 |
msgstr "IPsec の動作の標準的モードは鍵交換に UDP ポート 500 番 (NAT-T を使用する場合 UDP ポート 4500 番) を使います。さらに、IPsec パケットは 2 種類の専用 IP プロトコルを使います。ファイアウォールはこのプロトコルを通過させなければいけません。さらに、これらのパケットの受け入れ可否はプロトコル番号 (ESP は 50 番、AH は 51 番) に基づきます。" |
| 1332 |
|
| 1333 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1334 |
msgid "PPTP" |
| 1335 |
msgstr "PPTP" |
| 1336 |
|
| 1337 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1338 |
msgid "<primary>PPTP</primary>" |
| 1339 |
msgstr "<primary>PPTP</primary>" |
| 1340 |
|
| 1341 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1342 |
msgid "<primary>GRE, protocol</primary>" |
| 1343 |
msgstr "<primary>GRE、プロトコル</primary>" |
| 1344 |
|
| 1345 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1346 |
msgid "<primary>protocol</primary><secondary>GRE</secondary>" |
| 1347 |
msgstr "<primary>プロトコル</primary><secondary>GRE</secondary>" |
| 1348 |
|
| 1349 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1350 |
msgid "PPTP (for <emphasis>Point-to-Point Tunneling Protocol</emphasis>) uses two communication channels, one for control data and one for payload data; the latter uses the GRE protocol (<emphasis>Generic Routing Encapsulation</emphasis>). A standard PPP link is then set up over the data exchange channel." |
| 1351 |
msgstr "PPTP (<emphasis>Point-to-Point Tunneling Protocol</emphasis> の略語) は 2 種類の通信チャンネルを使います。1 つは制御データ用で、もう 1 つがペイロードデータ用です。ペイロードデータ用チャンネルは GRE プロトコル (<emphasis>Generic Routing Encapsulation</emphasis>) を使います。標準的な PPP リンクはペイロードデータ交換用チャンネル上に確立されます。" |
| 1352 |
|
| 1353 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1354 |
msgid "Configuring the Client" |
| 1355 |
msgstr "クライアントの設定" |
| 1356 |
|
| 1357 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1358 |
#, fuzzy |
| 1359 |
#| msgid "<primary>port</primary><secondary>TCP</secondary>" |
| 1360 |
msgid "<primary>PPTP</primary><secondary>Client</secondary>" |
| 1361 |
msgstr "<primary>ポート</primary><secondary>TCP</secondary>" |
| 1362 |
|
| 1363 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1364 |
msgid "<primary><emphasis role=\"pkg\">pptp-linux</emphasis></primary>" |
| 1365 |
msgstr "<primary><emphasis role=\"pkg\">pptp-linux</emphasis></primary>" |
| 1366 |
|
| 1367 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1368 |
msgid "The <emphasis role=\"pkg\">pptp-linux</emphasis> package contains an easily-configured PPTP client for Linux. The following instructions take their inspiration from the official documentation: <ulink type=\"block\" url=\"http://pptpclient.sourceforge.net/howto-debian.phtml\" />" |
| 1369 |
msgstr "<emphasis role=\"pkg\">pptp-linux</emphasis> パッケージには Linux 用に簡単に設定できる PPTP クライアントが含まれています。以下の説明は公式文書からヒントを得て作ったものです。<ulink type=\"block\" url=\"http://pptpclient.sourceforge.net/howto-debian.phtml\" />" |
| 1370 |
|
| 1371 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1372 |
#, fuzzy |
| 1373 |
#| msgid "<primary>server</primary><secondary>name</secondary>" |
| 1374 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ppp/</filename></secondary>" |
| 1375 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 1376 |
|
| 1377 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1378 |
msgid "The Falcot administrators created several files: <filename>/etc/ppp/options.pptp</filename>, <filename>/etc/ppp/peers/falcot</filename>, <filename>/etc/ppp/ip-up.d/falcot</filename>, and <filename>/etc/ppp/ip-down.d/falcot</filename>." |
| 1379 |
msgstr "Falcot の管理者はいくつかのファイルを作成しました。すなわち <filename>/etc/ppp/options.pptp</filename>、<filename>/etc/ppp/peers/falcot</filename>、<filename>/etc/ppp/ip-up.d/falcot</filename>、<filename>/etc/ppp/ip-down.d/falcot</filename> を作成しました。" |
| 1380 |
|
| 1381 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1382 |
msgid "The <filename>/etc/ppp/options.pptp</filename> file" |
| 1383 |
msgstr "<filename>/etc/ppp/options.pptp</filename> ファイル" |
| 1384 |
|
| 1385 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1386 |
msgid "" |
| 1387 |
"\n" |
| 1388 |
"# PPP options used for a PPTP connection\n" |
| 1389 |
"lock\n" |
| 1390 |
"noauth\n" |
| 1391 |
"nobsdcomp\n" |
| 1392 |
"nodeflate" |
| 1393 |
msgstr "" |
| 1394 |
"\n" |
| 1395 |
"# PPTP 接続時に利用する PPP オプション\n" |
| 1396 |
"lock\n" |
| 1397 |
"noauth\n" |
| 1398 |
"nobsdcomp\n" |
| 1399 |
"nodeflate" |
| 1400 |
|
| 1401 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1402 |
msgid "The <filename>/etc/ppp/peers/falcot</filename> file" |
| 1403 |
msgstr "<filename>/etc/ppp/peers/falcot</filename> ファイル" |
| 1404 |
|
| 1405 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1406 |
# Ref: man 8 pptp; |
| 1407 |
msgid "" |
| 1408 |
"\n" |
| 1409 |
"# vpn.falcot.com is the PPTP server\n" |
| 1410 |
"pty \"pptp vpn.falcot.com --nolaunchpppd\"\n" |
| 1411 |
"# the connection will identify as the \"vpn\" user\n" |
| 1412 |
"user vpn\n" |
| 1413 |
"remotename pptp\n" |
| 1414 |
"# encryption is needed\n" |
| 1415 |
"require-mppe-128\n" |
| 1416 |
"file /etc/ppp/options.pptp\n" |
| 1417 |
"ipparam falcot" |
| 1418 |
msgstr "" |
| 1419 |
"\n" |
| 1420 |
"# vpn.falcot.com は PPTP サーバです\n" |
| 1421 |
"pty \"pptp vpn.falcot.com --nolaunchpppd\"\n" |
| 1422 |
"# \"vpn\" ユーザで本人確認して接続します\n" |
| 1423 |
"user vpn\n" |
| 1424 |
"remotename pptp\n" |
| 1425 |
"# 暗号化を有効にします\n" |
| 1426 |
"require-mppe-128\n" |
| 1427 |
"file /etc/ppp/options.pptp\n" |
| 1428 |
"ipparam falcot" |
| 1429 |
|
| 1430 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1431 |
msgid "The <filename>/etc/ppp/ip-up.d/falcot</filename> file" |
| 1432 |
msgstr "<filename>/etc/ppp/ip-up.d/falcot</filename> ファイル" |
| 1433 |
|
| 1434 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1435 |
#, fuzzy |
| 1436 |
#| msgid "" |
| 1437 |
#| "\n" |
| 1438 |
#| "# Create the route to the Falcot network\n" |
| 1439 |
#| "if [ \"$6\" = \"falcot\" ]; then\n" |
| 1440 |
#| " # 192.168.0.0/24 is the (remote) Falcot network\n" |
| 1441 |
#| " route add -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" |
| 1442 |
#| "fi" |
| 1443 |
msgid "" |
| 1444 |
"\n" |
| 1445 |
"# Create the route to the Falcot network\n" |
| 1446 |
"if [ \"$6\" = \"falcot\" ]; then\n" |
| 1447 |
" # 192.168.0.0/24 is the (remote) Falcot network\n" |
| 1448 |
" ip route add 192.168.0.0/24 dev $1\n" |
| 1449 |
"fi" |
| 1450 |
msgstr "" |
| 1451 |
"\n" |
| 1452 |
"# Falcot ネットワークへの経路を作成します\n" |
| 1453 |
"if [ \"$6\" = \"falcot\" ]; then\n" |
| 1454 |
" # 192.168.0.0/24 is the (remote) Falcot network\n" |
| 1455 |
" route add -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" |
| 1456 |
"fi" |
| 1457 |
|
| 1458 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1459 |
msgid "The <filename>/etc/ppp/ip-down.d/falcot</filename> file" |
| 1460 |
msgstr "<filename>/etc/ppp/ip-down.d/falcot</filename> ファイル" |
| 1461 |
|
| 1462 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1463 |
#, fuzzy |
| 1464 |
#| msgid "" |
| 1465 |
#| "\n" |
| 1466 |
#| "# Delete the route to the Falcot network\n" |
| 1467 |
#| "if [ \"$6\" = \"falcot\" ]; then\n" |
| 1468 |
#| " # 192.168.0.0/24 is the (remote) Falcot network\n" |
| 1469 |
#| " route del -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" |
| 1470 |
#| "fi" |
| 1471 |
msgid "" |
| 1472 |
"\n" |
| 1473 |
"# Delete the route to the Falcot network\n" |
| 1474 |
"if [ \"$6\" = \"falcot\" ]; then\n" |
| 1475 |
" # 192.168.0.0/24 is the (remote) Falcot network\n" |
| 1476 |
" ip route del 192.168.0.0/24 dev $1\n" |
| 1477 |
"fi" |
| 1478 |
msgstr "" |
| 1479 |
"\n" |
| 1480 |
"# Falcot ネットワークへの経路を削除します\n" |
| 1481 |
"if [ \"$6\" = \"falcot\" ]; then\n" |
| 1482 |
" # 192.168.0.0/24 is the (remote) Falcot network\n" |
| 1483 |
" route del -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" |
| 1484 |
"fi" |
| 1485 |
|
| 1486 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1487 |
msgid "<emphasis>SECURITY</emphasis> MPPE" |
| 1488 |
msgstr "<emphasis>SECURITY</emphasis> MPPE" |
| 1489 |
|
| 1490 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1491 |
msgid "<primary>MPPE</primary>" |
| 1492 |
msgstr "<primary>MPPE</primary>" |
| 1493 |
|
| 1494 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1495 |
#, fuzzy |
| 1496 |
#| msgid "<primary>Microsoft</primary><secondary>Point-to-Point Encryption</secondary>" |
| 1497 |
msgid "<primary>Microsoft</primary><secondary>Point-to-Point Encryption</secondary><see>MPPE</see>" |
| 1498 |
msgstr "<primary>Microsoft</primary><secondary>Point-to-Point Encryption</secondary>" |
| 1499 |
|
| 1500 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1501 |
msgid "Securing PPTP involves using the MPPE feature (<emphasis>Microsoft Point-to-Point Encryption</emphasis>), which is available in official Debian kernels as a module." |
| 1502 |
msgstr "PPTP を安全なものにするには MPPE 機能 (<emphasis>Microsoft Point-to-Point Encryption</emphasis>) を使います。MPPE はモジュールとして公式の Debian カーネルで利用できます。" |
| 1503 |
|
| 1504 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1505 |
msgid "Configuring the Server" |
| 1506 |
msgstr "サーバの設定" |
| 1507 |
|
| 1508 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1509 |
#, fuzzy |
| 1510 |
#| msgid "<primary><command>bgpd</command></primary>" |
| 1511 |
msgid "<primary><command>pptpd</command></primary>" |
| 1512 |
msgstr "<primary><command>bgpd</command></primary>" |
| 1513 |
|
| 1514 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1515 |
msgid "<emphasis>CAUTION</emphasis> PPTP and firewalls" |
| 1516 |
msgstr "<emphasis>CAUTION</emphasis> PPTP とファイアウォール" |
| 1517 |
|
| 1518 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1519 |
msgid "Intermediate firewalls need to be configured to let through IP packets using protocol 47 (GRE). Moreover, the PPTP server's port 1723 needs to be open so that the communication channel can happen." |
| 1520 |
msgstr "中間ファイアウォールはプロトコル 47 番 (GRE) を使っている IP パケットを通過させるように設定されなければいけません。さらに、通信チャンネルを開くために PPTP サーバのポート 1723 番を開けることが必要です。" |
| 1521 |
|
| 1522 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1523 |
#, fuzzy |
| 1524 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 1525 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/pptpd.conf</filename></secondary>" |
| 1526 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 1527 |
|
| 1528 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1529 |
msgid "<command>pptpd</command> is the PPTP server for Linux. Its main configuration file, <filename>/etc/pptpd.conf</filename>, requires very few changes: <emphasis>localip</emphasis> (local IP address) and <emphasis>remoteip</emphasis> (remote IP address). In the example below, the PPTP server always uses the <literal>192.168.0.199</literal> address, and PPTP clients receive IP addresses from <literal>192.168.0.200</literal> to <literal>192.168.0.250</literal>." |
| 1530 |
msgstr "<command>pptpd</command> は Linux 用の PPTP サーバです。主設定ファイル <filename>/etc/pptpd.conf</filename> にはいくつかの変更が必要です。すなわち <emphasis>localip</emphasis> (ローカル IP アドレス) と <emphasis>remoteip</emphasis> (リモート IP アドレス) を変更する必要があります。以下の例では、PPTP サーバは常に <literal>192.168.0.199</literal> アドレスを使い、PPTP クライアントは <literal>192.168.0.200</literal> から <literal>192.168.0.250</literal> までの IP アドレスを受け取ります。" |
| 1531 |
|
| 1532 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1533 |
msgid "The <filename>/etc/pptpd.conf</filename> file" |
| 1534 |
msgstr "<filename>/etc/pptpd.conf</filename> ファイル" |
| 1535 |
|
| 1536 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1537 |
# Ref: man 5 pptpd.conf; |
| 1538 |
#, fuzzy |
| 1539 |
#| msgid "" |
| 1540 |
#| "\n" |
| 1541 |
#| "# TAG: speed\n" |
| 1542 |
#| "#\n" |
| 1543 |
#| "# Specifies the speed for the PPP daemon to talk at.\n" |
| 1544 |
#| "#\n" |
| 1545 |
#| "speed 115200\n" |
| 1546 |
#| "\n" |
| 1547 |
#| "# TAG: option\n" |
| 1548 |
#| "#\n" |
| 1549 |
#| "# Specifies the location of the PPP options file.\n" |
| 1550 |
#| "# By default PPP looks in '/etc/ppp/options'\n" |
| 1551 |
#| "#\n" |
| 1552 |
#| "option /etc/ppp/pptpd-options\n" |
| 1553 |
#| "\n" |
| 1554 |
#| "# TAG: debug\n" |
| 1555 |
#| "#\n" |
| 1556 |
#| "# Turns on (more) debugging to syslog\n" |
| 1557 |
#| "#\n" |
| 1558 |
#| "# debug\n" |
| 1559 |
#| "\n" |
| 1560 |
#| "# TAG: localip\n" |
| 1561 |
#| "# TAG: remoteip\n" |
| 1562 |
#| "#\n" |
| 1563 |
#| "# Specifies the local and remote IP address ranges.\n" |
| 1564 |
#| "#\n" |
| 1565 |
#| "# You can specify single IP addresses separated by commas or you can\n" |
| 1566 |
#| "# specify ranges, or both. For example:\n" |
| 1567 |
#| "#\n" |
| 1568 |
#| "# 192.168.0.234,192.168.0.245-249,192.168.0.254\n" |
| 1569 |
#| "#\n" |
| 1570 |
#| "# IMPORTANT RESTRICTIONS:\n" |
| 1571 |
#| "#\n" |
| 1572 |
#| "# 1. No spaces are permitted between commas or within addresses.\n" |
| 1573 |
#| "#\n" |
| 1574 |
#| "# 2. If you give more IP addresses than MAX_CONNECTIONS, it will\n" |
| 1575 |
#| "# start at the beginning of the list and go until it gets\n" |
| 1576 |
#| "# MAX_CONNECTIONS IPs. Others will be ignored.\n" |
| 1577 |
#| "#\n" |
| 1578 |
#| "# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n" |
| 1579 |
#| "# you must type 234-238 if you mean this.\n" |
| 1580 |
#| "#\n" |
| 1581 |
#| "# 4. If you give a single localIP, that's ok - all local IPs will\n" |
| 1582 |
#| "# be set to the given one. You MUST still give at least one remote\n" |
| 1583 |
#| "# IP for each simultaneous client.\n" |
| 1584 |
#| "#\n" |
| 1585 |
#| "#localip 192.168.0.234-238,192.168.0.245\n" |
| 1586 |
#| "#remoteip 192.168.1.234-238,192.168.1.245\n" |
| 1587 |
#| "#localip 10.0.1.1\n" |
| 1588 |
#| "#remoteip 10.0.1.2-100\n" |
| 1589 |
#| "localip 192.168.0.199\n" |
| 1590 |
#| "remoteip 192.168.0.200-250" |
| 1591 |
msgid "" |
| 1592 |
"\n" |
| 1593 |
"[..]\n" |
| 1594 |
"# TAG: localip\n" |
| 1595 |
"# TAG: remoteip\n" |
| 1596 |
"# Specifies the local and remote IP address ranges.\n" |
| 1597 |
"#\n" |
| 1598 |
"# These options are ignored if delegate option is set.\n" |
| 1599 |
"#\n" |
| 1600 |
"# Any addresses work as long as the local machine takes care of the\n" |
| 1601 |
"# routing. But if you want to use MS-Windows networking, you should\n" |
| 1602 |
"# use IP addresses out of the LAN address space and use the proxyarp\n" |
| 1603 |
"# option in the pppd options file, or run bcrelay.\n" |
| 1604 |
"#\n" |
| 1605 |
"# You can specify single IP addresses seperated by commas or you can\n" |
| 1606 |
"# specify ranges, or both. For example:\n" |
| 1607 |
"#\n" |
| 1608 |
"# 192.168.0.234,192.168.0.245-249,192.168.0.254\n" |
| 1609 |
"#\n" |
| 1610 |
"# IMPORTANT RESTRICTIONS:\n" |
| 1611 |
"#\n" |
| 1612 |
"# 1. No spaces are permitted between commas or within addresses.\n" |
| 1613 |
"#\n" |
| 1614 |
"# 2. If you give more IP addresses than the value of connections,\n" |
| 1615 |
"# it will start at the beginning of the list and go until it\n" |
| 1616 |
"# gets connections IPs. Others will be ignored.\n" |
| 1617 |
"#\n" |
| 1618 |
"# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n" |
| 1619 |
"# you must type 234-238 if you mean this.\n" |
| 1620 |
"#\n" |
| 1621 |
"# 4. If you give a single localIP, that's ok - all local IPs will\n" |
| 1622 |
"# be set to the given one. You MUST still give at least one remote\n" |
| 1623 |
"# IP for each simultaneous client.\n" |
| 1624 |
"#\n" |
| 1625 |
"# (Recommended)\n" |
| 1626 |
"#localip 192.168.0.1\n" |
| 1627 |
"#remoteip 192.168.0.234-238,192.168.0.245\n" |
| 1628 |
"# or\n" |
| 1629 |
"#localip 192.168.0.234-238,192.168.0.245\n" |
| 1630 |
"#remoteip 192.168.1.234-238,192.168.1.245\n" |
| 1631 |
"localip 192.168.0.199\n" |
| 1632 |
"remoteip 192.168.0.200-250" |
| 1633 |
msgstr "" |
| 1634 |
"\n" |
| 1635 |
"# TAG: speed\n" |
| 1636 |
"#\n" |
| 1637 |
"# PPTP デーモンの通信速度を指定します。\n" |
| 1638 |
"#\n" |
| 1639 |
"speed 115200\n" |
| 1640 |
"\n" |
| 1641 |
"# TAG: option\n" |
| 1642 |
"#\n" |
| 1643 |
"# PPP オプションファイルの場所を指定します。\n" |
| 1644 |
"# PPP はデフォルトで '/etc/ppp/options' を使います\n" |
| 1645 |
"#\n" |
| 1646 |
"option /etc/ppp/pptpd-options\n" |
| 1647 |
"\n" |
| 1648 |
"# TAG: debug\n" |
| 1649 |
"#\n" |
| 1650 |
"# syslog に詳細なデバッグ情報を出力します\n" |
| 1651 |
"#\n" |
| 1652 |
"# debug\n" |
| 1653 |
"\n" |
| 1654 |
"# TAG: localip\n" |
| 1655 |
"# TAG: remoteip\n" |
| 1656 |
"#\n" |
| 1657 |
"# ローカルとリモートの IP アドレス範囲を指定します。\n" |
| 1658 |
"#\n" |
| 1659 |
"# コンマで区切ることで、単独の IP アドレスおよび\n" |
| 1660 |
"# IP アドレス範囲を指定できます。以下は利用例です。\n" |
| 1661 |
"#\n" |
| 1662 |
"# 192.168.0.234,192.168.0.245-249,192.168.0.254\n" |
| 1663 |
"#\n" |
| 1664 |
"# 以下の重要な制約事項に注意してください。\n" |
| 1665 |
"#\n" |
| 1666 |
"# 1. コンマ間およびアドレス内部で空白文字を使わないでください。\n" |
| 1667 |
"#\n" |
| 1668 |
"# 2. MAX_CONNECTIONS よりも多くの IP アドレス を指定した場合、\n" |
| 1669 |
"# 使われる IP アドレスはリストの先頭から MAX_CONNECTIONS\n" |
| 1670 |
"# 個までの IP アドレスです。それ以外は使われません。\n" |
| 1671 |
"#\n" |
| 1672 |
"# 3. アドレス範囲を略記しないでください! たとえば 234 から 238 の範囲を指定するために\n" |
| 1673 |
"# 234-8 と記述するのは間違いです。その代わり 234-238 と記述してください。\n" |
| 1674 |
"#\n" |
| 1675 |
"# 4. ローカル IP は 1 つだけでも構いません。この場合、すべてのローカル IP は\n" |
| 1676 |
"# 指定したものになります。しかしながら、同時接続中のクライアントには\n" |
| 1677 |
"# 必ず異なるリモート IP を割り振らなければいけません。\n" |
| 1678 |
"#\n" |
| 1679 |
"#localip 192.168.0.234-238,192.168.0.245\n" |
| 1680 |
"#remoteip 192.168.1.234-238,192.168.1.245\n" |
| 1681 |
"#localip 10.0.1.1\n" |
| 1682 |
"#remoteip 10.0.1.2-100\n" |
| 1683 |
"localip 192.168.0.199\n" |
| 1684 |
"remoteip 192.168.0.200-250" |
| 1685 |
|
| 1686 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1687 |
#, fuzzy |
| 1688 |
#| msgid "<primary>traffic</primary><secondary>limitation</secondary>" |
| 1689 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ppp/pptpd-options</filename></secondary>" |
| 1690 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイゲン\">制限</secondary>" |
| 1691 |
|
| 1692 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1693 |
msgid "The PPP configuration used by the PPTP server also requires a few changes in <filename>/etc/ppp/pptpd-options</filename>. The important parameters are the server name (<literal>pptp</literal>), the domain name (<literal>falcot.com</literal>), and the IP addresses for DNS and WINS servers." |
| 1694 |
msgstr "さらに <filename>/etc/ppp/pptpd-options</filename> を編集して、PPTP サーバの使う PPP 設定を変更します。重要なパラメータはサーバ名 (<literal>pptp</literal>)、ドメイン名 (<literal>falcot.com</literal>)、DNS と WINS サーバの IP アドレスです。" |
| 1695 |
|
| 1696 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1697 |
msgid "The <filename>/etc/ppp/pptpd-options</filename> file" |
| 1698 |
msgstr "<filename>/etc/ppp/pptpd-options</filename> ファイル" |
| 1699 |
|
| 1700 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1701 |
# Ref: http://www.tldp.org/LDP/nag2/x-087-2-ppp.authentication.html; |
| 1702 |
#, fuzzy |
| 1703 |
#| msgid "" |
| 1704 |
#| "\n" |
| 1705 |
#| "## turn pppd syslog debugging on\n" |
| 1706 |
#| "#debug\n" |
| 1707 |
#| "\n" |
| 1708 |
#| "## change 'servername' to whatever you specify as your server name in chap-secrets\n" |
| 1709 |
#| "name pptp\n" |
| 1710 |
#| "## change the domainname to your local domain\n" |
| 1711 |
#| "domain falcot.com\n" |
| 1712 |
#| "\n" |
| 1713 |
#| "## these are reasonable defaults for WinXXXX clients\n" |
| 1714 |
#| "## for the security related settings\n" |
| 1715 |
#| "# The Debian pppd package now supports both MSCHAP and MPPE, so enable them\n" |
| 1716 |
#| "# here. Please note that the kernel support for MPPE must also be present!\n" |
| 1717 |
#| "auth\n" |
| 1718 |
#| "require-chap\n" |
| 1719 |
#| "require-mschap\n" |
| 1720 |
#| "require-mschap-v2\n" |
| 1721 |
#| "require-mppe-128\n" |
| 1722 |
#| "\n" |
| 1723 |
#| "## Fill in your addresses\n" |
| 1724 |
#| "ms-dns 192.168.0.1\n" |
| 1725 |
#| "ms-wins 192.168.0.1\n" |
| 1726 |
#| "\n" |
| 1727 |
#| "## Fill in your netmask\n" |
| 1728 |
#| "netmask 255.255.255.0\n" |
| 1729 |
#| "\n" |
| 1730 |
#| "## some defaults\n" |
| 1731 |
#| "nodefaultroute\n" |
| 1732 |
#| "proxyarp\n" |
| 1733 |
#| "lock" |
| 1734 |
msgid "" |
| 1735 |
"\n" |
| 1736 |
"# Enable connection debugging facilities.\n" |
| 1737 |
"# (see your syslog configuration for where pppd sends to)\n" |
| 1738 |
"#debug\n" |
| 1739 |
"\n" |
| 1740 |
"# Name of the local system for authentication purposes\n" |
| 1741 |
"# (must match the second field in /etc/ppp/chap-secrets entries)\n" |
| 1742 |
"name pptpd\n" |
| 1743 |
"\n" |
| 1744 |
"# Optional: domain name to use for authentication\n" |
| 1745 |
"## change the domainname to your local domain\n" |
| 1746 |
"domain falcot.com\n" |
| 1747 |
"\n" |
| 1748 |
"# Authentication\n" |
| 1749 |
"## these are reasonable defaults for WinXXXX clients\n" |
| 1750 |
"## for the security related settings\n" |
| 1751 |
"auth\n" |
| 1752 |
"refuse-pap\n" |
| 1753 |
"refuse-chap\n" |
| 1754 |
"refuse-mschap\n" |
| 1755 |
"# Require the peer to authenticate itself using MS-CHAPv2 [Microsoft\n" |
| 1756 |
"# Challenge Handshake Authentication Protocol, Version 2] authentication.\n" |
| 1757 |
"require-mschap-v2\n" |
| 1758 |
"# Require MPPE 128-bit encryption\n" |
| 1759 |
"# (note that MPPE requires the use of MSCHAP-V2 during authentication)\n" |
| 1760 |
"require-mppe-128\n" |
| 1761 |
"\n" |
| 1762 |
"# Network and Routing\n" |
| 1763 |
"## Fill in your addresses\n" |
| 1764 |
"ms-dns 192.168.0.1\n" |
| 1765 |
"ms-wins 192.168.0.1\n" |
| 1766 |
"\n" |
| 1767 |
"## Fill in your netmask\n" |
| 1768 |
"netmask 255.255.255.0\n" |
| 1769 |
"\n" |
| 1770 |
"## some defaults\n" |
| 1771 |
"nodefaultroute\n" |
| 1772 |
"proxyarp\n" |
| 1773 |
"lock" |
| 1774 |
msgstr "" |
| 1775 |
"\n" |
| 1776 |
"## pppd の syslog デバッグを有効化します\n" |
| 1777 |
"#debug\n" |
| 1778 |
"\n" |
| 1779 |
"## 「サーバ名」を chap-secrets 内の自分のサーバ名として指定したものに変更します\n" |
| 1780 |
"name pptp\n" |
| 1781 |
"## ドメイン名をローカルドメインに変更します\n" |
| 1782 |
"domain falcot.com\n" |
| 1783 |
"\n" |
| 1784 |
"## 以下は WinXXXX クライアントに対して\n" |
| 1785 |
"## 適当とされるデフォルトセキュリティ関連設定です\n" |
| 1786 |
"# Debian の pppd パッケージは MSCHAP と MPPE の両方をサポートしています。そのため\n" |
| 1787 |
"# ここでは両方を有効化しています。カーネルの MPPE サポートが必須という点にも注意してください!\n" |
| 1788 |
"auth\n" |
| 1789 |
"require-chap\n" |
| 1790 |
"require-mschap\n" |
| 1791 |
"require-mschap-v2\n" |
| 1792 |
"require-mppe-128\n" |
| 1793 |
"\n" |
| 1794 |
"## サービスに対応するアドレスを指定してください\n" |
| 1795 |
"ms-dns 192.168.0.1\n" |
| 1796 |
"ms-wins 192.168.0.1\n" |
| 1797 |
"\n" |
| 1798 |
"## ネットマスクを指定してください\n" |
| 1799 |
"netmask 255.255.255.0\n" |
| 1800 |
"\n" |
| 1801 |
"## 一部のデフォルト設定\n" |
| 1802 |
"nodefaultroute\n" |
| 1803 |
"proxyarp\n" |
| 1804 |
"lock" |
| 1805 |
|
| 1806 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1807 |
#, fuzzy |
| 1808 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 1809 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ppp/chap-secrets</filename></secondary>" |
| 1810 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 1811 |
|
| 1812 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1813 |
msgid "The last step involves registering the <literal>vpn</literal> user (and the associated password) in the <filename>/etc/ppp/chap-secrets</filename> file. Contrary to other instances where an asterisk (<literal>*</literal>) would work, the server name must be filled explicitly here. Furthermore, Windows PPTP clients identify themselves under the <literal><replaceable>DOMAIN</replaceable>\\\\<replaceable>USER</replaceable></literal> form, instead of only providing a user name. This explains why the file also mentions the <literal>FALCOT\\\\vpn</literal> user. It is also possible to specify individual IP addresses for users; an asterisk in this field specifies that dynamic addressing should be used." |
| 1814 |
msgstr "最後に、<literal>vpn</literal> ユーザ (と対応するパスワード) を <filename>/etc/ppp/chap-secrets</filename> ファイルに登録します。サーバ名だけは、アスタリスク (<literal>*</literal>) を使える他のインスタンスと異なり、明示的に指定しなければいけません。さらに、Windows PPTP クライアントはユーザ名ではなく <literal><replaceable>DOMAIN</replaceable>\\\\<replaceable>USER</replaceable></literal> という形を認証を行います。このため、<filename>/etc/ppp/chap-secrets</filename> ファイルに <literal>FALCOT\\\\vpn</literal> ユーザが追加されています。ユーザに割り当てる IP アドレスを明記することも可能です。IP アドレスフィールドのアスタリスクは動的にアドレスを割り当てることを意味します。" |
| 1815 |
|
| 1816 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1817 |
msgid "The <filename>/etc/ppp/chap-secrets</filename> file" |
| 1818 |
msgstr "<filename>/etc/ppp/chap-secrets</filename> ファイル" |
| 1819 |
|
| 1820 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1821 |
# Ref: http://www.tldp.org/LDP/nag/node121.html; |
| 1822 |
# Ref: http://www.tldp.org/LDP/nag2/x-087-2-ppp.authentication.html; |
| 1823 |
msgid "" |
| 1824 |
"\n" |
| 1825 |
"# Secrets for authentication using CHAP\n" |
| 1826 |
"# client server secret IP addresses\n" |
| 1827 |
"vpn pptp f@Lc3au *\n" |
| 1828 |
"FALCOT\\\\vpn pptp f@Lc3au *" |
| 1829 |
msgstr "" |
| 1830 |
"\n" |
| 1831 |
"# CHAP 認証用のログイン情報\n" |
| 1832 |
"# クライアント サーバ 秘密情報 IP アドレス\n" |
| 1833 |
"vpn pptp f@Lc3au *\n" |
| 1834 |
"FALCOT\\\\vpn pptp f@Lc3au *" |
| 1835 |
|
| 1836 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1837 |
msgid "<emphasis>SECURITY</emphasis> PPTP vulnerabilities" |
| 1838 |
msgstr "<emphasis>SECURITY</emphasis> PPTP 脆弱性" |
| 1839 |
|
| 1840 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1841 |
#, fuzzy |
| 1842 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 1843 |
msgid "<primary>PPTP</primary><secondary>vulnerabilities</secondary>" |
| 1844 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 1845 |
|
| 1846 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1847 |
msgid "Microsoft's first PPTP implementation drew severe criticism because it had many security vulnerabilities; most have since then been fixed in more recent versions. The configuration documented in this section uses the latest version of the protocol. Be aware though that removing some options (such as <literal>require-mppe-128</literal> and <literal>require-mschap-v2</literal>) would make the service vulnerable again." |
| 1848 |
msgstr "Microsoft の最初の PPTP 実装は多くのセキュリティ脆弱性を残していたためにさまざまな非難を浴びました。しかし、最近のバージョンではその多くが修正されています。この節で説明されている設定は PPTP プロトコルの最新のバージョンを使っています。いくつかのオプション (<literal>require-mppe-128</literal> や <literal>require-mschap-v2</literal> など) を無効化すると、サービスに脆弱性が生まれるという点に注意してください。" |
| 1849 |
|
| 1850 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1851 |
msgid "Quality of Service" |
| 1852 |
msgstr "Quality of Service" |
| 1853 |
|
| 1854 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1855 |
msgid "Principle and Mechanism" |
| 1856 |
msgstr "原理とメカニズム" |
| 1857 |
|
| 1858 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1859 |
#, fuzzy |
| 1860 |
#| msgid "<primary>network</primary><secondary>gateway</secondary>" |
| 1861 |
msgid "<primary>network</primary><secondary>QoS</secondary>" |
| 1862 |
msgstr "<primary>ネットワーク</primary><secondary>ゲートウェイ</secondary>" |
| 1863 |
|
| 1864 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1865 |
msgid "<primary>QoS</primary>" |
| 1866 |
msgstr "<primary>QoS</primary>" |
| 1867 |
|
| 1868 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1869 |
#, fuzzy |
| 1870 |
#| msgid "<primary>quality of service</primary>" |
| 1871 |
msgid "<primary>Quality of Service</primary><see>QoS</see>" |
| 1872 |
msgstr "<primary sortas=\"サービスノヒンシツ\">サービスの品質</primary>" |
| 1873 |
|
| 1874 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1875 |
#, fuzzy |
| 1876 |
#| msgid "<primary>quality</primary><secondary>of service</secondary>" |
| 1877 |
msgid "<primary>quality</primary><secondary>of service</secondary><see>QoS</see>" |
| 1878 |
msgstr "<primary sortas=\"ヒンシツ\">品質</primary><secondary sortas=\"サービスノヒンシツ\">サービスの品質</secondary>" |
| 1879 |
|
| 1880 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1881 |
#, fuzzy |
| 1882 |
#| msgid "<primary>service</primary><secondary>quality</secondary>" |
| 1883 |
msgid "<primary>service</primary><secondary>quality</secondary><see>QoS</see>" |
| 1884 |
msgstr "<primary sortas=\"サービスノヒンシツ\">サービスの品質</primary>" |
| 1885 |
|
| 1886 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1887 |
msgid "<emphasis>Quality of Service</emphasis> (or <emphasis>QoS</emphasis> for short) refers to a set of techniques that guarantee or improve the quality of the service provided to applications. The most popular such technique involves classifying the network traffic into categories, and differentiating the handling of traffic according to which category it belongs to. The main application of this differentiated services concept is <emphasis>traffic shaping</emphasis>, which limits the data transmission rates for connections related to some services and/or hosts so as not to saturate the available bandwidth and starve important other services. Traffic shaping is a particularly good fit for TCP traffic, since this protocol automatically adapts to available bandwidth." |
| 1888 |
msgstr "<emphasis>Quality of Service (サービスの品質)</emphasis> (略して <emphasis>QoS</emphasis>) はアプリケーションに提供されるサービスの品質を向上させる技術群を指します。最もよく使われる技術はネットワークトラフィックをカテゴリ分けして、トラフィックの所属するカテゴリごとにその取り扱いに違いを付ける技術です。サービスを差別化するという概念の主な用途が<emphasis>トラフィックシェーピング</emphasis>です。これは一部のサービスおよびホストに関連する接続のデータの転送率を制限します。これを使うことで、利用できる帯域幅が飽和することを避け、重要な他のサービスに支障が出ないようにします。トラフィックシェーピングは TCP トラフィックに対して特に有効です。なぜなら、TCP は利用できる帯域幅に自動的に適応するからです。" |
| 1889 |
|
| 1890 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1891 |
#, fuzzy |
| 1892 |
#| msgid "<emphasis>CULTURE</emphasis> SSL and TLS" |
| 1893 |
msgid "<emphasis>CULTURE</emphasis> Net neutrality and QoS" |
| 1894 |
msgstr "<emphasis>CULTURE</emphasis> SSL と TLS" |
| 1895 |
|
| 1896 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1897 |
#, fuzzy |
| 1898 |
#| msgid "<primary>network</primary><secondary>gateway</secondary>" |
| 1899 |
msgid "<primary>network</primary><secondary>neutrality</secondary>" |
| 1900 |
msgstr "<primary>ネットワーク</primary><secondary>ゲートウェイ</secondary>" |
| 1901 |
|
| 1902 |
msgid "Network neutrality is achieved when Internet service providers treat all Internet communications equally, that is, without any access limitation based on content, user, website, destination address, etc." |
| 1903 |
msgstr "" |
| 1904 |
|
| 1905 |
msgid "Quality of service can be implemented in a net neutral Internet, but only if Internet service providers can't charge a special fee for a higher-quality service." |
| 1906 |
msgstr "" |
| 1907 |
|
| 1908 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1909 |
msgid "It is also possible to alter the priorities on traffic, which allows prioritizing packets related to interactive services (such as <command>ssh</command> and <command>telnet</command>) or to services that only deal with small blocks of data." |
| 1910 |
msgstr "トラフィックの優先度を変更し、対話型サービス (<command>ssh</command> や <command>telnet</command> など) や小さなブロックのデータだけを取り扱うサービスに関連するパケットに高い優先度を付けることも可能です。" |
| 1911 |
|
| 1912 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1913 |
msgid "The Debian kernels include the features required for QoS along with their associated modules. These modules are many, and each of them provides a different service, most notably by way of special schedulers for the queues of IP packets; the wide range of available scheduler behaviors spans the whole range of possible requirements." |
| 1914 |
msgstr "Debian カーネルには、QoS 関連モジュールと一緒に QoS に必要な機能が含まれています。多くのモジュールが存在し、各モジュールが異なるサービスを提供します。中でも注目すべきは IP パケットの待ち行列用の特別なスケジューラです。このスケジューラはさまざまな用途に利用できるため、考え得るさまざまな要求に対応できます。" |
| 1915 |
|
| 1916 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1917 |
msgid "<emphasis>CULTURE</emphasis> LARTC — <emphasis>Linux Advanced Routing & Traffic Control</emphasis>" |
| 1918 |
msgstr "<emphasis>CULTURE</emphasis> LARTC (<emphasis>Linux Advanced Routing & Traffic Control</emphasis>)" |
| 1919 |
|
| 1920 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1921 |
#, fuzzy |
| 1922 |
#| msgid "<primary>network</primary><secondary>virtual private</secondary>" |
| 1923 |
msgid "<primary>network</primary><secondary>advanced routing</secondary><seealso>routing</seealso>" |
| 1924 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"カソウプライベート\">仮想プライベート</secondary>" |
| 1925 |
|
| 1926 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1927 |
msgid "<primary>routing</primary><secondary>advanced</secondary>" |
| 1928 |
msgstr "<primary>ルーティング</primary><secondary sortas=\"ジョウキュウルーティング\">上級ルーティング</secondary>" |
| 1929 |
|
| 1930 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1931 |
msgid "<primary>traffic</primary><secondary>control</secondary>" |
| 1932 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイギョ\">制御</secondary>" |
| 1933 |
|
| 1934 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1935 |
msgid "<primary>control of traffic</primary>" |
| 1936 |
msgstr "<primary sortas=\"セイギョ\">制御</primary><secondary>トラフィック</secondary>" |
| 1937 |
|
| 1938 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1939 |
#, fuzzy |
| 1940 |
#| msgid "The <emphasis>Linux Advanced Routing & Traffic Control</emphasis> HOWTO is the reference document covering everything there is to know about network quality of service. <ulink type=\"block\" url=\"http://www.lartc.org/howto/\" />" |
| 1941 |
msgid "The <emphasis>Linux Advanced Routing & Traffic Control</emphasis> HOWTO is the reference document covering everything there is to know about network quality of service. <ulink type=\"block\" url=\"https://www.lartc.org/howto/\" />" |
| 1942 |
msgstr "<emphasis>Linux Advanced Routing & Traffic Control</emphasis> HOWTO はネットワークのサービス品質に関して知っておくべきすべての内容をカバーする基礎的な文書です。<ulink type=\"block\" url=\"http://www.lartc.org/howto/\" />" |
| 1943 |
|
| 1944 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1945 |
msgid "Configuring and Implementing" |
| 1946 |
msgstr "設定と実践" |
| 1947 |
|
| 1948 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1949 |
msgid "<primary><emphasis>iproute</emphasis></primary>" |
| 1950 |
msgstr "<primary><emphasis>iproute</emphasis></primary>" |
| 1951 |
|
| 1952 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1953 |
msgid "<primary><command>tc</command></primary>" |
| 1954 |
msgstr "<primary><command>tc</command></primary>" |
| 1955 |
|
| 1956 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1957 |
msgid "QoS parameters are set through the <command>tc</command> command (provided by the <emphasis role=\"pkg\">iproute</emphasis> package). Since its interface is quite complex, using higher-level tools is recommended." |
| 1958 |
msgstr "QoS パラメータは <command>tc</command> コマンド (<emphasis role=\"pkg\">iproute</emphasis> パッケージに含まれます) を使って設定します。<command>tc</command> コマンドはインターフェースがかなり複雑なので、高レベルツールを使うことを推奨します。" |
| 1959 |
|
| 1960 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1961 |
msgid "Reducing Latencies: <command>wondershaper</command>" |
| 1962 |
msgstr "待ち時間の低減、<command>wondershaper</command>" |
| 1963 |
|
| 1964 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1965 |
msgid "<primary><command>wondershaper</command></primary>" |
| 1966 |
msgstr "<primary><command>wondershaper</command></primary>" |
| 1967 |
|
| 1968 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1969 |
msgid "<primary>limitation of traffic</primary>" |
| 1970 |
msgstr "<primary sortas=\"セイゲン\">制限</primary><secondary>トラフィック</secondary>" |
| 1971 |
|
| 1972 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1973 |
msgid "<primary>traffic</primary><secondary>limitation</secondary>" |
| 1974 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイゲン\">制限</secondary>" |
| 1975 |
|
| 1976 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1977 |
msgid "The main purpose of <command>wondershaper</command> (in the similarly-named package) is to minimize latencies independent of network load. This is achieved by limiting total traffic to a value that falls just short of the link saturation value." |
| 1978 |
msgstr "<command>wondershaper</command> (同名のパッケージに含まれます) の主目的はネットワーク負荷とは無関係に待ち時間を最小化することです。全トラフィックをある値に制限することにより、これは実現されます。この値には帯域を飽和させるよりほんの少しだけ小さな値を設定します。" |
| 1979 |
|
| 1980 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1981 |
#, fuzzy |
| 1982 |
#| msgid "Once a network interface is configured, setting up this traffic limitation is achieved by running <command>wondershaper <replaceable>interface</replaceable> <replaceable>download_rate</replaceable> <replaceable>upload_rate</replaceable></command>. The interface can be <literal>eth0</literal> or <literal>ppp0</literal> for example, and both rates are expressed in kilobits per second. The <command>wondershaper remove <replaceable>interface</replaceable></command> command disables traffic control on the specified interface." |
| 1983 |
msgid "Once a network interface is configured, setting up this traffic limitation is achieved by running <command>wondershaper <replaceable>interface</replaceable> <replaceable>download_rate</replaceable> <replaceable>upload_rate</replaceable></command>. The interface can be <literal>enp1s0</literal>, <literal>eth0</literal> or <literal>ppp0</literal> for example, and both rates are expressed in kilobits per second. The <command>wondershaper remove <replaceable>interface</replaceable></command> command disables traffic control on the specified interface." |
| 1984 |
msgstr "ネットワークインターフェースを設定した後、<command>wondershaper <replaceable>interface</replaceable> <replaceable>download_rate</replaceable> <replaceable>upload_rate</replaceable></command> を実行することでトラフィックが制限されます。ここで <replaceable>interface</replaceable> はたとえば <literal>eth0</literal> または <literal>ppp0</literal> などのインターフェース名で、<replaceable>download_rate</replaceable> および <replaceable>upload_rate</replaceable> はキロビット毎秒単位の値です。特定のインターフェースで実施されているトラフィック制限を無効化するには <command>wondershaper remove <replaceable>interface</replaceable></command> コマンドを使います。" |
| 1985 |
|
| 1986 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1987 |
#, fuzzy |
| 1988 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 1989 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/network/interfaces</filename></secondary>" |
| 1990 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 1991 |
|
| 1992 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1993 |
#, fuzzy |
| 1994 |
#| msgid "For an Ethernet connection, this script is best called right after the interface is configured. This is done by adding <literal>up</literal> and <literal>down</literal> directives to the <filename>/etc/network/interfaces</filename> file allowing declared commands to be run, respectively, after the interface is configured and before it is deconfigured. For example:" |
| 1995 |
msgid "For an Ethernet connection, historically this script would be called right after the interface is configured. This is done by adding <literal>up</literal> and <literal>down</literal> directives to the <filename>/etc/network/interfaces</filename> file allowing declared commands to be run, respectively, after the interface is configured and before it is deconfigured. Or in the PPP case, creating a script that calls <command>wondershaper</command> in <filename>/etc/ppp/ip-up.d/</filename> will enable traffic control as soon as the connection is up. Below is an example using this first method:" |
| 1996 |
msgstr "イーサネット接続の場合、<command>wondershaper</command> をインターフェースが設定された直後に呼び出すのが最良です。これを行うには、<filename>/etc/network/interfaces</filename> ファイルに <literal>up</literal> と <literal>down</literal> 指示文を追加して、それぞれインターフェースが開始された後と停止される前に実行するコマンドを宣言します。以下にその例を示します。" |
| 1997 |
|
| 1998 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1999 |
msgid "Changes in the <filename>/etc/network/interfaces</filename> file" |
| 2000 |
msgstr "<filename>/etc/network/interfaces</filename> ファイルの修正" |
| 2001 |
|
| 2002 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2003 |
msgid "" |
| 2004 |
"\n" |
| 2005 |
"iface eth0 inet dhcp\n" |
| 2006 |
" up /sbin/wondershaper eth0 500 100\n" |
| 2007 |
" down /sbin/wondershaper remove eth0" |
| 2008 |
msgstr "" |
| 2009 |
"\n" |
| 2010 |
"iface eth0 inet dhcp\n" |
| 2011 |
" up /sbin/wondershaper eth0 500 100\n" |
| 2012 |
" down /sbin/wondershaper remove eth0" |
| 2013 |
|
| 2014 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2015 |
msgid "<emphasis>GOING FURTHER</emphasis> Optimal configuration" |
| 2016 |
msgstr "<emphasis>GOING FURTHER</emphasis> 最適な設定" |
| 2017 |
|
| 2018 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2019 |
msgid "The <filename>/usr/share/doc/wondershaper/README.Debian.gz</filename> file describes, in some detail, the configuration method recommended by the package maintainer. In particular, it advises measuring the download and upload speeds so as to best evaluate real limits." |
| 2020 |
msgstr "<filename>/usr/share/doc/wondershaper/README.Debian.gz</filename> ファイルでは、パッケージメンテナの推奨する設定方法が少し詳しく説明されています。特に、ダウンロードとアップロード速度を計測することを勧めています。実際の速度を計測することで、制限を適切に見積もることが可能です。" |
| 2021 |
|
| 2022 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2023 |
msgid "Standard Configuration" |
| 2024 |
msgstr "標準的な設定" |
| 2025 |
|
| 2026 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2027 |
#, fuzzy |
| 2028 |
#| msgid "<primary>DHCP</primary>" |
| 2029 |
msgid "<primary>DSCP</primary>" |
| 2030 |
msgstr "<primary>DHCP</primary>" |
| 2031 |
|
| 2032 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2033 |
#, fuzzy |
| 2034 |
#| msgid "<primary>reverse zone</primary>" |
| 2035 |
msgid "<primary>Differentiated Services Code Point</primary><see>DSCP</see>" |
| 2036 |
msgstr "<primary sortas=\"ギャクビキゾーン\">逆引きゾーン</primary>" |
| 2037 |
|
| 2038 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2039 |
#, fuzzy |
| 2040 |
#| msgid "Barring a specific QoS configuration, the Linux kernel uses the <literal>pfifo_fast</literal> queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the ToS field (<emphasis>Type of Service</emphasis>) of this packet; modifying this field is enough to take advantage of the scheduling features. There are five possible values:" |
| 2041 |
msgid "Barring a specific QoS configuration, the Linux kernel uses the <literal>pfifo_fast</literal> queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the DSCP field (<emphasis>Differentiated Services Code Point</emphasis>) of this packet; modifying this 6-bit field is enough to take advantage of the scheduling features. Refer to <ulink url=\"https://en.wikipedia.org/wiki/Differentiated_services#Class_Selector\" /> for more information." |
| 2042 |
msgstr "明示的に QoS 設定を行わない場合、Linux カーネルは <literal>pfifo_fast</literal> キュースケジューラを使います。これは興味深い機能を提供します。各 IP パケットの優先度はパケットの ToS フィールド (<emphasis>Type of Service</emphasis>) によって決まります。スケジューリング機能を活用するには、このフィールドを修正するだけで十分です。ToS フィールドの取り得る値は以下の 5 種類です。" |
| 2043 |
|
| 2044 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2045 |
#, fuzzy |
| 2046 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2047 |
msgid "<primary>IP</primary><secondary>netfilter</secondary>" |
| 2048 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2049 |
|
| 2050 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2051 |
#, fuzzy |
| 2052 |
#| msgid "The ToS field can be set by applications that generate IP packets, or modified on the fly by <emphasis>netfilter</emphasis>. The following rules are sufficient to increase responsiveness for a server's SSH service:" |
| 2053 |
msgid "The DSCP field can be set by applications that generate IP packets, or modified on the fly by <emphasis>netfilter</emphasis>. The following rules are sufficient to increase responsiveness for a server's SSH service, note that the DSCP field must be set in hexadecimal:" |
| 2054 |
msgstr "ToS フィールドは IP パケットを生成するアプリケーションによって設定されるか、<emphasis>netfilter</emphasis> によってその場で修正されます。以下のルールを使うだけで、サーバの SSH サービスに対する応答性を増加させることが可能です。" |
| 2055 |
|
| 2056 |
msgid "" |
| 2057 |
"\n" |
| 2058 |
"nft add table ip mangle\n" |
| 2059 |
"nft add rule ip mangle PREROUTING tcp sport 22 counter ip dscp set 0x04\n" |
| 2060 |
"nft add rule ip mangle PREROUTING tcp dport 22 counter ip dscp set 0x04" |
| 2061 |
msgstr "" |
| 2062 |
|
| 2063 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2064 |
msgid "Dynamic Routing" |
| 2065 |
msgstr "動的ルーティング" |
| 2066 |
|
| 2067 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2068 |
#, fuzzy |
| 2069 |
#| msgid "<primary>routing</primary><secondary>dynamic</secondary>" |
| 2070 |
msgid "<primary>routing</primary><secondary>dynamic</secondary><seealso><command>frr</command></seealso>" |
| 2071 |
msgstr "<primary>ルーティング</primary><secondary sortas=\"ドウテキ\">動的</secondary>" |
| 2072 |
|
| 2073 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2074 |
#, fuzzy |
| 2075 |
#| msgid "<primary><command>ripd</command></primary>" |
| 2076 |
msgid "<primary><command>frr</command></primary>" |
| 2077 |
msgstr "<primary><command>ripd</command></primary>" |
| 2078 |
|
| 2079 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2080 |
#, fuzzy |
| 2081 |
#| msgid "<primary><command>quagga</command></primary>" |
| 2082 |
msgid "<primary><command>quagga</command></primary><see><command>frr</command></see>" |
| 2083 |
msgstr "<primary><command>quagga</command></primary>" |
| 2084 |
|
| 2085 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2086 |
#, fuzzy |
| 2087 |
#| msgid "<primary><command>zebra</command></primary>" |
| 2088 |
msgid "<primary><command>zebra</command></primary><see><command>frr</command></see>" |
| 2089 |
msgstr "<primary><command>zebra</command></primary>" |
| 2090 |
|
| 2091 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2092 |
#, fuzzy |
| 2093 |
#| msgid "The reference tool for dynamic routing is currently <command>quagga</command>, from the similarly-named package; it used to be <command>zebra</command> until development of the latter stopped. However, <command>quagga</command> kept the names of the programs for compatibility reasons which explains the <command>zebra</command> commands below." |
| 2094 |
msgid "The reference tool for dynamic routing is currently <command>frr</command> from the similarly-named package; it used to be <command>quagga</command>, and before that <command>zebra</command> until development of these stopped. However, <command>frr</command> kept the names of the programs for compatibility reasons which explains the <command>zebra</command> commands below." |
| 2095 |
msgstr "現在の動的ルーティングの標準ツールは <command>quagga</command> で、<command>quagga</command> は同名のパッケージに含まれます。以前の標準ツールは <command>zebra</command> でしたが、<command>zebra</command> は開発中止となったため <command>quagga</command> に取って代わられました。しかしながら、<command>quagga</command> は互換性の理由からプログラムの名前に <command>zebra</command> を使っています。" |
| 2096 |
|
| 2097 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2098 |
msgid "<emphasis>BACK TO BASICS</emphasis> Dynamic routing" |
| 2099 |
msgstr "<emphasis>BACK TO BASICS</emphasis> 動的ルーティング" |
| 2100 |
|
| 2101 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2102 |
msgid "Dynamic routing allows routers to adjust, in real time, the paths used for transmitting IP packets. Each protocol involves its own method of defining routes (shortest path, use routes advertised by peers, and so on)." |
| 2103 |
msgstr "動的ルーティングを使うことで、ルータは IP パケットの送信経路をリアルタイムで調整することが可能になります。プロトコルごとに経路を定義する方法 (最短経路、各装置が希望する経路など) は違います。" |
| 2104 |
|
| 2105 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2106 |
#, fuzzy |
| 2107 |
#| msgid "<primary>traffic</primary><secondary>limitation</secondary>" |
| 2108 |
msgid "<primary><command>ip</command></primary><secondary><literal>route</literal></secondary>" |
| 2109 |
msgstr "<primary>トラフィック</primary><secondary sortas=\"セイゲン\">制限</secondary>" |
| 2110 |
|
| 2111 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2112 |
msgid "<primary><command>route</command></primary>" |
| 2113 |
msgstr "<primary><command>route</command></primary>" |
| 2114 |
|
| 2115 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2116 |
#, fuzzy |
| 2117 |
#| msgid "In the Linux kernel, a route links a network device to a set of machines that can be reached through this device. The <command>route</command> command defines new routes and displays existing ones." |
| 2118 |
msgid "In the Linux kernel, a route links a network device to a set of machines that can be reached through this device. The <command>ip</command> command, when <literal>route</literal> is used as the first argument, defines new routes and displays existing ones. The <command>route</command> command was used for that purpose, but it is deprecated in favor of <command>ip</command>." |
| 2119 |
msgstr "Linux カーネルでは、ネットワークデバイスとそのデバイスを通過して到達できるマシン群を関連付けることで経路を定義します。<command>route</command> コマンドは新しい経路を定義したり、既存の経路を表示するために使われます。" |
| 2120 |
|
| 2121 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2122 |
#, fuzzy |
| 2123 |
#| msgid "Quagga is a set of daemons cooperating to define the routing tables to be used by the Linux kernel; each routing protocol (most notably BGP, OSPF and RIP) provides its own daemon. The <command>zebra</command> daemon collects information from other daemons and handles static routing tables accordingly. The other daemons are known as <command>bgpd</command>, <command>ospfd</command>, <command>ospf6d</command>, <command>ripd</command>, <command>ripngd</command>, <command>isisd</command>, and <command>babeld</command>." |
| 2124 |
msgid "FRR (FRRouting) is a set of daemons cooperating to define the routing tables to be used by the Linux kernel; each routing protocol (most notably BGP, OSPF and RIP) provides its own daemon(s). The <literal>zebra</literal> and <literal>staticd</literal> daemons, which are always started, collect information from other daemons and handle static routing tables accordingly. The other daemons are known as <command>bgpd</command>, <command>ospfd</command>, <command>ospf6d</command>, <command>ripd</command>, <command>ripngd</command>, <command>isisd</command>, etc." |
| 2125 |
msgstr "Quagga は複数のデーモン群で、これらが協力して Linux カーネルの使うルーティングテーブルを定義します。各ルーティングプロトコル (中でも注目すべきは BGP、OSPF、RIP) に対して専用のデーモンがあります。<command>zebra</command> デーモンは他のデーモンから情報を収集し、その情報に基づき静的ルーティングテーブルを操作します。ここで他のデーモンとは、<command>bgpd</command>、<command>ospfd</command>、<command>ospf6d</command>、<command>ripd</command>、<command>ripngd</command>、<command>isisd</command>、<command>babeld</command> として知られています。" |
| 2126 |
|
| 2127 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2128 |
msgid "<primary>OSPF</primary>" |
| 2129 |
msgstr "<primary>OSPF</primary>" |
| 2130 |
|
| 2131 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2132 |
msgid "<primary>BGP</primary>" |
| 2133 |
msgstr "<primary>BGP</primary>" |
| 2134 |
|
| 2135 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2136 |
msgid "<primary>RIP</primary>" |
| 2137 |
msgstr "<primary>RIP</primary>" |
| 2138 |
|
| 2139 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2140 |
msgid "<primary>IS-IS</primary>" |
| 2141 |
msgstr "<primary>IS-IS</primary>" |
| 2142 |
|
| 2143 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2144 |
msgid "<primary><command>bgpd</command></primary>" |
| 2145 |
msgstr "<primary><command>bgpd</command></primary>" |
| 2146 |
|
| 2147 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2148 |
msgid "<primary><command>ospfd</command></primary>" |
| 2149 |
msgstr "<primary><command>ospfd</command></primary>" |
| 2150 |
|
| 2151 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2152 |
msgid "<primary><command>ospf6d</command></primary>" |
| 2153 |
msgstr "<primary><command>ospf6d</command></primary>" |
| 2154 |
|
| 2155 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2156 |
msgid "<primary><command>ripd</command></primary>" |
| 2157 |
msgstr "<primary><command>ripd</command></primary>" |
| 2158 |
|
| 2159 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2160 |
msgid "<primary><command>ripngd</command></primary>" |
| 2161 |
msgstr "<primary><command>ripngd</command></primary>" |
| 2162 |
|
| 2163 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2164 |
msgid "<primary><command>isisd</command></primary>" |
| 2165 |
msgstr "<primary><command>isisd</command></primary>" |
| 2166 |
|
| 2167 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2168 |
#, fuzzy |
| 2169 |
#| msgid "<primary>server</primary><secondary>name</secondary>" |
| 2170 |
msgid "<primary>service</primary><secondary><filename>frr.service</filename></secondary>" |
| 2171 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 2172 |
|
| 2173 |
msgid "Daemons are enabled by creating the <filename>/etc/frr/<replaceable>daemon</replaceable>.conf</filename> config file, <replaceable>daemon</replaceable> being the name of the daemon to use, and editing the <filename>/etc/frr/daemon</filename> configuration file. The daemon config file must belong to the <literal>frr</literal> user and group with permissions of <literal>0640</literal> in order for the <filename>/etc/init.d/frr</filename> script or the <filename>frr.service</filename> systemd service file to invoke the daemon. The package <emphasis role=\"pkg\">frr</emphasis> provides configuration examples under <filename>/usr/share/doc/frr/examples/</filename>." |
| 2174 |
msgstr "" |
| 2175 |
|
| 2176 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2177 |
#, fuzzy |
| 2178 |
#| msgid "The configuration of each of these daemons requires knowledge of the routing protocol in question. These protocols cannot be described in detail here, but the <emphasis role=\"pkg\">quagga-doc</emphasis> provides ample explanation in the form of an <command>info</command> file. The same contents may be more easily browsed as HTML on the Quagga website: <ulink type=\"block\" url=\"http://www.nongnu.org/quagga/docs/docs-info.html\" />" |
| 2179 |
msgid "The configuration of each of these daemons requires knowledge of the routing protocol in question. These protocols cannot be described in detail here, but <emphasis role=\"pkg\">frr-doc</emphasis> provides ample explanation in the form of both <command>info</command> and HTML files. The same contents may be more browsed on the project's website: <ulink type=\"block\" url=\"http://docs.frrouting.org/en/latest/\" />" |
| 2180 |
msgstr "デーモンを設定するには、対象のルーティングプロトコルに関する知識が必要です。ここではそれぞれのプロトコルの詳細を説明できませんが、<emphasis role=\"pkg\">quagga-doc</emphasis> パッケージに含まれる <command>info</command> ファイルで十分な説明が行われています。また、同じ内容を Quagga のウェブサイト上で HTML として閲覧するほうが簡単かもしれません。<ulink type=\"block\" url=\"http://www.nongnu.org/quagga/docs/docs-info.html\" />" |
| 2181 |
|
| 2182 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2183 |
#, fuzzy |
| 2184 |
#| msgid "In addition, the syntax is very close to a standard router's configuration interface, and network administrators will adapt quickly to <command>quagga</command>." |
| 2185 |
msgid "In addition, the syntax is very close to a standard router's configuration interface, and network administrators will adapt quickly to <command>frr</command>." |
| 2186 |
msgstr "加えて、設定構文は標準的なルータの設定インターフェースととても似ているため、ネットワーク管理者は <command>quagga</command> に素早く順応するでしょう。" |
| 2187 |
|
| 2188 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2189 |
msgid "<emphasis>IN PRACTICE</emphasis> OSPF, BGP or RIP?" |
| 2190 |
msgstr "<emphasis>IN PRACTICE</emphasis> OSPF、BGP、RIP?" |
| 2191 |
|
| 2192 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2193 |
#, fuzzy |
| 2194 |
#| msgid "<primary>protocol</primary><secondary>ESP</secondary>" |
| 2195 |
msgid "<primary>protocol</primary><secondary>BGP</secondary>" |
| 2196 |
msgstr "<primary>プロトコル</primary><secondary>ESP</secondary>" |
| 2197 |
|
| 2198 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2199 |
#, fuzzy |
| 2200 |
#| msgid "<primary>protocol</primary><secondary>ESP</secondary>" |
| 2201 |
msgid "<primary>protocol</primary><secondary>RIP</secondary>" |
| 2202 |
msgstr "<primary>プロトコル</primary><secondary>ESP</secondary>" |
| 2203 |
|
| 2204 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2205 |
#, fuzzy |
| 2206 |
#| msgid "OSPF is generally the best protocol to use for dynamic routing on private networks, but BGP is more common for Internet-wide routing. RIP is rather ancient, and hardly used anymore." |
| 2207 |
msgid "<acronym>OSPF</acronym> (Open Shortest Path First) is generally the best protocol to use for dynamic routing on private networks, but <acronym>BGP</acronym> (Border Gateway Protocol) is more common for Internet-wide routing. <acronym>RIP</acronym> (Routing Information Protocol) is rather ancient, and hardly used anymore." |
| 2208 |
msgstr "一般に、OSPF はプライベートネットワークの動的ルーティングに使われる最良のプロトコルです。BGP はインターネット全体のルーティングに使われることが多いプロトコルです。RIP は比較的古典的で、ほとんど使われません。" |
| 2209 |
|
| 2210 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2211 |
#, fuzzy |
| 2212 |
#| msgid "<primary>port</primary><secondary>TCP</secondary>" |
| 2213 |
msgid "<primary>IP</primary><secondary>v4</secondary><seealso>IPv4</seealso>" |
| 2214 |
msgstr "<primary>ポート</primary><secondary>TCP</secondary>" |
| 2215 |
|
| 2216 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2217 |
#, fuzzy |
| 2218 |
#| msgid "<primary>firewall</primary><secondary>IPv6</secondary>" |
| 2219 |
msgid "<primary>IP</primary><secondary>v6</secondary><seealso>IPv6</seealso>" |
| 2220 |
msgstr "<primary>ファイアウォール</primary><secondary>IPv6</secondary>" |
| 2221 |
|
| 2222 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2223 |
#, fuzzy |
| 2224 |
#| msgid "<primary>IPv6</primary>" |
| 2225 |
msgid "<primary>IPv4</primary>" |
| 2226 |
msgstr "<primary>IPv6</primary>" |
| 2227 |
|
| 2228 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2229 |
msgid "<primary>IPv6</primary>" |
| 2230 |
msgstr "<primary>IPv6</primary>" |
| 2231 |
|
| 2232 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2233 |
msgid "<primary><emphasis role=\"pkg\">iputils-ping</emphasis></primary>" |
| 2234 |
msgstr "<primary><emphasis role=\"pkg\">iputils-ping</emphasis></primary>" |
| 2235 |
|
| 2236 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2237 |
msgid "<primary><emphasis role=\"pkg\">iputils-tracepath</emphasis></primary>" |
| 2238 |
msgstr "<primary><emphasis role=\"pkg\">iputils-tracepath</emphasis></primary>" |
| 2239 |
|
| 2240 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2241 |
#, fuzzy |
| 2242 |
#| msgid "IPv6, successor to IPv4, is a new version of the IP protocol designed to fix its flaws, most notably the scarcity of available IP addresses. This protocol handles the network layer; its purpose is to provide a way to address machines, to convey data to their intended destination, and to handle data fragmentation if needed (in other words, to split packets into chunks with a size that depends on the network links to be used on the path and to reassemble the chunks in their proper order on arrival)." |
| 2243 |
msgid "IPv6, successor to IPv4, is a newer version of the IP protocol designed to fix its flaws, most notably the scarcity of available IP addresses. This protocol handles the network layer; its purpose is to provide a way to address machines, to convey data to their intended destination, and to handle data fragmentation if needed (in other words, to split packets into chunks with a size that depends on the network links to be used on the path and to reassemble the chunks in their proper order on arrival)." |
| 2244 |
msgstr "IPv6 は IPv4 の後継で、IP プロトコルの新しいバージョンで、IPv4 の欠点 (中でも注目すべきは利用できる IP アドレスの枯渇) を解決するために設計されました。IPv6 はネットワーク層で動きます。そして IPv6 の目的はマシンをアドレス指定する方法を提供すること、目標の宛先にデータを伝達すること、必要ならばデータの断片化を取り扱うことです (言い換えれば、経路で使われるネットワークリンクに従ってパケットをあるサイズのチャンクに分割し、到着した時に適切な順番にチャンクを再構築することです)。" |
| 2245 |
|
| 2246 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2247 |
msgid "Debian kernels include IPv6 handling in the core kernel (with the exception of some architectures that have it compiled as a module named <literal>ipv6</literal>). Basic tools such as <command>ping</command> and <command>traceroute</command> have their IPv6 equivalents in <command>ping6</command> and <command>traceroute6</command>, available respectively in the <emphasis role=\"pkg\">iputils-ping</emphasis> and <emphasis role=\"pkg\">iputils-tracepath</emphasis> packages." |
| 2248 |
msgstr "Debian カーネルは IPv6 をコアカーネルでサポートします (<literal>ipv6</literal> という名前でコンパイルされたモジュールを使って IPv6 をサポートする一部のアーキテクチャを除きます)。<command>ping</command>、<command>traceroute</command> などの基本ツールには IPv6 用の <command>ping6</command>、<command>traceroute6</command> などの代替品があり、これらはそれぞれ <emphasis role=\"pkg\">iputils-ping</emphasis>、<emphasis role=\"pkg\">iputils-tracepath</emphasis> パッケージに含まれます。" |
| 2249 |
|
| 2250 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2251 |
msgid "The IPv6 network is configured similarly to IPv4, in <filename>/etc/network/interfaces</filename>. But if you want that network to be globally available, you must ensure that you have an IPv6-capable router relaying traffic to the global IPv6 network." |
| 2252 |
msgstr "IPv6 ネットワークは IPv4 と同様に <filename>/etc/network/interfaces</filename> で設定します。しかし、ネットワークをグローバルに利用できるようにしたい場合、グローバル IPv6 ネットワークへのトラフィックを中継するための IPv6 を取り扱うことができるルータを持っていなければいけません。" |
| 2253 |
|
| 2254 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2255 |
msgid "Example of IPv6 configuration" |
| 2256 |
msgstr "IPv6 設定の例" |
| 2257 |
|
| 2258 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2259 |
# Ref: $ man 5 interfaces; |
| 2260 |
# Ref: https://tools.ietf.org/html/rfc3849; |
| 2261 |
# Ref: http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/; |
| 2262 |
# Ref: http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/proc-sys-net-ipv6..html; |
| 2263 |
# Ref: http://www.gogo6.com/forum/topics/how-do-i-assign-several-ipv6; |
| 2264 |
# Ref: http://www.ruwenzori.net/ipv6/Jims_LAN_IPv6_global_connectivity_howto.html; |
| 2265 |
# Ref: https://wiki.debian.org/NetworkConfiguration; |
| 2266 |
# Tag: PTAL; |
| 2267 |
#, fuzzy |
| 2268 |
#| msgid "" |
| 2269 |
#| "\n" |
| 2270 |
#| "iface eth0 inet6 static\n" |
| 2271 |
#| " address 2001:db8:1234:5::1:1\n" |
| 2272 |
#| " netmask 64\n" |
| 2273 |
#| " # Disabling auto-configuration\n" |
| 2274 |
#| " # autoconf 0\n" |
| 2275 |
#| " # The router is auto-configured and has no fixed address\n" |
| 2276 |
#| " # (accept_ra 1). If it had:\n" |
| 2277 |
#| " # gateway 2001:db8:1234:5::1" |
| 2278 |
msgid "" |
| 2279 |
"\n" |
| 2280 |
"iface enp7s0 inet6 static\n" |
| 2281 |
" address 2001:db8:1234:5::1:1/64\n" |
| 2282 |
" # Disabling auto-configuration\n" |
| 2283 |
" # autoconf 0\n" |
| 2284 |
" # The router is auto-configured and has no fixed address\n" |
| 2285 |
" # (accept_ra 1). If it had:\n" |
| 2286 |
" # gateway 2001:db8:1234:5::1" |
| 2287 |
msgstr "" |
| 2288 |
"\n" |
| 2289 |
"iface eth0 inet6 static\n" |
| 2290 |
" address 2001:db8:1234:5::1:1\n" |
| 2291 |
" netmask 64\n" |
| 2292 |
" # 自動設定の無効化\n" |
| 2293 |
" # autoconf 0\n" |
| 2294 |
" # ルータが自動設定されており、ルータが固定アドレスを持っていない場合は\n" |
| 2295 |
" # accept_ra 1 を有効化してください。それ以外の場合は以下を有効化してください。\n" |
| 2296 |
" # gateway 2001:db8:1234:5::1" |
| 2297 |
|
| 2298 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2299 |
#, fuzzy |
| 2300 |
#| msgid "<primary>SSL</primary>" |
| 2301 |
msgid "<primary>SLAAC</primary>" |
| 2302 |
msgstr "<primary>SSL</primary>" |
| 2303 |
|
| 2304 |
msgid "<primary>Stateless Address Autoconfiguration</primary><see>SLAAC</see>" |
| 2305 |
msgstr "" |
| 2306 |
|
| 2307 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2308 |
msgid "IPv6 subnets usually have a netmask of 64 bits. This means that 2<superscript>64</superscript> distinct addresses exist within the subnet. This allows Stateless Address Autoconfiguration (<acronym>SLAAC</acronym>) to pick an address based on the network interface's MAC address. By default, if <acronym>SLAAC</acronym> is activated in your network and IPv6 on your computer, the kernel will automatically find IPv6 routers and configure the network interfaces." |
| 2309 |
msgstr "IPv6 サブネットのネットマスクは通常 64 ビットです。これは、サブネットの中に 2<superscript>64</superscript> 個の異なるアドレスが存在することを意味します。この特徴のおかげで、インターフェースの MAC アドレスに基づいたアドレスを選ぶステートレスアドレス自動設定 (<acronym>SLAAC</acronym>) を使うことが可能です。ネットワークで <acronym>SLAAC</acronym> が有効化されコンピュータで IPv6 が有効化された場合、デフォルトでカーネルは自動的に IPv6 ルータを探してネットワークインターフェースを設定します。" |
| 2310 |
|
| 2311 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2312 |
#, fuzzy |
| 2313 |
#| msgid "<primary>ISC</primary>" |
| 2314 |
msgid "<primary>MAC</primary>" |
| 2315 |
msgstr "<primary>ISC</primary>" |
| 2316 |
|
| 2317 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2318 |
#, fuzzy |
| 2319 |
#| msgid "<primary>IP address</primary><secondary>private</secondary>" |
| 2320 |
msgid "<primary>IPv6</primary><secondary>privacy extensions</secondary>" |
| 2321 |
msgstr "<primary>IP アドレス</primary><secondary>プライベート</secondary>" |
| 2322 |
|
| 2323 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2324 |
#, fuzzy |
| 2325 |
#| msgid "This behavior may have privacy implications. If you switch networks frequently, e.g. with a laptop, you might not want your <acronym>MAC</acronym> address being a part of your public IPv6 address. This makes it easy to identify the same device across networks. A solution to this are IPv6 privacy extensions (which Debian enables by default if IPv6 connectivity is detected during initial installation), which will assign an additional randomly generated address to the interface, periodically change them and prefer them for outgoing connections. Incoming connections can still use the address generated by SLAAC. The following example, for use in <filename>/etc/network/interfaces</filename>, activates these privacy extensions." |
| 2326 |
msgid "This behavior may have privacy implications. If you switch networks frequently, e.g. with a laptop, you might not want your <acronym>MAC</acronym> address being a part of your public IPv6 address. This makes it easy to identify the same device across networks. A solution to this are IPv6 privacy extensions (which Debian enables by default if IPv6 connectivity is detected during initial installation), which will assign an additional randomly generated address to the interface, periodically change them and prefer them for outgoing connections. Incoming connections can still use the address generated by SLAAC. The following example, for use in <filename>/etc/network/interfaces</filename>, activates these privacy extensions for the interface <replaceable>enp7s0</replaceable>." |
| 2327 |
msgstr "SLAAC の挙動はプライバシーを推測される危険性をはらんでいます。たとえばラップトップでネットワークを頻繁に切り替える場合、公開 IPv6 アドレスの一部に <acronym>MAC</acronym> アドレスを含めたくないかもしれません。SLAAC のせいで、異なるネットワーク上の同じデバイスを容易に識別できるようになります。この問題に対する解決策が IPv6 プライバシー拡張です (初回インストール時に IPv6 接続が検出された場合、Debian は IPv6 プライバシー拡張をデフォルトで有効化します)。IPv6 プライバシー拡張を使うとインターフェースにランダムに生成されたアドレスを割り当て、定期的にこれを変更し、外部に出る接続にはこのアドレスを使うようになります。外部から入ってくる接続は SLAAC で生成されたアドレスを使うことも可能です。以下の例では <filename>/etc/network/interfaces</filename> の中で IPv6 プライバシー拡張を有効化しています。" |
| 2328 |
|
| 2329 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2330 |
msgid "IPv6 privacy extensions" |
| 2331 |
msgstr "IPv6 プライバシー拡張" |
| 2332 |
|
| 2333 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2334 |
#, fuzzy |
| 2335 |
#| msgid "" |
| 2336 |
#| "\n" |
| 2337 |
#| "iface eth0 inet6 auto\n" |
| 2338 |
#| " # Prefer the randomly assigned addresses for outgoing connections.\n" |
| 2339 |
#| " privext 2" |
| 2340 |
msgid "" |
| 2341 |
"\n" |
| 2342 |
"iface enp7s0 inet6 auto\n" |
| 2343 |
" # Prefer the randomly assigned addresses for outgoing connections.\n" |
| 2344 |
" privext 2" |
| 2345 |
msgstr "" |
| 2346 |
"\n" |
| 2347 |
"iface eth0 inet6 auto\n" |
| 2348 |
" # 外部へ接続する際にランダムに割り当てられたアドレスを使います。\n" |
| 2349 |
" privext 2" |
| 2350 |
|
| 2351 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2352 |
msgid "<emphasis>TIP</emphasis> Programs built with IPv6" |
| 2353 |
msgstr "<emphasis>TIP</emphasis> プログラムの IPv6 対応" |
| 2354 |
|
| 2355 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2356 |
#, fuzzy |
| 2357 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 2358 |
msgid "<primary>mailing lists</primary><secondary><email>[email protected]</email></secondary>" |
| 2359 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 2360 |
|
| 2361 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2362 |
#, fuzzy |
| 2363 |
#| msgid "Many pieces of software need to be adapted to handle IPv6. Most of the packages in Debian have been adapted already, but not all. If your favorite package does not work with IPv6 yet, you can ask for help on the <emphasis>debian-ipv6</emphasis> mailing-list. They might know about an IPv6-aware replacement and could file a bug to get the issue properly tracked. <ulink type=\"block\" url=\"http://lists.debian.org/debian-ipv6/\" />" |
| 2364 |
msgid "Many pieces of software need to be adapted to handle IPv6. Most of the packages in Debian have been adapted already, but not all. If your favorite package does not work with IPv6 yet, you can ask for help on the <emphasis>debian-ipv6</emphasis> mailing-list. They might know about an IPv6-aware replacement and could file a bug to get the issue properly tracked. <ulink type=\"block\" url=\"https://lists.debian.org/debian-ipv6/\" />" |
| 2365 |
msgstr "多くのソフトウェアを IPv6 に対応させる必要があります。Debian に含まれるほとんどのパッケージは既に IPv6 に対応済みですが、すべてではありません。もしお気に入りのパッケージがまだ IPv6 に対応していない場合、<emphasis>debian-ipv6</emphasis> メーリングリストで助けを求めることも可能です。彼らは IPv6 に対応している代替ソフトウェアを知っているかもしれませんし、この問題について適切な追跡が行えるようなバグ報告を投稿できるかもしれません。<ulink type=\"block\" url=\"http://lists.debian.org/debian-ipv6/\" />" |
| 2366 |
|
| 2367 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2368 |
#, fuzzy |
| 2369 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2370 |
msgid "<primary>IPv6</primary><secondary>firewall</secondary>" |
| 2371 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2372 |
|
| 2373 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2374 |
msgid "<primary>firewall</primary><secondary>IPv6</secondary>" |
| 2375 |
msgstr "<primary>ファイアウォール</primary><secondary>IPv6</secondary>" |
| 2376 |
|
| 2377 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2378 |
msgid "<primary><command>ip6tables</command></primary>" |
| 2379 |
msgstr "<primary><command>ip6tables</command></primary>" |
| 2380 |
|
| 2381 |
msgid "IPv6 connections can be restricted, in the same fashion as for IPv4. <command>nft</command> can be used to create firewall rules for IPv4 and IPv6 (see <xref linkend=\"sect.nftables\" />)." |
| 2382 |
msgstr "" |
| 2383 |
|
| 2384 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2385 |
msgid "Tunneling" |
| 2386 |
msgstr "トンネル" |
| 2387 |
|
| 2388 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2389 |
#, fuzzy |
| 2390 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2391 |
msgid "<primary>IPv6</primary><secondary>tunneling</secondary>" |
| 2392 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2393 |
|
| 2394 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2395 |
msgid "<emphasis>CAUTION</emphasis> IPv6 tunneling and firewalls" |
| 2396 |
msgstr "<emphasis>CAUTION</emphasis> IPv6 トンネルとファイアウォール" |
| 2397 |
|
| 2398 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2399 |
#, fuzzy |
| 2400 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2401 |
msgid "<primary>IPv6</primary><secondary>tunnel broker</secondary>" |
| 2402 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2403 |
|
| 2404 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2405 |
msgid "IPv6 tunneling over IPv4 (as opposed to native IPv6) requires the firewall to accept the traffic, which uses IPv4 protocol number 41." |
| 2406 |
msgstr "IPv4 上に IPv6 トンネルを作るには (ネイティブ IPv6 とは対照的に) IPv4 プロトコル 41 番を使うトラフィックを受け入れるファイアウォールが必要です。" |
| 2407 |
|
| 2408 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2409 |
#, fuzzy |
| 2410 |
#| msgid "If a native IPv6 connection is not available, the fallback method is to use a tunnel over IPv4. Gogo6 is one (free) provider of such tunnels: <ulink type=\"block\" url=\"http://www.gogo6.com/freenet6/tunnelbroker\" />" |
| 2411 |
msgid "If a native IPv6 connection is not available, the fallback method is to use a tunnel over IPv4. Hurricane Electric is one (free) provider of such tunnels: <ulink type=\"block\" url=\"https://tunnelbroker.net\" />" |
| 2412 |
msgstr "ネイティブ IPv6 接続が利用できない場合、IPv4 上のトンネルを経由する代替法が使われます。gogo6 はこのようなトンネルの (無料) プロバイダです。<ulink type=\"block\" url=\"http://www.gogo6.com/freenet6/tunnelbroker\" />" |
| 2413 |
|
| 2414 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2415 |
#, fuzzy |
| 2416 |
#| msgid "<primary>Source NAT</primary>" |
| 2417 |
msgid "<primary>Hurricane Electric</primary>" |
| 2418 |
msgstr "<primary>Source NAT</primary>" |
| 2419 |
|
| 2420 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2421 |
#, fuzzy |
| 2422 |
#| msgid "<primary>router</primary>" |
| 2423 |
msgid "<primary>tunnel broker</primary>" |
| 2424 |
msgstr "<primary>ルータ</primary>" |
| 2425 |
|
| 2426 |
msgid "To use a Hurricane Electric tunnel, you need to register an account, login, select a free tunnel and edit the file <filename>/etc/network/interfaces</filename> with the generated code." |
| 2427 |
msgstr "" |
| 2428 |
|
| 2429 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2430 |
msgid "<primary><command>radvd</command></primary>" |
| 2431 |
msgstr "<primary><command>radvd</command></primary>" |
| 2432 |
|
| 2433 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2434 |
#, fuzzy |
| 2435 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2436 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/radvd.conf</filename></secondary>" |
| 2437 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2438 |
|
| 2439 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2440 |
#, fuzzy |
| 2441 |
#| msgid "<primary>server</primary><secondary>name</secondary>" |
| 2442 |
msgid "<primary>service</primary><secondary><filename>radvd.service</filename></secondary>" |
| 2443 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 2444 |
|
| 2445 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2446 |
#, fuzzy |
| 2447 |
#| msgid "The machine then becomes the access router for a subnet with a 56-bit prefix. Once the tunnel is aware of this change, the local network must be told about it; this implies installing the <command>radvd</command> daemon (from the similarly-named package). This IPv6 configuration daemon has a role similar to <command>dhcpd</command> in the IPv4 world." |
| 2448 |
msgid "You can install and configure the <command>radvd</command> daemon (from the similarly-named package) if you want to use the configured computer as a router for a local network. This IPv6 configuration daemon has a role similar to <command>dhcpd</command> in the IPv4 world." |
| 2449 |
msgstr "これでマシンは 56 ビットのプレフィックスを持つサブネット用のアクセスルータになります。Freenet6 トンネルが設定変更を検出したら、ローカルネットワークに設定変更を通知しなければいけません。これを行うには <command>radvd</command> デーモン (同名のパッケージに含まれます) をインストールします。<command>radvd</command> IPv6 設定デーモンは IPv4 で言うところの <command>dhcpd</command> と同様の役割を果たします。" |
| 2450 |
|
| 2451 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2452 |
#, fuzzy |
| 2453 |
#| msgid "<primary>network</primary><secondary>virtual private</secondary>" |
| 2454 |
msgid "<primary><command>ip</command></primary><secondary><literal>address</literal></secondary>" |
| 2455 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"カソウプライベート\">仮想プライベート</secondary>" |
| 2456 |
|
| 2457 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2458 |
# Ref: http://www.gogo6.com/forum/topics/how-to-install-the-client-on-1; |
| 2459 |
#, fuzzy |
| 2460 |
#| msgid "The <filename>/etc/radvd.conf</filename> configuration file must then be created (see <filename>/usr/share/doc/radvd/examples/simple-radvd.conf</filename> as a starting point). In our case, the only required change is the prefix, which needs to be replaced with the one provided by Freenet6; it can be found in the output of the <command>ifconfig</command> command, in the block concerning the <literal>tun</literal> interface." |
| 2461 |
msgid "The <filename>/etc/radvd.conf</filename> configuration file must then be created (see <filename>/usr/share/doc/radvd/examples/simple-radvd.conf</filename> as a starting point). In our case, the only required change is the prefix, which needs to be replaced with the one provided by Hurricane Electric; it can be found in the output of the <command>ip a</command> command, in the block concerning the <literal>he-ipv6</literal> interface." |
| 2462 |
msgstr "<filename>/etc/radvd.conf</filename> 設定ファイルを作成しなければいけません (ひな形の <filename>/usr/share/doc/radvd/examples/simple-radvd.conf</filename> を参照してください)。Freenet6 を使う場合、プレフィックス設定を Freenet6 から提供されたものに変更するだけで十分です。プレフィックスを探すには <command>ifconfig</command> コマンドの出力から <literal>tun</literal> インターフェースを含むブロックを参照します。" |
| 2463 |
|
| 2464 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2465 |
#, fuzzy |
| 2466 |
#| msgid "Then run <command>service gogoc restart</command> and <command>service radvd start</command>, and the IPv6 network should work." |
| 2467 |
msgid "Then run <command>systemctl start radvd</command>. The IPv6 network should now work." |
| 2468 |
msgstr "この後 <command>service gogoc restart</command> と <command>service radvd start</command> を実行すれば、IPv6 ネットワークが使えるはずです。" |
| 2469 |
|
| 2470 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2471 |
msgid "Domain Name Servers (DNS)" |
| 2472 |
msgstr "ドメインネームサーバ (DNS)" |
| 2473 |
|
| 2474 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2475 |
msgid "<primary>DNS</primary>" |
| 2476 |
msgstr "<primary>DNS</primary>" |
| 2477 |
|
| 2478 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2479 |
#, fuzzy |
| 2480 |
#| msgid "<primary>zone</primary><secondary>DNS</secondary>" |
| 2481 |
msgid "<primary>Domain Name Service</primary><see>DNS</see>" |
| 2482 |
msgstr "<primary>ゾーン</primary><secondary>DNS</secondary>" |
| 2483 |
|
| 2484 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2485 |
msgid "<primary>server</primary><secondary>name</secondary>" |
| 2486 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 2487 |
|
| 2488 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2489 |
#, fuzzy |
| 2490 |
#| msgid "<primary>Network</primary><secondary>Address Translation</secondary>" |
| 2491 |
msgid "<primary>IP</primary><secondary>address mapping</secondary>" |
| 2492 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"アドレスヘンカン\">アドレス変換</secondary>" |
| 2493 |
|
| 2494 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2495 |
#, fuzzy |
| 2496 |
#| msgid "The <emphasis>Domain Name Service</emphasis> (DNS) is a fundamental component of the Internet: it maps host names to IP addresses (and vice-versa), which allows the use of <literal>www.debian.org</literal> instead of <literal>5.153.231.4</literal> or <literal>2001:41c8:1000:21::21:4</literal>." |
| 2497 |
msgid "The <emphasis>Domain Name Service</emphasis> (DNS) is a fundamental component of the Internet: it maps host names to IP addresses (and vice-versa), which allows the use of <literal>www.debian.org</literal> instead of <literal>130.89.148.77</literal> or <literal>2001:67c:2564:a119::77</literal>." |
| 2498 |
msgstr "<emphasis>ドメインネームサービス</emphasis> (DNS) はインターネットの基礎要素です。つまり DNS はホスト名を IP アドレスに対応付け (逆に IP アドレスをホスト名に対応付けることも行います)、<literal>5.153.231.4</literal> や <literal>2001:41c8:1000:21::21:4</literal> の代わりに <literal>www.debian.org</literal> を使えるようにします。" |
| 2499 |
|
| 2500 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2501 |
msgid "DNS records are organized in zones; each zone matches either a domain (or a subdomain) or an IP address range (since IP addresses are generally allocated in consecutive ranges). A primary server is authoritative on the contents of a zone; secondary servers, usually hosted on separate machines, provide regularly refreshed copies of the primary zone." |
| 2502 |
msgstr "DNS レコードはゾーン分けされています。それぞれのゾーンはドメイン (またはサブドメイン) か IP アドレス範囲に対応付けられます (なぜなら、ゾーンは通常連続した IP アドレス範囲を割り当てられるからです)。プライマリサーバはあるゾーンに含まれる内容の情報を提供する権威的なサーバです。さらに、セカンダリサーバは通常プライマリサーバとは別のマシン上でホストされ、定期的にプライマリゾーンのコピーをとるサーバです。" |
| 2503 |
|
| 2504 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2505 |
msgid "<primary>zone</primary><secondary>DNS</secondary>" |
| 2506 |
msgstr "<primary>ゾーン</primary><secondary>DNS</secondary>" |
| 2507 |
|
| 2508 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2509 |
msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2510 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2511 |
|
| 2512 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2513 |
#, fuzzy |
| 2514 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2515 |
msgid "<primary>DNS</primary><secondary>resource record</secondary>" |
| 2516 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2517 |
|
| 2518 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2519 |
#, fuzzy |
| 2520 |
#| msgid "Each zone can contain records of various kinds (<emphasis>Resource Records</emphasis>):" |
| 2521 |
msgid "Each zone can contain records of various kinds (<emphasis>Resource Records</emphasis>), these are some of the most common:" |
| 2522 |
msgstr "各ゾーンには、さまざまな種類のレコード (<emphasis>リソースレコード</emphasis>) が含まれます。" |
| 2523 |
|
| 2524 |
msgid "<literal>A</literal> (<emphasis>address record</emphasis>): IPv4 address. This is the most common form to point a domain to an IPv4 address." |
| 2525 |
msgstr "" |
| 2526 |
|
| 2527 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2528 |
#, fuzzy |
| 2529 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2530 |
msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>A</literal></tertiary>" |
| 2531 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2532 |
|
| 2533 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2534 |
#, fuzzy |
| 2535 |
#| msgid "<literal>CNAME</literal>: alias (<emphasis>canonical name</emphasis>). <indexterm><primary>CNAME, DNS record</primary></indexterm>" |
| 2536 |
msgid "<literal>CNAME</literal> (<emphasis>canonical name record</emphasis>): alias" |
| 2537 |
msgstr "<literal>CNAME</literal>。別名 (<emphasis>canonical name</emphasis>) を意味します。<indexterm><primary>CNAME、DNS レコード</primary></indexterm>" |
| 2538 |
|
| 2539 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2540 |
#, fuzzy |
| 2541 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2542 |
msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>CNAME</literal></tertiary>" |
| 2543 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2544 |
|
| 2545 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2546 |
#, fuzzy |
| 2547 |
#| msgid "<literal>MX</literal>: <emphasis>mail exchange</emphasis>, an email server. This information is used by other email servers to find where to send email addressed to a given address. Each MX record has a priority. The highest-priority server (with the lowest number) is tried first (see sidebar <xref linkend=\"sidebar.smtp\" />); other servers are contacted in order of decreasing priority if the first one does not reply. <indexterm><primary>MX</primary><secondary>DNS record</secondary></indexterm>" |
| 2548 |
msgid "<literal>MX</literal> (<emphasis>mail exchange</emphasis>): an email server. This information is used by other email servers to find where to send email addressed to a given address. Each MX record has a priority. The highest-priority server (with the lowest number) is tried first (see sidebar <xref linkend=\"sidebar.smtp\" />); other servers are contacted in order of decreasing priority if the first one does not reply." |
| 2549 |
msgstr "<literal>MX</literal>。<emphasis>mail exchange</emphasis> つまり電子メールサーバを意味します。MX レコードは電子メールサーバが自分の管理下にないアドレス宛の電子メールの送信先を見つけるために使われます。それぞれの MX レコードには優先度があります。最も優先度の高いサーバ (最も低い番号のサーバ) に対する送信を最初に試行します (補注<xref linkend=\"sidebar.smtp\" />を参照してください)。さらに、最初のサーバからの応答がなかった場合、他のサーバを優先度の高い順に試行します。<indexterm><primary>MX</primary><secondary>DNS レコード</secondary></indexterm>" |
| 2550 |
|
| 2551 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2552 |
#, fuzzy |
| 2553 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2554 |
msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>MX</literal></tertiary>" |
| 2555 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2556 |
|
| 2557 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2558 |
#, fuzzy |
| 2559 |
#| msgid "<literal>PTR</literal>: mapping of an IP address to a name. Such a record is stored in a “reverse DNS” zone named after the IP address range. For example, <literal>1.168.192.in-addr.arpa</literal> is the zone containing the reverse mapping for all addresses in the <literal>192.168.1.0/24</literal> range. <indexterm><primary>PTR, DNS record</primary></indexterm>" |
| 2560 |
msgid "<literal>PTR</literal> (<emphasis>pointer</emphasis>): mapping of an IP address to a name. Such a record is stored in a “reverse DNS” zone named after the IP address range. For example, <literal>1.168.192.in-addr.arpa</literal> is the zone containing the reverse mapping for all addresses in the <literal>192.168.1.0/24</literal> range." |
| 2561 |
msgstr "<literal>PTR</literal>。ある IP アドレスに対する名前の対応付けを意味します。<literal>PTR</literal> レコードはある IP アドレス範囲に対応付けられた「逆引き DNS」ゾーンに保存されます。たとえば、<literal>1.168.192.in-addr.arpa</literal> は <literal>192.168.1.0/24</literal> 範囲に含まれる全アドレスの逆引き対応が保存されているゾーンです。<indexterm><primary>PTR、DNS レコード</primary></indexterm>" |
| 2562 |
|
| 2563 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2564 |
#, fuzzy |
| 2565 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2566 |
msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>PTR</literal></tertiary>" |
| 2567 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2568 |
|
| 2569 |
msgid "<literal>AAAA</literal> (<emphasis>IPv6 address record</emphasis>): IPv6 address." |
| 2570 |
msgstr "" |
| 2571 |
|
| 2572 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2573 |
#, fuzzy |
| 2574 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2575 |
msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>AAAA</literal></tertiary>" |
| 2576 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2577 |
|
| 2578 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2579 |
#, fuzzy |
| 2580 |
#| msgid "<literal>NS</literal>: maps a name to a name server. Each domain must have at least one NS record. These records point at a DNS server that can answer queries concerning this domain; they usually point at the primary and secondary servers for the domain. These records also allow DNS delegation; for instance, the <literal>falcot.com</literal> zone can include an NS record for <literal>internal.falcot.com</literal>, which means that the <literal>internal.falcot.com</literal> zone is handled by another server. Of course, this server must declare an <literal>internal.falcot.com</literal> zone. <indexterm><primary>NS, DNS record</primary></indexterm>" |
| 2581 |
msgid "<literal>NS</literal> (<emphasis>name server</emphasis>): maps a name to a name server. Each domain must have at least one NS record. These records point at a DNS server that can answer queries concerning this domain; they usually point at the primary and secondary servers for the domain. These records also allow DNS delegation; for instance, the <literal>falcot.com</literal> zone can include an NS record for <literal>internal.falcot.com</literal>, which means that the <literal>internal.falcot.com</literal> zone is handled by another server. Of course, this server must declare an <literal>internal.falcot.com</literal> zone." |
| 2582 |
msgstr "<literal>NS</literal>。名前とネームサーバの対応付けを意味します。それぞれのドメインは最低 1 つの NS レコードを持っています。NS レコードでは、このドメインに対する問い合わせに答えることができる DNS サーバを指定します。これは通常そのドメインに対するプライマリおよびセカンダリサーバです。NS レコードを使って DNS の権限委譲を指定することも可能です。たとえば、<literal>falcot.com</literal> ゾーンの NS レコードには <literal>internal.falcot.com</literal> が含まれます。これは <literal>internal.falcot.com</literal> ゾーンは別のサーバが担当していることを意味します。もちろん、このサーバは <literal>internal.falcot.com</literal> ゾーンを宣言しなければいけません。<indexterm><primary>NS、DNS レコード</primary></indexterm>" |
| 2583 |
|
| 2584 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2585 |
#, fuzzy |
| 2586 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2587 |
msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>NS</literal></tertiary>" |
| 2588 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2589 |
|
| 2590 |
msgid "DNS software" |
| 2591 |
msgstr "" |
| 2592 |
|
| 2593 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2594 |
msgid "<primary>ISC</primary>" |
| 2595 |
msgstr "<primary>ISC</primary>" |
| 2596 |
|
| 2597 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2598 |
#, fuzzy |
| 2599 |
#| msgid "<primary>Internet Software Consortium</primary>" |
| 2600 |
msgid "<primary>Internet Software Consortium</primary><see>ISC</see>" |
| 2601 |
msgstr "<primary>Internet Software Consortium</primary>" |
| 2602 |
|
| 2603 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2604 |
msgid "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>" |
| 2605 |
msgstr "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>" |
| 2606 |
|
| 2607 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2608 |
#, fuzzy |
| 2609 |
#| msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 2610 |
msgid "<primary>DNS</primary><secondary><emphasis role=\"pkg\">bind9</emphasis></secondary><seealso><command>bind</command></seealso>" |
| 2611 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 2612 |
|
| 2613 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2614 |
#, fuzzy |
| 2615 |
#| msgid "The reference name server, Bind, was developed and is maintained by ISC (<emphasis>Internet Software Consortium</emphasis>). It is provided in Debian by the <emphasis role=\"pkg\">bind9</emphasis> package. Version 9 brings two major changes compared to previous versions. First, the DNS server can now run under an unprivileged user, so that a security vulnerability in the server does not grant root privileges to the attacker (as was seen repeatedly with versions 8.x)." |
| 2616 |
msgid "The reference name server, Bind, was developed and is maintained by ISC (the <emphasis>Internet Software Consortium</emphasis>). It is provided in Debian by the <emphasis role=\"pkg\">bind9</emphasis> package. Version 9 brings two major changes compared to previous versions. First, the DNS server can now run under an unprivileged user, so that a security vulnerability in the server does not grant root privileges to the attacker (as was seen repeatedly with versions 8.x)." |
| 2617 |
msgstr "標準的なネームサーバである Bind は ISC (<emphasis>Internet Software Consortium</emphasis>) によって開発およびメンテナンスされています。Debian において Bind を提供するパッケージは <emphasis role=\"pkg\">bind9</emphasis> です。Bind バージョン 9 では、前のバージョンに比べて 2 種類の大きな変更が導入されました。1 番目は DNS サーバを非特権ユーザとして実行するという変更です。これにより、サーバのセキュリティ脆弱性によって攻撃者に root 権限を渡してしまうことがなくなりました (バージョン 8.x ではこのようなことがよくありました)。" |
| 2618 |
|
| 2619 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2620 |
msgid "Furthermore, Bind supports the DNSSEC standard for signing (and therefore authenticating) DNS records, which allows blocking any spoofing of this data during man-in-the-middle attacks." |
| 2621 |
msgstr "2 番目は Bind が DNS レコードの署名 (すなわち DNS レコードの認証) に DNSSEC 標準をサポートするようになった変更です。これにより、中間者攻撃で DNS レコードが偽装された場合に、偽装された DNS レコードを遮断することが可能になりました。" |
| 2622 |
|
| 2623 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2624 |
msgid "<emphasis>CULTURE</emphasis> DNSSEC" |
| 2625 |
msgstr "<emphasis>CULTURE</emphasis> DNSSEC" |
| 2626 |
|
| 2627 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2628 |
msgid "<primary>DNSSEC</primary>" |
| 2629 |
msgstr "<primary>DNSSEC</primary>" |
| 2630 |
|
| 2631 |
msgid "<primary>Domain Name System Security Extensions</primary><see>DNSSEC</see>" |
| 2632 |
msgstr "" |
| 2633 |
|
| 2634 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2635 |
#, fuzzy |
| 2636 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2637 |
msgid "<primary>DNS</primary><secondary>security extensions</secondary><see>DNSSEC</see>" |
| 2638 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2639 |
|
| 2640 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2641 |
#, fuzzy |
| 2642 |
#| msgid "The DNSSEC norm is quite complex; this partly explains why it is not in widespread usage yet (even if it perfectly coexists with DNS servers unaware of DNSSEC). To understand all the ins and outs, you should check the following article. <ulink type=\"block\" url=\"http://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions\" />" |
| 2643 |
msgid "The DNSSEC norm is quite complex; this partly explains why it is not in widespread usage yet (even if it perfectly coexists with DNS servers unaware of DNSSEC). To understand all the ins and outs, you should check the following article. <ulink type=\"block\" url=\"https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions\" />" |
| 2644 |
msgstr "DNSSEC の規格はかなり複雑です。さらに DNSSEC はその複雑さにより、まだ広く使われている規格ではありません (DNSSEC に未対応の DNS サーバと完全に共存するにも関わらず使われていません)。一部始終を理解するには、以下の記事を参照してください。<ulink type=\"block\" url=\"http://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions\" />" |
| 2645 |
|
| 2646 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2647 |
#, fuzzy |
| 2648 |
#| msgid "Configuring" |
| 2649 |
msgid "Configuring bind" |
| 2650 |
msgstr "設定" |
| 2651 |
|
| 2652 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2653 |
#, fuzzy |
| 2654 |
#| msgid "<primary>zone</primary><secondary>DNS</secondary>" |
| 2655 |
msgid "<primary>daemon</primary><secondary>bind</secondary>" |
| 2656 |
msgstr "<primary>ゾーン</primary><secondary>DNS</secondary>" |
| 2657 |
|
| 2658 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2659 |
#, fuzzy |
| 2660 |
#| msgid "<primary>record</primary><secondary>DNS</secondary>" |
| 2661 |
msgid "<primary>server</primary><secondary>DNS</secondary>" |
| 2662 |
msgstr "<primary>レコード</primary><secondary>DNS</secondary>" |
| 2663 |
|
| 2664 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2665 |
#, fuzzy |
| 2666 |
#| msgid "<primary>network</primary><secondary>DHCP configuration</secondary>" |
| 2667 |
msgid "<primary><command>bind</command></primary><secondary>configuration</secondary>" |
| 2668 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"DHCP セッテイ\">DHCP 設定</secondary>" |
| 2669 |
|
| 2670 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2671 |
msgid "Configuration files for <command>bind</command>, irrespective of version, have the same structure." |
| 2672 |
msgstr "バージョンによらず <command>bind</command> の設定ファイルは同じ構造をしています。" |
| 2673 |
|
| 2674 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2675 |
msgid "The Falcot administrators created a primary <literal>falcot.com</literal> zone to store information related to this domain, and a <literal>168.192.in-addr.arpa</literal> zone for reverse mapping of IP addresses in the local networks." |
| 2676 |
msgstr "Falcot の管理者は <literal>falcot.com</literal> ドメインに関連する情報を保存するためにプライマリ <literal>falcot.com</literal> ゾーンを作成し、ローカルネットワーク内の IP アドレスとの逆引き対応を付けるために <literal>168.192.in-addr.arpa</literal> ゾーンを作成しました。" |
| 2677 |
|
| 2678 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2679 |
msgid "<emphasis>CAUTION</emphasis> Names of reverse zones" |
| 2680 |
msgstr "<emphasis>CAUTION</emphasis> 逆引きゾーンの名前" |
| 2681 |
|
| 2682 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2683 |
msgid "<primary>zone</primary><secondary>reverse</secondary>" |
| 2684 |
msgstr "<primary>ゾーン</primary><secondary sortas=\"ギャクビキ\">逆引き</secondary>" |
| 2685 |
|
| 2686 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2687 |
msgid "<primary>reverse zone</primary>" |
| 2688 |
msgstr "<primary sortas=\"ギャクビキゾーン\">逆引きゾーン</primary>" |
| 2689 |
|
| 2690 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2691 |
#, fuzzy |
| 2692 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2693 |
msgid "<primary>DNS</primary><secondary>reverse zone</secondary>" |
| 2694 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2695 |
|
| 2696 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2697 |
msgid "<primary><literal>in-addr.arpa</literal></primary>" |
| 2698 |
msgstr "<primary><literal>in-addr.arpa</literal></primary>" |
| 2699 |
|
| 2700 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2701 |
msgid "<primary><literal>ip6.arpa</literal></primary>" |
| 2702 |
msgstr "<primary><literal>ip6.arpa</literal></primary>" |
| 2703 |
|
| 2704 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2705 |
msgid "<primary>nibble format</primary>" |
| 2706 |
msgstr "<primary>ニブルフォーマット</primary>" |
| 2707 |
|
| 2708 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2709 |
msgid "Reverse zones have a particular name. The zone covering the <literal>192.168.0.0/16</literal> network needs to be named <literal>168.192.in-addr.arpa</literal>: the IP address components are reversed, and followed by the <literal>in-addr.arpa</literal> suffix." |
| 2710 |
msgstr "逆引きゾーンには特定の名前が付けられています。<literal>192.168.0.0/16</literal> ネットワークに対する逆引きゾーンは <literal>168.192.in-addr.arpa</literal> のように名付けなければいけません。具体的に言えば、IP アドレス部分の順序を逆にして、その後ろに <literal>in-addr.arpa</literal> サフィックスを付けます。" |
| 2711 |
|
| 2712 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2713 |
msgid "For IPv6 networks, the suffix is <literal>ip6.arpa</literal> and the IP address components which are reversed are each character in the full hexadecimal representation of the IP address. As such, the <literal>2001:0bc8:31a0::/48</literal> network would use a zone named <literal>0.a.1.3.8.c.b.0.1.0.0.2.ip6.arpa</literal>." |
| 2714 |
msgstr "IPv6 ネットワークの場合、IP アドレスを完全に 16 進数表記した時の文字を逆順にして、その後ろに <literal>ip6.arpa</literal> サフィックスを付けます。つまり、<literal>2001:0bc8:31a0::/48</literal> ネットワークはゾーン名として <literal>0.a.1.3.8.c.b.0.1.0.0.2.ip6.arpa</literal> を使います。" |
| 2715 |
|
| 2716 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2717 |
msgid "<emphasis>TIP</emphasis> Testing the DNS server" |
| 2718 |
msgstr "<emphasis>TIP</emphasis> DNS サーバのテスト" |
| 2719 |
|
| 2720 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2721 |
msgid "<primary><command>host</command></primary>" |
| 2722 |
msgstr "<primary><command>host</command></primary>" |
| 2723 |
|
| 2724 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2725 |
msgid "The <command>host</command> command (in the <emphasis role=\"pkg\">bind9-host</emphasis> package) queries a DNS server, and can be used to test the server configuration. For example, <command>host machine.falcot.com localhost</command> checks the local server's reply for the <literal>machine.falcot.com</literal> query. <command>host <replaceable>ipaddress</replaceable> localhost</command> tests the reverse resolution." |
| 2726 |
msgstr "<command>host</command> コマンド (<emphasis role=\"pkg\">bind9-host</emphasis> パッケージに含まれます) は引数に DNS サーバを与えることができ、DNS サーバの設定をテストするために使うことも可能です。たとえば <command>host machine.falcot.com localhost</command> を使うと、<literal>localhost</literal> 上の DNS サーバに <literal>machine.falcot.com</literal> を問い合わせた際の応答を確認することが可能です。<command>host <replaceable>ipaddress</replaceable> localhost</command> を使うと逆引き設定をテストすることが可能です。" |
| 2727 |
|
| 2728 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2729 |
#, fuzzy |
| 2730 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2731 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/bind/named.conf</filename></secondary>" |
| 2732 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2733 |
|
| 2734 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2735 |
msgid "The following configuration excerpts, taken from the Falcot files, can serve as starting points to configure a DNS server:" |
| 2736 |
msgstr "以下に Falcot のファイルから抜粋した設定を載せます。これは DNS サーバの設定の足掛かりになります。" |
| 2737 |
|
| 2738 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2739 |
msgid "Excerpt of <filename>/etc/bind/named.conf.local</filename>" |
| 2740 |
msgstr "<filename>/etc/bind/named.conf.local</filename> の抜粋" |
| 2741 |
|
| 2742 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2743 |
msgid "" |
| 2744 |
"\n" |
| 2745 |
"zone \"falcot.com\" {\n" |
| 2746 |
" type master;\n" |
| 2747 |
" file \"/etc/bind/db.falcot.com\";\n" |
| 2748 |
" allow-query { any; };\n" |
| 2749 |
" allow-transfer {\n" |
| 2750 |
" 195.20.105.149/32 ; // ns0.xname.org\n" |
| 2751 |
" 193.23.158.13/32 ; // ns1.xname.org\n" |
| 2752 |
" };\n" |
| 2753 |
"};\n" |
| 2754 |
"\n" |
| 2755 |
"zone \"internal.falcot.com\" {\n" |
| 2756 |
" type master;\n" |
| 2757 |
" file \"/etc/bind/db.internal.falcot.com\";\n" |
| 2758 |
" allow-query { 192.168.0.0/16; };\n" |
| 2759 |
"};\n" |
| 2760 |
"\n" |
| 2761 |
"zone \"168.192.in-addr.arpa\" {\n" |
| 2762 |
" type master;\n" |
| 2763 |
" file \"/etc/bind/db.192.168\";\n" |
| 2764 |
" allow-query { 192.168.0.0/16; };\n" |
| 2765 |
"};" |
| 2766 |
msgstr "" |
| 2767 |
"\n" |
| 2768 |
"zone \"falcot.com\" {\n" |
| 2769 |
" type master;\n" |
| 2770 |
" file \"/etc/bind/db.falcot.com\";\n" |
| 2771 |
" allow-query { any; };\n" |
| 2772 |
" allow-transfer {\n" |
| 2773 |
" 195.20.105.149/32 ; // ns0.xname.org\n" |
| 2774 |
" 193.23.158.13/32 ; // ns1.xname.org\n" |
| 2775 |
" };\n" |
| 2776 |
"};\n" |
| 2777 |
"\n" |
| 2778 |
"zone \"internal.falcot.com\" {\n" |
| 2779 |
" type master;\n" |
| 2780 |
" file \"/etc/bind/db.internal.falcot.com\";\n" |
| 2781 |
" allow-query { 192.168.0.0/16; };\n" |
| 2782 |
"};\n" |
| 2783 |
"\n" |
| 2784 |
"zone \"168.192.in-addr.arpa\" {\n" |
| 2785 |
" type master;\n" |
| 2786 |
" file \"/etc/bind/db.192.168\";\n" |
| 2787 |
" allow-query { 192.168.0.0/16; };\n" |
| 2788 |
"};" |
| 2789 |
|
| 2790 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2791 |
msgid "Excerpt of <filename>/etc/bind/db.falcot.com</filename>" |
| 2792 |
msgstr "<filename>/etc/bind/db.falcot.com</filename> の抜粋" |
| 2793 |
|
| 2794 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2795 |
# Ref: https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-bind-zone.html; |
| 2796 |
# Ref: http://www.zytrax.com/books/dns/ch8/soa.html; |
| 2797 |
# Ref: https://www.ietf.org/rfc/rfc1912.txt; |
| 2798 |
msgid "" |
| 2799 |
"; falcot.com Zone \n" |
| 2800 |
"; admin.falcot.com. => zone contact: [email protected]\n" |
| 2801 |
"$TTL 604800\n" |
| 2802 |
"@ IN SOA falcot.com. admin.falcot.com. (\n" |
| 2803 |
" 20040121 ; Serial\n" |
| 2804 |
" 604800 ; Refresh\n" |
| 2805 |
" 86400 ; Retry\n" |
| 2806 |
" 2419200 ; Expire\n" |
| 2807 |
" 604800 ) ; Negative Cache TTL\n" |
| 2808 |
";\n" |
| 2809 |
"; The @ refers to the zone name (\"falcot.com\" here)\n" |
| 2810 |
"; or to $ORIGIN if that directive has been used\n" |
| 2811 |
";\n" |
| 2812 |
"@ IN NS ns\n" |
| 2813 |
"@ IN NS ns0.xname.org.\n" |
| 2814 |
"\n" |
| 2815 |
"internal IN NS 192.168.0.2\n" |
| 2816 |
"\n" |
| 2817 |
"@ IN A 212.94.201.10\n" |
| 2818 |
"@ IN MX 5 mail\n" |
| 2819 |
"@ IN MX 10 mail2\n" |
| 2820 |
"\n" |
| 2821 |
"ns IN A 212.94.201.10\n" |
| 2822 |
"mail IN A 212.94.201.10\n" |
| 2823 |
"mail2 IN A 212.94.201.11\n" |
| 2824 |
"www IN A 212.94.201.11\n" |
| 2825 |
"\n" |
| 2826 |
"dns IN CNAME ns" |
| 2827 |
msgstr "" |
| 2828 |
"; falcot.com ゾーン\n" |
| 2829 |
"; admin.falcot.com. でゾーン連絡先アドレスに [email protected] を指定したことになります\n" |
| 2830 |
"$TTL 604800\n" |
| 2831 |
"@ IN SOA falcot.com. admin.falcot.com. (\n" |
| 2832 |
" 20040121 ; Serial\n" |
| 2833 |
" 604800 ; Refresh\n" |
| 2834 |
" 86400 ; Retry\n" |
| 2835 |
" 2419200 ; Expire\n" |
| 2836 |
" 604800 ) ; Negative Cache TTL\n" |
| 2837 |
";\n" |
| 2838 |
"; @ はゾーン名 (ここでは \"falcot.com\") または\n" |
| 2839 |
"; $ORIGIN 指示文が使われていた場合 $ORIGIN を意味します\n" |
| 2840 |
";\n" |
| 2841 |
"@ IN NS ns\n" |
| 2842 |
"@ IN NS ns0.xname.org.\n" |
| 2843 |
"\n" |
| 2844 |
"internal IN NS 192.168.0.2\n" |
| 2845 |
"\n" |
| 2846 |
"@ IN A 212.94.201.10\n" |
| 2847 |
"@ IN MX 5 mail\n" |
| 2848 |
"@ IN MX 10 mail2\n" |
| 2849 |
"\n" |
| 2850 |
"ns IN A 212.94.201.10\n" |
| 2851 |
"mail IN A 212.94.201.10\n" |
| 2852 |
"mail2 IN A 212.94.201.11\n" |
| 2853 |
"www IN A 212.94.201.11\n" |
| 2854 |
"\n" |
| 2855 |
"dns IN CNAME ns" |
| 2856 |
|
| 2857 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2858 |
msgid "<emphasis>CAUTION</emphasis> Syntax of a name" |
| 2859 |
msgstr "<emphasis>CAUTION</emphasis> 名前の構文" |
| 2860 |
|
| 2861 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2862 |
msgid "The syntax of machine names follows strict rules. For instance, <literal>machine</literal> implies <literal>machine.<replaceable>domain</replaceable></literal>. If the domain name should not be appended to a name, said name must be written as <literal>machine.</literal> (with a dot as suffix). Indicating a DNS name outside the current domain therefore requires a syntax such as <literal>machine.otherdomain.com.</literal> (with the final dot)." |
| 2863 |
msgstr "マシン名の構文には厳密なルールがあります。たとえば、<literal>machine</literal> は <literal>machine.<replaceable>domain</replaceable></literal> を意味します。名前にこのドメイン名を加えるべきでない場合、名前を <literal>machine.</literal> のように表記 (ドットを後置) しなければいけません。このため、現在のドメインの外部にある DNS 名を表すには <literal>machine.otherdomain.com.</literal> のような構文 (最後にドットを後置) が必要です。" |
| 2864 |
|
| 2865 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2866 |
msgid "Excerpt of <filename>/etc/bind/db.192.168</filename>" |
| 2867 |
msgstr "<filename>/etc/bind/db.192.168</filename> の抜粋" |
| 2868 |
|
| 2869 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2870 |
msgid "" |
| 2871 |
"; Reverse zone for 192.168.0.0/16\n" |
| 2872 |
"; admin.falcot.com. => zone contact: [email protected]\n" |
| 2873 |
"$TTL 604800\n" |
| 2874 |
"@ IN SOA ns.internal.falcot.com. admin.falcot.com. (\n" |
| 2875 |
" 20040121 ; Serial\n" |
| 2876 |
" 604800 ; Refresh\n" |
| 2877 |
" 86400 ; Retry\n" |
| 2878 |
" 2419200 ; Expire\n" |
| 2879 |
" 604800 ) ; Negative Cache TTL\n" |
| 2880 |
"\n" |
| 2881 |
" IN NS ns.internal.falcot.com.\n" |
| 2882 |
"\n" |
| 2883 |
"; 192.168.0.1 -> arrakis\n" |
| 2884 |
"1.0 IN PTR arrakis.internal.falcot.com.\n" |
| 2885 |
"; 192.168.0.2 -> neptune\n" |
| 2886 |
"2.0 IN PTR neptune.internal.falcot.com.\n" |
| 2887 |
"\n" |
| 2888 |
"; 192.168.3.1 -> pau\n" |
| 2889 |
"1.3 IN PTR pau.internal.falcot.com." |
| 2890 |
msgstr "" |
| 2891 |
"; 192.168.0.0/16 用の逆引きゾーン\n" |
| 2892 |
"; admin.falcot.com. でゾーン連絡先アドレスに [email protected] を指定したことになります\n" |
| 2893 |
"$TTL 604800\n" |
| 2894 |
"@ IN SOA ns.internal.falcot.com. admin.falcot.com. (\n" |
| 2895 |
" 20040121 ; Serial\n" |
| 2896 |
" 604800 ; Refresh\n" |
| 2897 |
" 86400 ; Retry\n" |
| 2898 |
" 2419200 ; Expire\n" |
| 2899 |
" 604800 ) ; Negative Cache TTL\n" |
| 2900 |
"\n" |
| 2901 |
" IN NS ns.internal.falcot.com.\n" |
| 2902 |
"\n" |
| 2903 |
"; 192.168.0.1 を arrakis に対応付けます\n" |
| 2904 |
"1.0 IN PTR arrakis.internal.falcot.com.\n" |
| 2905 |
"; 192.168.0.2 を neptune に対応付けます\n" |
| 2906 |
"2.0 IN PTR neptune.internal.falcot.com.\n" |
| 2907 |
"\n" |
| 2908 |
"; 192.168.3.1 を pau に対応付けます\n" |
| 2909 |
"1.3 IN PTR pau.internal.falcot.com." |
| 2910 |
|
| 2911 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2912 |
#, fuzzy |
| 2913 |
#| msgid "<primary>Dynamic Host Configuration Protocol</primary>" |
| 2914 |
msgid "<primary>DHCP</primary><seealso>Dynamic Host Configuration Protocol</seealso>" |
| 2915 |
msgstr "<primary>Dynamic Host Configuration Protocol</primary>" |
| 2916 |
|
| 2917 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2918 |
#, fuzzy |
| 2919 |
#| msgid "<primary>Dynamic Host Configuration Protocol</primary>" |
| 2920 |
msgid "<primary>Dynamic Host Configuration Protocol</primary><seealso>DHCP</seealso>" |
| 2921 |
msgstr "<primary>Dynamic Host Configuration Protocol</primary>" |
| 2922 |
|
| 2923 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2924 |
msgid "<primary>network</primary><secondary>DHCP configuration</secondary>" |
| 2925 |
msgstr "<primary>ネットワーク</primary><secondary sortas=\"DHCP セッテイ\">DHCP 設定</secondary>" |
| 2926 |
|
| 2927 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2928 |
#, fuzzy |
| 2929 |
#| msgid "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>" |
| 2930 |
msgid "<primary><emphasis role=\"pkg\">isc-dhcp-server</emphasis></primary>" |
| 2931 |
msgstr "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>" |
| 2932 |
|
| 2933 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2934 |
msgid "DHCP (for <emphasis>Dynamic Host Configuration Protocol</emphasis>) is a protocol by which a machine can automatically get its network configuration when it boots. This allows centralizing the management of network configurations, and ensuring that all desktop machines get similar settings." |
| 2935 |
msgstr "DHCP (<emphasis>Dynamic Host Configuration Protocol</emphasis> の略語) はマシンが起動時にネットワーク設定を自動的に取得することを可能にするプロトコルです。DHCP のおかげでネットワーク設定の管理を中央集権化し、すべてのデスクトップマシンに類似した設定を行うことが可能になります。" |
| 2936 |
|
| 2937 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2938 |
msgid "A DHCP server provides many network-related parameters. The most common of these is an IP address and the network where the machine belongs, but it can also provide other information, such as DNS servers, WINS servers, NTP servers, and so on." |
| 2939 |
msgstr "DHCP サーバは多くのネットワーク関連パラメータを提供します。DHCP サーバが提供する最も一般的なパラメータは IP アドレスとマシンの所属するネットワークです。しかしながら、DHCP サーバは DNS サーバ、WINS サーバ、NTP サーバなどの情報を提供することも可能です。" |
| 2940 |
|
| 2941 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2942 |
msgid "The Internet Software Consortium (also involved in developing <command>bind</command>) is the main author of the DHCP server. The matching Debian package is <emphasis role=\"pkg\">isc-dhcp-server</emphasis>." |
| 2943 |
msgstr "(<command>bind</command> の開発にも参加している) Internet Software Consortium は DHCP サーバの主開発者です。彼らの開発した DHCP サーバを含む Debian パッケージは <emphasis role=\"pkg\">isc-dhcp-server</emphasis> です。" |
| 2944 |
|
| 2945 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2946 |
msgid "Configuring" |
| 2947 |
msgstr "設定" |
| 2948 |
|
| 2949 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2950 |
#, fuzzy |
| 2951 |
#| msgid "<primary>DNS</primary><secondary>zone</secondary>" |
| 2952 |
msgid "<primary>DHCP</primary><secondary></secondary>" |
| 2953 |
msgstr "<primary>DNS</primary><secondary>ゾーン</secondary>" |
| 2954 |
|
| 2955 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2956 |
#, fuzzy |
| 2957 |
#| msgid "<primary>server</primary><secondary>name</secondary>" |
| 2958 |
msgid "<primary>server</primary><secondary>DHCP</secondary>" |
| 2959 |
msgstr "<primary>サーバ</primary><secondary>ネームサーバ</secondary>" |
| 2960 |
|
| 2961 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2962 |
#, fuzzy |
| 2963 |
#| msgid "<primary>zone</primary><secondary>DNS</secondary>" |
| 2964 |
msgid "<primary>daemon</primary><secondary>dhcpd</secondary>" |
| 2965 |
msgstr "<primary>ゾーン</primary><secondary>DNS</secondary>" |
| 2966 |
|
| 2967 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2968 |
#, fuzzy |
| 2969 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2970 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/dhcp/dhcpd.conf</filename></secondary>" |
| 2971 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2972 |
|
| 2973 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2974 |
#, fuzzy |
| 2975 |
#| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2976 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/dhcp/dhcpd6.conf</filename></secondary>" |
| 2977 |
msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>" |
| 2978 |
|
| 2979 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2980 |
#, fuzzy |
| 2981 |
#| msgid "The first elements that need to be edited in the DHCP server configuration file (<filename>/etc/dhcp/dhcpd.conf</filename>) are the domain name and the DNS servers. If this server is alone on the local network (as defined by the broadcast propagation), the <literal>authoritative</literal> directive must also be enabled (or uncommented). One also needs to create a <literal>subnet</literal> section describing the local network and the configuration information to be provided. The following example fits a <literal>192.168.0.0/24</literal> local network with a router at <literal>192.168.0.1</literal> serving as the gateway. Available IP addresses are in the range <literal>192.168.0.128</literal> to <literal>192.168.0.254</literal>." |
| 2982 |
msgid "The first elements that need to be edited in the DHCP server configuration files (<filename>/etc/dhcp/dhcpd.conf</filename>, and <filename>/etc/dhcp/dhcpd6.conf</filename> for IPv6) are the domain name and the DNS servers. If this server is alone on the local network (as defined by the broadcast propagation), the <literal>authoritative</literal> directive must also be enabled (or uncommented). One also needs to create a <literal>subnet</literal> section describing the local network and the configuration information to be provided. The following example fits a <literal>192.168.0.0/24</literal> local network with a router at <literal>192.168.0.1</literal> serving as the gateway. Available IP addresses are in the range <literal>192.168.0.128</literal> to <literal>192.168.0.254</literal>." |
| 2983 |
msgstr "DHCP サーバの設定ファイル (<filename>/etc/dhcp/dhcpd.conf</filename>) で最初に編集する必要がある場所はドメイン名と DNS サーバです。DHCP サーバがローカルネットワーク (ブロードキャストが届く範囲として定義されます) に 1 台しかない場合、<literal>authoritative</literal> 指示文を有効化しなければいけません (コメントを外さなければいけません)。また、<literal>subnet</literal> セクションを作成し、そこに通知先のローカルネットワークと設定情報を記述する必要があります。以下は <literal>192.168.0.1</literal> にゲートウェイを担当しているルータが存在する <literal>192.168.0.0/24</literal> ローカルネットワーク用の設定例です。配布される IP アドレスは <literal>192.168.0.128</literal> から <literal>192.168.0.254</literal> までの範囲です。" |
| 2984 |
|
| 2985 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2986 |
msgid "Excerpt of <filename>/etc/dhcp/dhcpd.conf</filename>" |
| 2987 |
msgstr "<filename>/etc/dhcp/dhcpd.conf</filename> の抜粋" |
| 2988 |
|
| 2989 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2990 |
# Ref: man 5 dhcpd.conf; |
| 2991 |
# Ref: less /usr/share/doc/isc-dhcp-server/examples/dhcpd.conf.example; |
| 2992 |
msgid "" |
| 2993 |
"\n" |
| 2994 |
"#\n" |
| 2995 |
"# Sample configuration file for ISC dhcpd for Debian\n" |
| 2996 |
"#\n" |
| 2997 |
"\n" |
| 2998 |
"# The ddns-updates-style parameter controls whether or not the server will\n" |
| 2999 |
"# attempt to do a DNS update when a lease is confirmed. We default to the\n" |
| 3000 |
"# behavior of the version 2 packages ('none', since DHCP v2 didn't\n" |
| 3001 |
"# have support for DDNS.)\n" |
| 3002 |
"ddns-update-style interim;\n" |
| 3003 |
"\n" |
| 3004 |
"# option definitions common to all supported networks...\n" |
| 3005 |
"option domain-name \"internal.falcot.com\";\n" |
| 3006 |
"option domain-name-servers ns.internal.falcot.com;\n" |
| 3007 |
"\n" |
| 3008 |
"default-lease-time 600;\n" |
| 3009 |
"max-lease-time 7200;\n" |
| 3010 |
"\n" |
| 3011 |
"# If this DHCP server is the official DHCP server for the local\n" |
| 3012 |
"# network, the authoritative directive should be uncommented.\n" |
| 3013 |
"authoritative;\n" |
| 3014 |
"\n" |
| 3015 |
"# Use this to send dhcp log messages to a different log file (you also\n" |
| 3016 |
"# have to hack syslog.conf to complete the redirection).\n" |
| 3017 |
"log-facility local7;\n" |
| 3018 |
"\n" |
| 3019 |
"# My subnet\n" |
| 3020 |
"subnet 192.168.0.0 netmask 255.255.255.0 {\n" |
| 3021 |
" option routers 192.168.0.1;\n" |
| 3022 |
" option broadcast-address 192.168.0.255;\n" |
| 3023 |
" range 192.168.0.128 192.168.0.254;\n" |
| 3024 |
" ddns-domainname \"internal.falcot.com\";\n" |
| 3025 |
"}" |
| 3026 |
msgstr "" |
| 3027 |
"\n" |
| 3028 |
"#\n" |
| 3029 |
"# Debian の ISC dhcpd 用設定ファイルの見本\n" |
| 3030 |
"#\n" |
| 3031 |
"\n" |
| 3032 |
"# ddns-update-style パラメータは IP アドレスのリースが確認されたら\n" |
| 3033 |
"# このサーバが DNS 更新を試行するか否かを制御します。\n" |
| 3034 |
"# デフォルト設定値はバージョン 2 パッケージの挙動です\n" |
| 3035 |
"# ('none'。なぜなら DHCP v2 は DDNS をサポートしていなかったからです)。\n" |
| 3036 |
"ddns-update-style interim;\n" |
| 3037 |
"\n" |
| 3038 |
"# すべてのネットワークに共通のオプションを定義します。\n" |
| 3039 |
"option domain-name \"internal.falcot.com\";\n" |
| 3040 |
"option domain-name-servers ns.internal.falcot.com;\n" |
| 3041 |
"\n" |
| 3042 |
"default-lease-time 600;\n" |
| 3043 |
"max-lease-time 7200;\n" |
| 3044 |
"\n" |
| 3045 |
"# この DHCP サーバがローカルネットワークの公式 DHCP サーバならば、\n" |
| 3046 |
"# authoritative 指示文を有効化するべきです。\n" |
| 3047 |
"authoritative;\n" |
| 3048 |
"\n" |
| 3049 |
"# dhcp ログメッセージを別のログファイルへ送信するには以下の設定を使います\n" |
| 3050 |
"# (これを正しく動作させるには syslog.conf の設定も必要です)。\n" |
| 3051 |
"log-facility local7;\n" |
| 3052 |
"\n" |
| 3053 |
"# 自分のサブネット\n" |
| 3054 |
"subnet 192.168.0.0 netmask 255.255.255.0 {\n" |
| 3055 |
" option routers 192.168.0.1;\n" |
| 3056 |
" option broadcast-address 192.168.0.255;\n" |
| 3057 |
" range 192.168.0.128 192.168.0.254;\n" |
| 3058 |
" ddns-domainname \"internal.falcot.com\";\n" |
| 3059 |
"}" |
| 3060 |
|
| 3061 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3062 |
msgid "DHCP and DNS" |
| 3063 |
msgstr "DHCP と DNS" |
| 3064 |
|
| 3065 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3066 |
msgid "<primary>DNS</primary><secondary>automated updates</secondary>" |
| 3067 |
msgstr "<primary>DNS</primary><secondary sortas=\"ジドウコウシン\">自動更新</secondary>" |
| 3068 |
|
| 3069 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3070 |
#, fuzzy |
| 3071 |
#| msgid "<primary><command>ripngd</command></primary>" |
| 3072 |
msgid "<primary><command>bind</command></primary>" |
| 3073 |
msgstr "<primary><command>ripngd</command></primary>" |
| 3074 |
|
| 3075 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3076 |
msgid "A nice feature is the automated registering of DHCP clients in the DNS zone, so that each machine gets a significant name (rather than something impersonal such as <literal>machine-192-168-0-131.internal.falcot.com</literal>). Using this feature requires configuring the DNS server to accept updates to the <literal>internal.falcot.com</literal> DNS zone from the DHCP server, and configuring the latter to submit updates for each registration." |
| 3077 |
msgstr "DNS ゾーン内に DHCP クライアントを自動登録するという便利な機能を使うことが可能です。自動登録機能を使えば、各マシンの意味のある名前を使ってアクセスできるようになります (自動登録機能を使わない場合、<literal>machine-192-168-0-131.internal.falcot.com</literal> などの匿名性のある名前を使ってアクセスすることになります)。自動登録機能を使うには、DHCP サーバから <literal>internal.falcot.com</literal> DNS ゾーンの更新を受け入れるように DNS サーバを設定して、各クライアントの登録情報の更新を DNS サーバに送信するように DHCP サーバを設定します。" |
| 3078 |
|
| 3079 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3080 |
#, fuzzy |
| 3081 |
#| msgid "In the <command>bind</command> case, the <literal>allow-update</literal> directive needs to be added to each of the zones that the DHCP server is to edit (the one for the <literal>internal.falcot.com</literal> domain, and the reverse zone). This directive lists the IP addresses allowed to perform these updates; it should therefore contain the possible addresses of the DHCP server (both the local address and the public address, if appropriate)." |
| 3082 |
msgid "In the <command>bind</command> case (see <xref linkend=\"sect.dns-software\" />), the <literal>allow-update</literal> directive needs to be added to each of the zones that the DHCP server is to edit (the one for the <literal>internal.falcot.com</literal> domain, and the reverse zone). This directive lists the IP addresses allowed to perform these updates; it should therefore contain the possible addresses of the DHCP server (both the local address and the public address, if appropriate)." |
| 3083 |
msgstr "<command>bind</command> の場合、DHCP サーバから更新を受け入れる各ゾーンに <literal>allow-update</literal> 指示文を追加する必要があります (<literal>internal.falcot.com</literal> ドメインと逆引きゾーンの両方に追加する必要があります)。<literal>allow-update</literal> 指示文は更新を受け入れる IP アドレスをリストします。つまり、考え得る DHCP サーバの全アドレスを列挙します (必要に応じて、ローカルアドレスと公開アドレスの両方を指定します)。" |
| 3084 |
|
| 3085 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3086 |
msgid "" |
| 3087 |
"\n" |
| 3088 |
"allow-update { 127.0.0.1 192.168.0.1 212.94.201.10 !any };" |
| 3089 |
msgstr "" |
| 3090 |
"\n" |
| 3091 |
"allow-update { 127.0.0.1 192.168.0.1 212.94.201.10 !any };" |
| 3092 |
|
| 3093 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3094 |
# Tag: PTAL; |
| 3095 |
msgid "Beware! A zone that can be modified <emphasis>will</emphasis> be changed by <command>bind</command>, and the latter will overwrite its configuration files at regular intervals. Since this automated procedure produces files that are less human-readable than manually-written ones, the Falcot administrators handle the <literal>internal.falcot.com</literal> domain with a delegated DNS server; this means the <literal>falcot.com</literal> zone file stays firmly under their manual control." |
| 3096 |
msgstr "注意してください! 更新を受け入れることを許可したゾーンは <command>bind</command> により<emphasis>変更され</emphasis>、設定ファイルは定期的に上書きされます。この自動手続きにより作成されるファイルは手作業で書かれたものよりも人間にとって読みづらいため、Falcot の管理者は権限委譲された DNS サーバを使って <literal>internal.falcot.com</literal> ドメインを管理しています。これは <literal>falcot.com</literal> ゾーンファイルは手作業で管理されることを意味します。" |
| 3097 |
|
| 3098 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3099 |
#, fuzzy |
| 3100 |
#| msgid "The DHCP server configuration excerpt above already includes the directives required for DNS zone updates: they are the <literal>ddns-update-style interim;</literal> and <literal>ddns-domain-name \"internal.falcot.com\";</literal> lines in the block describing the subnet." |
| 3101 |
msgid "The DHCP server configuration excerpt above already includes the directives required for DNS zone updates: they are the <literal>ddns-update-style interim;</literal> and <literal>ddns-domain-name \"internal.falcot.com\";</literal> lines." |
| 3102 |
msgstr "上で引用した DHCP サーバの設定には、既に DNS ゾーンの更新に必要な指示文が含まれています。すなわちその指示文とは <literal>ddns-update-style interim;</literal> とサブネットを表すブロック中の <literal>ddns-domain-name \"internal.falcot.com\";</literal> です。" |
| 3103 |
|
| 3104 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3105 |
msgid "Network Diagnosis Tools" |
| 3106 |
msgstr "ネットワーク診断ツール" |
| 3107 |
|
| 3108 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3109 |
#, fuzzy |
| 3110 |
#| msgid "<primary>network</primary><secondary>gateway</secondary>" |
| 3111 |
msgid "<primary>network</primary><secondary>diagnosis</secondary>" |
| 3112 |
msgstr "<primary>ネットワーク</primary><secondary>ゲートウェイ</secondary>" |
| 3113 |
|
| 3114 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3115 |
#, fuzzy |
| 3116 |
#| msgid "When a network application does not run as expected, it is important to be able to look under the hood. Even when everything seems to run smoothly, running a network diagnosis can help ensure everything is working as it should. Several diagnosis tools exists for this purpose; each one operates on a different level." |
| 3117 |
msgid "When a network application does not run as expected, it is important to be able to look under the hood. Even when everything seems to run smoothly, running a network diagnosis can help ensure everything is working as it should. Several diagnosis tools exists for this purpose; each one operates on a different level. It would go beyond the scope of this book to discuss all tools, so we will focus on the more well-known and commonly used tools in the following sections." |
| 3118 |
msgstr "ネットワークアプリケーションが期待通りに動かない場合、中身を確かめることが重要です。すべてが問題なく動いているように見える場合でも、ネットワーク診断を実行すればすべてがあるべき姿で動いていることを確かめる手助けになります。この目的で複数の診断ツールが存在します。そして、各ツールは異なるレベルを診断します。" |
| 3119 |
|
| 3120 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3121 |
msgid "Local Diagnosis: <command>netstat</command>" |
| 3122 |
msgstr "ローカルの診断、<command>netstat</command>" |
| 3123 |
|
| 3124 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3125 |
msgid "<primary><command>netstat</command></primary>" |
| 3126 |
msgstr "<primary><command>netstat</command></primary>" |
| 3127 |
|
| 3128 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3129 |
msgid "Let's first mention the <command>netstat</command> command (in the <emphasis role=\"pkg\">net-tools</emphasis> package); it displays an instant summary of a machine's network activity. When invoked with no argument, this command lists all open connections; this list can be very verbose since it includes many Unix-domain sockets (widely used by daemons) which do not involve the network at all (for example, <literal>dbus</literal> communication, <literal>X11</literal> traffic, and communications between virtual filesystems and the desktop)." |
| 3130 |
msgstr "最初に <command>netstat</command> コマンド (<emphasis role=\"pkg\">net-tools</emphasis> パッケージに含まれます) を紹介しましょう。<command>netstat</command> コマンドはマシンのその瞬間のネットワーク活動に関する要約を表示します。何も引数を渡さずに実行した場合、<command>netstat</command> コマンドは開かれた接続をリストします。このリストはとても長くなる場合があります。なぜなら、このリストには多くの Unix ドメインソケットが含まれるからです (Unix ドメインソケットはデーモンによって広く使われています)。Unix ドメインソケットはネットワークに関与するものではありません (<literal>dbus</literal> 通信、<literal>X11</literal> トラフィック、仮想ファイルシステムとデスクトップ間の通信などに関与するものです)。" |
| 3131 |
|
| 3132 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3133 |
msgid "Common invocations therefore use options that alter <command>netstat</command>'s behavior. The most frequently used options include:" |
| 3134 |
msgstr "一般的に <command>netstat</command> を実行する際には標準の挙動を変更するオプションを使います。最も頻繁に使われるオプションを以下に挙げます。" |
| 3135 |
|
| 3136 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3137 |
msgid "<literal>-t</literal>, which filters the results to only include TCP connections;" |
| 3138 |
msgstr "<literal>-t</literal>。TCP 接続だけが表示されます。" |
| 3139 |
|
| 3140 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3141 |
msgid "<literal>-u</literal>, which works similarly for UDP connections; these options are not mutually exclusive, and one of them is enough to stop displaying Unix-domain connections;" |
| 3142 |
msgstr "<literal>-u</literal>。UDP 接続だけが表示されます。<literal>-t</literal> と <literal>-u</literal> オプションは同時に使えます。Unix ドメインソケットの表示を抑制するにはどちらか一方を使うだけで十分です。" |
| 3143 |
|
| 3144 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3145 |
msgid "<literal>-a</literal>, to also list listening sockets (waiting for incoming connections);" |
| 3146 |
msgstr "<literal>-a</literal>。リッスンしている (接続を待ち受けている) ソケットも表示されます。" |
| 3147 |
|
| 3148 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3149 |
# Ref: $ man 1 netstat; |
| 3150 |
# Ref: $ vimdiff <(netstat -epan) <(netstat -epa); |
| 3151 |
msgid "<literal>-n</literal>, to display the results numerically: IP addresses (no DNS resolution), port numbers (no aliases as defined in <filename>/etc/services</filename>) and user ids (no login names);" |
| 3152 |
msgstr "<literal>-n</literal>。結果が数値的に表示されます。すなわち、IP アドレス (DNS で名前解決しません)、ポート番号 (<filename>/etc/services</filename> の定義する別名を使いません)、ユーザ id (ログイン名を使いません) を使って表示されます。" |
| 3153 |
|
| 3154 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3155 |
msgid "<literal>-p</literal>, to list the processes involved; this option is only useful when <command>netstat</command> is run as root, since normal users will only see their own processes;" |
| 3156 |
msgstr "<literal>-p</literal>。関連付けられたプロセスが表示されます。<command>netstat</command> を root 権限で実行した場合にのみ、このオプションは役に立ちます。なぜなら、普通のユーザは自分のプロセス以外を見ることができないからです。" |
| 3157 |
|
| 3158 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3159 |
msgid "<literal>-c</literal>, to continuously refresh the list of connections." |
| 3160 |
msgstr "<literal>-c</literal>。継続的に接続リストを更新します。" |
| 3161 |
|
| 3162 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3163 |
msgid "Other options, documented in the <citerefentry><refentrytitle>netstat</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page, provide an even finer control over the displayed results. In practice, the first five options are so often used together that systems and network administrators practically acquired <command>netstat -tupan</command> as a reflex. Typical results, on a lightly loaded machine, may look like the following:" |
| 3164 |
msgstr "<citerefentry><refentrytitle>netstat</refentrytitle> <manvolnum>8</manvolnum></citerefentry> マニュアルページに書かれている他のオプションを使えば、表示される結果をさらに細かく制御することが可能です。実質的には上に挙げたオプションのうち最初の 5 種類を組み合わせて使うことが多いため、結果としてシステムとネットワークの管理者は <command>netstat -tupan</command> を身に付けることが多いです。負荷の高くないマシンでは、以下のような典型的な結果を返します。" |
| 3165 |
|
| 3166 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3167 |
msgid "" |
| 3168 |
"\n" |
| 3169 |
"<computeroutput># </computeroutput><userinput>netstat -tupan</userinput>\n" |
| 3170 |
"<computeroutput>Active Internet connections (servers and established)\n" |
| 3171 |
"Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name\n" |
| 3172 |
"tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 397/rpcbind \n" |
| 3173 |
"tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 431/sshd \n" |
| 3174 |
"tcp 0 0 0.0.0.0:36568 0.0.0.0:* LISTEN 407/rpc.statd \n" |
| 3175 |
"tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 762/exim4 \n" |
| 3176 |
"tcp 0 272 192.168.1.242:22 192.168.1.129:44452 ESTABLISHED 1172/sshd: roland [\n" |
| 3177 |
"tcp6 0 0 :::111 :::* LISTEN 397/rpcbind \n" |
| 3178 |
"tcp6 0 0 :::22 :::* LISTEN 431/sshd \n" |
| 3179 |
"tcp6 0 0 ::1:25 :::* LISTEN 762/exim4 \n" |
| 3180 |
"tcp6 0 0 :::35210 :::* LISTEN 407/rpc.statd \n" |
| 3181 |
"udp 0 0 0.0.0.0:39376 0.0.0.0:* 916/dhclient \n" |
| 3182 |
"udp 0 0 0.0.0.0:996 0.0.0.0:* 397/rpcbind \n" |
| 3183 |
"udp 0 0 127.0.0.1:1007 0.0.0.0:* 407/rpc.statd \n" |
| 3184 |
"udp 0 0 0.0.0.0:68 0.0.0.0:* 916/dhclient \n" |
| 3185 |
"udp 0 0 0.0.0.0:48720 0.0.0.0:* 451/avahi-daemon: r\n" |
| 3186 |
"udp 0 0 0.0.0.0:111 0.0.0.0:* 397/rpcbind \n" |
| 3187 |
"udp 0 0 192.168.1.242:123 0.0.0.0:* 539/ntpd \n" |
| 3188 |
"udp 0 0 127.0.0.1:123 0.0.0.0:* 539/ntpd \n" |
| 3189 |
"udp 0 0 0.0.0.0:123 0.0.0.0:* 539/ntpd \n" |
| 3190 |
"udp 0 0 0.0.0.0:5353 0.0.0.0:* 451/avahi-daemon: r\n" |
| 3191 |
"udp 0 0 0.0.0.0:39172 0.0.0.0:* 407/rpc.statd \n" |
| 3192 |
"udp6 0 0 :::996 :::* 397/rpcbind \n" |
| 3193 |
"udp6 0 0 :::34277 :::* 407/rpc.statd \n" |
| 3194 |
"udp6 0 0 :::54852 :::* 916/dhclient \n" |
| 3195 |
"udp6 0 0 :::111 :::* 397/rpcbind \n" |
| 3196 |
"udp6 0 0 :::38007 :::* 451/avahi-daemon: r\n" |
| 3197 |
"udp6 0 0 fe80::5054:ff:fe99::123 :::* 539/ntpd \n" |
| 3198 |
"udp6 0 0 2001:bc8:3a7e:210:a:123 :::* 539/ntpd \n" |
| 3199 |
"udp6 0 0 2001:bc8:3a7e:210:5:123 :::* 539/ntpd \n" |
| 3200 |
"udp6 0 0 ::1:123 :::* 539/ntpd \n" |
| 3201 |
"udp6 0 0 :::123 :::* 539/ntpd \n" |
| 3202 |
"udp6 0 0 :::5353 :::* 451/avahi-daemon: r\n" |
| 3203 |
"</computeroutput>" |
| 3204 |
msgstr "" |
| 3205 |
"\n" |
| 3206 |
"<computeroutput># </computeroutput><userinput>netstat -tupan</userinput>\n" |
| 3207 |
"<computeroutput>稼働中のインターネット接続 (サーバと確立)\n" |
| 3208 |
"Proto 受信-Q 送信-Q 内部アドレス 外部アドレス 状態 PID/Program name\n" |
| 3209 |
"tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 397/rpcbind \n" |
| 3210 |
"tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 431/sshd \n" |
| 3211 |
"tcp 0 0 0.0.0.0:36568 0.0.0.0:* LISTEN 407/rpc.statd \n" |
| 3212 |
"tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 762/exim4 \n" |
| 3213 |
"tcp 0 272 192.168.1.242:22 192.168.1.129:44452 ESTABLISHED 1172/sshd: roland [\n" |
| 3214 |
"tcp6 0 0 :::111 :::* LISTEN 397/rpcbind \n" |
| 3215 |
"tcp6 0 0 :::22 :::* LISTEN 431/sshd \n" |
| 3216 |
"tcp6 0 0 ::1:25 :::* LISTEN 762/exim4 \n" |
| 3217 |
"tcp6 0 0 :::35210 :::* LISTEN 407/rpc.statd \n" |
| 3218 |
"udp 0 0 0.0.0.0:39376 0.0.0.0:* 916/dhclient \n" |
| 3219 |
"udp 0 0 0.0.0.0:996 0.0.0.0:* 397/rpcbind \n" |
| 3220 |
"udp 0 0 127.0.0.1:1007 0.0.0.0:* 407/rpc.statd \n" |
| 3221 |
"udp 0 0 0.0.0.0:68 0.0.0.0:* 916/dhclient \n" |
| 3222 |
"udp 0 0 0.0.0.0:48720 0.0.0.0:* 451/avahi-daemon: r\n" |
| 3223 |
"udp 0 0 0.0.0.0:111 0.0.0.0:* 397/rpcbind \n" |
| 3224 |
"udp 0 0 192.168.1.242:123 0.0.0.0:* 539/ntpd \n" |
| 3225 |
"udp 0 0 127.0.0.1:123 0.0.0.0:* 539/ntpd \n" |
| 3226 |
"udp 0 0 0.0.0.0:123 0.0.0.0:* 539/ntpd \n" |
| 3227 |
"udp 0 0 0.0.0.0:5353 0.0.0.0:* 451/avahi-daemon: r\n" |
| 3228 |
"udp 0 0 0.0.0.0:39172 0.0.0.0:* 407/rpc.statd \n" |
| 3229 |
"udp6 0 0 :::996 :::* 397/rpcbind \n" |
| 3230 |
"udp6 0 0 :::34277 :::* 407/rpc.statd \n" |
| 3231 |
"udp6 0 0 :::54852 :::* 916/dhclient \n" |
| 3232 |
"udp6 0 0 :::111 :::* 397/rpcbind \n" |
| 3233 |
"udp6 0 0 :::38007 :::* 451/avahi-daemon: r\n" |
| 3234 |
"udp6 0 0 fe80::5054:ff:fe99::123 :::* 539/ntpd \n" |
| 3235 |
"udp6 0 0 2001:bc8:3a7e:210:a:123 :::* 539/ntpd \n" |
| 3236 |
"udp6 0 0 2001:bc8:3a7e:210:5:123 :::* 539/ntpd \n" |
| 3237 |
"udp6 0 0 ::1:123 :::* 539/ntpd \n" |
| 3238 |
"udp6 0 0 :::123 :::* 539/ntpd \n" |
| 3239 |
"udp6 0 0 :::5353 :::* 451/avahi-daemon: r\n" |
| 3240 |
"</computeroutput>" |
| 3241 |
|
| 3242 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3243 |
msgid "As expected, this lists established connections, two SSH connections in this case, and applications waiting for incoming connections (listed as <literal>LISTEN</literal>), notably the Exim4 email server listening on port 25." |
| 3244 |
msgstr "予想通り、確立された接続 (2 つの SSH 接続) と接続を待ち受けているアプリケーション (<literal>LISTEN</literal> と記載されます。特に 25 番をリッスンしている Exim4 電子メールサーバ) が表示されます。" |
| 3245 |
|
| 3246 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3247 |
msgid "Remote Diagnosis: <command>nmap</command>" |
| 3248 |
msgstr "リモートの診断、<command>nmap</command>" |
| 3249 |
|
| 3250 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3251 |
msgid "<primary><command>nmap</command></primary>" |
| 3252 |
msgstr "<primary><command>nmap</command></primary>" |
| 3253 |
|
| 3254 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3255 |
msgid "<command>nmap</command> (in the similarly-named package) is, in a way, the remote equivalent for <command>netstat</command>. It can scan a set of “well-known” ports for one or several remote servers, and list the ports where an application is found to answer to incoming connections. Furthermore, <command>nmap</command> is able to identify some of these applications, sometimes even their version number. The counterpart of this tool is that, since it runs remotely, it cannot provide information on processes or users; however, it can operate on several targets at once." |
| 3256 |
msgstr "<command>nmap</command> (同名のパッケージに含まれます) はある意味でリモートに対する <command>netstat</command> に相当します。<command>nmap</command> は 1 台または数台のリモートサーバに対して「well-known」ポート群をスキャンし、入ってきた接続に応答したアプリケーションの見つかったポートをリストします。さらに、<command>nmap</command> は一部のアプリケーションを識別することが可能です。場合によってはアプリケーションのバージョン番号さえも識別することが可能です。<command>nmap</command> は <command>netstat</command> と対照的にリモートから実行されるため、プロセスやユーザの情報を提供できません。しかしながら、<command>nmap</command> は複数のリモートサーバに対して一気に実行できます。" |
| 3257 |
|
| 3258 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3259 |
msgid "A typical <command>nmap</command> invocation only uses the <literal>-A</literal> option (so that <command>nmap</command> attempts to identify the versions of the server software it finds) followed by one or more IP addresses or DNS names of machines to scan. Again, many more options exist to finely control the behavior of <command>nmap</command>; please refer to the documentation in the <citerefentry> <refentrytitle>nmap</refentrytitle> <manvolnum>1</manvolnum> </citerefentry> manual page." |
| 3260 |
msgstr "<command>nmap</command> を実行する際の典型例は <literal>-A</literal> オプション (<command>nmap</command> は見つかったサーバソフトウェアのバージョンを識別しようとします) だけを使い、その後ろにスキャンする 1 つか複数の IP アドレスまたは DNS 名を渡すことです。繰り返しになりますが、他にも多くのオプションが存在し、<command>nmap</command> の挙動をさらに細かく制御することが可能です。<citerefentry> <refentrytitle>nmap</refentrytitle> <manvolnum>1</manvolnum> </citerefentry> マニュアルページを参照してください。" |
| 3261 |
|
| 3262 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3263 |
#, fuzzy |
| 3264 |
#| msgid "" |
| 3265 |
#| "\n" |
| 3266 |
#| "<computeroutput># </computeroutput><userinput>nmap mirtuel</userinput>\n" |
| 3267 |
#| "<computeroutput>\n" |
| 3268 |
#| "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n" |
| 3269 |
#| "Nmap scan report for mirtuel (192.168.1.242)\n" |
| 3270 |
#| "Host is up (0.000013s latency).\n" |
| 3271 |
#| "rDNS record for 192.168.1.242: mirtuel.internal.placard.fr.eu.org\n" |
| 3272 |
#| "Not shown: 998 closed ports\n" |
| 3273 |
#| "PORT STATE SERVICE\n" |
| 3274 |
#| "22/tcp open ssh\n" |
| 3275 |
#| "111/tcp open rpcbind\n" |
| 3276 |
#| "\n" |
| 3277 |
#| "Nmap done: 1 IP address (1 host up) scanned in 2.41 seconds\n" |
| 3278 |
#| "# </computeroutput><userinput>nmap -A localhost</userinput>\n" |
| 3279 |
#| "<computeroutput>\n" |
| 3280 |
#| "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n" |
| 3281 |
#| "Nmap scan report for localhost (127.0.0.1)\n" |
| 3282 |
#| "Host is up (0.000013s latency).\n" |
| 3283 |
#| "Other addresses for localhost (not scanned): 127.0.0.1\n" |
| 3284 |
#| "Not shown: 997 closed ports\n" |
| 3285 |
#| "PORT STATE SERVICE VERSION\n" |
| 3286 |
#| "22/tcp open ssh OpenSSH 6.7p1 Debian 3 (protocol 2.0)\n" |
| 3287 |
#| "|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)\n" |
| 3288 |
#| "25/tcp open smtp Exim smtpd 4.84\n" |
| 3289 |
#| "| smtp-commands: mirtuel Hello localhost [127.0.0.1], SIZE 52428800, 8BITMIME, PIPELINING, HELP, \n" |
| 3290 |
#| "|_ Commands supported: AUTH HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP \n" |
| 3291 |
#| "111/tcp open rpcbind 2-4 (RPC #100000)\n" |
| 3292 |
#| "| rpcinfo: \n" |
| 3293 |
#| "| program version port/proto service\n" |
| 3294 |
#| "| 100000 2,3,4 111/tcp rpcbind\n" |
| 3295 |
#| "| 100000 2,3,4 111/udp rpcbind\n" |
| 3296 |
#| "| 100024 1 36568/tcp status\n" |
| 3297 |
#| "|_ 100024 1 39172/udp status\n" |
| 3298 |
#| "Device type: general purpose\n" |
| 3299 |
#| "Running: Linux 3.X\n" |
| 3300 |
#| "OS CPE: cpe:/o:linux:linux_kernel:3\n" |
| 3301 |
#| "OS details: Linux 3.7 - 3.15\n" |
| 3302 |
#| "Network Distance: 0 hops\n" |
| 3303 |
#| "Service Info: Host: mirtuel; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n" |
| 3304 |
#| "\n" |
| 3305 |
#| "OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .\n" |
| 3306 |
#| "Nmap done: 1 IP address (1 host up) scanned in 11.54 seconds\n" |
| 3307 |
#| "</computeroutput>" |
| 3308 |
msgid "" |
| 3309 |
"\n" |
| 3310 |
"<computeroutput># </computeroutput><userinput>nmap debian</userinput>\n" |
| 3311 |
"<computeroutput><![CDATA[Starting Nmap 7.80 ( https://nmap.org ) at 2022-02-22 20:58 CET\n" |
| 3312 |
"Nmap scan report for debian (192.168.122.57)\n" |
| 3313 |
"Host is up (0.000087s latency).\n" |
| 3314 |
"Not shown: 996 closed ports\n" |
| 3315 |
"PORT STATE SERVICE\n" |
| 3316 |
"22/tcp open ssh\n" |
| 3317 |
"79/tcp open finger\n" |
| 3318 |
"80/tcp open http\n" |
| 3319 |
"113/tcp open ident\n" |
| 3320 |
"\n" |
| 3321 |
"Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds\n" |
| 3322 |
"]]># </computeroutput><userinput>nmap -A localhost</userinput>\n" |
| 3323 |
"<computeroutput><![CDATA[nmap -A localhost\n" |
| 3324 |
"Starting Nmap 7.80 ( https://nmap.org ) at 2022-02-22 20:56 CET\n" |
| 3325 |
"Stats: 0:01:16 elapsed; 0 hosts completed (1 up), 1 undergoing Service Scan\n" |
| 3326 |
"Service scan Timing: About 83.33% done; ETC: 20:57 (0:00:15 remaining)\n" |
| 3327 |
"Nmap scan report for localhost (127.0.0.1)\n" |
| 3328 |
"Host is up (0.000086s latency).\n" |
| 3329 |
"Other addresses for localhost (not scanned): ::1\n" |
| 3330 |
"Not shown: 994 closed ports\n" |
| 3331 |
"PORT STATE SERVICE VERSION\n" |
| 3332 |
"22/tcp open ssh OpenSSH 8.4p1 Debian 5 (protocol 2.0)\n" |
| 3333 |
"|_auth-owners: foobar\n" |
| 3334 |
"25/tcp open smtp Postfix smtpd\n" |
| 3335 |
"|_auth-owners: foobar\n" |
| 3336 |
"|_smtp-commands: debian, PIPELINING, SIZE 10240000, VRFY, ETRN, STARTTLS, ENHANCEDSTATUSCODES, 8BITMIME, DSN, SMTPUTF8, CHUNKING, \n" |
| 3337 |
"| ssl-cert: Subject: commonName=debian\n" |
| 3338 |
"| Subject Alternative Name: DNS:debian\n" |
| 3339 |
"| Not valid before: 2022-02-22T14:48:42\n" |
| 3340 |
"|_Not valid after: 2032-02-20T14:48:42\n" |
| 3341 |
"|_ssl-date: TLS randomness does not represent time\n" |
| 3342 |
"79/tcp open finger?\n" |
| 3343 |
"|_auth-owners: foobar\n" |
| 3344 |
"|_finger: ERROR: Script execution failed (use -d to debug)\n" |
| 3345 |
"80/tcp open http Apache httpd 2.4.52 ((Debian))\n" |
| 3346 |
"|_auth-owners: foobar\n" |
| 3347 |
"|_http-server-header: Apache/2.4.52 (Debian)\n" |
| 3348 |
"|_http-title: Apache2 Debian Default Page: It works\n" |
| 3349 |
"113/tcp open ident Liedentd (Claimed user: foobar)\n" |
| 3350 |
"|_auth-owners: foobar\n" |
| 3351 |
"631/tcp open ipp CUPS 2.3\n" |
| 3352 |
"|_auth-owners: foobar\n" |
| 3353 |
"| http-robots.txt: 1 disallowed entry \n" |
| 3354 |
"|_/\n" |
| 3355 |
"|_http-server-header: CUPS/2.3 IPP/2.1\n" |
| 3356 |
"|_http-title: Home - CUPS 2.3.3op2\n" |
| 3357 |
"Service Info: Host: debian; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n" |
| 3358 |
"\n" |
| 3359 |
"Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .\n" |
| 3360 |
"Nmap done: 1 IP address (1 host up) scanned in 87.91 seconds\n" |
| 3361 |
"]]></computeroutput>" |
| 3362 |
msgstr "" |
| 3363 |
"\n" |
| 3364 |
"<computeroutput># </computeroutput><userinput>nmap mirtuel</userinput>\n" |
| 3365 |
"<computeroutput>\n" |
| 3366 |
"Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-10 00:46 JST\n" |
| 3367 |
"Nmap scan report for mirtuel (192.168.1.242)\n" |
| 3368 |
"Host is up (0.000013s latency).\n" |
| 3369 |
"rDNS record for 192.168.1.242: mirtuel.internal.placard.fr.eu.org\n" |
| 3370 |
"Not shown: 998 closed ports\n" |
| 3371 |
"PORT STATE SERVICE\n" |
| 3372 |
"22/tcp open ssh\n" |
| 3373 |
"111/tcp open rpcbind\n" |
| 3374 |
"\n" |
| 3375 |
"Nmap done: 1 IP address (1 host up) scanned in 2.41 seconds\n" |
| 3376 |
"# </computeroutput><userinput>nmap -A localhost</userinput>\n" |
| 3377 |
"<computeroutput>\n" |
| 3378 |
"Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-10 00:46 JST\n" |
| 3379 |
"Nmap scan report for localhost (127.0.0.1)\n" |
| 3380 |
"Host is up (0.000013s latency).\n" |
| 3381 |
"Other addresses for localhost (not scanned): 127.0.0.1\n" |
| 3382 |
"Not shown: 997 closed ports\n" |
| 3383 |
"PORT STATE SERVICE VERSION\n" |
| 3384 |
"22/tcp open ssh OpenSSH 6.7p1 Debian 3 (protocol 2.0)\n" |
| 3385 |
"|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)\n" |
| 3386 |
"25/tcp open smtp Exim smtpd 4.84\n" |
| 3387 |
"| smtp-commands: mirtuel Hello localhost [127.0.0.1], SIZE 52428800, 8BITMIME, PIPELINING, HELP, \n" |
| 3388 |
"|_ Commands supported: AUTH HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP \n" |
| 3389 |
"111/tcp open rpcbind 2-4 (RPC #100000)\n" |
| 3390 |
"| rpcinfo: \n" |
| 3391 |
"| program version port/proto service\n" |
| 3392 |
"| 100000 2,3,4 111/tcp rpcbind\n" |
| 3393 |
"| 100000 2,3,4 111/udp rpcbind\n" |
| 3394 |
"| 100024 1 36568/tcp status\n" |
| 3395 |
"|_ 100024 1 39172/udp status\n" |
| 3396 |
"Device type: general purpose\n" |
| 3397 |
"Running: Linux 3.X\n" |
| 3398 |
"OS CPE: cpe:/o:linux:linux_kernel:3\n" |
| 3399 |
"OS details: Linux 3.7 - 3.15\n" |
| 3400 |
"Network Distance: 0 hops\n" |
| 3401 |
"Service Info: Host: mirtuel; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n" |
| 3402 |
"\n" |
| 3403 |
"OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .\n" |
| 3404 |
"Nmap done: 1 IP address (1 host up) scanned in 11.54 seconds\n" |
| 3405 |
"</computeroutput>" |
| 3406 |
|
| 3407 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3408 |
#, fuzzy |
| 3409 |
#| msgid "As expected, the SSH and Exim4 applications are listed. Note that not all applications listen on all IP addresses; since Exim4 is only accessible on the <literal>lo</literal> loopback interface, it only appears during an analysis of <literal>localhost</literal> and not when scanning <literal>mirtuel</literal> (which maps to the <literal>eth0</literal> interface on the same machine)." |
| 3410 |
msgid "As expected, e.g. the SSH, Apache and Postfix applications are listed. Note that not all applications listen on all IP addresses; since Postfix is only accessible on the <literal>lo</literal> loopback interface, it only appears during an analysis of <literal>localhost</literal> and not when scanning <literal>debian</literal> (which maps to the <literal>enp1s0</literal> interface on the same machine)." |
| 3411 |
msgstr "予想通り、SSH と Exim4 アプリケーションが表示されます。すべてのアプリケーションがすべての IP アドレスをリッスンしているわけではない点に注意してください。すなわち、Exim4 は <literal>lo</literal> ループバックインターフェースからのみアクセスできますから、<literal>localhost</literal> の解析にのみ表示され <literal>mirtuel</literal> (これは同じマシンの <literal>eth0</literal> インターフェースに対応付けられています) をスキャンした時には表示されません。" |
| 3412 |
|
| 3413 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3414 |
msgid "Sniffers: <command>tcpdump</command> and <command>wireshark</command>" |
| 3415 |
msgstr "スニファ、<command>tcpdump</command> と <command>wireshark</command>" |
| 3416 |
|
| 3417 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3418 |
msgid "<primary><command>tcpdump</command></primary>" |
| 3419 |
msgstr "<primary><command>tcpdump</command></primary>" |
| 3420 |
|
| 3421 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3422 |
msgid "<primary><command>wireshark</command></primary>" |
| 3423 |
msgstr "<primary><command>wireshark</command></primary>" |
| 3424 |
|
| 3425 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3426 |
msgid "Sometimes, one needs to look at what actually goes on the wire, packet by packet. These cases call for a “frame analyzer”, more widely known as a <emphasis>sniffer</emphasis>. Such a tool observes all the packets that reach a given network interface, and displays them in a user-friendly way." |
| 3427 |
msgstr "しばしば実際にワイヤを行き来する情報をパケットごとに見る必要がある場合があります。この際に使われるツールは「フレームアナライザ」と呼ばれ、<emphasis>スニファ</emphasis>としても広く知られています。この種のツールは指定したネットワークに到達したすべてのパケットを観察し、ユーザにわかりやすい方法でパケットを表示します。" |
| 3428 |
|
| 3429 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3430 |
msgid "The venerable tool in this domain is <command>tcpdump</command>, available as a standard tool on a wide range of platforms. It allows many kinds of network traffic capture, but the representation of this traffic stays rather obscure. We will therefore not describe it in further detail." |
| 3431 |
msgstr "ネットワークトラフィック解析分野における由緒あるツールが <command>tcpdump</command> です。<command>tcpdump</command> は広範囲のプラットフォームで利用できる標準的なツールです。<command>tcpdump</command> を使うと多くの種類のネットワークトラフィックをキャプチャできますが、<command>tcpdump</command> のトラフィックの表現は決してわかりやすいものではありません。このため <command>tcpdump</command> に関しては詳しく説明しません。" |
| 3432 |
|
| 3433 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3434 |
msgid "A more recent (and more modern) tool, <command>wireshark</command> (in the <emphasis role=\"pkg\">wireshark</emphasis> package), has become the new reference in network traffic analysis due to its many decoding modules that allow for a simplified analysis of the captured packets. The packets are displayed graphically with an organization based on the protocol layers. This allows a user to visualize all protocols involved in a packet. For example, given a packet containing an HTTP request, <command>wireshark</command> displays, separately, the information concerning the physical layer, the Ethernet layer, the IP packet information, the TCP connection parameters, and finally the HTTP request itself." |
| 3435 |
msgstr "より最近の (そしてより現代的な) ツールである <command>wireshark</command> (<emphasis role=\"pkg\">wireshark</emphasis> パッケージに含まれます) はキャプチャされたパケットの解析を単純化する多くのデコーディングモジュールのおかげでネットワークトラフィック解析分野における新しい標準的なツールになりつつあります。パケットはプロトコル層に基づいてグラフィカルに表示されます。<command>wireshark</command> を使うと、ユーザはあるパケットに関わるすべてのプロトコルを可視化することが可能です。たとえば、HTTP リクエストを含むパケットに対して、<command>wireshark</command> は物理層、イーサネット層、IP パケット情報、TCP 接続パラメータ、最後に HTTP リクエスト自身に関連する情報を別々に表示します。" |
| 3436 |
|
| 3437 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3438 |
msgid "The <command>wireshark</command> network traffic analyzer" |
| 3439 |
msgstr "<command>wireshark</command> ネットワークトラフィックアナライザ" |
| 3440 |
|
| 3441 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3442 |
#, fuzzy |
| 3443 |
#| msgid "In our example, the packets traveling over SSH are filtered out (with the <literal>!tcp.port == 22</literal> filter). The packet currently displayed was developed at the HTTP layer." |
| 3444 |
msgid "In our example, the packets traveling over SSH are filtered out (with the <literal>!tcp.port == 22</literal> filter). The packet currently displayed was developed at the transport layer of the SSHv2 protocol." |
| 3445 |
msgstr "上の例では、SSH を通じて移動するパケットを (<literal>!tcp.port == 22</literal> フィルタを使って) 除去しています。ここで詳細を表示されているパケットは HTTP 層で作られたものです。" |
| 3446 |
|
| 3447 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3448 |
msgid "<emphasis>TIP</emphasis> <command>wireshark</command> with no graphical interface: <command>tshark</command>" |
| 3449 |
msgstr "<emphasis>TIP</emphasis> グラフィカルインターフェースを持たない <command>wireshark</command>、<command>tshark</command>" |
| 3450 |
|
| 3451 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3452 |
msgid "<primary><command>tshark</command></primary>" |
| 3453 |
msgstr "<primary><command>tshark</command></primary>" |
| 3454 |
|
| 3455 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3456 |
msgid "When one cannot run a graphical interface, or does not wish to do so for whatever reason, a text-only version of <command>wireshark</command> also exists under the name <command>tshark</command> (in a separate <emphasis role=\"pkg\">tshark</emphasis> package). Most of the capture and decoding features are still available, but the lack of a graphical interface necessarily limits the interactions with the program (filtering packets after they've been captured, tracking of a given TCP connection, and so on). It can still be used as a first approach. If further manipulations are intended and require the graphical interface, the packets can be saved to a file and this file can be loaded into a graphical <command>wireshark</command> running on another machine." |
| 3457 |
msgstr "グラフィカルインターフェースを実行できない場合や何らかの理由で実行したくない場合に備えて、<command>wireshark</command> のテキスト版 <command>tshark</command> (<emphasis role=\"pkg\">tshark</emphasis> パッケージに分割されています) が存在します。キャプチャとデコード機能のほとんどを利用できますが、グラフィカルインターフェースがないことでプログラムとのやり取りが制限されます (たとえば、パケットがキャプチャされた後にフィルタをかけたり、特定の TCP 接続を追跡したりすることが不可能です)。しかし <command>tshark</command> を足掛かりとして使うことが可能です。さらなる操作が必要だったりグラフィカルインターフェースが必要な操作を行う場合、パケットをファイルに保存してそのファイルを別のマシンで実行されているグラフィカルな <command>wireshark</command> で読み込むことが可能です。" |
| 3458 |
|
| 3459 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3460 |
#~ msgid "<primary>TCP, port</primary>" |
| 3461 |
#~ msgstr "<primary>TCP、ポート</primary>" |
| 3462 |
|
| 3463 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3464 |
#~ msgid "<primary>UDP, port</primary>" |
| 3465 |
#~ msgstr "<primary>UDP、ポート</primary>" |
| 3466 |
|
| 3467 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3468 |
#~ msgid "<primary>SNAT</primary>" |
| 3469 |
#~ msgstr "<primary>SNAT</primary>" |
| 3470 |
|
| 3471 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3472 |
#~ msgid "<primary>DNAT</primary>" |
| 3473 |
#~ msgstr "<primary>DNAT</primary>" |
| 3474 |
|
| 3475 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3476 |
#, fuzzy |
| 3477 |
#~| msgid "<primary>X.509, certificate</primary>" |
| 3478 |
#~ msgid "<primary>certificates</primary>" |
| 3479 |
#~ msgstr "<primary>X.509</primary><secondary sortas=\"ショウメイショ\">証明書</secondary>" |
| 3480 |
|
| 3481 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3482 |
#~ msgid "<primary>X.509, certificate</primary>" |
| 3483 |
#~ msgstr "<primary>X.509</primary><secondary sortas=\"ショウメイショ\">証明書</secondary>" |
| 3484 |
|
| 3485 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3486 |
#~ msgid "<primary>SSH</primary>" |
| 3487 |
#~ msgstr "<primary>SSH</primary>" |
| 3488 |
|
| 3489 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3490 |
#~ msgid "<primary>Point-to-Point Tunneling Protocol</primary>" |
| 3491 |
#~ msgstr "<primary>Point-to-Point Tunneling Protocol</primary>" |
| 3492 |
|
| 3493 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3494 |
#, fuzzy |
| 3495 |
#~| msgid "<primary>gateway</primary>" |
| 3496 |
#~ msgid "<primary>net neutrality</primary>" |
| 3497 |
#~ msgstr "<primary>ゲートウェイ</primary>" |
| 3498 |
|
| 3499 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3500 |
#~ msgid "In the PPP case, creating a script that calls <command>wondershaper</command> in <filename>/etc/ppp/ip-up.d/</filename> will enable traffic control as soon as the connection is up." |
| 3501 |
#~ msgstr "PPP の場合、<filename>/etc/ppp/ip-up.d/</filename> 内に <command>wondershaper</command> を呼び出すスクリプトを作成することで、接続が開始された後の可能な限り早い時期にトラフィック制御を行うように設定できます。" |
| 3502 |
|
| 3503 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3504 |
#, fuzzy |
| 3505 |
#~| msgid "<primary><command>route</command></primary>" |
| 3506 |
#~ msgid "<primary><command>ip route</command></primary>" |
| 3507 |
#~ msgstr "<primary><command>route</command></primary>" |
| 3508 |
|
| 3509 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3510 |
#~ msgid "<primary>IPv6 firewall</primary>" |
| 3511 |
#~ msgstr "<primary>IPv6 ファイアウォール</primary>" |
| 3512 |
|
| 3513 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3514 |
#~ msgid "<literal>A</literal>: IPv4 address. <indexterm><primary>A, DNS record</primary></indexterm>" |
| 3515 |
#~ msgstr "<literal>A</literal>。IPv4 アドレスを意味します。<indexterm><primary>A、DNS レコード</primary></indexterm>" |
| 3516 |
|
| 3517 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3518 |
#~ msgid "<literal>AAAA</literal>: IPv6 address. <indexterm><primary>AAAA, DNS record</primary></indexterm>" |
| 3519 |
#~ msgstr "<literal>AAAA</literal>。IPv6 アドレスを意味します。<indexterm><primary>AAAA、DNS レコード</primary></indexterm>" |
| 3520 |
|
| 3521 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3522 |
#~ msgid "<primary>DNS record</primary>" |
| 3523 |
#~ msgstr "<primary>DNS レコード</primary>" |
| 3524 |
|
| 3525 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3526 |
#~ msgid "<primary>DHCP</primary>" |
| 3527 |
#~ msgstr "<primary>DHCP</primary>" |
| 3528 |
|
| 3529 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3530 |
#~ msgid "<emphasis>NOTE</emphasis> <emphasis>easy-rsa</emphasis> before <emphasis role=\"distribution\">Jessie</emphasis>" |
| 3531 |
#~ msgstr "<emphasis>NOTE</emphasis> <emphasis role=\"distribution\">Jessie</emphasis> 以前の <emphasis>easy-rsa</emphasis>" |
| 3532 |
|
| 3533 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3534 |
#~ msgid "In versions of Debian up to <emphasis role=\"distribution\">Wheezy</emphasis>, <emphasis>easy-rsa</emphasis> was distributed as part of the <emphasis role=\"pkg\">openvpn</emphasis> package, and its scripts were to be found under <filename>/usr/share/doc/openvpn/examples/easy-rsa/2.0/</filename>. Setting up a CA involved copying that directory, instead of using the <command>make-cadir</command> command as documented here." |
| 3535 |
#~ msgstr "<emphasis role=\"distribution\">Wheezy</emphasis> までの Debian のバージョンでは、<emphasis>easy-rsa</emphasis> は <emphasis role=\"pkg\">openvpn</emphasis> パッケージの一部として配布されており、<emphasis>easy-rsa</emphasis> のスクリプトは <filename>/usr/share/doc/openvpn/examples/easy-rsa/2.0/</filename> 以下に含まれていました。認証局を設定するには、ここで説明されているように <command>make-cadir</command> コマンドを使うのではなく、このディレクトリをコピーする必要がありました。" |
| 3536 |
|
| 3537 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3538 |
#~ msgid "" |
| 3539 |
#~ "\n" |
| 3540 |
#~ "<computeroutput>$ </computeroutput><userinput>vim vars\n" |
| 3541 |
#~ "</userinput><computeroutput>$ </computeroutput><userinput>grep KEY_ vars\n" |
| 3542 |
#~ "</userinput><computeroutput>export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`\n" |
| 3543 |
#~ "export KEY_DIR=\"$EASY_RSA/keys\"\n" |
| 3544 |
#~ "echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR\n" |
| 3545 |
#~ "export KEY_SIZE=2048\n" |
| 3546 |
#~ "export KEY_EXPIRE=3650\n" |
| 3547 |
#~ "export KEY_COUNTRY=\"FR\"\n" |
| 3548 |
#~ "export KEY_PROVINCE=\"Loire\"\n" |
| 3549 |
#~ "export KEY_CITY=\"Saint-Étienne\"\n" |
| 3550 |
#~ "export KEY_ORG=\"Falcot Corp\"\n" |
| 3551 |
#~ "export KEY_EMAIL=\"[email protected]\"\n" |
| 3552 |
#~ "export KEY_OU=\"Certificate authority\"\n" |
| 3553 |
#~ "export KEY_NAME=\"Certificate authority for Falcot Corp\"\n" |
| 3554 |
#~ "# If you'd like to sign all keys with the same Common Name, uncomment the KEY_CN export below\n" |
| 3555 |
#~ "# export KEY_CN=\"CommonName\"\n" |
| 3556 |
#~ "$ </computeroutput><userinput>. ./vars\n" |
| 3557 |
#~ "</userinput><computeroutput>NOTE: If you run ./clean-all, I will be doing a rm -rf on /home/roland/pki-falcot/keys\n" |
| 3558 |
#~ "$ </computeroutput><userinput>./clean-all\n" |
| 3559 |
#~ "</userinput>" |
| 3560 |
#~ msgstr "" |
| 3561 |
#~ "\n" |
| 3562 |
#~ "<computeroutput>$ </computeroutput><userinput>vim vars\n" |
| 3563 |
#~ "</userinput><computeroutput>$ </computeroutput><userinput>grep KEY_ vars\n" |
| 3564 |
#~ "</userinput><computeroutput>export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`\n" |
| 3565 |
#~ "export KEY_DIR=\"$EASY_RSA/keys\"\n" |
| 3566 |
#~ "echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR\n" |
| 3567 |
#~ "export KEY_SIZE=2048\n" |
| 3568 |
#~ "export KEY_EXPIRE=3650\n" |
| 3569 |
#~ "export KEY_COUNTRY=\"FR\"\n" |
| 3570 |
#~ "export KEY_PROVINCE=\"Loire\"\n" |
| 3571 |
#~ "export KEY_CITY=\"Saint-Étienne\"\n" |
| 3572 |
#~ "export KEY_ORG=\"Falcot Corp\"\n" |
| 3573 |
#~ "export KEY_EMAIL=\"[email protected]\"\n" |
| 3574 |
#~ "export KEY_OU=\"Certificate authority\"\n" |
| 3575 |
#~ "export KEY_NAME=\"Certificate authority for Falcot Corp\"\n" |
| 3576 |
#~ "# If you'd like to sign all keys with the same Common Name, uncomment the KEY_CN export below\n" |
| 3577 |
#~ "# export KEY_CN=\"CommonName\"\n" |
| 3578 |
#~ "$ </computeroutput><userinput>. ./vars\n" |
| 3579 |
#~ "</userinput><computeroutput>NOTE: If you run ./clean-all, I will be doing a rm -rf on /home/roland/pki-falcot/keys\n" |
| 3580 |
#~ "$ </computeroutput><userinput>./clean-all\n" |
| 3581 |
#~ "</userinput>" |
| 3582 |
|
| 3583 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3584 |
#~ msgid "" |
| 3585 |
#~ "\n" |
| 3586 |
#~ "<computeroutput>$ </computeroutput><userinput>./build-key-server vpn.falcot.com\n" |
| 3587 |
#~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n" |
| 3588 |
#~ ".....................................................................................................................+++\n" |
| 3589 |
#~ "...........+++\n" |
| 3590 |
#~ "writing new private key to 'vpn.falcot.com.key'\n" |
| 3591 |
#~ "-----\n" |
| 3592 |
#~ "You are about to be asked to enter information that will be incorporated\n" |
| 3593 |
#~ "into your certificate request.\n" |
| 3594 |
#~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 3595 |
#~ "There are quite a few fields but you can leave some blank\n" |
| 3596 |
#~ "For some fields there will be a default value,\n" |
| 3597 |
#~ "If you enter '.', the field will be left blank.\n" |
| 3598 |
#~ "-----\n" |
| 3599 |
#~ "Country Name (2 letter code) [FR]:\n" |
| 3600 |
#~ "State or Province Name (full name) [Loire]:\n" |
| 3601 |
#~ "Locality Name (eg, city) [Saint-Étienne]:\n" |
| 3602 |
#~ "Organization Name (eg, company) [Falcot Corp]:\n" |
| 3603 |
#~ "Organizational Unit Name (eg, section) [Certificate authority]:\n" |
| 3604 |
#~ "Common Name (eg, your name or your server's hostname) [vpn.falcot.com]:\n" |
| 3605 |
#~ "Name [Certificate authority for Falcot Corp]:\n" |
| 3606 |
#~ "Email Address [[email protected]]:\n" |
| 3607 |
#~ "\n" |
| 3608 |
#~ "Please enter the following 'extra' attributes\n" |
| 3609 |
#~ "to be sent with your certificate request\n" |
| 3610 |
#~ "A challenge password []:\n" |
| 3611 |
#~ "An optional company name []:\n" |
| 3612 |
#~ "Using configuration from /home/roland/pki-falcot/openssl-1.0.0.cnf\n" |
| 3613 |
#~ "Check that the request matches the signature\n" |
| 3614 |
#~ "Signature ok\n" |
| 3615 |
#~ "The Subject's Distinguished Name is as follows\n" |
| 3616 |
#~ "countryName :PRINTABLE:'FR'\n" |
| 3617 |
#~ "stateOrProvinceName :PRINTABLE:'Loire'\n" |
| 3618 |
#~ "localityName :T61STRING:'Saint-\\0xFFFFFFC3\\0xFFFFFF89tienne'\n" |
| 3619 |
#~ "organizationName :PRINTABLE:'Falcot Corp'\n" |
| 3620 |
#~ "organizationalUnitName:PRINTABLE:'Certificate authority'\n" |
| 3621 |
#~ "commonName :PRINTABLE:'vpn.falcot.com'\n" |
| 3622 |
#~ "name :PRINTABLE:'Certificate authority for Falcot Corp'\n" |
| 3623 |
#~ "emailAddress :IA5STRING:'[email protected]'\n" |
| 3624 |
#~ "Certificate is to be certified until Mar 6 14:54:56 2025 GMT (3650 days)\n" |
| 3625 |
#~ "Sign the certificate? [y/n]:</computeroutput><userinput>y\n" |
| 3626 |
#~ "</userinput><computeroutput>\n" |
| 3627 |
#~ "\n" |
| 3628 |
#~ "1 out of 1 certificate requests certified, commit? [y/n]</computeroutput><userinput>y\n" |
| 3629 |
#~ "</userinput><computeroutput>Write out database with 1 new entries\n" |
| 3630 |
#~ "Data Base Updated\n" |
| 3631 |
#~ "$ </computeroutput><userinput>./build-dh\n" |
| 3632 |
#~ "</userinput><computeroutput>Generating DH parameters, 2048 bit long safe prime, generator 2\n" |
| 3633 |
#~ "This is going to take a long time\n" |
| 3634 |
#~ "[…]\n" |
| 3635 |
#~ "</computeroutput>" |
| 3636 |
#~ msgstr "" |
| 3637 |
#~ "\n" |
| 3638 |
#~ "<computeroutput>$ </computeroutput><userinput>./build-key-server vpn.falcot.com\n" |
| 3639 |
#~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n" |
| 3640 |
#~ ".....................................................................................................................+++\n" |
| 3641 |
#~ "...........+++\n" |
| 3642 |
#~ "writing new private key to 'vpn.falcot.com.key'\n" |
| 3643 |
#~ "-----\n" |
| 3644 |
#~ "You are about to be asked to enter information that will be incorporated\n" |
| 3645 |
#~ "into your certificate request.\n" |
| 3646 |
#~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 3647 |
#~ "There are quite a few fields but you can leave some blank\n" |
| 3648 |
#~ "For some fields there will be a default value,\n" |
| 3649 |
#~ "If you enter '.', the field will be left blank.\n" |
| 3650 |
#~ "-----\n" |
| 3651 |
#~ "Country Name (2 letter code) [FR]:\n" |
| 3652 |
#~ "State or Province Name (full name) [Loire]:\n" |
| 3653 |
#~ "Locality Name (eg, city) [Saint-Étienne]:\n" |
| 3654 |
#~ "Organization Name (eg, company) [Falcot Corp]:\n" |
| 3655 |
#~ "Organizational Unit Name (eg, section) [Certificate authority]:\n" |
| 3656 |
#~ "Common Name (eg, your name or your server's hostname) [vpn.falcot.com]:\n" |
| 3657 |
#~ "Name [Certificate authority for Falcot Corp]:\n" |
| 3658 |
#~ "Email Address [[email protected]]:\n" |
| 3659 |
#~ "\n" |
| 3660 |
#~ "Please enter the following 'extra' attributes\n" |
| 3661 |
#~ "to be sent with your certificate request\n" |
| 3662 |
#~ "A challenge password []:\n" |
| 3663 |
#~ "An optional company name []:\n" |
| 3664 |
#~ "Using configuration from /home/roland/pki-falcot/openssl-1.0.0.cnf\n" |
| 3665 |
#~ "Check that the request matches the signature\n" |
| 3666 |
#~ "Signature ok\n" |
| 3667 |
#~ "The Subject's Distinguished Name is as follows\n" |
| 3668 |
#~ "countryName :PRINTABLE:'FR'\n" |
| 3669 |
#~ "stateOrProvinceName :PRINTABLE:'Loire'\n" |
| 3670 |
#~ "localityName :T61STRING:'Saint-\\0xFFFFFFC3\\0xFFFFFF89tienne'\n" |
| 3671 |
#~ "organizationName :PRINTABLE:'Falcot Corp'\n" |
| 3672 |
#~ "organizationalUnitName:PRINTABLE:'Certificate authority'\n" |
| 3673 |
#~ "commonName :PRINTABLE:'vpn.falcot.com'\n" |
| 3674 |
#~ "name :PRINTABLE:'Certificate authority for Falcot Corp'\n" |
| 3675 |
#~ "emailAddress :IA5STRING:'[email protected]'\n" |
| 3676 |
#~ "Certificate is to be certified until Mar 6 14:54:56 2025 GMT (3650 days)\n" |
| 3677 |
#~ "Sign the certificate? [y/n]:</computeroutput><userinput>y\n" |
| 3678 |
#~ "</userinput><computeroutput>\n" |
| 3679 |
#~ "\n" |
| 3680 |
#~ "1 out of 1 certificate requests certified, commit? [y/n]</computeroutput><userinput>y\n" |
| 3681 |
#~ "</userinput><computeroutput>Write out database with 1 new entries\n" |
| 3682 |
#~ "Data Base Updated\n" |
| 3683 |
#~ "$ </computeroutput><userinput>./build-dh\n" |
| 3684 |
#~ "</userinput><computeroutput>Generating DH parameters, 2048 bit long safe prime, generator 2\n" |
| 3685 |
#~ "This is going to take a long time\n" |
| 3686 |
#~ "[…]\n" |
| 3687 |
#~ "</computeroutput>" |
| 3688 |
|
| 3689 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3690 |
#~ msgid "" |
| 3691 |
#~ "\n" |
| 3692 |
#~ "<computeroutput>$ </computeroutput><userinput>./build-key JoeSmith\n" |
| 3693 |
#~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n" |
| 3694 |
#~ "................................+++\n" |
| 3695 |
#~ "..............................................+++\n" |
| 3696 |
#~ "writing new private key to 'JoeSmith.key'\n" |
| 3697 |
#~ "-----\n" |
| 3698 |
#~ "You are about to be asked to enter information that will be incorporated\n" |
| 3699 |
#~ "into your certificate request.\n" |
| 3700 |
#~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 3701 |
#~ "There are quite a few fields but you can leave some blank\n" |
| 3702 |
#~ "For some fields there will be a default value,\n" |
| 3703 |
#~ "If you enter '.', the field will be left blank.\n" |
| 3704 |
#~ "-----\n" |
| 3705 |
#~ "Country Name (2 letter code) [FR]:\n" |
| 3706 |
#~ "State or Province Name (full name) [Loire]:\n" |
| 3707 |
#~ "Locality Name (eg, city) [Saint-Étienne]:\n" |
| 3708 |
#~ "Organization Name (eg, company) [Falcot Corp]:\n" |
| 3709 |
#~ "Organizational Unit Name (eg, section) [Certificate authority]:</computeroutput><userinput>Development unit\n" |
| 3710 |
#~ "</userinput><computeroutput>Common Name (eg, your name or your server's hostname) [JoeSmith]:</computeroutput><userinput>Joe Smith\n" |
| 3711 |
#~ "</userinput><computeroutput>[…]</computeroutput>" |
| 3712 |
#~ msgstr "" |
| 3713 |
#~ "\n" |
| 3714 |
#~ "<computeroutput>$ </computeroutput><userinput>./build-key JoeSmith\n" |
| 3715 |
#~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n" |
| 3716 |
#~ "................................+++\n" |
| 3717 |
#~ "..............................................+++\n" |
| 3718 |
#~ "writing new private key to 'JoeSmith.key'\n" |
| 3719 |
#~ "-----\n" |
| 3720 |
#~ "You are about to be asked to enter information that will be incorporated\n" |
| 3721 |
#~ "into your certificate request.\n" |
| 3722 |
#~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" |
| 3723 |
#~ "There are quite a few fields but you can leave some blank\n" |
| 3724 |
#~ "For some fields there will be a default value,\n" |
| 3725 |
#~ "If you enter '.', the field will be left blank.\n" |
| 3726 |
#~ "-----\n" |
| 3727 |
#~ "Country Name (2 letter code) [FR]:\n" |
| 3728 |
#~ "State or Province Name (full name) [Loire]:\n" |
| 3729 |
#~ "Locality Name (eg, city) [Saint-Étienne]:\n" |
| 3730 |
#~ "Organization Name (eg, company) [Falcot Corp]:\n" |
| 3731 |
#~ "Organizational Unit Name (eg, section) [Certificate authority]:</computeroutput><userinput>Development unit\n" |
| 3732 |
#~ "</userinput><computeroutput>Common Name (eg, your name or your server's hostname) [JoeSmith]:</computeroutput><userinput>Joe Smith\n" |
| 3733 |
#~ "</userinput><computeroutput>[…]</computeroutput>" |
| 3734 |
|
| 3735 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3736 |
#~ msgid "<primary><command>racoon</command></primary>" |
| 3737 |
#~ msgstr "<primary><command>racoon</command></primary>" |
| 3738 |
|
| 3739 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3740 |
# Tag: PTAL; |
| 3741 |
#~ msgid "IPsec, despite being the standard in IP VPNs, is rather more involved in its implementation. The IPsec engine itself is integrated in the Linux kernel; the required user-space parts, the control and configuration tools, are provided by the <emphasis role=\"pkg\">ipsec-tools</emphasis> package. In concrete terms, each host's <filename>/etc/ipsec-tools.conf</filename> contains the parameters for <emphasis>IPsec tunnels</emphasis> (or <emphasis>Security Associations</emphasis>, in the IPsec terminology) that the host is concerned with; the <command>/etc/init.d/setkey</command> script provides a way to start and stop a tunnel (each tunnel is a secure link to another host connected to the virtual private network). This file can be built by hand from the documentation provided by the <citerefentry><refentrytitle>setkey</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page. However, explicitly writing the parameters for all hosts in a non-trivial set of machines quickly becomes an arduous task, since the number of tunnels grows fast. Installing an IKE daemon (for <emphasis>IPsec Key Exchange</emphasis>) such as <emphasis role=\"pkg\">racoon</emphasis> or <emphasis role=\"pkg\">strongswan</emphasis> makes the process much simpler by bringing administration together at a central point, and more secure by rotating the keys periodically." |
| 3742 |
#~ msgstr "IPsec は IP VPN の標準的ツールになりつつあるにも関わらず、IPsec の実装は複雑です。IPsec エンジンそれ自身は Linux カーネルに統合されています。ユーザ空間部分で必要となる制御と設定ツールは <emphasis role=\"pkg\">ipsec-tools</emphasis> パッケージに含まれています。具体的には、それぞれのホストの <filename>/etc/ipsec-tools.conf</filename> にはホストが接続する <emphasis>IPsec トンネル</emphasis> (IPsec 用語で <emphasis>Security Association</emphasis>) のパラメータが含まれます。<command>/etc/init.d/setkey</command> スクリプトを使うことで、トンネルを開始したり停止することが可能です (それぞれのトンネルは仮想ネットワークに接続された他のホストと安全なリンクを確立しています)。このファイルは <citerefentry><refentrytitle>setkey</refentrytitle> <manvolnum>8</manvolnum></citerefentry> マニュアルページに含まれる文書を使って手作業で作ることも可能です。しかしながら、多数のマシン群にすべてのホスト用のパラメータを明示的に書くことはすぐに難しい作業になります。なぜなら、トンネルの数はすぐに増えるからです。たとえば <emphasis role=\"pkg\">racoon</emphasis> や <emphasis role=\"pkg\">strongswan</emphasis> などの IKE (<emphasis>IPsec Key Exchange</emphasis> の略語) デーモンをインストールすることで、一元管理による作業の簡素化と鍵の定期的な切り替えによる作業の安全化が可能になります。" |
| 3743 |
|
| 3744 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3745 |
#~ msgid "Normal-Service (0);" |
| 3746 |
#~ msgstr "通常のサービス (0)。" |
| 3747 |
|
| 3748 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3749 |
#~ msgid "Minimize-Cost (2);" |
| 3750 |
#~ msgstr "コストの最小化 (2)。" |
| 3751 |
|
| 3752 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3753 |
#~ msgid "Maximize-Reliability (4);" |
| 3754 |
#~ msgstr "信頼度の最大化 (4)。" |
| 3755 |
|
| 3756 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3757 |
#~ msgid "Maximize-Throughput (8);" |
| 3758 |
#~ msgstr "速度の最大化 (8)。" |
| 3759 |
|
| 3760 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3761 |
#~ msgid "Minimize-Delay (16)." |
| 3762 |
#~ msgstr "遅延の最小化 (16)。" |
| 3763 |
|
| 3764 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3765 |
#~ msgid "<primary>ToS</primary>" |
| 3766 |
#~ msgstr "<primary>ToS</primary>" |
| 3767 |
|
| 3768 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3769 |
#~ msgid "<primary>Type of Service</primary>" |
| 3770 |
#~ msgstr "<primary>Type of Service</primary>" |
| 3771 |
|
| 3772 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3773 |
#~ msgid "" |
| 3774 |
#~ "\n" |
| 3775 |
#~ "iptables -t mangle -A PREROUTING -p tcp --sport ssh -j TOS --set-tos Minimize-Delay\n" |
| 3776 |
#~ "iptables -t mangle -A PREROUTING -p tcp --dport ssh -j TOS --set-tos Minimize-Delay" |
| 3777 |
#~ msgstr "" |
| 3778 |
#~ "\n" |
| 3779 |
#~ "iptables -t mangle -A PREROUTING -p tcp --sport ssh -j TOS --set-tos Minimize-Delay\n" |
| 3780 |
#~ "iptables -t mangle -A PREROUTING -p tcp --dport ssh -j TOS --set-tos Minimize-Delay" |
| 3781 |
|
| 3782 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3783 |
#~ msgid "<primary>BABEL wireless mesh routing</primary>" |
| 3784 |
#~ msgstr "<primary>BABEL wireless mesh routing</primary>" |
| 3785 |
|
| 3786 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3787 |
#~ msgid "<primary><command>babeld</command></primary>" |
| 3788 |
#~ msgstr "<primary><command>babeld</command></primary>" |
| 3789 |
|
| 3790 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3791 |
#~ msgid "Daemons are enabled by editing the <filename>/etc/quagga/daemons</filename> file and creating the appropriate configuration file in <filename>/etc/quagga/</filename>; this configuration file must be named after the daemon, with a <filename>.conf</filename> extension, and belong to the <literal>quagga</literal> user and the <literal>quaggavty</literal> group, in order for the <filename>/etc/init.d/quagga</filename> script to invoke the daemon." |
| 3792 |
#~ msgstr "これらのデーモンを有効化するには、<filename>/etc/quagga/daemons</filename> ファイルを編集し、適切な設定ファイルを <filename>/etc/quagga/</filename> の中に作成してください。さらに、この設定ファイルはデーモンにちなんで命名され、<filename>.conf</filename> 拡張子を付けられ、<literal>quagga</literal> ユーザと <literal>quaggavty</literal> グループに所有されなければいけません。これは <filename>/etc/init.d/quagga</filename> スクリプトが対象のデーモンを呼び出せるようにするためです。" |
| 3793 |
|
| 3794 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3795 |
#~ msgid "IPv6 connections can be restricted, in the same fashion as for IPv4: the standard Debian kernels include an adaptation of <emphasis>netfilter</emphasis> for IPv6. This IPv6-enabled <emphasis>netfilter</emphasis> is configured in a similar fashion to its IPv4 counterpart, except the program to use is <command>ip6tables</command> instead of <command>iptables</command>." |
| 3796 |
#~ msgstr "IPv6 接続は IPv4 と同様の方法で制限することが可能です。すなわち 標準的な Debian カーネルは IPv6 用の <emphasis>netfilter</emphasis> に対応しています。IPv6 対応の <emphasis>netfilter</emphasis> を設定するには IPv4 でやったのと同様の方法を使います。ただし、<command>iptables</command> の代わりに <command>ip6tables</command> を使います。" |
| 3797 |
|
| 3798 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3799 |
#~ msgid "<primary>Freenet6</primary>" |
| 3800 |
#~ msgstr "<primary>Freenet6</primary>" |
| 3801 |
|
| 3802 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3803 |
#~ msgid "<primary>Gogo6</primary>" |
| 3804 |
#~ msgstr "<primary>gogo6</primary>" |
| 3805 |
|
| 3806 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3807 |
#~ msgid "To use a Freenet6 tunnel, you need to register for a Freenet6 Pro account on the website, then install the <emphasis role=\"pkg\">gogoc</emphasis> package and configure the tunnel. This requires editing the <filename>/etc/gogoc/gogoc.conf</filename> file: <literal>userid</literal> and <literal>password</literal> lines received by e-mail should be added, and <literal>server</literal> should be replaced with <literal>authenticated.freenet6.net</literal>." |
| 3808 |
#~ msgstr "Freenet6 トンネルを使うには、ウェブサイトから Freenet6 Pro アカウントを登録し、<emphasis role=\"pkg\">gogoc</emphasis> パッケージをインストールし、トンネルを設定します。<filename>/etc/gogoc/gogoc.conf</filename> ファイルを編集する必要があります。具体的に言えば、電子メールで受け取った <literal>userid</literal> と <literal>password</literal> 行を追加し、<literal>server</literal> を <literal>authenticated.freenet6.net</literal> に置き替えます。" |
| 3809 |
|
| 3810 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3811 |
#~ msgid "IPv6 connectivity is proposed to all machines on a local network by adding the three following directives to the <filename>/etc/gogoc/gogoc.conf</filename> file (assuming the local network is connected to the eth0 interface):" |
| 3812 |
#~ msgstr "IPv6 接続をローカルネットワークのすべてのマシンに提供するには、以下の 3 つの指示文を <filename>/etc/gogoc/gogoc.conf</filename> ファイルに追加します (ここで、ローカルネットワークは eth0 インターフェースに接続されていると仮定します)。" |
| 3813 |
|
| 3814 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3815 |
#~ msgid "" |
| 3816 |
#~ "\n" |
| 3817 |
#~ "host_type=router\n" |
| 3818 |
#~ "prefixlen=56\n" |
| 3819 |
#~ "if_prefix=eth0" |
| 3820 |
#~ msgstr "" |
| 3821 |
#~ "\n" |
| 3822 |
#~ "host_type=router\n" |
| 3823 |
#~ "prefixlen=56\n" |
| 3824 |
#~ "if_prefix=eth0" |
| 3825 |
|
| 3826 |
#~ msgid "<emphasis>CULTURE</emphasis> <command>ethereal</command> and <command>wireshark</command>" |
| 3827 |
#~ msgstr "<emphasis>CULTURE</emphasis> <command>ethereal</command> と <command>wireshark</command>" |
| 3828 |
|
| 3829 |
#~ msgid "<primary><command>ethereal</command></primary>" |
| 3830 |
#~ msgstr "<primary><command>ethereal</command></primary>" |
| 3831 |
|
| 3832 |
#~ msgid "<primary><command>tethereal</command></primary>" |
| 3833 |
#~ msgstr "<primary><command>tethereal</command></primary>" |
| 3834 |
|
| 3835 |
#~ msgid "<command>wireshark</command> seems to be relatively young; however, it is only the new name for a software application previously known as <command>ethereal</command>. When its main developer left the company where he was employed, he was not able to arrange for the transfer of the registered trademark. As an alternative he went for a name change; only the name and the icons for the software actually changed." |
| 3836 |
#~ msgstr "<command>wireshark</command> は比較的若いように見えます。しかしながら、<command>wireshark</command> は <command>ethereal</command> として知られていたソフトウェアの新しい名前に過ぎません。<command>ethereal</command> の主開発者は雇用されていた会社を離れた時、登録済みの商標の移動を手配できませんでした。代案として、彼は名前を変えました。従って実際のところ、<command>wireshark</command> は <command>ethereal</command> の名前とアイコンだけを変えたものに過ぎません。" |
| 3837 |
|
| 3838 |
#~ msgid "Presentation" |
| 3839 |
#~ msgstr "プレゼンテーション" |