Translation status

61 Strings 88%
Browse Translate
2,592 Words 73%

Strings status

61
All strings — 2,592 words Browse Translate Zen
54
Translated strings — 1,909 words Browse Translate Zen
7
Unfinished strings — 683 words Browse Translate Zen
7
Strings marked for edit — 683 words Browse Translate Zen
7
Unfinished strings without suggestions — 683 words Browse Translate Zen
1
Strings with any failing checks — 1 word Browse Translate Zen
1
Translated strings with any failing checks — 1 word Browse Translate Zen
14
Translated strings with dismissed checks — 375 words Browse Translate Zen
1
Failing check: Inconsistent — 1 word Browse Translate Zen
1
Strings with comments — 13 words Browse Translate Zen
61
Strings without a label — 2,592 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
books/arch-handbook/partii This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 6 37 2 0 0 0
books/developers-handbook/policies/_index This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. This translation is locked. BSD-2-Clause 0% 93 2,145 13,148 91 2 0 0
books/handbook/colophon This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 3 25 166 3 0 0 0
books/arch-handbook/partiii This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 4 30 2 1 0 0
books/handbook/wayland/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 135 4,028 26,832 135 0 0 0
books/fdp-primer/see-also/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 18 77 865 18 0 0 0
books/developers-handbook/kerneldebug/_index This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 210 5,085 33,598 210 0 0 0
books/fdp-primer/rosetta/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 62 417 4,051 62 0 0 0
books/developers-handbook/partiv This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 4 35 2 0 0 0
articles/license-guide/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 89 2,782 18,589 89 1 0 0
Browse all components

Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/articles/filtering-bridges/_index.po
Translation file Download documentation/content/es/articles/filtering-bridges/_index.po
Last change May 21, 2023, 6:17 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 61 2,592 15,293
Translated 88% 54 73% 1,909 73% 11,211
Needs editing 11% 7 26% 683 26% 4,082
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 1 1% 3
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

4 changes 0 changes 2 changes 2 changes 0 changes 0 changes 2 changes 0 changes 58 changes 0 changes 7 changes 0 changes 0 changes 0 changes 0 changes 1 change 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 16 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

2,592
Hosted words
61
Hosted strings
88%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+97%
Hosted words
+100%
+100%
Hosted strings
—
+88%
Translated
—
+100%
Contributors
—
User avatar None

New strings to translate

Documentation / articles/filtering-bridges/_index — Spanish

7 new strings to translate appeared to the translation. 11 days ago
User avatar None

Resource update

Documentation / articles/filtering-bridges/_index — Spanish

The "documentation/content/es/articles/filtering-bridges/_index.po" file was changed. 11 days ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Spanish

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).
Hay dos reglas para pasar el tráfico SMTP y DNS hacia el servidor de correo y el servidor de nombres si los tienes. Obviamente el conjunto entero de reglas debería estar personalizado al estilo de cada uno, esto es sólo un ejemplo específico (el formato de las reglas está descrito con detalle en la página de manual de man:ipfw[8]). Como alternativa es posible especificar la dirección IP en lugar del nombre del host (requerido si la máquina no tiene IP).
11 days ago
User avatar None

Source string changed

Documentation / articles/filtering-bridges/_index — Spanish

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 in order 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).
11 days ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Spanish

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).
Ahora es el momento de crear tu propio archivo de configuración con las reglas personalizadas del firewall para proteger la red interna. Te encontrarás con algunas complicaciones porque no todas las funcionalidades del firewall están disponibles en los paquetes bridge. Hay además una diferencia entre los paquetes que están en proceso de reenvío y los paquetes que estás recibiendo la máquina local. En general, los paquetes de entrada pasan por el firewall solo una vez, no dos veces, como suele ser el caso; en realidad se filtran solo después de la recepción, por lo que las reglas que usan `out` o `xmit` nunca coincidirán. Yo utilizo`in via`, que es una sintaxis más antigua pero tiene sentido cuando la lees. Otra limitación es que solo puedes usar solo los comandos `pass` o `reject` para los paquetes filtrados por un bridge. Opciones más complejas como `divert`, `forward` o `reject` no están disponibles. Estas opciones pueden seguir utilizándose, pero solo en el tráfico hacia o desde la propia máquina bridge (si tiene una dirección IP).
11 days ago
User avatar None

Source string changed

Documentation / articles/filtering-bridges/_index — Spanish

Now it is time to create your own file with custom firewall rules, in order 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).
11 days ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Spanish

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.
En este punto deberías poder insertar la máquina entre dos conjuntos de hosts sin comprometer las habilidades de comunicación entre ellas. Si es así, el siguiente paso es añadir las partes `net.link.ether.bridge._[blah]_=_[blah]_` de estas filas al fichero [.filename]#/etc/sysctl.conf# para que se ejecuten en el arranque.
11 days ago
User avatar None

Source string changed

Documentation / articles/filtering-bridges/_index — Spanish

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, in order to have them execute at startup.
11 days ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Spanish

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.
Hay otra cosa importante que hay que saber. Cuando se ejecuta IP over Ethernet, en realidad hay dos protocolos Ethernet en uso: uno es IP, el otro es ARP. ARP realiza la conversión de la dirección IP de un host a su dirección de Ethernet (capa MAC). Para permitir la comunicación entre dos hosts separados por el bridge, es necesario que el bridge reenvíe los paquetes ARP. Dicho protocolo no está incluido en la capa IP, ya que solo existe con IP over Ethernet. El firewall de FreeBSD filtra exclusivamente en la capa IP y, por lo tanto, todos los paquetes no IP (ARP incluido) se reenvían sin ser filtrados, aunque el firewall esté configurado para no permitir nada.
11 days ago
User avatar None

Source string changed

Documentation / articles/filtering-bridges/_index — Spanish

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). In order tTo 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.
11 days ago
Browse all translation changes