Closed VictorLowther closed 3 years ago
@pin Please merge this.
For anyone who cares this, you can use following steps before merged.
step 1:
go get github.com/pin/tftp
go mod download github.com/digitalrebar/tftp
step 2: add replace
in your go.mod
, it should looks like:
module yourmodelname
go 1.16
require (
github.com/pin/tftp v2.1.0+incompatible
)
replace github.com/pin/tftp v2.1.0+incompatible => github.com/digitalrebar/tftp v0.0.0-20200914190809-39d58dc90c67
LGTM! Sorry for the delay!
@pin Please make a release of just add a new tag v2.1.1
.
Go will use the highest version as the latest version.
That means v2.1.0
is newer than the latest v0.0.0-20210809155059-0161c5dd2e96
.
I've just made v.2.2.0 - assuming that will also work. Please let me know if that is not enough.
…d them on.
If you have an interface with multiple IP addresses in the same subnet bound to it, the server code opens a listen socket on all addresses to communicate back to the client, which can cause the kernel to send packets back to the client from a different IP address than the client sent its initial request to. Most of the commandline TFTP clients don't care, but several of the ones embedded in NIC firmware do. To fix that, have the server side code open its client-specific listen socket on the address it recieved the incoming request on.