arm server ,pxe can't get snp.efi

[fremindmm]

I have an arm server , i install tinker ，when i apply my arm server ，
pxe can't get snp.efi ，

Expected Behaviour

smee log
{"level":"info","ts":1724672419.027686,"caller":"reservation/handler.go:86","msg":"received DHCP packet","mac":"00:07:3e:93:57:34","xid":"0xe6d566bb","interface":"eth0","type":"DISCOVER"}
{"level":"info","ts":1724672419.0279543,"caller":"reservation/handler.go:141","msg":"sent DHCP response","mac":"00:07:3e:93:57:34","xid":"0xe6d566bb","interface":"eth0","type":"OFFER","bootFileName":"snp.efi","nextServer":"192.168.16.220","ipAddress":"192.168.16.171","destination":"10.42.0.9:67"}

server pxe log

when i debug i can see logs 👍
root@node172:/etc# tftp 192.168.16.220
tftp> get snp.efi
Transfer timed out.

Current Behaviour

can‘t to pxe and install os， block in tftp process。

Possible Solution

use cobbler

Steps to Reproduce (for bugs)

use a netcard I350 Gigabit Network Connection to pxe you can see this bug

Context

I use a nfs server mount iso by redfish ,skip this bug.
cobbler also can work.

Your Environment

ubuntu 22.04
192.168.16.220 server
client 192.168.16.171 arm
pxe net card info
*-network:0
description: Ethernet interface
product: I350 Gigabit Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:2b:00.0
logical name: enp43s0f0
version: 01
serial: 00:07:3e:93:57:34
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.15.0-119-generic duplex=full firmware=1.63, 0x800009fb ip=192.168.16.171 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:28 memory:80065e00000-80065e1ffff ioport:303000(size=32) memory:80065e40000-80065e43fff memory:82802400000-8280241ffff memory:82802420000-8280243ffff

• How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:
  use k3s

• Link to your project or a code example to reproduce issue:

[jacobweinstock]

Hey @fremindmm , thanks for posting. Mind sharing how you have deployed Smee? Mind clarifying all the IP's involved here? 192.168.16.220, 192.168.16.171, 192.168.0.87. Also, what is the layer2 subnet in use here?