Bug #2398
closedtftpd and tftp-proxy (inetd?) dies after WAN periodic reset
0%
Description
When the WAN (PPPoE in my case) connection is restarted by custom periodic reset or when connection resetted by ISP, the tftpd and tftp-proxy (inetd?) services dies.
Starting manually tftpd service in "Status -> Services" doesn't work.
The only way to restart service again is by clicking on "Save" in "Services -> TFTP" properties page.
Updated by Xavier Romain over 12 years ago
TFTP package info from config.xml :
<package> <name>TFTP</name> <website/> <descr><![CDATA[Trivial File Transport Protocol is a very simple file transfer protocol. Often used with routers, voip phones and more.]]></descr> <category>Services</category> <pkginfolink/> <config_file>http://www.pfsense.com/packages/config/tftp2/tftp.xml</config_file> <depends_on_package_base_url>http://files.pfsense.org/packages/8/All/</depends_on_package_base_url> <version>2.0</version> <status>Stable</status> <required_version>2.0</required_version> <configurationfile>tftp.xml</configurationfile> <filter_rule_function>tftp_generate_rules</filter_rule_function> </package> <menu> <name>TFTP</name> <tooltiptext>Add or Remove files for TFTP.</tooltiptext> <section>Services</section> <configfile>tftp.xml</configfile> <url>tftp_files.php</url> </menu> <tab> <text>Files</text> <url>tftp_files.php</url> </tab> <service> <name>tftp</name> <executable>inetd</executable> <description><![CDATA[Trivial File Transport Protocol is a very simple file transfer protocol. Often used with routers, voip phones and more.]]></description> </service> <tftpd> <config> <tftpdinterface>lan</tftpdinterface> </config> </tftpd>
Updated by Mark Blackman over 12 years ago
I've not spotted the trigger condition, but I can confirm I'm seeing the same condition
with '2.1-DEVELOPMENT (amd64) built on Sun May 13 02:42:10 EDT 2012'
I have to save the config to restart it, even a reboot didn't help.
Updated by Xavier Romain about 12 years ago
I've found a workaround long time ago but I forgot to mention here.
- installed Cron package
- added line : "/usr/sbin/inetd -wW -R 0 -a 127.0.0.1 /var/etc/inetd.conf" 1 minute after resetting WAN connection.
This workaround reload tftpd and everything works fine since 6 months.
I've not already tested this issue with pfSense 2.1
Updated by Jim Pingle about 12 years ago
In /etc/inc/filter.inc around like 1858, try changing the place where it does a kill -HUP on inetd with two commands that kill it with KILL and then restarts it.
It may be that HUP isn't enough to make inetd reattach in your case.
Updated by Chris Buechler almost 9 years ago
- Status changed from New to Closed
this likely fixed a number of versions ago. at a minimum, the same issue doesn't exist in 2.3