I have tftp running on a computer. done with yum install tftp and yum install tftp-server. The computer has 2 network cards in it. Everything else on this computer is working fine.
My tftp config is :
# 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 { socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -v -s /tftpboot disable = no per_source = 11 cps = 100 2 flags = IPv4 }
When I am on the computer and I "tftp localhost" an request a file it will give it to me. when I "tftp localip" it will say connection timeout, when I "tftp INTERNETIP" is says connection refused. note localhost, localip and INTERNETIP are all the same computer.
I have the firewall allowing tftp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:tftp ACCEPT udp -- anywhere anywhere state NEW udp dpt:tftp
What might I be missing here?
Thanks, Jerry
Did you check your logs to see what the error(s)s was/were? It will pretty much tell you exactly what happened there.
Then of course I do this when I deal with inetd or more specifically in this case xinetd... YMMV
netstat -a | more
then I would tailor some /etc/hosts.allow and /etc/hosts.deny files
# # hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In particular # you should know that NFS uses portmap! ALL:ALL
And then
# # hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # in.tftpd in.telnetd sshd # in.tftpd: someipaddressornetworkhere
what it sounds like is a SOURCE and/or destination ip address issue with the firewall or hosts.allow and hosts.deny files.
- rh
-- Robert Hanson - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net
If you can try turning off your firewall (even if it looks good for me), while testing, /etc/init.d/iptables stop
regards,
Guillermo.
On 7/12/06, Robert List list06@abbacomm.net wrote:
Did you check your logs to see what the error(s)s was/were? It will pretty much tell you exactly what happened there.
Then of course I do this when I deal with inetd or more specifically in this case xinetd... YMMV
netstat -a | more
then I would tailor some /etc/hosts.allow and /etc/hosts.deny files
# # hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In particular # you should know that NFS uses portmap! ALL:ALL
And then
# # hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # in.tftpd in.telnetd sshd # in.tftpd: someipaddressornetworkhere
what it sounds like is a SOURCE and/or destination ip address issue with the firewall or hosts.allow and hosts.deny files.
- rh
-- Robert Hanson - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Blue Quartz + CentOS FAQ
http://www.nuonce.net/bq-kb.php#1#1 [ 1 ] CentOS + BlueQuartz: Umlauts and special characters. Also may effect CMS type applications
http://www.nuonce.net/bq-kb.php#2#2 [ 2 ] ProFTPD takes a long time to connect
http://www.nuonce.net/bq-kb.php#3#3 [ 3 ] I am getting a long spam what can I do that is cheap?
http://www.nuonce.net/bq-kb.php#2
Try this fix, it helped me.
_____
From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Guillermo Garron Sent: Wednesday, July 12, 2006 3:38 PM To: CentOS mailing list Subject: Re: [CentOS] tftp question
If you can try turning off your firewall (even if it looks good for me), while testing, /etc/init.d/iptables stop
regards,
Guillermo.
On 7/12/06, Robert List list06@abbacomm.net wrote:
Did you check your logs to see what the error(s)s was/were? It will pretty much tell you exactly what happened there.
Then of course I do this when I deal with inetd or more specifically in this case xinetd... YMMV
netstat -a | more
then I would tailor some /etc/hosts.allow and /etc/hosts.deny files
# # hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In particular # you should know that NFS uses portmap! ALL:ALL
And then
# # hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # in.tftpd in.telnetd sshd # in.tftpd: someipaddressornetworkhere
what it sounds like is a SOURCE and/or destination ip address issue with the firewall or hosts.allow and hosts.deny files.
- rh
-- Robert Hanson - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Chris Heiner -
Guillermo Garron -
Jerry Geis -
Robert List