Language Translated Untranslated Untranslated words Untranslated characters 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 0 0 0 4 0 0
Chinese (Simplified) (zh_CN) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 6% 57 2,600 15,312 0 0 0
Chinese (Traditional) (zh_TW) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 3% 59 2,602 15,323 0 0 0
Dutch (nl_NL) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 61 2,607 15,362 1 0 0
French (fr_FR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 61 2,607 15,362 0 0 0
German (de_DE) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 60 2,606 15,354 0 0 0
Italian (it_IT) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 61 2,607 15,362 0 0 0
Norwegian Bokmål This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 60 2,605 15,342 0 0 0
Persian This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 3% 59 2,605 15,351 0 0 0
Portuguese (Brazil) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 27% 44 2,436 14,354 26 9 0
Spanish This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0 0 0 0 0 1
Turkish (tr_TR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 3% 59 2,602 15,323 0 0 0
Please sign in to see the alerts.

Overview

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

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 732 31,284 184,344
Source 61 2,607 15,362
Translated 20% 151 17% 5,407 17% 31,899
Needs editing 3% 26 5% 1,674 5% 10,049
Failing checks 4% 31 5% 1,696 5% 10,265
Strings with suggestions 1% 9 1% 175 1% 1,149
Not translated strings 75% 555 77% 24,203 77% 142,396
Last year Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 75 changes 0 changes 82 changes 0 changes 13 changes 0 changes 26 changes 0 changes 23 changes 0 changes 0 changes 0 changes 22 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

31,284
Hosted words
732
Hosted strings
20%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Resource update

Documentation / articles/filtering-bridges/_index — Spanish

Resource update 12 days ago
User avatar fernape

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

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 puedes haber notado es que existe una regla para permitir que la máquina que hace de bridge hable y otra para los hosts internos. Recuerdea 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 `in via fxp0` funcionan para ambas rutas. En general, si utiliza las reglas `in via` 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.
12 days ago
User avatar None

Resource update

Documentation / articles/filtering-bridges/_index — Spanish

Resource update 12 days ago
User avatar fernape

Translation 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).
Ahora es el momento de crear stu propio archivo de configuración con las reglas personalizadas del firewall para proteger la red interna. STe 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 usted 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).
12 days ago
User avatar fernape

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

At this point, to enable the bridge, you have to execute the following commands (having the shrewdness to replace the names of the two network interfaces [.filename]#fxp0# and [.filename]#xl0# with your own ones):
En este momento para habilitar el bridge debes ejecutar los siguientes comandos (no olvide reemplazar los nombres de las dos interfaces de red <[.filename]#fxp0# y [.filename]#xl0# por las suyas):
12 days ago
User avatar fernape

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

If there are any problems, you should sort them out now before proceeding.
Si hay algún problema, debes solucionarlo ahora antes de continuar.
12 days ago
User avatar fernape

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

About the configuration of the network interfaces, the most used way is to assign an IP to only one of the network cards, but the bridge will work equally even if both interfaces or none has a configured IP. In the last case (IP-less) the bridge machine will be still more hidden, as inaccessible from the network: to configure it, you have to login from console or through a third network interface separated from the bridge. Sometimes, during the system startup, some programs require network access, say for domain resolution: in this case it is necessary to assign an IP to the external interface (the one connected to Internet, where DNS server resides), since the bridge will be activated at the end of the startup procedure. It means that the [.filename]#fxp0# interface (in our case) must be mentioned in the ifconfig section of the [.filename]#/etc/rc.conf# file, while the [.filename]#xl0# is not. Assigning an IP to both the network cards does not make much sense, unless, during the start procedure, applications should access to services on both Ethernet segments.
En cuanto a la configuración de las interfaces de red la forma más utilizada es asignar solo una IP a una de las tarjetas de red; el bridge funcionará igualmente, aunque ambas interfaces tengan una o no tengan ninguna IP configurada. En el último caso (IP-less) la máquina bridge quedará aún más oculta, ya que es inaccesible desde la red. Para configurarla, debes iniciar sesión desde la consola o mediante una tercera interfaz de red separada del bridge. A veces durante el inicio del sistema algunos programas requieren acceso a la red, por ejemplo para la resolución del dominio. En este caso es necesario asignar una IP a la interfaz externa (la que está conectada a Internet, donde se encuentra el servidor DNS) ya que el bridge se activará al final del procedimiento de arranque. Esto significa que la interfaz [.filename]#fxp0# (en nuestro caso) debe añadirse en la sección ifconfig del archivo [.filename]#/etc/rc.conf#, mientras que [.filename]#fxp0# no. Asignar una IP a ambas tarjetas de red no tiene mucho sentido, a menos que durante el procedimiento de inicio las aplicaciones tengan que acceder a servicios en ambos segmentos Ethernet.
12 days ago
User avatar fernape

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

Before rebooting in order 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, in order 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#:
Antes de reiniciar para cargar el nuevo kernel o los módulos requeridos (de acuerdo con el método de instalación elegido anteriormente) debes realizar algunos cambios en el archivo de configuración [.filename]#/etc/rc.conf#. La regla predeterminada del firewall es rechazar todos los paquetes IP. Inicialmente configuraremos un firewall en modo `open` para verificar que funciona sin ningún problema en relación con el filtrado de paquetes (en el caso de que vaya a ejecutar este procedimiento de forma remota dicha configuración evitará que permanezca aislado de la red). Coloqueca estas líneas en el archivo [.filename]#/etc/rc.conf#:
12 days ago
User avatar fernape

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

Before rebooting in order 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, in order 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#:
Antes de reiniciar para cargar el nuevo kernel o los módulos requeridos (de acuerdo con el método de instalación elegido anteriormente) debes realizar algunos cambios en el archivo de configuración [.filename]#/etc/rc.conf#. La regla predeterminada del firewall es rechazar todos los paquetes IP. Inicialmente configuraremos un firewall en modo `open` para verificar que funciona sin ningún problema en relación con el filtrado de paquetes (en el caso de que vaya a ejecutar este procedimiento de forma remota dicha configuración evitará que permanezca aislado de la red). Coloque estas líneas en el archivo [.filename]#/etc/rc.conf#:
12 days ago
User avatar fernape

Translation changed

Documentation / articles/filtering-bridges/_index — Spanish

So you have decided to use the older but well tested installation method. To begin, you have to add the following rows to your kernel configuration file:
Si sigues este método es porque has decidido utilizar el método de instalación más antiguo y también el que ha sido más probado más. Para empezar, debes agregar las siguientes líneas a tu archivo de configuración del kernel:
12 days ago
Browse all component changes