ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: "Oleg K. Artemjev" <olli@rbauto.ru>
To: community@altlinux.ru
Subject: [Comm] ?:tftp/xinetd/cisco
Date: Thu, 21 Aug 2003 18:45:49 +0400
Message-ID: <20030821184549.1b196cbb.olli@rbauto.ru> (raw)

Добрый вечер.

Как-то странно отваливается tftpd. Вопрос - это мне так повезло на нерабочую
опцию наткнуться или он в мастере 2.0 кривой от рождения? :? Или я таки сам 
виноват и злобный буратина? ?-) Так все таки - what's the f***?

Вот что у меня имеется:

система: Alt Master 2.0:
===========================================================================
[root@ws002 root]# uname -a
Linux ws002.mo.sim 2.4.18-alt6master-up #1 Tue Apr 16 14:50:56 MSD 2002 i686 unknown
[root@ws002 root]#
===========================================================================

конфиги:
===========================================================================
[root@ws002 root]# cat /etc/xinetd.conf | grep -v ^\$| grep -v ^\#
defaults
{
        log_type = SYSLOG authpriv
        log_on_success = PID HOST USERID EXIT DURATION
        log_on_failure = HOST RECORD USERID
        instances = 25
        per_source = 5
        only_from = 127.0.0.1
}
includedir /etc/xinetd.d
[root@ws002 root]# cat /etc/xinetd.d/tftp| grep -v ^\$| grep -v ^\#
service tftp
{
        disable         = no
        socket_type     = dgram
        wait            = yes
        user            = root
        server          = /usr/sbin/in.tftpd
        server_args     = -v -c -u tftp -s /0tftpd-storedir
}
[root@ws002 root]#
[olli@ws002 tmp]$ cat /etc/hosts.allow | grep tftpd
in.tftpd: 62.141.68.169
in.tftpd: 127.0.0.1
in.tftpd: 62.118.145.167
in.tftpd: 172.16.11.1
in.tftpd: 192.168.100.241
in.tftpd: 192.168.200.241
in.tftpd: 192.168.100.244
in.tftpd: 192.168.100.246
in.tftpd: 192.168.100.249
in.tftpd: 192.168.200.249
[olli@ws002 tmp]$ 
[root@ws002 root]# /etc/rc.d/init.d/ipchains status
Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):
[root@ws002 root]# 
===========================================================================

каталог:
===========================================================================
[olli@ws002 tmp]$ lsattr /0tftpd-storedir/
-------------- /0tftpd-storedir//startup-config
-------------- /0tftpd-storedir//running-config
[olli@ws002 tmp]$ lsattr -d /0tftpd-storedir/
-------------- /0tftpd-storedir/
[olli@ws002 tmp]$ ls -ld /0tftpd-storedir/
drwxrwxrwt    2 root     root         1024 Авг  4 10:33 /0tftpd-storedir/
[olli@ws002 tmp]$ ls -l /0tftpd-storedir/
total 0
-rw-rw-rw-    1 root     wheel           0 Янв 22  2003 running-config
-rw-rw-rw-    1 root     wheel           0 Янв 22  2003 startup-config
[olli@ws002 tmp]$ 
===========================================================================

на киске:
===========================================================================
3550gbic@4=cs241#copy run tftp
Source filename [running-config]?
Address or name of remote host []? 192.168.100.2
Destination filename [3550gbic@4=cs241-confg]? 3550gbic@4=cs241.running-config.20030821.17:45
.....
%Error opening tftp://192.168.100.2/3550gbic@4=cs241.running-config.20030821.17:45 (Timed out)
3550gbic@4=cs241#ping 192.168.100.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
=3550gbic@4=cs241#sh ru | in ess 192
 ip address 192.168.100.241 255.255.255.0
 ip address 192.168.200.241 255.255.255.0
3550gbic@4=cs241#

И еще:

Password: 
3550gbic@4=cs241>en
Password: 
3550gbic@4=cs241#copy run tftp
Source filename [running-config]? 
Address or name of remote host []? 192.168.100.2
Destination filename [3550gbic@4=cs241-confg]? running-config
.....
%Error opening tftp://192.168.100.2/running-config (Timed out)
3550gbic@4=cs241#
==========================================================================

