kczekirda added a comment.
https://reviews.freebsd.org/D10854
REVISION DETAIL
https://reviews.freebsd.org/D10603
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, oshogbo, tsoome, bapt, sbruno, freebsd-net-list, #network
Cc: avg, rgrimes
__
bapt added a comment.
https://lists.freebsd.org/pipermail/freebsd-hackers/2017-May/051053.html
REVISION DETAIL
https://reviews.freebsd.org/D10603
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, oshogbo, tsoome, bapt, sbruno, freebsd-net-list,
avg added a comment.
My opinion is that pxeboot is in the same league as ipxe. Of course, pxeboot
is more specialized, but it is still a chain-loaded PXE boot client.
I see two possibilities of providing FreeBSD specific boot information.
Either we provide it via FreeBSD vendor extensions
bapt added a comment.
The other option would be to use nfs:/ http:/ etc and tell the user they
should configure their dhcp server to only send the rootpath if the loader is
not ipxe, that may work, but not allow ipxe server would allow to do that
(checking userclass iPXE)
REVISION DETAIL
kczekirda added a comment.
tftpfs it's not bad, but you don't know what ipxe will do in the next commit.
The problem is that we want to think about all.
REVISION DETAIL
https://reviews.freebsd.org/D10603
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To:
tsoome added a comment.
In https://reviews.freebsd.org/D10603#223350, @bapt wrote:
> What I mean is we cannot use the one I listed above because they are
interpreted by ipxe. For example if one netboots from qemu it will use ipxe
under the hood first, then if you pass rootpath tftp:/ ipx
bapt added a comment.
What I mean is we cannot use the one I listed above because they are
interpreted by ipxe. For example if one netboots from qemu it will use ipxe
under the hood first, then if you pass rootpath tftp:/ ipxe will say
Next server: 192.168.42.1
Filename: /pxeboot
tsoome added a comment.
In https://reviews.freebsd.org/D10603#223317, @bapt wrote:
> so ipxe will catch and use: iscsi:/ tftp:/ nfs:/ http:/ https:/ etc, maybe
we should use tftpfs:/
>
> In this case pxe will give a message saying (ignore unsupported root path)
and continue what do y
bapt added a comment.
so ipxe will catch and use: iscsi:/ tftp:/ nfs:/ http:/ https:/ etc, maybe we
should use tftpfs:/
In this case pxe will give a message saying (ignore unsupported root path)
and continue what do you think?
REVISION DETAIL
https://reviews.freebsd.org/D10603
EMAIL
kczekirda added a comment.
In https://reviews.freebsd.org/D10603#223305, @tsoome wrote:
> In https://reviews.freebsd.org/D10603#223301, @bapt wrote:
>
> > We need to find a better mechanism, as this break usage where rootpath
/something was before this patch expecting NFS to be locate
tsoome added a comment.
In https://reviews.freebsd.org/D10603#223301, @bapt wrote:
> We need to find a better mechanism, as this break usage where rootpath
/something was before this patch expecting NFS to be located on the same
serveur as the tftp server. This is now broken (it is used
bapt added a comment.
We need to find a better mechanism, as this break usage where rootpath
/something was before this patch expecting NFS to be located on the same
serveur as the tftp server. This is now broken (it is used quite a lot
apparently)
REVISION DETAIL
https://reviews.freebsd.
bapt closed this revision.
bapt added a comment.
Committed as https://reviews.freebsd.org/rS317886
REVISION DETAIL
https://reviews.freebsd.org/D10603
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, oshogbo, tsoome, bapt, sbruno, freebsd-net-l
bapt accepted this revision.
REVISION DETAIL
https://reviews.freebsd.org/D10603
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, oshogbo, tsoome, bapt, sbruno, freebsd-net-list, #network
Cc: rgrimes
___
tsoome accepted this revision.
This revision has a positive review.
REVISION DETAIL
https://reviews.freebsd.org/D10603
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, oshogbo, tsoome, bapt, sbruno, freebsd-net-list, #network
Cc: rgrimes
_
bapt added a comment.
Yes simple and efficient I like this I wonder why I took a very complicated
path in the first place.
Give me some time to test it on our production server. I don't think we need
to keep compatibility with option 150 given as far as I know only I and @sbruno
used it
rgrimes added a comment.
I am happy with this, it moves us forward, and removes the option 150 hack.
I am pretty sure that you can actually dole out more than 1 tftp server by
careful use of dhcp server configurations, ie the dhcp server has full control
over what next-server you are told t
kczekirda created this revision.
REVISION SUMMARY
Don't use DHCP 150 option to decide which protocol use to netboot. When
root-path includes ip address - go thru NFS, if ip address not exists in
root-path - go thru TFTP from server which ip address is in next-server.
But there is one limita
18 matches
Mail list logo
