On Tue, Jun 24, 2003 at 10:37:19PM +0200, Kenny Gryp wrote:
> Jun 24 22:19:55 firewall /bsd: pf: BAD state: TCP 212.123.18.196:80
> 212.123.18.196:80 213.224.186.172:4004 [lo=2075491983 high=2075524103 win=1
> modulator=0] [lo=133175873 high=133175874 win=32120 modulator=0] 4:2 PA
> seq=1331755
Yes, i've got some BAD state messages.
Some of them:
Jun 24 22:19:55 firewall /bsd: pf: BAD state: TCP 212.123.18.196:80 212.123.18.196:80
213.224.186.172:4004 [lo=2075491983 high=2075524103 win=1 modulator=0] [lo=133175873
high=133175874 win=32120 modulator=0] 4:2 PA seq=133175544 ack=207549198
On Mon, Jun 23, 2003 at 02:44:49PM +0200, Kenny Gryp wrote:
> What could be the cause of this?
1) Add 'keep state' to all 'pass' rules
2) Add 'log' to all 'block' rules
3) Turn on debug logging (pfctl -xm, see /var/log/messages)
Without 'keep state', you have to manually ensure that packets of e
Hi,
I Have configured an OpenBSD 3.3 bridge with 3 network interfaces in the bridge
configuration.
The bridge works fine, but one problem appears when i put my pf on.
Some customers are complaining about connectivity problems. My firewall logs nothing.
Customers (http
users) report that there is
