nanog mailing list archives
Re: FW: router startup behavior
From: Stephen Griffin <stephen.griffin () rcn com>
Date: Fri, 18 Jan 2002 16:03:35 -0500 (EST)
In the referenced message, Jared Mauch said:
You may want to consider using tftp/rcp/whatnot loaded files for this. As it loads [most if not all depending on the config length] all of the config then parses it promptly. this will prevent leakage in rare cases. - jared
I have noted that even tftp-loaded files run the risk of a BGP scan occuring between the parsing of "no access-list foo" and the parsing of the first "access-list foo" line. It appears Brand C takes the non-existance of an access-list to mean "implicit permit". I think this is probably the source of much of the seen mini-leaks. As someone else mentioned, prefix-lists (again brand C) do allow for insertion and deletion of individual items at "any" point in the list, so may be a good workaround. However, if you are doing anything at all "interesting" in your acls, it becomes a lot more difficult to translate over to prefix-lists. One major item that seems missing is the ability to match less-specifics. There are certain instances when this would be really nifty. Brand C extended acls, and Brand J prefix-lists seem to be able to partially cover this, but not perfectly.
Current thread:
- RE: router startup behavior, (continued)
- RE: router startup behavior Paul Donner (Jan 14)
- Re: router startup behavior Ratul Mahajan (Jan 14)
- Re: router startup behavior Pierfrancesco Caci (Jan 14)
- Message not available
- Re: router startup behavior Lincoln Dale (Jan 15)
- RE: router startup behavior Steve Naslund (Jan 14)
- RE: router startup behavior Borchers, Mark (Jan 15)
- Re: router startup behavior Havard Eidnes (Jan 16)
- FW: router startup behavior Borchers, Mark (Jan 15)
- Re: FW: router startup behavior Simon Lockhart (Jan 15)
- Re: FW: router startup behavior Jared Mauch (Jan 17)
- Re: FW: router startup behavior Stephen Griffin (Jan 18)
- Re: FW: router startup behavior Jared Mauch (Jan 18)
- Re: FW: router startup behavior Simon Lockhart (Jan 15)