Project

General

Profile

Actions
Copy link

Bug #12896

closed

``HTTPClient`` option does not work for static mappings

Added by Viktor Gurov about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
DHCP (IPv4)
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:

Description

The HTTPClient option works fine for interfaces and pools, but not for static mappings.

Related issues

Related to Feature #11659: Support for UEFI HTTP Boot option in DHCPv4 ServerClosedViktor Gurov03/10/2021

Actions
Actions
Copy link
 #1

Updated by Viktor Gurov about 2 years ago

  • Related to Feature #11659: Support for UEFI HTTP Boot option in DHCPv4 Server added
Actions
Copy link
 #3

Updated by Jim Pingle about 2 years ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.7.0
  • Plus Target Version set to 22.05
Actions
Copy link
 #4

Updated by Viktor Gurov about 2 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Danilo Zrenjanin about 2 years ago

  • Status changed from Feedback to Resolved

Tested aginst:

2.7.0-DEVELOPMENT (amd64)
built on Sat Mar 05 06:18:38 UTC 2022
FreeBSD 12.3-STABLE

It looks OK!

host s_lan_0 {
    hardware ethernet 22:33:44:55:66:77;
    fixed-address 192.168.20.22;

    if substring (option vendor-class-identifier, 0, 10) = "HTTPClient" {
        filename "http://192.168.20.13/boot/grub/x86_64-efi/core.efi";
    }

Marking this ticket resolved.

Actions
Copy link
 #6

Updated by Jim Pingle about 2 years ago

  • Subject changed from HTTPClient option does not work for static mappings to ``HTTPClient`` option does not work for static mappings

Updating subject for release notes.

Actions
Copy link

Also available in: Atom PDF