• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Set up multiple option 43 sets in combination with option 60 vendor class

Scheduled Pinned Locked Moved DHCP and DNS
dhcpdhcpoption
1 Posts 1 Posters 831 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D
    Dakpan
    last edited by Apr 8, 2020, 7:32 AM

    Is there a way in the pfsense GUI to link an option 43 to a specific vendor class? ( the so called option 60)
    I use option 43 on a lot of boxes with no issues, but now I stumbled on a case where I had to set up option 43 for more than one vendor.

    Lets take a quick example to point out my problem:

    I have Unifi AP's who wants to receive a hex in DHCP option 43, value C0:A8:01:01 for example.
    The device identifies itself as vendor class "ubnt"
    On the other hand I have Mitel telephones who want to receive a hex in DHCP option 43, value 03:04:AC:10:1E:01
    The device identifies itself as vendor class "Amadeus IP Phone"

    I find no way to link my option 60 to one of the option 43's, I thought perhaps the order would do, but that isn't the case.
    If I set up my additional DHCP options like so:

    60 STRING "ubnt"
    43 STRING C0:A8:01:01
    60 STRING "Amadeus IP Phone"
    43 STRING 03:04:AC:10:1E:01

    My phones receive only the ubnt option 43, if I turn the order around, my ubnt's only get the phones option 43.
    In other words, the PF presents the first option 43 and makes an option 60 completely useless.

    Anyone inspired for a workaround?

    1 Reply Last reply Reply Quote 0
    • C CZvacko referenced this topic on May 16, 2024, 9:36 AM
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
      This community forum collects and processes your personal information.
      consent.not_received