fedorajunky
5th September 2005, 08:28 PM
tftp server on Fedora Core 4 system fails when tftp client from FC2 system attempts a tftp file transfer:
tftpd: read(ack): No route to host,
I have just installed Fedora Core 4 on a new system, red. The FC4 system was then updated using yum. I configured and chkconfig'ed on the tftp service for this system. The tftp server fails when a FC2 client, blue, attempts a file transfer and the following error is sent to /var/log/messages; "tftpd: read(ack): No route to host". The client tftp session on the FC2 system times out. The routing and network seem to be just fine, as far as I can tell.
Could someone please help me resolve this issue? Thanks in advance for any and all clues or help on this problem.
Details for this problem follow:
'blue' is an FC4 system with a static IP address of 192.168.1.20
'red' is an FC2 system with a static IP address of 192.168.1.10
/* start tftp session on FC2 system */
[root@red root]# tftp -V
tftp-hpa 0.33, with readline
[root@red root]# tftp 192.168.1.20
tftp> get notes
Transfer timed out.
tftp>
/* /var/log/messages on the FC4 system */
Sep 5 18:55:31 blue in.tftpd[18944]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:31 blue in.tftpd[18944]: tftpd: read(ack): No route to host
Sep 5 18:55:36 blue in.tftpd[18945]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:36 blue in.tftpd[18945]: tftpd: read(ack): No route to host
Sep 5 18:55:41 blue in.tftpd[18947]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:41 blue in.tftpd[18947]: tftpd: read(ack): No route to host
Sep 5 18:55:46 blue in.tftpd[18949]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:46 blue in.tftpd[18949]: tftpd: read(ack): No route to host
Sep 5 18:55:51 blue in.tftpd[18950]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:51 blue in.tftpd[18950]: tftpd: read(ack): No route to host
------
/* FC4 system */
[root@blue ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:09:8F:39:18
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:9ff:fe8f:3918/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33008 errors:0 dropped:0 overruns:0 frame:0
TX packets:15983 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42006168 (40.0 MiB) TX bytes:1156304 (1.1 MiB)
Interrupt:10 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1610 errors:0 dropped:0 overruns:0 frame:0
TX packets:1610 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1870772 (1.7 MiB) TX bytes:1870772 (1.7 MiB)
[root@blue ~]# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
[root@blue ~]# traceroute -nr 192.168.1.10
traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 38 byte packets
1 192.168.1.10 9.962 ms !<10> 10.005 ms !<10> 10.316 ms !<10>
[root@blue ~]# cd /tftpboot
[root@blue tftpboot]# ls /tftpboot/
linux-install notes
[root@blue tftpboot]# netstat -a | grep tftp
udp 0 0 *:tftp *:*
[root@blue tftpboot]# chkconfig --list xinetd
xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
[root@blue tftpboot]# cd /etc/xinetd.d
[root@blue xinetd.d]# cat tftp
# default: off
# description: The tftp server serves files using the trivial file transfer \
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware printers, \
# and to start the installation process for some operating systems.
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -v -s /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}
[root@blue xinetd.d]#
tftpd: read(ack): No route to host,
I have just installed Fedora Core 4 on a new system, red. The FC4 system was then updated using yum. I configured and chkconfig'ed on the tftp service for this system. The tftp server fails when a FC2 client, blue, attempts a file transfer and the following error is sent to /var/log/messages; "tftpd: read(ack): No route to host". The client tftp session on the FC2 system times out. The routing and network seem to be just fine, as far as I can tell.
Could someone please help me resolve this issue? Thanks in advance for any and all clues or help on this problem.
Details for this problem follow:
'blue' is an FC4 system with a static IP address of 192.168.1.20
'red' is an FC2 system with a static IP address of 192.168.1.10
/* start tftp session on FC2 system */
[root@red root]# tftp -V
tftp-hpa 0.33, with readline
[root@red root]# tftp 192.168.1.20
tftp> get notes
Transfer timed out.
tftp>
/* /var/log/messages on the FC4 system */
Sep 5 18:55:31 blue in.tftpd[18944]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:31 blue in.tftpd[18944]: tftpd: read(ack): No route to host
Sep 5 18:55:36 blue in.tftpd[18945]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:36 blue in.tftpd[18945]: tftpd: read(ack): No route to host
Sep 5 18:55:41 blue in.tftpd[18947]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:41 blue in.tftpd[18947]: tftpd: read(ack): No route to host
Sep 5 18:55:46 blue in.tftpd[18949]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:46 blue in.tftpd[18949]: tftpd: read(ack): No route to host
Sep 5 18:55:51 blue in.tftpd[18950]: RRQ from 192.168.1.10 filename notes
Sep 5 18:55:51 blue in.tftpd[18950]: tftpd: read(ack): No route to host
------
/* FC4 system */
[root@blue ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:09:8F:39:18
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:9ff:fe8f:3918/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33008 errors:0 dropped:0 overruns:0 frame:0
TX packets:15983 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42006168 (40.0 MiB) TX bytes:1156304 (1.1 MiB)
Interrupt:10 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1610 errors:0 dropped:0 overruns:0 frame:0
TX packets:1610 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1870772 (1.7 MiB) TX bytes:1870772 (1.7 MiB)
[root@blue ~]# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
[root@blue ~]# traceroute -nr 192.168.1.10
traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 38 byte packets
1 192.168.1.10 9.962 ms !<10> 10.005 ms !<10> 10.316 ms !<10>
[root@blue ~]# cd /tftpboot
[root@blue tftpboot]# ls /tftpboot/
linux-install notes
[root@blue tftpboot]# netstat -a | grep tftp
udp 0 0 *:tftp *:*
[root@blue tftpboot]# chkconfig --list xinetd
xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
[root@blue tftpboot]# cd /etc/xinetd.d
[root@blue xinetd.d]# cat tftp
# default: off
# description: The tftp server serves files using the trivial file transfer \
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware printers, \
# and to start the installation process for some operating systems.
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -v -s /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}
[root@blue xinetd.d]#
