Detail report for faq/pf/it/rdr.html, v 1.27:


[en]
33s 35p

please, use a max of 72 chars per line -->

<a href="../../index.html">
<img alt="[OpenBSD]" height=30 width=141 src="../../images/smalltitle.gif" border="0">
</a>

[it]
33s 35p
translated version available but not linked to!

please, use a max of 72 chars per line -->

<a href="../../../index.html">
<img alt="[OpenBSD]" height=30 width=141 src="../../../images/smalltitle.gif" border="0">
</a>

[en]
158s 160p

filter engine will see the <i>translated</i> packet as it looks after
it's had its destination IP address and/or destination port changed to
match the redirection address/port specified in the <tt>rdr</tt> rule.
Consider this scenario:
158s 160p
filter engine will see the <i>translated</i> packet as it looks after
it's had its destination IP address and/or destination port changed to
match the redirection address/port specified in the <tt>rdr</tt> rule.
Consider this scenario:

[it]
162s 164p

Inoltre bisogna fare attenzione al fatto che la traslazione avviene
<i>prima</i> del filtraggio, quindi il firewall vedrà i pacchetti
<i>traslati</i> dalla regola <i>rdr</i> in indirizzo IP e/o porta di
destinazione. Consideriamo questo scenario:
162s 164p
Inoltre bisogna fare attenzione al fatto che la traslazione avviene
<i>prima</i> del filtraggio, quindi il firewall vedrà i pacchetti
<i>traslati</i> dalla regola <i>rdr</i> in indirizzo IP e/o porta di
destinazione. Consideriamo questo scenario:

[en]
369s 371p

<p>
<hr>
<a href="index.html"><img height="24" width="24" src="../../images/back.gif" border="0" alt="[back]"></a>
<a href="mailto:www@openbsd.org">www@openbsd.org</a>
<br>

[it]
379s 381p
broken link

<p>
<hr>
<a href="../../it/index.html"><img height="24" width="24" src="../../../images/back.gif" border="0" alt="[back]"></a>
<a href="mailto:www@openbsd.org">www@openbsd.org</a>
<br>