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/tr_TR/articles/filtering-bridges/_index.po
Last change April 6, 2021, 1:08 a.m.
Last author Anonymous

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 61 2,591 15,287
Translated 3% 2 1% 5 1% 39
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 96% 59 99% 2,586 99% 15,248
Last 12 months 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 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

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

Trends of last 30 days

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

New string to translate

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

1 new string to translate appeared in the translation. a year ago
User avatar None

Resource update

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

The "documentation/content/tr_TR/articles/filtering-bridges/_index.po" file was changed. a year ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

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.
 
a year ago
User avatar None

New strings to translate

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

7 new strings to translate appeared to the translation. 2 years ago
User avatar None

Resource update

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

The "documentation/content/tr_TR/articles/filtering-bridges/_index.po" file was changed. 2 years ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

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).
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

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).
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

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.
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

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.
 
2 years ago
User avatar None

String updated in the repository

Documentation / articles/filtering-bridges/_index — Turkish (tr_TR)

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#:
 
2 years ago
Browse all translation changes