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,
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
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
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
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
___
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
bapt added a comment.
This is ugly, but maybe less that abusing dhcp options :)
REVISION DETAIL
https://reviews.freebsd.org/D10485
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, bapt, oshogbo, tsoome, sbruno, #network, freebsd-net-list, imp,
bapt added a comment.
Using the dhcp option 150 is a hack, I used one that is not used and not
common to avoid any issue with existing setups where option 66 is used for
something else (given it is common) I was maybe going to far with that.
IMHO the best is to detect the protocol in the
bapt accepted this revision.
REVISION DETAIL
https://reviews.freebsd.org/D9847
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, tsoome, glebius, freebsd-net-list, #network, gnn, smh, oshogbo,
bapt
Cc: smh
_
This revision was automatically updated to reflect the committed changes.
Closed by commit rS311659: remove network mask calculation for Classful network
(authored by bapt).
REPOSITORY
rS FreeBSD src repository
CHANGES SINCE LAST UPDATE
https://reviews.freebsd.org/D8740?vs=22858&id=23726
RE
bapt accepted this revision.
REVISION DETAIL
https://reviews.freebsd.org/D8740
EMAIL PREFERENCES
https://reviews.freebsd.org/settings/panel/emailpreferences/
To: kczekirda, imp, ian, oshogbo, tsoome, freebsd-net-list, glebius, #network,
bapt
Cc: glebius
_
13 matches
Mail list logo
