According to Phil Maley: While burning my CPU.
>
> Hi all,
>
> For a long time I had our bbs set up so that incoming telnet
> connections would bring up a NODE response instead of the
> standard TELNET login. I had set this up by making the entries
> in /etc/services as follows:
>
> telnet 24/tcp
> node 23/tcp
>
> It worked fine until I upgraded the machine to RedHat 5.2. After that,
> telnet originating from the machine would try to access port 24 on the
> distant machine. It seems the telnet software on our box now checks
> /etc/services to see what port it should be using instead of assuming
> that it should be 23.
>
> Richard's suggestion of calling the non-standard telnet port something
> different looks like it might overcome my problem, but it might also
> leave /etc/services with no entry labelled "telnet". Does anyone know
> what really happens and whether the lack of any "telnet" entry will
> cause problems?
Your /etc/services regarding "telnet" should look like;
telnet 23/tcp
telnet 23/udp
have node defined something like the following.
node 3694/tcp node # LinuxNode
Then edit /etc/inetd.conf as per ./ax25-utils-2.1.42!/node/README
You could then also add my suggestion of port 24 for telnet to inetd.conf
and services.
Dont forget after the changes restart the inetd process with
kill -HUP pidof inetd
>
> 73
> Phil vk6ad
>
> >
> > You could use the following.
> >
> > /etc/services
> >
> > ted 24/tcp # Allow telnets on this port.
> >
> > /etc/inetd.conf
> >
> > ted stream tcp nowait root /usr/sbin/tcpd in.telnetd
> >
> > kill -HUP pidof inetd
> >
> > A user then would do from his console.
> >
> > telnet ve1drg 24
> >
> > That way known trusted users could access your machine and use there
> > accounts.
> >
--
Regards Richard.
[EMAIL PROTECTED]
