I have installed the TFTP client application by following the below link: https://askubuntu.com/questions/201505/how-do-i-install-and-run-a-tftp-server By default, the block size of the **TFTP packet header is 512 bytes**. I am trying to increase the blocksize by adding the --blocksize 1468 flag into /etc/xinetd.d/tftp file by following the below reference: https://askubuntu.com/questions/644031/tftpd-hpa-how-can-i-set-blksize-option After making the required changes by following the above link still I am getting the same 512 Data packet size. Can anyone share me the code for the same so I can change the block size configuration for the same?

I have a client app that launch in async mode a bash script that send a file to a TFTP server. The issue is that I don't know how to show user the progress of this transfer, worst of all this operation is about 2-3 minutes long. My workaround was to use --trace option with atftp command and put it in a file and every n-second I read this file to show user the progress in %. atftp -p -l test.png --verbose --trace 192.168.1.1 > progress.txt atftp -p --trace -l test.png 192.168.1.1 | tee progress.txt There is a problem, strangely atftp doesn't seems to put anything on that file, meanwhile classic tftp did it. Did I missing something about atftp or did you suggest other way to retrieve progress status of this operation? Unfortunately I'm on a Debian Squeeze on a very legacy configuration. Thanks in advance and have a nice day. EDIT: first workaround found, I put tftp interactive mode (so I can active trace) in a script and pipe out the output of that script. Now I must find a way to read only the last row data every n-seconds.

I am trying to send/receive a file using TFTP from the network switch to ubuntu(VirtualBox on Windows 10 Pro), but getting an error code 5 By following the steps mentioned below it seems like my localhost is working with TFTP server, I can send and receive the file using localhost: /home/abc# tftp localhost tftp> put test Sent 16 bytes in 0.0 seconds tftp> get test Received 16 bytes in 0.0 seconds root@abc:/home/abc# ls -l /var/lib/tftpboot/ total 4 -rwxrwxrwx 1 root root 14 Sep 6 18:03 test ***When I used the command in the switch to send/receive the file then I get the error message:*** ***Trivial File Transfer Protocol*** ***Opcode: Error Code (5)*** ***[Destination File: test]*** ***Error code: Access violation (2)*** ***Error message: Access violation*** ***[Expert Info (Warning/Response): TFTP ERROR packet]*** ***[TFTP ERROR packet]*** ***[Severity level: Warning]*** ***[Group: Response]*** ***Would you please guide me on how to fix this issue?*** **https://icesquare.com/wordpress/how-to-setup-tftp-on-ubuntu/** First, let’s install all the necessary packages: sudo apt-get install xinetd tftpd tftp -y Next, we need to create a configuration file: sudo nano /etc/xinetd.d/tftp Put the following content into the file. service tftp { protocol = udp port = 69 socket_type = dgram wait = yes user = nobody server = /usr/sbin/in.tftpd server_args = var/lib/tftpboot -s disable = no } In the server_args, I have var/lib/tftpboot, which represents the location of the tftp root, i.e., /var/lib/tftpboot. Notice that I skip the root /. Now let’s change the ownership of the directory: sudo mkdir /var/lib/tftpboot sudo chown -R nobody:nobody /var/lib/tftpboot sudo chmod -R 777 /var/lib/tftpboot and start the TFTP service: sudo service xinetd stop sudo service xinetd start Verify the TFTP is running correctly or not: netstat -na | grep LIST | grep 69 You should see something like this: tcp 0 0 0.0.0.0:69 0.0.0.0:* LISTEN Test: Upload a file to TFTP Server Now let’s test the TFTP server by logging into the server first: tftp localhost and upload a file: tftp> put myfile.jpg Sent 56733279 bytes in 5.7 seconds Quit: q Make sure that file has been uploaded: ls -l /var/lib/tftpboot Test: Download a file from TFTP Server Now, let’s go to a different directory and download the file we just upload. cd some_other_directory and log in to the tftp server again: tftp localhost and get the file: tftp> get myfile.jpg Received 56733279 bytes in 5.7 seconds

