User Details
- User Since
- Feb 7 2016, 8:29 PM (512 w, 4 d)
- Roles
- Administrator
Aug 17 2025
Jul 22 2025
Jul 18 2025
Jul 17 2025
Jul 11 2025
Jul 9 2025
Jun 30 2025
Jun 29 2025
Jun 22 2025
@dmbaturin if we can't identify a fix, why do we put 1.4.3? Must be moved to rolling
May 21 2025
Apr 14 2025
Apr 13 2025
Mar 6 2025
Feb 25 2025
Jan 27 2025
Jan 14 2025
Jan 10 2025
Dec 28 2024
Dec 7 2024
Nov 28 2024
Nov 26 2024
Nov 21 2024
@sarthurdev and need to be in 1.4?
@sarthurdev, does this require backporting?
Nov 20 2024
@Viacheslav @dmbaturin need to be fixed in 1.4.1
Nov 18 2024
Nov 17 2024
@rob, we may need a bit of help with this from you
Nov 16 2024
For support requests, use forum.vyos.io
Use forum.vyos.io for support requests
Nov 15 2024
Maybe ask the author to resubmit against the current?
Nov 14 2024
@evgmol can you please review the pull request provided, if ok we should merge it
DHCP option 66 is not intended to carry an HTTP URL. According to RFC 2132, option 66 is specifically designed to provide the TFTP (Trivial File Transfer Protocol) server name, typically used to specify a hostname or IP address of a server from which the client can download a boot file via TFTP, not HTTP.
can be ipv4 or hostname
This is not a bug, this is according to RFC
@Apachez I recall you have cited it but do not recall where it was here or at the forum
Nov 13 2024
Nov 11 2024
Hey @insignia96
Give it a try and come back if you have questions or doubts
@Viacheslav @dmbaturin can you take a look and suggest if the approach suggested by @insignia96 is ok?
Nov 10 2024
Nov 9 2024
Thanks for bringing this to our attention @paulywog
Nov 8 2024
@Viacheslav, does this require a backport?