Don't use Cisco's GUI!!!
Man, I'd heard that the Cisco GUI was no good, but I thought it was CLI bigots that just don't like Graphical interfaces.
Do you mean drop to the command line on a PIX firewall? How do you do this? We can only manager our PIX501 through the stupid Java GUI (That only works on MS Java Virtual Machine - the SUN Machine crashes it).
'tis been a while since I configured one, but just like a Cisco router, it can be configured via either a LAN connection or through a serial port.
Wait I just tried TELNET. I never knew that I could do that.
Telneting in is a really bad idea. You might as well not use it as a firewall... IOS supports SSH1. You should at least use that...
christopher baus (www.baus.net)
Considering most books are written from a CLI point of view, why the hell would you use any GUI with any cisco gear?
"Considering most books are written from a CLI point of view"
I find that for opening a port on the firewall, and directing it to an internal server, the GUI is a lot faster. Especially since this is a task I do every three or four months. The CLI may be more usable on a day-to-day basis, but the GUI is a lot more learnable, at least for simple things like this.
The thing that amuses me about router and firewall CLI command syntax is how it pretends to be a natural language parser (display route table, add route nnn.nnn.nnn.nnn blah gateway filter blah metric blah, allow SMTP port blah blah), and yet if you drop an element or mistype the parser comes back with something like ? or 'unrecognised command'.
Well, in the case of IOS in general, not sure what to type, say you wanted to enable a routing protocol (lets hope nobody actually does this), while in the config section, type router then ? and you get a list of protocols, not sure what's next in the syntax? type ? and get a list.
Fog Creek Home