I have a kvm host, with bridge network, so the vms get IP info directly from router itself. I have created a pxeboot env with dnsmasq acting as dhcp proxy, and kickstart as method of installation passed via pxeboot menu. So far all working fine. but here's the problem, whenever I want to set static IP on a vm, I have to modify kickstart file with IP information. this is manageable for small number of vms, but now I introduced terraform for vm provisioning , and I want IP information to be passed on with use of terraform variables to kickstart file. so below is line of kickstart with static IP info

network  --bootproto=static --device=enp1s0 --ip=192.168.1.220 --netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=8.8.8.8 --noipv6 --activate

and here's variables that I have defined in terraform code

variable "vm_ip" {
  default = "192.168.1.200"
}

variable "vm_netmask" {
  default = "255.255.255.0"
}

variable "gat_eway" {
  default = "192.168.1.1"
}

variable "name_server" {
  default = "8.8.8.8"
}

any idea how to pass these variables to kickstart, so vm can get static IP with use of terraform variables?

first, I installed apache & started its service

yum install httpd && systemctl enabled httpd --now

then I mounted dvd iso & copied its content to apache dir

mount -o ro ~/Downloads/rockylinux9.iso /mnt/iso

cp -rv /mnt/iso/* /var/www/html/install-media/

and copied kickstart file under

cp ~/kickstart-rockylinux9.cfg /var/www/html/install-media/kickstart/

then I installed tftp-server & syslinux & started tftp-server

yum install tftp-server syslinux

then I created these dirs & copied kernel files to below path

mkdir -p /var/lib/tftpboot/{images,pxelinux.cfg}

cp /var/www/html/install-media/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/images/

then I copied menu files from syslinux dir

cp /usr/share/syslinux/{menu.c32,pxelinux.0} /var/lib/tftpboot/

finally created menu file /var/lib/tftpboot/pxelinux.cfg/default with below content

default menu.c32
prompt 0
timeout 300
ontimeout 2

menu title PXE Boot Menu
label 1
  menu label ^1 - Install Rocky Linux 9
  kernel images/vmlinuz
  append initrd=images/initrd.img showopts method=http://192.168.1.254/install-media/  devfs=nomount ks=http://192.168.1.254/install-media/kickstart/kickstart-rockylinux9.cfg 

Now the critical part is dnsmasq.conf, as my physical host is on bridged network with kvm installed on it. so dnsmasq is supposed to proxy dhcp request to my router

# cat /etc/dnsmasq.con

# Enable proxy DHCP for PXE
port=0
dhcp-range=192.168.1.0,proxy
# Specify PXE options
dhcp-boot=pxelinux.0,,192.168.1.254
enable-tftp
tftp-root=/var/lib/tftpboot

here's my kickstart file

# Generated by Anaconda 34.25.5.9
# Generated by pykickstart v3.32
#version=RHEL9
# Use graphical install
graphical

# Remove CDROM installation media line
# cdrom

# Specify the HTTP repository
repo --name="AppStream" --baseurl=http://192.168.1.254/install-media/ 

%addon com_redhat_kdump --disable
%end

# Keyboard layouts
keyboard --xlayouts='us'

# System language
lang en_US.UTF-8

# Network information
network --bootproto=dhcp --device=enp1s0 --noipv6 --activate
network --hostname=ks-sample2

# Packages to install
%packages
@^minimal-environment
%end

# Firstboot configuration
firstboot --enable

# Disk and partition configuration
ignoredisk --only-use=vda
clearpart --none --initlabel
part /boot --fstype="xfs" --ondisk=vda --size=1024
part pv.50 --fstype="lvmpv" --ondisk=vda --size=70655
volgroup rl --pesize=4096 pv.50
logvol swap --fstype="swap" --size=7167 --name=swap --vgname=rl
logvol / --fstype="xfs" --size=63484 --name=root --vgname=rl

I am unable to boot, after getting IP info properly from dhcp it says, No boot devices found.

I am using bitbake to generate my u-boot and linux images. I have two boards, one of which is running a simple TFTP server written in c++ code. U-Boot can tftp boot ~50MB in around 7 seconds. When it boots in the the linux image it just TFTP booted from it takes about 2.5 minutes. I was using the builtin busybox tftp, so I thought that might be the issue. So I added tftp-hpa to my linux image and re-tried with that tftp -m binary -c get and got basically the same result. The tftp server always writes 512 byte chunks and reports and re-tries, which there are none. So I am at a bit of a loss to explain this difference. Its all the exact hardware, the *only* difference is one is running from u-boot and the other is running from Linux. What might be the difference? - any way I can test/resolve this? **Clarifications** - U-boot takes 7 seconds to tftp-get/transfer the FIT image from the server - Linux (once booted) takes 2.5 minutes to tftp-get/transfer the same image - By adding tftp-hpa to my bitbake recepie, it has replaced the busybox implementation - My question is how to make the linux tftp transfer the same speed as the u-boot transfer. - The simple c++ tftp server is on a separate board, running on linux, its always running and is left unchanged for all these tests ### Update Using rsync to copy the files when in linux is very fast also... so that is a workaround - but still does not answer *why* tftp in linux is so slow.

I am trying to boot linux mint from a server I set up in virtualbox. Server is running in linux mint, and the client that I'm testing on (also virtualbox) is disk-less and booting over network. After splash screen vmlinuz and initrd are received correctly, until I get the following error: Any info on what might be going wrong?

I'm trying to build a minimal kernel where tftp works. I'm using busybox for initramfs and I'll be running the kernel on an arm64 virtual machine. The command for getting file is tftp -g -r axpu_ldd_kc.ko my_ip_addr(of course my tftp server is working). But the response is : tftp: sendto: Network is unreachable So I added some network stuff in the kernel configuration (linux-5.10.0-rc5) but still doesn't work. I can't figure out what more to add just to make tftp work Could anyone tell me what is missing from the defconfig below? (using e1000 in qemu virtual machine). (As you can see, I added CONFIG_NF_CONNTRACK_TFTP for which the menuconfig says it's TFTP support. And the .config file has CONFIG_NF_NAT_TFTP set to =y. I show the defconfig because .config is too long) # CONFIG_SWAP is not set # CONFIG_CROSS_MEMORY_ATTACH is not set CONFIG_PREEMPT=y # CONFIG_CPU_ISOLATION is not set CONFIG_LOG_BUF_SHIFT=12 CONFIG_LOG_CPU_MAX_BUF_SHIFT=10 CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=10 CONFIG_USER_NS=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="../../../../ab21sim/ab21tsim/busybox-1.32.1/initramfs.cpio.gz" # CONFIG_RD_BZIP2 is not set # CONFIG_RD_LZMA is not set # CONFIG_RD_XZ is not set # CONFIG_RD_LZO is not set # CONFIG_RD_LZ4 is not set # CONFIG_RD_ZSTD is not set CONFIG_PERF_EVENTS=y CONFIG_SLAB=y CONFIG_NR_CPUS=2 # CONFIG_RODATA_FULL_DEFAULT_ENABLED is not set # CONFIG_ARM64_TAGGED_ADDR_ABI is not set # CONFIG_ARM64_UAO is not set # CONFIG_ARM64_RAS_EXTN is not set # CONFIG_ARM64_CNP is not set # CONFIG_ARM64_PTR_AUTH is not set # CONFIG_ARM64_AMU_EXTN is not set # CONFIG_ARM64_TLB_RANGE is not set # CONFIG_ARM64_BTI is not set # CONFIG_ARM64_E0PD is not set # CONFIG_ARCH_RANDOM is not set # CONFIG_ARM64_SVE is not set # CONFIG_EFI is not set # CONFIG_SECCOMP is not set # CONFIG_BLK_DEV_BSG is not set # CONFIG_MQ_IOSCHED_DEADLINE is not set # CONFIG_MQ_IOSCHED_KYBER is not set CONFIG_BINFMT_MISC=y CONFIG_FLATMEM_MANUAL=y # CONFIG_COMPACTION is not set CONFIG_NET=y CONFIG_INET=y CONFIG_NETFILTER=y CONFIG_NF_CONNTRACK=y CONFIG_NF_CONNTRACK_TFTP=y CONFIG_NF_NAT=y CONFIG_DEVTMPFS=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=1 CONFIG_BLK_DEV_RAM_SIZE=65536 CONFIG_NETDEVICES=y # CONFIG_KEYBOARD_ATKBD is not set # CONFIG_INPUT_MOUSE is not set CONFIG_SERIO_LIBPS2=y CONFIG_VT_HW_CONSOLE_BINDING=y # CONFIG_LEGACY_PTYS is not set CONFIG_SERIAL_AMBA_PL011=y CONFIG_SERIAL_AMBA_PL011_CONSOLE=y # CONFIG_HWMON is not set # CONFIG_USB_SUPPORT is not set CONFIG_RTC_CLASS=y # CONFIG_RTC_HCTOSYS is not set # CONFIG_RTC_INTF_SYSFS is not set # CONFIG_RTC_INTF_PROC is not set # CONFIG_RTC_INTF_DEV is not set CONFIG_RTC_DRV_M48T59=y # CONFIG_VHOST_MENU is not set # CONFIG_IOMMU_SUPPORT is not set # CONFIG_NVMEM_SYSFS is not set CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_DNOTIFY is not set # CONFIG_INOTIFY_USER is not set CONFIG_AUTOFS4_FS=y CONFIG_ISO9660_FS=y CONFIG_PROC_KCORE=y # CONFIG_MISC_FILESYSTEMS is not set CONFIG_LSM="lockdown,yama,loadpin,safesetid,integrity" CONFIG_DEBUG_INFO=y CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y CONFIG_DEBUG_FS=y CONFIG_DEBUG_KERNEL=y CONFIG_DETECT_HUNG_TASK=y # CONFIG_SCHED_DEBUG is not set # CONFIG_RCU_TRACE is not set By the way, the qemu command is this : > /home/ckim/ProjX/QEMU/qemu-6.2.0/build-baremetal/aarch64-softmmu/qemu-system-aarch64 > -machine ab21q,gic-version=max,secure=off,virtualization=true -cpu max -kernel /home/ckim/ProjX/LinuxDevDrv/kernel-release-RD-INFRA-2020.11.30/arch/arm64/boot/Image > -m 2048M -nographic -netdev user,id=net0,tftp=/opt/tftp -device e1000,netdev=net0 -machine iommu=smmuv3 --append "root=/dev/ram > init=/init nokaslr earlycon ip=dhcp hugepages=16" And by the -netdev and -device e1000 options, the user mode network backend is implemented in the qemu that makes us communicate with outside world. The virtual machine has the IP address 10.0.2.15. I've used this user networking mode many times before. (with full kernel default configuration, this tftp runs ok. but I wanted to reduce the kernel Image size from almost 36MB to about 6MB for fast running the test). Please see qemu network modes here : https://wiki.qemu.org/Documentation/Networking ADD : (as requested by dirkt) I have DHCP server inside the VM (see above Networking document), my VM has static IP address. and my host too. I believe DHCP client on VM works and DHCP server runs by the qemu program (so qemu program makes the network environment for the VM). I can login to the VM and I can do debug. (but I'm doing other task today). Here is the ip addr command response. / # tftp -g -r axpu_ldd_kc.ko 129.254.32.30 tftp: sendto: Network is unreachable / # ip addr 1: lo: mtu 65536 qdisc noop qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: sit0@NONE: mtu 1480 qdisc noop qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 ADD2 : (for dirkt's comment) I added PCI and PCIE and e1000 (Intel Etheret card) hoping this could be it. But it was not. Below is the result in the shell. ifconfig: SIOCSIFADDR: No such device route: SIOCADDRT: Network is unreachable /bin/sh: can't access tty; job control turned off / # tftp -g -r axpu_ldd_kc.ko 129.254.32.30 tftp: sendto: Network is unreachable

I wonder if anyone succeeded starting a tftpd in a network namespace (I'm using tftp-server-5.2-22.el7.x86_64.rpm)? I.e., starting tftpd in a default NS is trivial:

bash# systemctl start tftp
bash# systemctl status tftp
* tftp.service - Tftp Server
   Loaded: loaded (/usr/lib/systemd/system/tftp.service; indirect; vendor preset: disabled)
   Active: active (running) since Mon 2023-08-28 05:32:00 PDT; 3s ago
...

However, if I try to modify its service-unit file, namely this line:

[Service]
ExecStart=/usr/sbin/in.tftpd -s /var/lib/tftpboot

prepending command with either ip netns exec ns-red ... or with nsenter --net=/run/netns/ns-red ..., it never works, the system logs throws these errors:

systemd: tftp.service: Got no socket.
systemd: tftp.service: Failed to run 'start' task: Invalid argument
systemd: tftp.service: Failed with result 'resources'.
systemd: Failed to start Tftp Server.

Any help is greatly appreciated!

I've got a tftp server running on a virtual machine host, and I'm trying to tftp a linux kernel onto a TI AM33 processor. Both devices are connected on the same network switch. I'm noticing that TFTP is much slower on uboot 2020 compared to uboot 2013. My uboot 2013 has a transfer time of ~14 seconds, and 2020 has a transfer time of 5 minutes. Is there something in the configuration that I can change. I have set TFTP_BLOCKSIZE to 1464 and TFTP_WINDOWSIZE I've tried values between 1-16. Are there variables in the UDP stack that it would be good to check? This is a picture of wireshark for the device. I was wondering if the response time seems quick enough as well? In wireshark I'm seeing an average response time of .00043 seconds Is that slow for TFTP?

I've set up my pfsense server with tftp to support PXE booting. I've configured it to boot the latest (as of posting) version of netboot.xyz. This works to a point, but I've tried loading a few Linux images and they all seem to die with the same error messages. Key output text includes: ... mount: mounting tmpfs on /cdrom failed: Invalid argument ... curl: (23) Failed writing body (0 != 16384) Unable to find a live file system on the network ... Screenshot: I'm not sure if this is a tftp issue (I doubt it), a pfsense issue (I doubt it), a netboot.xyz issue (my main guess) or something else.

I want to try doing a PXE install for the first time. Every single tutorial I've read seem to indicate it requires a DHCP server configured to point to the TFTP server with the boot image. I don't understand why DHCP should be required though, isn't it possible to just manually configure computer's IP and network settings, and manually specify the IP where the TFTP server is located? If not, is there any particular reason why you wouldn't be allowed to do this, or given a simple prompt in the pxe menu asking to manually specify the network path?

I image bare metal servers to CentOS 7 and 8 all of the the time via network DHCP/TFTP using UEFI options, from a CentOS 7 PXE server. I'm looking to also build Ubuntu 20.04 servers. I've followed the docs, extracted vmlinuz and initrd from the casper dir of the Ubuntu ISO and just placed them at the base tftpboot dir. Things hum along, the ISO downloads to the client, after it enters BusyBox and fires up initramfs, it completes loading the ISO, but then stops at "Unable to find a live file system on the network". The thing is, I'm able to navigate and find the ISO on the client, and I'm even able to mount it and see that all of the contents are there. I've used different ISOs (Ubuntu desktop, for example). I've verified sha sums of the ISO. Here's the grub.cfg that I'm using, paring everything back to isolate the issue.

timeout=30
timeout_style=menu

menuentry 'Ubuntu 20.04.2' {
  linuxefi /vmlinuz ip=dhcp url=http://10.10.10.1/ubuntu-20.04.2-live-server-amd64.iso 
  initrdefi /initrd
}

menuentry 'CentOS 7.8' {
  linuxefi /centos/images/pxeboot/vmlinuz ip=dhcp inst.repo=http://10.10.10.1:/centos 
  initrdefi /centos/images/pxeboot/initrd.img
}

The CentOS install works just fine (/centos is the path to a dump of a CentOS ISO). Is there anything I'm missing?

I have a TFTP server running on Windows-10 machine. I am using MobaXterm it has TFTP server. I tested client server running on same windows 10, machine, able to communicate. TFTP -i 192.168.1.7 get test.txt Transfer successful: 11 bytes in 1 second(s), 11 bytes/s My TFTP server directory on windows is :-- **C:\S32G2_images** My target board, using uboot i am trying to TFTPboot buts connection is not establishing with the TFTP server running on the windows 10 machine. **Please suggest how to resolve this ?** Target Board Uboot setting :-- PC, running windows-10 :-- Ping to TFTP server working from Uboot :-- trying to connect to TFTP server from Linux U-boot failing :-- Windows Firewall setting :--

While setting up a PXE boot server on a CentOS 7 machine, I encountered a strange problem with TFTP. I cannot retrieve any files from the TFTP server without encountering a timeout problem. The boot process comes so far that I correctly get an IP address and a file name from the DHCP server. However, when the boot files are to be retrieved from the TFTP server, a "TFTP open timeout" message comes. If I manually make a TFTP connection to the PXE server from a local computer, I immediately get access to the server. But if I try with a "get pxelinux.0" command, I get another timeout message. My firewall is set up correctly and it also makes no difference if I completely turn off the firewall. SeLinux is also disabled. If I make a tcpdump on port 69 I get the following message: 12:34:33.477401 IP 172.16.1.202.ah-esp-encap > tools.dmz.tuxme.dk.tftp: 27 RRQ "pxelinux.0" octet tsize 0 12:34:35.481131 IP 172.16.1.202.acp-port > tools.dmz.tuxme.dk.tftp: 27 RRQ "pxelinux.0" octet tsize 0 12:34:39.490793 IP 172.16.1.202.msync > tools.dmz.tuxme.dk.tftp: 27 RRQ "pxelinux.0" octet tsize 0 12:34:45.477712 IP 172.16.1.202.gxs-data-port > tools.dmz.tuxme.dk.tftp: 27 RRQ "pxelinux.0" octet tsize 0 12:34:53.441801 IP 172.16.1.202.vrtl-vmf-sa > tools.dmz.tuxme.dk.tftp: 27 RRQ "pxelinux.0" octet tsize 0 12:35:03.384065 IP 172.16.1.202.newlixengine > tools.dmz.tuxme.dk.tftp: 32 RRQ "pxelinux.0" octet blksize 1456 12:35:39.414843 IP 172.16.1.202.newlixconfig > tools.dmz.tuxme.dk.tftp: 32 RRQ "pxelinux.0" octet blksize 1456 12:36:51.422568 IP 172.16.1.202.tsrmagt > tools.dmz.tuxme.dk.tftp: 32 RRQ "pxelinux.0" octet blksize 1456 12:38:39.406732 IP 172.16.1.202.tpcsrvr > tools.dmz.tuxme.dk.tftp: 32 RRQ "pxelinux.0" octet blksize 1456 Unfortunately, the system log shows nothing useful: Jan 15 13:13:19 tools xinetd: EXIT: tftp status=67 pid=7954 duration=0(sec) Jan 15 13:13:21 tools xinetd: START: tftp pid=7955 from=172.16.1.202 Jan 15 13:13:21 tools in.tftpd: no user tftp: Success Jan 15 13:13:21 tools xinetd: EXIT: tftp status=67 pid=7955 duration=0(sec) Jan 15 13:13:25 tools xinetd: START: tftp pid=7956 from=172.16.1.202 Jan 15 13:13:25 tools in.tftpd: no user tftp: Success Jan 15 13:13:25 tools xinetd: EXIT: tftp status=67 pid=7956 duration=0(sec) Jan 15 13:13:31 tools xinetd: START: tftp pid=7957 from=172.16.1.202 Jan 15 13:13:31 tools in.tftpd: no user tftp: Success The rights to the /var/lib/tftpboot directory are 0755. Here are my setup file: /etc/xinetd.d/tftp: service tftp socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -c -v -u tftp -p -U 117 -s /var/lib/tftpboot disable = no per_source = 11 cps = 100 2 flags = IPv4

On a Ubuntu GNS3 VM, I am trying to setup an active online-device. Here is the sketch of the Ifconfig on this GNS3 VM host: docker0: flags=4099 mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:7f:07:8c:49 txqueuelen 0 (Ethernet) ... ens160: flags=4163 mtu 1500 inet 10.31.1.116 netmask 255.255.240.0 broadcast 10.31.15.255 ... gns3tap0-1: flags=4163 mtu 1500 inet6 fe80::60a2:8ff:fe4d:5672 prefixlen 64 scopeid 0x20 ether 62:a2:08:4d:56:72 txqueuelen 1000 (Ethernet) ... lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) ... virbr0: flags=4163 mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ... And also on this VM, I have a tftp service started, that will provides the device license files for the incoming requests. I have double-checked and this tftp service is up and working OK. And here is the diagram of my GNS3 Project that has been setup on this GNS3 VM. As you may find out, there is connection sequence as: **cloud Cisco Router Switch -> X-1, which is my device at the end**. From my device console, I was able to ping outside network and VM, but somehow, I could not tftp the license file from it. here is my device console log: # # execute ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=115 time=16.352 ms 64 bytes from 8.8.8.8: seq=1 ttl=115 time=12.175 ms 64 bytes from 8.8.8.8: seq=2 ttl=115 time=18.031 ms 64 bytes from 8.8.8.8: seq=3 ttl=115 time=14.223 ms --- 8.8.8.8 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 12.175/15.195/18.031 ms # execute ping 10.31.1.116 PING 10.31.1.116 (10.31.1.116): 56 data bytes 64 bytes from 10.31.1.116: seq=0 ttl=63 time=11.037 ms 64 bytes from 10.31.1.116: seq=1 ttl=63 time=17.924 ms 64 bytes from 10.31.1.116: seq=2 ttl=63 time=14.249 ms --- 10.31.1.116 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 11.037/14.403/17.924 ms # execute bios get 10.31.1.116 FX200FTQ2109C0PU.rom tftp: timeout Get BIOS file failed... Any idea what could be wrong ? This is the first time I am trying to setup the devices in such environment. Thanks for the help.

I am using HPA's tftp server for PXE boot. When I try downloading an image from my tftp server using curl, the transfer rate is less than 3 MB/s, even on my 1Gb network. curl -o initrd.gz tftp://192.168.0.4:69/boot/debian/initrd.gz Is this an inherent limitation of the tftp protocol, or can this be configured?

Some time ago, I've configured LTSP on Debian machine. I've been using it from time to time and it worked. Today it stopped working and I cannot figure out what's wrong. Client says: Intel UNDI, PXE-2.1 PXE Software Copyright (C) 1997-2000 Intel Corporation Copyright (C) 2010 Oracle Corporation CLIENT MAC ADDR: 08 00 27 06 AB AB GUID: 8E607128-4C80-4960-BF72-347FDBDB27B5 CLIEHT IP: 192.168.1.163 MASK: 255.255.255.0 DHCP IP: 192.168.1.1 GATEWAY IP: 192.168.1.1 PXE-E35: TFTP read timeout PXE-E39: TFTP cannot read from connection PXE-MOF: Exiting Intel PXE ROM. FATAL: Could not read from the boot medium! System halted. I took a look at server's log, but tftp's logs doesn't seem to be useful: Dec 7 22:44:25 Serwer in.tftpd: RRQ from 192.168.1.163 filename /ltsp/i386/pxelinux.0 Dec 7 22:44:25 Serwer in.tftpd: tftp: client does not accept options Dec 7 22:44:25 Serwer in.tftpd: RRQ from 192.168.1.163 filename /ltsp/i386/pxelinux.0 (those messages above are generated by tftp with --verbose mode). So it looks like I've a connection from tftp clients to server, but why did it die? I could not find any way to see more log informations.

I am working with an external SATA drive, and would like to be able to have remote hosts be able to TFTP download files from it. However, when I set my TFTP base directory to my mount location, I get the following error on the client when I attempt to download:

: (68) TFTP: File Not Found

As a sanity check, I stopped TFTP on the server, unmounted the drive, and created a file in the root filesystem with the same name, in same directory that I had mounted the drive to previously. I then restarted TFTP, tried to download again on the client, and had no issues pulling down the file. Are there any considerations I may have missed in regards to trying to TFTP from the drive? For what it's worth, the TFTP server is running on a VirtualBox Red Hat 7.3 VM, and my client is the VM host (Windows 10). I'm using cURL from a Cygwin session to do the TFTP downloads

On my home LAN, I have * A router/switch which is also a DHCP server * A desktop * A (really really old) laptop, which won't even boot from USB I want to use PXE to install a (32-bit) Linux distro on that laptop. I have two problems (that I know of): 1. The pages I see discuss doing this (e.g. this question here on the site) all say I need to setup a DHCP server on my machine... which is fine, except that there's already that other DHCP server. Won't the laptop prefer the other server? 2. Will any bootable 32-bit ISO work? 3. How do I know which files from the distro's mounted ISO to copy where? Note: To be more specific, I'll try to install Linux Lite .