-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TFTP bug: response source IP is not client request #122
Comments
This can be fixed by update Linux kernel routing table, using following command
But I think this is still a bug, and |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
My machine has two IPs, one on loopback interface and another on an ethernet interface.
I hope client can use loopback address as tftp server address.
My IP is:
tftpd is listened on 0.0.0.0 using
s.ListenAndServe(":69")
If client request 192.0.2.255, server will got following err
Please notes source of response packet use
xgbe0
's IP as source.If client request 192.0.2.1, it's ok.
If listened on loopback, using
s.ListenAndServe("192.0.2.255:69")
, and client request 192.0.2.255. It still usexgbe0
's ip to response.The text was updated successfully, but these errors were encountered: