Translation status

61 Strings 100%
Browse Translate
2,591 Words 100%

Strings status

61
All strings — 2,591 words Browse Translate Zen
61
Translated strings — 2,591 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
13
Translated strings with dismissed checks — 374 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,591 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
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. Fix this component to clear its alerts. BSD-2-Clause 0% 62 417 4,051 62 0 0 0
books/developers-handbook/policies/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 51 1,159 7,777 51 0 0 0
books/arch-handbook/scsi/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 356 8,562 62,236 356 0 0 0
books/handbook/zfs/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 548 19,871 137,385 548 1 0 0
books/fdp-primer/weblate/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 157 1,843 13,659 157 0 0 0
books/developers-handbook/ipv6/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 293 6,065 41,292 293 0 0 0
books/handbook/wayland/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 144 4,141 27,667 144 0 0 0
books/developers-handbook/x86/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 927 21,323 120,708 927 1 0 0
books/handbook/disks/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 669 14,395 91,356 668 2 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 March 3, 2024, 10:14 p.m.
Last author Juan David Jaramillo Ortiz

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 61 2,591 15,287
Translated 100% 61 100% 2,591 100% 15,287
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 1 1% 12
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

0 changes 0 changes 0 changes 0 changes 1 change 11 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 16 changes 0 changes 0 changes 0 changes 8 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

2,591
Hosted words
61
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Committed changes

Documentation / articles/filtering-bridges/_index — Spanish

Committed changes 8 months ago
User avatar juanda097

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

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.
El concepto de firewall con estado se incluyó por primera vez en FreeBSD 4.0. Esto supone una gran mejora para el tráfico UDP, el cual generalmenteque suele consistir esn una solicitud dque salidae, seguida poco después por una respuesta con exactamente el mismo conjunto de direcciones IP y números de puerto (pero obviamente con el origen y el destino invertidos, por supuesto). Con los firewalls que no mantienen el estado no hay forma de lidiar con este tipo de tráfico en una única sesión. Pero con un firewall que puede "recordar" un paquete saliente de UDP y, durante los próximos minutos, permitir una respuesta el manejo de servicios UDP es trivial. El siguiente ejemplo muestra cómo hacerlo. Es posible hacer lo mismo con los paquetes TCP. Esto le permite evitar algunos ataques de denegación de servicio y y otras maldades, pero también hace que su tabla de estado crezca rápidamente de tamaño.
8 months ago
User avatar juanda097

New contributor

Documentation / articles/filtering-bridges/_index — Spanish

New contributor 8 months ago
User avatar None

New string to translate

Documentation / articles/filtering-bridges/_index — Spanish

1 new string to translate appeared in the translation. 10 months ago
User avatar None

Resource update

Documentation / articles/filtering-bridges/_index — Spanish

The "documentation/content/es/articles/filtering-bridges/_index.po" file was changed. 10 months 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).
10 months ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Spanish

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.
El concepto de firewall con estado se incluyó por primera vez en FreeBSD 4.0. Es una gran mejora para el tráfico UDP, el cual generalmente es una solicitud de salida seguida poco después por una respuesta con exactamente el mismo conjunto de direcciones IP y números de puerto (pero obviamente con origen y destino invertidos). Con los firewalls que no mantienen el estado no hay forma de lidiar con este tipo de tráfico en una única sesión. Pero con un firewall que puede "recordar" un paquete saliente de UDP y, durante los próximos minutos, permitir una respuesta el manejo de servicios UDP es trivial. El siguiente ejemplo muestra cómo hacerlo. Es posible hacer lo mismo con los paquetes TCP. Esto le permite evitar algunos ataques de denegación de servicio y y otras maldades, pero también hace que su tabla de estado crezca rápidamente de tamaño.
10 months ago
User avatar None

Source string changed

Documentation / articles/filtering-bridges/_index — Spanish

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 exact 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.
10 months 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).
10 months 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.
10 months ago
Browse all translation changes