Tftp package doesn't work but found a workaround
-
OK I figured it out. WAN gets an outbound NAT rule from 127.0.0.1 automatically, and LAN does not. So I switched to Manual Outbound NAT and added a rule on LAN from 127.0.0.1 to any, translate to Interface Address, and it started to reply.
-
Wow, yeah this works. Thank you so much ! ;D
-
I added this so I don't forget about it next week (unless someone else picks up on it before I get a chance): http://redmine.pfsense.org/issues/1528
-
You guys rock !
For info, I also posted this => http://forum.pfsense.org/index.php/topic,36713.0.html
Do not know if this is relevant in this forum but just to report it. -
I replied there. The issue doesn't exist with the current version of the TFTP package that I have installed.
-
Is this the latest version trough the package installation interface ? or is there another way to install it ? Package version of TFTP I have is 2.0
-
2.0 sounds right, you might have to delete the package and then reinstall it, instead of just trying to upgrade it.
-
jimp,
I noticed that the backup/restore doesn't function anymore. Receiving a 404 error. If needed, I'll add start a new thread and report the bug on redmine.
-
All of the issues should be fixed now. I also added a control to the interface to select where you want it to take connections (WAN, LAN, etc) that adds the proper NAT rules (port forward, outbound nat for localhost) which should let it "Just Work
" for most people.The only thing I didn't add was a check in the code that would complain if there was a conflict with the TFTP Proxy settings. I'll add that in eventually.
-
Glad to see to see some work on this package.
Another issue with this package is that clicking on the file does not actually present the file for download. I've tried this in both Chrome and Firefox. Can anyone else verify this?
-
Yeah that doesn't appear to work. I'll look into it.
-
ok, clicking the links to download the files should work again. I cleaned up some more code along the way.
