Invalid destination MAC address in TFTP RRQ

Open
#745 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
raspberry-pi
Domain
embedded-iot, networking

Research direction

Start by reproducing network boot on an RPi 3 and capture the ARP and TFTP traffic described in the report. Compare the RRQs for bootcode.bin and later files, focusing on when the destination MAC becomes zero. Done means subsequent RRQ packets use the resolved TFTP server MAC and are received by the server.

Written by the indexing model from the issue text.

Description

Waiting for internal response

When booting from network, RPi 3 successfully loads bootcode.bin from TFTP server, then bootcode is attempting to load other files, but with zero destination mac address, and RRQ packets have not been received by TFTP server.

I've tried last master version of bootcode.bin, last "next" and some older versions with no luck.

There is a dump:
11:59:07.446234 b8:27:eb:f9:92:f7 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 10.23.16.13 tell 10.23.16.10, length 46
11:59:07.446251 38:d5:47:1c:aa:34 > b8:27:eb:f9:92:f7, ethertype ARP (0x0806), length 42: Reply 10.23.16.13 is-at 38:d5:47:1c:aa:34, length 28
11:59:07.446375 b8:27:eb:f9:92:f7 > 38:d5:47:1c:aa:34, ethertype IPv4 (0x0800), length 63: 10.23.16.10.49152 > 10.23.16.13.69: 21 RRQ "bootcode.bin" octet
11:59:07.469377 b8:27:eb:f9:92:f7 > 38:d5:47:1c:aa:34, ethertype IPv4 (0x0800), length 62: 10.23.16.10.49152 > 10.23.16.13.69: 20 RRQ "bootsig.bin" octet
11:59:09.589113 b8:27:eb:f9:92:f7 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 71: 10.23.16.10.49154 > 10.23.16.13.69: 29 RRQ "autoboot.txt" octet tsize 0
11:59:11.155156 b8:27:eb:f9:92:f7 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 69: 10.23.16.10.49155 > 10.23.16.13.69: 27 RRQ "config.txt" octet tsize 0
11:59:12.155515 b8:27:eb:f9:92:f7 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 71: 10.23.16.10.49156 > 10.23.16.13.69: 29 RRQ "recovery.elf" octet tsize 0
11:59:12.451694 38:d5:47:1c:aa:34 > b8:27:eb:f9:92:f7, ethertype ARP (0x0806), length 42: Request who-has 10.23.16.10 tell 10.23.16.13, length 28
11:59:12.451806 b8:27:eb:f9:92:f7 > 38:d5:47:1c:aa:34, ethertype ARP (0x0806), length 60: Reply 10.23.16.10 is-at b8:27:eb:f9:92:f7, length 46
11:59:13.451956 b8:27:eb:f9:92:f7 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 68: 10.23.16.10.49157 > 10.23.16.13.69: 26 RRQ "start.elf" octet tsize 0
11:59:15.158692 b8:27:eb:f9:92:f7 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 68: 10.23.16.10.49158 > 10.23.16.13.69: 26 RRQ "fixup.dat" octet tsize 0

Dominant language
No language data
Stars
5.6k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/firmware

All issues in raspberrypi/firmware

Similar issues

More Embedded & IoT issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.