Being so simple,
TFTP works flawlessly with IPv6 with no protocol-level modifications.
At the protocol level, TFTP is IP version agnostic,
so we won't belabor these demos.
However, we need to make a small change to the xinetd TFTP service configuration.
All we must do is add the IPv6 flag to the service configuration,
instructing xinetd to listen on UDP port 69 for both
IPv4 and IPv6 local addresses.
Then we must restart the TFTP service.
That's all the reconfiguration needed.
Let's jump over to the client.
I'll be fancy and print the upload and download scripts at
once as each one is only one line long.
The download script uses the server's IPv6 address and issues
the get R1.cfg command to download the file.
The upload script uses the same IPv6 address,
except issues the put R3.cfg command to perform an upload.
Let's run the download script first.
The output is terse, but clear.
The UDP port 69 control session is formed to the server's IPv6 address first.
Then R1.cfg is downloaded without issue, and a rollup is provided.
The file was downloaded just fine too.
Now for the upload.
We see three more lines of output.
First, our TFTP control session targets the server's IPv6 address.
R3.cfg is uploaded to the server.
You can trust me that the file was transferred successfully.
I suggest we explore the packet captures next to see if there are any differences between IPv4 TFTP and IPv6 TFTP.