On Wed, Nov 23, 2011 at 8:36 PM, James Harr wrote:
> Second rancid.
+3
> If SFTOS supports per-command authorization (via RADIUS/TACACS), you can
it does
> limit the script account to only be able to use 'show run' and whatever
> else it needs (even when it logs in).
>
you can
> That said, i
On Thu, Nov 24, 2011 at 12:03 PM, Christopher Morrow
wrote:
> On Wed, Nov 23, 2011 at 8:36 PM, James Harr wrote:
>> Second rancid.
>
> +3
>
>> If SFTOS supports per-command authorization (via RADIUS/TACACS), you can
>
> it does
>
>> limit the script account to only be able to use 'show run' and w
That's the problem - as a propellorhead I don't make the purchasing decisions.
I can recommend products but low cost speaks more loudly than "this gear is a
dog to work with".
I don't really believe that manufacturers make crippleware user interfaces for
thier products to encourage people to bu
On 11/21/11 14:18 , Nathan Eisenberg wrote:
>> Look at the number that are refusing to make generous prefix
>> allocations
>> to residential end users and limiting them to /56, /60, or even worse,
>> /64.
>
> Owen,
>
> What does Joe Sixpack do at home with a /48 that he cannot do with a /56 or a
Hi,
Op 24 nov 2011, om 21:09 heeft Joel jaeggli het volgende geschreven:
> On 11/21/11 14:18 , Nathan Eisenberg wrote:
>>> Look at the number that are refusing to make generous prefix
>>> allocations
>>> to residential end users and limiting them to /56, /60, or even worse,
>>> /64.
>>
>> Owen,
On 11/24/2011 11:58, Jonathon Exley wrote:
> That's the problem - as a propellorhead I don't make the purchasing
> decisions. I can recommend products but low cost speaks more loudly than
> "this gear is a dog to work with".
That's where you get a chance to impress the business folks by using
t
Doug Barton writes:
> On 11/24/2011 11:58, Jonathon Exley wrote:
>> That's the problem - as a propellorhead I don't make the purchasing
>> decisions. I can recommend products but low cost speaks more loudly than
>> "this gear is a dog to work with".
>
> That's where you get a chance to impres
I may have a different opinion here, but I not sure I'd call any CLI easy
to work with. Cisco's training machine is so efficient that some learn IOS
before leaving high school, so the fact that we all consider IOS easy to
work with is relative. Just look at the "router" command. Most of us know
On Sun, Nov 20, 2011 at 8:40 PM, Tyler Haske wrote:
> I'm looking for a mentor who can help me focus my career so eventually I
> wind up working at one of the Tier I ISPs as a senior tech. I want to
> handle the big pipes that hold everyone's data.
Replying on-list, as I think a route for this d
Yeah, I guess Cisco IOS isn't that good an example of a consistent syntax.
Others do it better - Junos sets the ASN with the 'routing-options
autonomous-system' command, and TiMOS uses 'router autonomous-system'
My rant wasn't about having to deal with new CLIs but about the lack of CLIs in
tho
That's kinda what I was talking about. That command isn't that bad actually.
MQC and juniper firewall filters (in set mode) are no simpler. The annoying
part is the obscurity.
Sent from my iPhone
On Nov 24, 2011, at 11:38 PM, Jonathon Exley
wrote:
> Yeah, I guess Cisco IOS isn't that good
Jonathon Exley wrote;
>
> That's the problem - as a propellorhead I don't make the purchasing decisi
> ons. I can recommend products but low cost speaks more loudly than "this g
> ear is a dog to work with".
> I don't really believe that manufacturers make crippleware user interfaces
> for thi
12 matches
Mail list logo
