home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.sys.cisco
- Path: sparky!uunet!munnari.oz.au!comp.vuw.ac.nz!canterbury.ac.nz!cantsc.canterbury.ac.nz!cctr127
- From: cctr127@csc.canterbury.ac.nz (Jason Haar)
- Subject: ACLs
- Message-ID: <C1FMz4.I4n@cantua.canterbury.ac.nz>
- Nntp-Posting-Host: cantsc.canterbury.ac.nz
- Reply-To: Jason Haar <j.haar@csc.canterbury.ac.nz>
- Organization: University of Canterbury, Christchurch, New Zealand.
- X-Newsreader: TIN [version 1.1 PL8]
- Date: Mon, 25 Jan 1993 23:09:03 GMT
- Lines: 25
-
-
- Howdy,
-
- I have a problem (suprise, suprise ;-)
-
- I want to give a node on my LAN off-site access on the nntp port _only_
-
- Currently I have configured our cisco (which is the gateway) to let anyone
- talk to this host on the nntp port, and on any port over 1000 - and visa
- versa for connections from the other direction. This works fine, but means
- that the node is still open for connections over 1000 - which I don't want.
-
- (just enabling port 119 isn't enough as there are two ports to every
- connection)
-
- Is there any other ACL set I could use to ensure that _only_ connections
- to .OR. from port nntp were allowed?
-
- --
-
- Cheers
-
- Jason Haar, Network Consultant
- CSC, University of Canterbury, Christchurch, New Zealand
- phone: +64-3-3642 2336 fax: +64-3-364 2332
-