-
-
Notifications
You must be signed in to change notification settings - Fork 53
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 sending wrong IP address #14
Comments
I see this too, pretty logical as well as the docker container is only ware of its internal nic's if you're not in That having said; no further/other configuration is need to get this up and running. As long as you fwd port 69/udp you can serve your LAN. |
I've had similar experience when trying to run netbooxyz containerized without host networking. A fix for that is running TFTP server in a mode where only port 69 is used for both commands and data. |
For what it's worth I've had a similar problem that turned out to be due to running docker in an environment with multiple MACs and IPs - solved by running on a host with a single IP |
this merge and option fixed the issue for me on macos, thank you! |
I had to apply the same "fix", otherwise I got a timeout error: tftp 10.10.0.60 69
tftp> get netboot.xyz.efi
Transfer timed out.
tftp> Wouldn't it be better to set the Or may it be possible to add some information regarding this problem to the wiki? |
I currently face the issue where the TFTP server seems to answer with the wrong IP address (from Docker). I am using the default docker-compose.yml file.
10.10.0.103
is my client,10.10.3.6
is thenext-server
and192.168.192.2
is the IP address of the Docker container running netboot.xyz.The following is the tcpdump output on the host machine (where Docker is **running).
The following is the tcpdump output on docker container itself (please don't mind the time offset).
I tried running the Docker container with
network_mode: host
which leads to the fact that no Docker internal IP address is shown in the TCPdump output but it fails to start fully because of nginx (I have somehting running on port 80 on the hardware server so nginx cannot bind on it).What do I need to configure in order to get this up and running?
The text was updated successfully, but these errors were encountered: