John Howie wrote:
> Hi Rick,
>
> That is an excellent point and a good debate to have.
>
> I have not looked in detail at how PXEBOOT does it, but I think a
> clean up of the code to somehow pass arguments to the kernel is
> preferable to having a diskless client send a slew of needless
> request
On 6/1/14, 8:01 PM, Rick Macklem wrote:
John Howie wrote:
[...]
Actually, I tend to think that using the code in sys/nfs/bootp_subr.c
is preferable to using the NFS stuff in stand that pxeboot does.
The only reason I know for pxeboot doing the NFS stuff and filling in
the nfsv3_diskless struct
Hi Rick,
That is an excellent point and a good debate to have.
I have not looked in detail at how PXEBOOT does it, but I think a clean up of
the code to somehow pass arguments to the kernel is preferable to having a
diskless client send a slew of needless requests to the DHCP server to request
Hi Steinar,
I could ask you to 'prove it', too, but I can easily check when I get back from
my current travels :-)
It important to note that even if it does (as I think it does) it is NOT in
violation of the RFC. The RFC simply says that if a client wants something it
should ask for it, and no
> In short, no, I have no packet traces. Given that the DHCP code in the
> FreeBSD boot loader and NFS subsystem does not request those options, but
> that ISC-DHCP does provide them, I will go out on a limb and say that it
> must be serving them without being asked if they are configured.
In that
John Howie wrote:
> Hi all,
>
> I apologize for the cross posting of this email, but I believe it
> will be
> of interest to people across all three groups. Please feel free to
> forward
> to additional groups if you feel they would benefit.
>
> I have seen a few posts on and off over the years a
Hi Steinar,
In short, no, I have no packet traces. Given that the DHCP code in the
FreeBSD boot loader and NFS subsystem does not request those options, but
that ISC-DHCP does provide them, I will go out on a limb and say that it
must be serving them without being asked if they are configured.
Re
> Section 3.5 of RFC 2131 (the DHCP RFC) states that "...Second, in its
> initial DHCPDISCOVER or DHCPREQUEST message, a client may provide the
> server with a list of specific parameters the client is interested in"
> and "...The client can inform the server which configuration parameters
> the cl
Hi all,
I apologize for the cross posting of this email, but I believe it will be
of interest to people across all three groups. Please feel free to forward
to additional groups if you feel they would benefit.
I have seen a few posts on and off over the years about Windows Server
DHCP not working
