Revision e59771e7
Added by Chris Buechler over 16 years ago
| usr/local/www/system_advanced.php | ||
|---|---|---|
| 385 | 385 |
<tr> |
| 386 | 386 |
<td width="22%" valign="top" class="vncell"> </td> |
| 387 | 387 |
<td width="78%" class="vtable"> |
| 388 |
<input name="filteringbridge_enable" type="checkbox" id="filteringbridge_enable" value="yes" <?php if ($pconfig['filteringbridge_enable']) echo "checked"; ?>> |
|
| 389 | 388 |
<strong>Enable filtering bridge</strong><span class="vexpl"><br> |
| 390 |
This will cause bridged packets to pass through the packet |
|
| 391 |
filter in the same way as routed packets do (by default bridged |
|
| 392 |
packets are always passed). If you enable this option, you'll |
|
| 393 |
have to add filter rules to selectively permit traffic from |
|
| 394 |
bridged interfaces.</span></td> |
|
| 389 |
This setting no longer exists as it is unnecessary. Filtering |
|
| 390 |
occurs on the member interfaces of the bridge and cannot be |
|
| 391 |
disabled. </span></td> |
|
| 395 | 392 |
</tr> |
| 396 | 393 |
<tr> |
| 397 | 394 |
<td width="22%" valign="top"> </td> |
Also available in: Unified diff
remove "enable filtering bridge" checkbox, it has been ignored for months. don't entirely remove at this time as there is information all over the place that references it.