In article <mdidc.138670$ >,
Martin Bilgrav <> wrote:
:conf net IP:/file.cfg
You need to have set up a tftp-server command first, as otherwise
it will make nasty assumptions about the interface to use. That's the
only -real- function of the tftp-server command, IMHO: it's the only
place you can set the interface.
:Have any tftp file there, partial or complete
You must not have read the details of my postings on the subject
The inputs accepted for tftp files are slightly different than those
accepted for typing in commands. Generally speaking, you need to use
complete commands in the tftp file: the command completion for
tftp is -different- than the command completion for interactive commands.
There are a few commands which are not accepted via tftp. And
you can tftp in a line that contains a question-mark (e.g., in
a remark or in an isakmp key), which you can't do interactively.
:lines are ignored if they are the same
ACL lines are ignored if they duplicate an existing ACL line. Some
of the other lines will, if duplicated, result in errors that lead to
you being told the tftp failed.
:lines with no-prefixed are removed
Unless, that is, it's a "no ip address" on the interface you're
tftp'ing through, or unless you manage to turn off the rip passive
listener that was providing the route to the tftp server.
There is a way around these problems, which I've documented in previous
postings.
So.... you cannot, in fact, use "any tftp file, partial or complete":
you have to be a bit careful about what's in your tftp file. Once
you have the little tricks down, though, it sure is a useful technique!
--
Before responding, take into account the possibility that the Universe
was created just an instant ago, and that you have not actually read
anything, but were instead created intact with a memory of having read it.