Skip to content
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.

Sign up for GitHub

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

Jump to bottom

RPI3B+ bootloader possibly doesn't handle dhcp correctly #986

Closed
mangodan2003 opened this issue May 3, 2018 · 4 comments
Closed

RPI3B+ bootloader possibly doesn't handle dhcp correctly #986

mangodan2003 opened this issue May 3, 2018 · 4 comments
Labels
Bootcode/Netboot/PXE Specific flag for issues with the bootcode and network booting Waiting for internal response

Comments

@mangodan2003
Copy link

When booting a bunch (8 in this case) of slave/client RPis simultaneously occasionally 2 or more will be offered the same IP. At first I thought this was an error on the part of the DHCP server, but apparently not [1].

When this happens all PIs offered the same IP fail to boot, where as in theory one should request and get the IP whilst the others will have to start the process again.

[1] http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q1/010353.html

We have worked around this for now but this might need investigating.
@mangodan2003
Copy link
Author

mangodan2003 commented May 3, 2018 •
edited
Loading

on top of this there seems to be a error with the timing of retries, after power on there is a delay of some seconds before the first attempt, when this fails the following 3 attempts all happen at near the same time then a short while later is the final attempt :

May 3 13:36:13 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:b3:ab:c2
May 3 13:36:13 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.84 b8:27:eb:b3:ab:c2
May 3 13:36:16 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:95:fa
May 3 13:36:16 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.76 b8:27:eb:87:95:fa
May 3 13:36:19 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:53:de:0a
May 3 13:36:19 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.50 b8:27:eb:53:de:0a
May 3 13:36:22 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:d9:59:00
May 3 13:36:22 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.83 b8:27:eb:d9:59:00
May 3 13:36:25 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:fb:d8
May 3 13:36:25 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.92 b8:27:eb:87:fb:d8
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.73 b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.91 b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:fb:d8
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.92 b8:27:eb:87:fb:d8
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:95:fa
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.76 b8:27:eb:87:95:fa
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:53:de:0a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.50 b8:27:eb:53:de:0a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:d9:59:00
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.83 b8:27:eb:d9:59:00
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:b3:ab:c2
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.84 b8:27:eb:b3:ab:c2
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.91 b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.73 b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:c3:3c:2e
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.74 b8:27:eb:c3:3c:2e
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:d9:59:00
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.83 b8:27:eb:d9:59:00
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:fb:d8
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.92 b8:27:eb:87:fb:d8
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:b3:ab:c2
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.84 b8:27:eb:b3:ab:c2
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:53:de:0a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.50 b8:27:eb:53:de:0a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:95:fa
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.76 b8:27:eb:87:95:fa
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.91 b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.73 b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:c3:3c:2e
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.74 b8:27:eb:c3:3c:2e
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:53:de:0a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.50 b8:27:eb:53:de:0a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:fb:d8
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.92 b8:27:eb:87:fb:d8
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:d9:59:00
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.83 b8:27:eb:d9:59:00
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:b3:ab:c2
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.84 b8:27:eb:b3:ab:c2
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:95:fa
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.76 b8:27:eb:87:95:fa
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.73 b8:27:eb:2e:94:16
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.91 b8:27:eb:1d:7e:2a
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPREQUEST(enp1s0) 10.3.2.74 b8:27:eb:c3:3c:2e
May 3 13:36:28 router dnsmasq-dhcp[772]: DHCPACK(enp1s0) 10.3.2.74 b8:27:eb:c3:3c:2e raspberrypi
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:b3:ab:c2
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.84 b8:27:eb:b3:ab:c2
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:95:fa
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.76 b8:27:eb:87:95:fa
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:87:fb:d8
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.92 b8:27:eb:87:fb:d8
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:53:de:0a
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.50 b8:27:eb:53:de:0a
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:d9:59:00
May 3 13:36:32 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.83 b8:27:eb:d9:59:00
May 3 13:36:33 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:2e:94:16
May 3 13:36:33 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.73 b8:27:eb:2e:94:16
May 3 13:36:33 router dnsmasq-dhcp[772]: DHCPDISCOVER(enp1s0) b8:27:eb:1d:7e:2a
May 3 13:36:33 router dnsmasq-dhcp[772]: DHCPOFFER(enp1s0) 10.3.2.91 b8:27:eb:1d:7e:2a

@mangodan2003
Copy link
Author

Ignore the last post, it seems to be some odd behaviour of syslog timestamping. tcpdump shows there are seconds between each.

@mangodan2003 mangodan2003 mentioned this issue May 8, 2018
Closed
@JamesH65
Copy link
Contributor

JamesH65 commented Jan 9, 2019

@ghollingworth I believe there have been quite a few changes in boocode, are they likely to have fixed this?

@JamesH65 JamesH65 added Waiting for internal response Bootcode/Netboot/PXE Specific flag for issues with the bootcode and network booting labels Jan 9, 2019
@ghollingworth
Copy link
Contributor

This is a known issue with the way the Pi uses the DHCP service.

@arcivanov arcivanov mentioned this issue Feb 21, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bootcode/Netboot/PXE Specific flag for issues with the bootcode and network booting Waiting for internal response
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ghollingworth @mangodan2003 @JamesH65