Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Cisco 2611 2nd thread
- To: <tlug@example.com>
- Subject: Re: Cisco 2611 2nd thread
- From: Sven Simon <sven@example.com>
- Date: Thu, 17 May 2001 19:44:23 -0500 (CDT)
- Content-Type: TEXT/PLAIN; charset=US-ASCII
- In-Reply-To: <20010518015621.D28749@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <DBooxC.A.G6C.pBHB7@example.com>
- Resent-Sender: tlug-request@example.com
On Fri, 18 May 2001, Jonathan Q wrote: > > I'm curious, what's he using for a router now? He's using an old Ascend Pipeline 130 up until now. > In this case you will have to write your access lists so that > they specifically deny access only to those IPs on which > the servers reside, except for the ports that need to be > open. As noted above, you can write access lists that do > this on a per-IP basis, so you can say "Allow connections > to w.x.y.z on port 25, deny connections to w.x.y.z on any other port." > For example. I'd recommend allowing ssh connections, too. Oh, ok. It's simpler to deny access on a per IP basis, it's actually quite the only possibility in my case. So, I'll be using only one ethernet interface and in case he'll get some more IP once, we'd be able to put them on the other interface. And of course ssh will be allowed to the servers, too :) SVEN
- Follow-Ups:
- Re: Cisco 2611 2nd thread
- From: Jonathan Q <jq@example.com>
- References:
- Re: Cisco 2611 2nd thread
- From: Jonathan Q <jq@example.com>
Home | Main Index | Thread Index
- Prev by Date: RE: Samba on 7.1 not working :(
- Next by Date: RE: Samba on 7.1 not working :(
- Prev by thread: Re: Cisco 2611 2nd thread
- Next by thread: Re: Cisco 2611 2nd thread
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links