Re: [pfSense-discussion] can't filter on transparent bridge

2008-09-13 Thread Eugen Leitl
On Sat, Sep 13, 2008 at 02:57:07PM +0200, Matthias May wrote:

 You shouldnt need 3 NIC's.
 I'm not sure but you could also try to disable the anti-webgui-lockout rule.

It seems there was some persistent weirdness, perhaps from former
upgrades. I've reset one firewall to factory defaults, and now
the pf rules look more sane when switched to transparent bridge.

Still not quite there (need allow rule for web GUI on WAN) but
it seems I'm no longer dead stuck. I'll follow up on the end result,
given that I want to operate two transparent bridges in a poor
man's failover (no CARP).

Thanks.

-- 
Eugen* Leitl a href=http://leitl.org;leitl/a http://leitl.org
__
ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org
8B29F6BE: 099D 78BA 2FD3 B014 B08A  7779 75B0 2443 8B29 F6BE


Re: [pfSense-discussion] can't filter on transparent bridge

2008-09-13 Thread Chris Buechler
On Sat, Sep 13, 2008 at 8:46 AM, Eugen Leitl [EMAIL PROTECTED] wrote:

 I can't get an 1.2.1-RC1 full with two NICs (VIA mini ITX) to filter traffic
 using http://pfsense.trendchiller.com/transparent_firewall.pdf

 No rules either in WAN or LAN, to the bridge must block
 everything -- but doesn't. No change when I define explict
 blocking rules for everything.


There are some default rules on LAN, like the anti-lockout rule that
could be passing the traffic. You can disable that on the Advanced
page. That's the only one I can think of offhand that would pass
traffic, though LAN is a bit special in 1.2x and there could be
something else I'm not thinking of offhand.

Note the enable filtering bridge checkbox does nothing in 1.2.1 and
should have done nothing in 1.2. In 1.2, turning that on actually can
create some weird problems with filtering in some circumstances.
That's a hold over from the way m0n0wall does things, and should have
been removed when we switched to if_bridge. If you're running bridging
on 1.2, I recommend leaving that disabled. It adds rules to the bridge
itself, when the bridge should never have rules. The member interfaces
get rules added, and you want to filter on both the member interfaces
and not the bridge itself.