"Matthew G. Marsh" wrote:
> 
> On Wed, 18 Aug 1999, Colin Bradford wrote:
> 
> > On Wed, 18 Aug 1999, root wrote:
> >
> > > Lars Marowsky-Bree wrote:
> > > > On 1999-08-18T11:01:10,
> > > >    root <[EMAIL PROTECTED]> said:
> 
> [snip]
> 
> > > > > I could emulate IOS with LRP, but WTF in their right mind would want to?
> > > > Because it works. And has the best CLI in existance.
> > > It doesn't come near the power, flexablity, and widely known bourne
> > > shell.
> > > When you can access a cisco via ssh, and can do for loops from IOS let
> > > me know.
> > >   : >A
> > B
> > The CLI for IOS is designed to enable you to configure a Cisco(tm)
> > router. Why do I want to do loops? SSH would be useful, but that's a
> > daemon problem, not a CLI one. Note that to backup the entire
> > configuration of a router, I type:
> >
> > write net
> >
> > at the enable prompt. That's powerful. That's what I need to do _to
> > configure a router_.
> 
> Oh I hate to jump in - But... Running and configuring Cisco's every day
> makes me agree strongly with both points. SSH or some alternative
> encrypted access would be excellent. Cisco does not even support
> SNMPv2-encrypt extensions. Also I have several KSH scripts with loops to
> add/remove/modify access control lists. The excruciating alternative is
> typing them in. How DOS....
> 
> Oh - write net is cute and only works IF you have a tftp server with
> appropriate permissions etcetc. BTW - I use the SNMP version of this
> command as well as the counterpart - telling the Cisco to load its config
> from the tftp server. I do this for a particular purpose:

Oh that backs up to a remote machine? I thought he just meant local.
In that case with LRP you must go through the monotonous, high strength
encypted, cronable task of:

mount /dev/boot /mnt
scp /mnt/* myhost:/home/me/
umount /dev/boot

After backing up the packages locally.
(The /dev/boot link is created at boot time in LRP, that is a working
example)

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to