Hi, yes, but since the extended access-list range is 100 - 199, this means that extended access lists are supported: #access-class ? <1-199> IP access list <1300-2699> IP expanded access list WORD Access-list name Catalin
Tom Storey <[EMAIL PROTECTED]> wrote: "Expanded" access-lists are not extended access-lists. It is meerly an expanded *range* of standard access-lists. adl-bdr1(config)#access-list ? <1-99> IP standard access list <100-199> IP extended access list <1300-1999> IP standard access list (expanded range) <2000-2699> IP extended access list (expanded range) ----- Original Message ----- From: "Jared Mauch" To: "Collins, Richard (SNL US)" Cc: Sent: Friday, September 14, 2007 1:44 AM Subject: Re: [c-nsp] vty access-list > On Thu, Sep 13, 2007 at 08:55:07AM -0700, Collins, Richard (SNL US) wrote: > > Yes I think that you have to use a standard access-list on the VTY. I > > No, you can use an extended access-list as well. > > 2610(config-line)#access-class ? > <1-199> IP access list > <1300-2699> IP expanded access list > WORD Access-list name > > - Jared > > -- > Jared Mauch | pgp key available via finger from [EMAIL PROTECTED] > clue++; | http://puck.nether.net/~jared/ My statements are only mine. > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ --------------------------------- Yahoo! Answers - Get better answers from someone who knows. Tryit now. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
