From: Joseph Brunner (joe@affirmedsystems.com)
Date: Mon Aug 13 2007 - 23:04:08 ART
My take is the router KNOWS on whose behalf its undertaking this
operation...
If you look at the doc CD (as you should be used to by now)
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124tcr/ttsv_
r/ter_t1ht.htm#wp1012161
it makes pretty clear sense...
"To determine the protocols that can be used for outgoing connections from a
line"
and where are you coming from if your on Con0?
Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Gregory Gombas
Sent: Monday, August 13, 2007 9:44 PM
To: Cisco certification
Subject: Re: Understanding Line Console Commands
Anyone want to take a stab at this one?
On 8/12/07, Gregory Gombas <ggombas@gmail.com> wrote:
> I'm a little confused regarding the logic of line console commands.
>
> For example:
> line con 0
> transport output none
>
> I understand this command prevents you from telnetting from the router
> and also prevents you from doing DNS lookups while consoled in, I just
> don't understand the logic of it.
>
> When you log into router1 via console, and initate a telnet to
> router2, the telnet traffic is not going out of the console of
> router1, rather it is using its ethernet or serial interface etc. to
> establish the telnet session to router2.
>
> The same thing applies with DNS lookups, you are not doing a DNS query
> out your console interface so why would you tell your console not to
> output this traffic?
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:11 ART