Differences

This shows you the differences between two versions of the page.

--- computers:tftpmac [2022/05/24 03:09] – created jon
+++ computers:tftpmac [2022/05/24 17:49] (current) – jon
@@ Line 1: / Line 1: @@
-Before entering tftp, change your directory
+====== TFTP on macOS ======
+===== Client =====
+Before entering tftp, change your directory in terminal where the file you want to push is sent.
+<code>
+tftp 192.168.x.x
+</code>
+Prompt switches to tftp>
+<code>
+bin
+# sets tftp to binary mode
+trace on
+# gives you verbose output
+put [firmware file]
+</code>
+===== Server =====
+The server is disabled by default.
+Starting the tftp server
+<code>
+sudo launchctl load -F /System/Library/LaunchDaemons/tftp.plist
+</code>
+Stopping the tftp server
+<code>
+sudo launchctl unload -F /System/Library/LaunchDaemons/tftp.plist
+</code>
+Check the process to ensure the server is running. If there is a blank response, server is not running.
+<code>
+netstat -atp UDP | grep tftp
+</code>
+The tftp server uses /private/tftpboot as its default folder. You can use command+shift+g to enter the path directly. Any files you wish for the client to receive, you must move the files there.
+<code>
+cp filename /private/tftpboot
+</code>
+Since the folder is restricted, you need to set the correct permissions on the file.
+<code>
+chmod -R 766 /private/tftpboot
+</code>
+There is a gotcha with the TFTP daemon, which is you cant copy a file to the TFTP daemon if that file does not already exist there.  To work around it you can just create a file and set the permission for it. Then your devices will just send data into the pre-created file.
+### Create the file
+touch /private/tftpboot/FILENAME
+### Set permissions
+chmod -R 766 /private/tftpboot
-cd (drag the folder contains the firmware file to Terminal)“
-“tftp 192.168.1.1“
- “binary“
- “put [firmware file]”