Language Translated Untranslated Untranslated words Checks Suggestions Comments
English This translation is used for source strings. This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause
Chinese (Simplified) (zh_CN) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 6% 56 2,587
Chinese (Traditional) (zh_TW) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 3% 58 2,589
Dutch (nl_NL) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 60 2,594
French (fr_FR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 60 2,594
German (de_DE) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 59 2,593
Italian (it_IT) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 60 2,594
Norwegian Bokmål This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 59 2,592
Persian This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 60 2,594
Portuguese (Brazil) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 28% 43 2,423 4 9
Spanish This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 28% 43 2,423 6
Turkish (tr_TR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 3% 58 2,589
Please sign in to see the alerts.
Project website docs.freebsd.org/en
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
Translation license BSD 2-Clause "Simplified" License
Filemask documentation/content/*/articles/filtering-bridges/_index.po
Languages 12
Source strings 60
Source words 2,594
Source characters 15,268
Hosted strings 720
Hosted words 31,128
Hosted characters 183,216
'''
'''
3 days ago
Abstract
摘要
3 days ago
New contributor 3 days ago
User avatar None

Automatic translation

Documentation / articles/filtering-bridges/_indexSpanish

Many parts of this article have been taken, updated and adapted from an old text about bridging, edited by Nick Sayer. A pair of inspirations are due to an introduction on bridging by Steve Peterson.
Muchas partes de este artículo han sido obtenidas, actualizadas y adaptadas de un texto antiguo sobre el bridging, editado por Nick Sayer. Unas cuantas ideas muy inspiradoras vienen de una introducción sobre el bridging que escribió Steve Peterson.
3 days ago
New contributor 3 days ago
User avatar None

Automatic translation

Documentation / articles/filtering-bridges/_indexSpanish

The only other thing that is a little weird that you may have noticed is that there is a rule to let the bridge machine speak, and another for internal hosts. Remember that this is because the two sets of traffic will take different paths through the kernel and into the packet filter. The inside net will go through the bridge, while the local machine will use the normal IP stack to speak. Thus the two rules to handle the different cases. The `in via fxp0` rules work for both paths. In general, if you use `in via` rules throughout the filter, you will need to make an exception for locally generated packets, because they did not come in via any of our interfaces.
Lo único raro que puede haber notado es que existe una regla para permitir que la máquina que hace de bridge hable y otra para los hosts internos. Recuerde que esto sucede porque los dos conjuntos de tráfico tendrán diferentes rutas a través del kernel y del filtro de paquetes. La red interna pasará por el bridge, mientras que la máquina local utilizará el stack normal de IP para hablar. Por lo tanto, cada regla se ocupa de una cosa diferente. Las reglas <literal>in via fxp0</literal> funcionan para ambas rutas. En general, si utiliza las reglas <option>in via</option> en todo el filtro, debe añadir una excepción para los paquetes generados localmente, ya que no llegaron a través de ninguna de nuestras interfaces.
3 days ago
New contributor 3 days ago
User avatar None

Automatic translation

Documentation / articles/filtering-bridges/_indexSpanish

People that are used to setting up firewalls are probably also used to either having a `reset` or a `forward` rule for ident packets (TCP port 113). Unfortunately, this is not an applicable option with the bridge, so the best thing is to simply pass them to their destination. As long as that destination machine is not running an ident daemon, this is relatively harmless. The alternative is dropping connections on port 113, which creates some problems with services like IRC (the ident probe must timeout).
Quienes estén acostumbrados a configurar firewalls probablemente también suelan usar una regla <option>reset</option> o <option>forward</option> para los paquetes ident (<acronym>TCP</acronym> puerto 113). Por desgracia esta no es una opción válida con el bridge, por lo tanto la mejor opción es simplemente pasarlos a su destino. A menos que la máquina de destino esté ejecutando un dæmon ident es realmente inofensivo. La alternativa es eliminar las conexiones en el puerto 113, lo que creará algunos problemas con servicios como <acronym>IRC</acronym> (el probe del ident dará timeout).
3 days ago
New contributor 3 days ago
User avatar None

Automatic translation

Documentation / articles/filtering-bridges/_indexSpanish

The last rule seems to be an exact duplicate of the default rule, that is, do not let anything pass that is not specifically allowed. But there is a difference: all suspected traffic will be logged.
La última regla parece ser un duplicado exacto de la regla predeterminada, es decir, no dejar pasar nada que no esté específicamente permitido. Pero hay una diferencia: todo tráfico sospechoso será registrado.
3 days ago
Browse all component changes

Daily activity

Daily activity

Weekly activity

Weekly activity