概览

项目网站 docs.freebsd.org/en
翻译许可证 BSD 2-Clause "Simplified" License
翻译进程
  • 可以直接翻译。
  • 可以提出翻译建议。
  • 只允许指定的用户贡献。
  • 该翻译使用双语文件。
文件掩码 documentation/content/*/articles/filtering-bridges/_index.po
翻译文件 下载 documentation/content/nb_NO/articles/filtering-bridges/_index.po
最后更改 2021年4月6日 01:08
最后作者 Anonymous

字符串统计数据

字符串百分比 托管的字符串数 字数百分比 托管的单词数 字符百分比 托管的字符数
总数 61 2591 15287
已翻译数 1% 1 1% 2 1% 20
需要编辑 0% 0 0% 0 0% 0
只读 0% 0 0% 0 0% 0
未通过的检查数 0% 0 0% 0 0% 0
带有建议的字符串数 0% 0 0% 0 0% 0
未翻译的字符串数 98% 60 99% 2589 99% 15267
过去 12 个月 上一年

过去 12 个月内的活动

0 个更改 0 个更改 0 个更改 0 个更改 9 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 3 个更改 0 个更改 0 个更改 0 个更改
三月 四月 五月 六月 七月 八月 九月 十月 十一月 十二月 一月 二月

快速数字

2591
托管的单词数
61
托管的字符串数
1%
已翻译
0
贡献者
及之前 30 天

过去 30 天的趋势

—
托管的单词数
+100%
—
托管的字符串数
+100%
—
已翻译
+1%
—
贡献者
—
用户头像 无

要翻译的新字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

翻译中出现了 1 条要翻译的新字符串。 1 年前
用户头像 无

资源更新

Documentation / articles/filtering-bridges/_index — 书面挪威语

文件 documentation/content/nb_NO/articles/filtering-bridges/_index.po 已更改。 1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

New in FreeBSD 4.0, is the concept of stateful filtering. This is a big improvement for UDP traffic, which typically is a request going out, followed shortly thereafter by a response with the same set of IP addresses and port numbers (but with source and destination reversed, of course). For firewalls that have no statekeeping, there is almost no way to deal with this sort of traffic as a single session. But with a firewall that can "remember" an outgoing UDP packet and, for the next few minutes, allow a response, handling UDP services is trivial. The following example shows how to do it. It is possible to do the same thing with TCP packets. This allows you to avoid some denial of service attacks and other nasty tricks, but it also typically makes your state table grow quickly in size.
 
1 年前
用户头像 无

要翻译的新字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

翻译中出现了 7 条要翻译的新字符串。 1 年前
用户头像 无

资源更新

Documentation / articles/filtering-bridges/_index — 书面挪威语

文件 documentation/content/nb_NO/articles/filtering-bridges/_index.po 已更改。 1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

There are two rules for passing SMTP and DNS traffic towards the mail server and the name server, if you have them. Obviously the whole rule set should be flavored to personal taste, this is only a specific example (rule format is described accurately in the man:ipfw[8] man page). Note that for "relay" and "ns" to work, name service lookups must work _before_ the bridge is enabled. This is an example of making sure that you set the IP on the correct network card. Alternatively it is possible to specify the IP address instead of the host name (required if the machine is IP-less).
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

Now it is time to create your own file with custom firewall rules, to secure the inside network. There will be some complication in doing this because not all of the firewall functionalities are available on bridged packets. Furthermore, there is a difference between the packets that are in the process of being forwarded and packets that are being received by the local machine. In general, incoming packets are run through the firewall only once, not twice as is normally the case; in fact they are filtered only upon receipt, so rules that use `out` or `xmit` will never match. Personally, I use `in via` which is an older syntax, but one that has a sense when you read it. Another limitation is that you are restricted to use only `pass` or `drop` commands for packets filtered by a bridge. Sophisticated things like `divert`, `forward` or `reject` are not available. Such options can still be used, but only on traffic to or from the bridge machine itself (if it has an IP address).
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

At this point you should be able to insert the machine between two sets of hosts without compromising any communication abilities between them. If so, the next step is to add the `net.link.ether.bridge._[blah]_=_[blah]_` portions of these rows to the [.filename]#/etc/sysctl.conf# file, to have them execute at startup.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

There is another important thing to know. When running IP over Ethernet, there are actually two Ethernet protocols in use: one is IP, the other is ARP. ARP does the conversion of the IP address of a host into its Ethernet address (MAC layer). To allow the communication between two hosts separated by the bridge, it is necessary that the bridge will forward ARP packets. Such protocol is not included in the IP layer, since it exists only with IP over Ethernet. The FreeBSD firewall filters exclusively on the IP layer and therefore all non-IP packets (ARP included) will be forwarded without being filtered, even if the firewall is configured to not permit anything.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/filtering-bridges/_index — 书面挪威语

Before rebooting to load the new kernel or the required modules (according to the previously chosen installation method), you have to make some changes to the [.filename]#/etc/rc.conf# configuration file. The default rule of the firewall is to reject all IP packets. Initially we will set up an `open` firewall, to verify its operation without any issue related to packet filtering (in case you are going to execute this procedure remotely, such configuration will avoid you to remain isolated from the network). Put these lines in [.filename]#/etc/rc.conf#:
 
1 年前
浏览翻译的所有变化