Old Synopsis: ipfw allow tcp from any to any established allow Sync pass through
New Synopsis: [ipfw] ipfw allow tcp from any to any established allow Sync pass
through
Responsible-Changed-From-To: freebsd-bugs->freebsd-ipfw
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Nov 16 08:
Ian Smith wrote:
On Sat, 15 Nov 2008, Jin Guojun[VFF] wrote:
>I think this is a bug in ipfw because after change the rule order, the
>problem persists:
>0056626 3090 deny ip from 221.192.199.36 to any
>65330 2018 983473 allow tcp from any to any established
>65535
Ian Smith wrote:
On Sat, 15 Nov 2008, Jin Guojun[VFF] wrote:
>I think this is a bug in ipfw because after change the rule order, the
>problem persists:
>0056626 3090 deny ip from 221.192.199.36 to any
>65330 2018 983473 allow tcp from any to any established
>65535
Synopsis: [ipfw] ipfw allow tcp from any to any established allow Sync pass
through
State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Mon Nov 17 02:46:08 UTC 2008
State-Changed-Why:
Closed at submitter's request.
http://www.freebsd.org/cgi/query-pr.cgi?pr=128902
On Sun, 16 Nov 2008, Jin Guojun[VFF] wrote:
> Ian Smith wrote:
>
> > On Sat, 15 Nov 2008, Jin Guojun[VFF] wrote:
> >
> > >I think this is a bug in ipfw because after change the rule order, the
> > >problem persists:
> > >0056626 3090 deny ip from 221.192.199.36 to any
Ian Smith wrote:
On Sun, 16 Nov 2008, Jin Guojun[VFF] wrote:
> Ian Smith wrote:
>
> > On Sat, 15 Nov 2008, Jin Guojun[VFF] wrote:
> >
> > >I think this is a bug in ipfw because after change the rule order, the
> > >problem persists:
> > >0056626 3090 deny ip from 221.192.1
