Hi,
You (Jon Simola) wrote:
> If that's a bridge config, synproxy will not work. It's not possible
> to tell from the documentation you provided.
No, it is the pf box is acting as gateway.
But the reply packet from webserver is dropped at the dmz interface.
If I allow this reply explicitly, synpr
On 6/16/05, Andy Hilker <[EMAIL PROTECTED]> wrote:
> pass in log quick proto tcp from x.x.x.x to port {
> 80,443 } flags S/SA synproxy state
I've used this a couple times to stop infected clients without totally
locking them out:
pass in quick on vlan130 proto tcp from x.x.x.174
Hi,
i have a problem with using synproxy (FreeBSD 5.4 Release p2).
# Client with x.x.x.x do not get an answer with synproxy, keep state works
pass in log quick proto tcp from x.x.x.x to port {
80,443 } flags S/SA synproxy state
# log said
rule 101/0(match): block in on em1: IP
