Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]tlug: IPchains question
- To: "Tokyo Linux Users' Group" <tlug@example.com>
- Subject: tlug: IPchains question
- From: "Scott M. Stone" <sstone@example.com>
- Date: Mon, 12 Jun 2000 15:09:43 -0700 (PDT)
- Content-Type: TEXT/PLAIN; charset=US-ASCII
- Reply-To: tlug@example.com
- Sender: owner-tlug
What's the equivalent, in ipchains, of the following Ciscoism: access-list 101 permit tcp 192.168.81.0 0.0.0.255 any established (basically what this does is allow 192.168.81.0/24's ESTABLISHED TCP connections to anywhere.. ie, if the RST or ACK bits are set on an incoming packet, it flags it as part of the already-established connection and lets it through. If the bits are not present, it thinks it's a new connection and therefore denies it). How does ipchains do that? -------------------------- Scott M. Stone, CCNA <sstone@example.com> UNIX Systems and Network Engineer Taos - The SysAdmin Company ----------------------------------------------------------------------- Next Meeting (w/ YLUG): June 16 (Fri) 19:00 Mizonoguchi Marui Family 12F Next Technical Meeting: July 8 (Sat) 13:30 Topic: TBA ----------------------------------------------------------------------- more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: kids (was: MS ordered split)
- Next by Date: tlug: IPchains problem solved
- Prev by thread: tlug: memory locking
- Next by thread: tlug: IPchains problem solved
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links