On Tue, Mar 03, 2020 at 10:35:51PM +1100, David wrote: > On Tue, 3 Mar 2020 at 19:38, <to...@tuxteam.de> wrote: > > On Tue, Mar 03, 2020 at 12:36:42AM +0100, deloptes wrote: > > > > The trick was to add following line to the dhcpd.conf > > > > > > option vendor-encapsulated-options > > > 6:1:3:a:4:0:50:58:45:9:14:0:0:11:52:61:73:70:62:65:72:72:79:20:50:69:20:42:6f:6f:74:ff;
[...] > > Thanks for making all of us smarter. To throw my two cents in, I did some > > legwork, and (as usually) Wikipedia [1] provides some light. > > [...] > > > But the codes, alas, are not interpretable according to the > > ref given. An exercise for the reader :) > > > > [1] https://en.wikipedia.org/wiki/DHCP#Options > > My guess (untested) would be per Section 8.4 in > https://tools.ietf.org/html/rfc2132 > with the leading Code=43 and Len=n > octets possibly prepended by the software. > > And a bit of idle searching [1] suggests that perhaps (untested) > only the trailing "Raspberry Pi Boot" string is required. Thanks :) Cheers -- t
signature.asc
Description: Digital signature
