I think I got it
I install sucessly (or at the same time) :
xinetd & xinetd-ipv6 (install script seems not to warn me about that ...)
then the trouble you can see
Buchan Milne wrote:
On Mon, 28 Oct 2002, denis wrote:
Buchan Milne wrote:
On Mon, 28 Oct 2002, denis wrote:
OK, we have:
1-firewall : check
2-hosts allow/deny : check
3-valid xinetd file : check
4-is xinetd running? : yes
ps -ef |grep inet
root 1 0 15:21 ? 00:00:00 xinetd -stayalive -reuse -pidfil
# service xinetd status
# service xinetd restart
5-Is the port open : yes (cf /etc/services)
# netstat -anl|grep 25
netstat -anl|grep 23 (better fort telnt ...)
D'uh, being playing smtp client too much the last few days ...
tcp 0 0 147.94.26.130:36274 147.94.37.14:23
ESTABLISHED
udp 0 0 147.94.26.130:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
unix 2 [ ACC ] STREAM LISTENING 4023 /var/lib/sasl/mux
unix 23 [ ] DGRAM 3198 /dev/log
> # netstat -anl|grep 23
Something isn't right, there's no listening socket:
[root@bgmilne bgmilne]# urpmi telnet-server --media 9.0-local1
installing
/home/bgmilne/downloads/linux-mandrake/mandrake/9.0/i586//Mandrake/RPMS/telnet-server-krb5-1.2.5-1mdk.i586.rpm
Preparing...
##################################################
1:telnet-server-krb5
##################################################
[root@bgmilne bgmilne]# vi /etc/xinetd.d/telnet
[root@bgmilne bgmilne]# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
[root@bgmilne bgmilne]# netstat -anl|grep 23
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.225:32803 146.232.145.5:22
ESTABLISHED
udp 0 0 192.168.1.1:123 0.0.0.0:*
udp 0 0 192.168.0.225:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
[snip]
[root@bgmilne bgmilne]# service shorewall clear
Processing /etc/shorewall/shorewall.conf ...
Processing /etc/shorewall/params ...
Clearing Shorewall...done.
[root@bgmilne bgmilne]# telnet -l bgmilne bgmilne
Trying 192.168.1.1...
Connected to bgmilne (192.168.1.1).
Escape character is '^]'.
Password:
Last login: Sun Oct 27 23:21:20 from bgmilne
Works for me ...
So, it's either xinetd or telnetd itself. Check your syslog to see what
xinetd says, or try and launch telnetd standalone.
Buchan
