Hi,
yesterday I've upgraded from 23 to 24. This completely broke my DHCP setup. I use VLAN's with a central DHCP server which evaluates DHCP option 82 and agent.circuit-id like this:
class "PL-VLAN204" {
match if option agent.circuit-id = "lagg0_vlan204";
}
DHCP relay with v23 tags the DHCP requests with the interface name in agent.circuit-id. DHCP relay in v24 stopped doing so and seems to use tags like "001a", "001b" and so on. For some reason my DHCP server does not match these tags.
How to get back the old agent.circuit-id's ?
TIA
Matthias
Ditto to this, DHCP relay is completely broken now after updating this morning. I see requests going to Infoblox and Infoblox is responding. Devices aren't getting IPs.
Can someone explain this to me? I get the part that it's not working, but the details that matter from the DHCRelay side elude me (is it a setting, can it be turned off) and pointing to "config changes" that may be in part dhcrelay's fault but also appear to be a mismatch between client and server that can likely be adjusted in one of those easily?
Cheers,
Franco
Hi,
I'm sorry but I have to bring this topic back up.
Today I upgraded my Opnsense:
"opnsense upgraded: 24.1.4 -> 24.1.9_4"
My network consists of different VLANs and I had configured DHCP Relay with option 82 for each VLAN.
I use a pair of KEA DHCPv4 Servers in VLAN 20.
Before the update DHCP relay used to fill option 82 with the Device Name of the VLAN, e.g.
EVAL_DEBUG_OPTION Pushing option 82 with value 0x010A766C616E302E312E3232
which could be resolved to ASCII "vlan0.1.22" by KEA.
After the update that behaviour seems to be broken on OPNsense DHCP Relay side.
In KEA i only receive
EVAL_DEBUG_OPTION Pushing option 82 with value 0x01020002020400000000
This results in all my devices not getting IP adresses atm.
If I can help out tracking down that bug in any way please tell me how to support :)
Best Regards
Dennis
I'm also experiencing this problem on 24.7.6.
Agent Circuit ID seems to be changing after reboot on the same relay entry. I've observed values like 000f, 0010.
This makes it impossible to apply policies on a DHCP server based on agent ID.