On Sat, Oct 14, 2000 at 09:49:22AM -0700, Dwight Johnson wrote:
> On Sat, 14 Oct 2000, Shaul Karl wrote:
> 
> > > # update-inetd --add telnet
> > > The entry definition does not contain any whitespace characters!
> > > 
> > > What does this message mean? What am I doing wrong?
> > > 
> > I do not understand you well, can you write the context of what you are 
> > doing?
> > Anyway, if you are just trying to run update-inetd and are getting this 
> > message then you might check the possibility that the script is broken.
> 
> I am running Debian 2.2., a new installation (my first). I would like to
> add telnet to the services of inetd.conf. The file cautions me to use only
> update-inetd to do this.
> 
> My general question is 'How do I use update-inetd to add telnet to my
> inetd.conf services?' I have read the update-inetd man page and the
> associated man pages and it is still not clear.

what i've done on my home lan masquerading server is
        apt-get install xinetd
and then munge /etc/xinetd.conf to include

service telnet
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = telnetd
        group           = telnetd
        server          = /usr/sbin/in.telnetd
        bind            = 192.168.1.1
}

i have a public address 208.33.90.85 and a private interface for
my home intranet lan, 192.168.1.1 -- so here, telnet is available
only on my internal network because i told xinetd to bind to just
that one interface.

        $ nmap 192.168.1.1
        Starting nmap V. 2.12 by Fyodor ([EMAIL PROTECTED], 
www.insecure.org/nmap/)
        Interesting ports on linus (192.168.1.1):
        Port    State       Protocol  Service
        21      open        tcp        ftp             
        22      open        tcp        ssh             
        23      open        tcp        telnet          
        25      open        tcp        smtp            
        53      open        tcp        domain          
        80      open        tcp        http            
        110     open        tcp        pop-3           
        113     open        tcp        auth            

        $ nmap 208.33.90.85
        Starting nmap V. 2.12 by Fyodor ([EMAIL PROTECTED], 
www.insecure.org/nmap/)
        Interesting ports on server (208.33.90.85):
        Port    State       Protocol  Service
        21      open        tcp        ftp             
        22      open        tcp        ssh             
        25      open        tcp        smtp            
        53      open        tcp        domain          
        80      open        tcp        http            
        110     open        tcp        pop-3           
        113     open        tcp        auth            

i've got telnet listening on port 23 (telnet port) for the internal 192.168.*.*
but there's non on the public address 208.33.90.85 at all.

very nice.

-- 
things are more like they used to be than they are now.

[EMAIL PROTECTED] *** http://www.dontUthink.com/

Reply via email to