в логах:
==========================================================================
Aug 21 14:58:05 ws002 xinetd[23522]: Started working: 3 available services
Aug 21 14:58:07 ws002 xinetd: xinetd startup succeeded
Aug 21 14:58:37 ws002 xinetd[23522]: START: tftp pid=23526 from=127.0.0.1
Aug 21 15:13:37 ws002 xinetd[23522]: EXIT: tftp status=0 pid=23526 duration=900(sec)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {general_handler} (24840) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24840]: {bad_signal} Received 10 signals in 1 seconds. Exiting...
Aug 21 17:46:50 ws002 xinetd[23522]: START: tftp pid=24840 from=192.168.100.241
Aug 21 17:46:50 ws002 xinetd[23522]: EXIT: tftp status=1 pid=24840 duration=0(sec)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24841]: {general_handler} (24841) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[23522]: START: tftp pid=24841 from=192.168.100.241
Aug 21 17:46:50 ws002 xinetd[24841]: {bad_signal} Received 10 signals in 1 seconds. Exiting...
Aug 21 17:46:50 ws002 xinetd[23522]: EXIT: tftp status=1 pid=24841 duration=0(sec)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[23522]: START: tftp pid=24842 from=192.168.100.241
Aug 21 17:46:50 ws002 xinetd[24842]: {general_handler} (24842) Unexpected signal: 11 (Segmentation fault)
Aug 21 17:46:50 ws002 xinetd[24842]: {bad_signal} Received 10 signals in 1 seconds. Exiting...
==========================================================================

в tcpdump:
==========================================================================
[root@ws002 root]# tcpdump -i eth0 -lenvvv '(ether src 00:05:5D:28:3C:AE or ether dst 00:05:5D:28:3C:AE)'| grep tftp
tcpdump: listening on eth0
18:35:30.730836 0:c:ce:d3:bc:0 0:5:5d:28:3c:ae ip 73: 192.168.100.241.53773 > 192.168.100.2.tftp: [udp sum ok]  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 0, len 59)
18:35:34.732060 0:c:ce:d3:bc:0 0:5:5d:28:3c:ae ip 73: 192.168.100.241.53773 > 192.168.100.2.tftp: [udp sum ok]  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 1, len 59)
18:35:34.732110 0:5:5d:28:3c:ae 0:c:ce:d3:bc:0 ip 101: 192.168.100.2 > 192.168.100.241: icmp: 192.168.100.2 udp port tftp unreachable for 192.168.100.241.53773 > 192.168.100.2.tftp:  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 1, len 59) [tos 0xc0]  (ttl 255, id 48476, len 87)
18:35:39.732441 0:c:ce:d3:bc:0 0:5:5d:28:3c:ae ip 73: 192.168.100.241.53773 > 192.168.100.2.tftp: [udp sum ok]  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 2, len 59)
18:35:39.732468 0:5:5d:28:3c:ae 0:c:ce:d3:bc:0 ip 101: 192.168.100.2 > 192.168.100.241: icmp: 192.168.100.2 udp port tftp unreachable for 192.168.100.241.53773 > 192.168.100.2.tftp:  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 2, len 59) [tos 0xc0]  (ttl 255, id 48477, len 87)
18:35:45.732882 0:c:ce:d3:bc:0 0:5:5d:28:3c:ae ip 73: 192.168.100.241.53773 > 192.168.100.2.tftp: [udp sum ok]  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 3, len 59)
18:35:52.733393 0:c:ce:d3:bc:0 0:5:5d:28:3c:ae ip 73: 192.168.100.241.53773 > 192.168.100.2.tftp: [udp sum ok]  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 4, len 59)
18:35:52.733422 0:5:5d:28:3c:ae 0:c:ce:d3:bc:0 ip 101: 192.168.100.2 > 192.168.100.241: icmp: 192.168.100.2 udp port tftp unreachable for 192.168.100.241.53773 > 192.168.100.2.tftp:  31 WRQ "3550gbic@4=cs241-confg" (ttl 255, id 4, len 59) [tos 0xc0]  (ttl 255, id 48478, len 87)
==========================================================================

-- 
Bye.Olli.			http://olli.digger.org.ru



             reply	other threads:[~2003-08-21 14:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21 14:45 Oleg K. Artemjev [this message]
2003-08-21 15:08 ` [Comm] ?:tftp/xinetd/cisco Michael Shigorin
2003-08-22  4:05   ` Grigory Batalov
2003-08-22  8:03     ` Michael Shigorin
2003-08-22  8:30       ` Oleg K. Artemjev
2003-08-22  8:33         ` Michael Shigorin
2003-08-21 21:49 ` [Comm] ?:tftp/xinetd/cisco Dmitry Lebkov
2003-08-21 22:54   ` [Comm] ?:tftp/xinetd/cisco Michael Shigorin
2003-08-21 23:07     ` Dmitry Lebkov
2003-08-21 23:16       ` [Comm] [JT] " Michael Shigorin
2003-08-22  6:50   ` [Comm] ?:tftp/xinetd/cisco Oleg K. Artemjev
2003-08-22  4:20 ` Alexey I. Froloff
2003-08-22  6:16   ` Oleg K. Artemjev
2003-08-22  6:58     ` Dmitry Lebkov
2003-08-22  8:03   ` [Comm] ?:tftp/xinetd/cisco Michael Shigorin
2003-08-22  8:10     ` Alexey I. Froloff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030821184549.1b196cbb.olli@rbauto.ru \
    --to=olli@rbauto.ru \
    --cc=community@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git