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.

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

Explicitly call-out Vendor Class identifier for PXE #1637

Merged
merged 1 commit into from
Jun 8, 2021

Conversation

virtualjmills
Copy link
Contributor

Vendor Class identifier was buried in some tcpdump parsed output further down in the page. Explicitly calling it out up-top, in some environments this is used as an initial pass filter by the DHCP server to determine which set of responses / behavior to use when interacting with the PXE Client system.

Vendor Class identifier was buried in some tcpdump parsed output further down in the page. Explicitly calling it out up-top, in some environments this is used as an initial pass filter by the DHCP server to determine which set of responses / behavior to use when interacting with the PXE Client system.
@lurch
Copy link
Contributor

lurch commented Aug 1, 2020

Is this the same for network-booting on both a Pi 3B+ and also a Pi 4B ?
ping @timg236

Copy link
Contributor

@timg236 timg236 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same on pi4

@JamesH65
Copy link
Contributor

JamesH65 commented Oct 5, 2020

@timg236 Are you OK with this change? Seems sane to me.

@timg236
Copy link
Contributor

timg236 commented Oct 5, 2020

The ROM doesn't do TFTP boot on Pi4 although the behaviour is the same in bootloader. I think this page is really about Pi3 ROM

@lurch
Copy link
Contributor

lurch commented Oct 6, 2020

I wonder if that page needs to be "refactored" slightly to show which parts of the net-boot process are different between Pi3 ROM and Pi4 EEPROM (e.g. Pi4 EEPROM probably doesn't request bootcode.bin?), and which parts are common to both? 🤷

@aallan
Copy link
Contributor

aallan commented Jun 7, 2021

I'd encourage you to wrap this PR up in the next week or so as we're in the process of transitioning the documentation from the current Markdown-based source format to Asciidoc. At some point soon — probably around the end of June, beginning of July — we will freeze the current documentation repo. After that time contributions and PRs based on the Markdown source will not be accepted, and any PRs that are still open will be closed.

See #1911 for full details.

@timg236
Copy link
Contributor

timg236 commented Jun 8, 2021

ok to merge

@aallan aallan added ready to merge The OP says this PR is ready to merge? Anyone object? and removed 7 day closure labels Jun 8, 2021
@aallan aallan merged commit d1ce2a7 into raspberrypi:master Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to merge The OP says this PR is ready to merge? Anyone object?
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants