Mailing List Archive

why not use only one integrated configuration port?
I think one deamon one telnet configuration port is crazy.
In fact only one port is enough, just like vtysh, we use one telnet port, such as 2666, to configure all the deamon.
It is very easy, I think.
Re: why not use only one integrated configuration port? [ In reply to ]
On Mon, 29 Dec 2003, Pan Zhen Yu wrote:

> I think one deamon one telnet configuration port is crazy. In fact
> only one port is enough, just like vtysh, we use one telnet port,
> such as 2666, to configure all the deamon. It is very easy, I
> think.

maybe one day, possibly, hopefully. indeed, I think i probably will
configure the telnet port disabled altogether in my RPM builds ->
make vtysh the default access method.

regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
warning: do not ever send email to spam@dishone.st
Fortune:
The "cutting edge" is getting rather dull.
-- Andy Purshottam
Re: why not use only one integrated configuration port? [ In reply to ]
--On Friday, January 2, 2004 4:05 AM +0000 Paul Jakma <paul@clubi.ie> wrote:

> On Mon, 29 Dec 2003, Pan Zhen Yu wrote:
>
>> I think one deamon one telnet configuration port is crazy. In fact
>> only one port is enough, just like vtysh, we use one telnet port,
>> such as 2666, to configure all the deamon. It is very easy, I
>> think.
>
> maybe one day, possibly, hopefully. indeed, I think i probably will
> configure the telnet port disabled altogether in my RPM builds ->
> make vtysh the default access method.

Some of us *only* run bgpd. I have no interest in running another daemon
just to get access to one that is already running.