VLAN and DHCP Relay Issues on Hyper-V

[franco]

ok happy to hear

[Seimus]

If its not DNS, its asymmetric routing, if its not asymmetric routing its Hyper-V 

Good to hear you found the problem. I didn't even know There is such a options like DHCP Guard.

Regards,
S.

[Bob.Dig]

I didn't even know There is such a options like DHCP Guard.

Why not?
It is right in the GUI, well explained there and disabled by default.

Hope this helps others!

I don't think so, it is kinda to obvious.

[Seimus]

I didn't even know There is such a options like DHCP Guard.

Why not?
It is right in the GUI, well explained there and disabled by default.

Because I don't use Hyper-V so I cant not know things about systems I do not use.

Regards,
S.

[authelia]

As a data point it would help to know if this is is a version before 24.1.6 or if this started with 24.1.6. If we don't have these data points it's harder to narrow this down (even if it is just a configuration hiccup).

This problem occurs only after 24.1.6.

• I am not using Hyper-V
• Everything is on physical devices.
• DHCP guard is not enabled.
• As a workaround, I have enabled DHCPv4 on Opnsense

[WM54]

Unfortunately I am also facing DHCP relay issues since updated to 24.1.6 - in earlier versions all worked as expected and I observed no issues.

Currently it seems that the DHCP relays suddenly stop to work and the clients are not longer able to receive DHCP addresses or renew the lease. Until lease expiry, the clients work as expected, but when the has expired, they are disconnected.
Also I am observing "BAD_ADDRESS" entries in the DHCP server, which I didn't notice before.

In some cases a restart of the DHCP relays solves the issue for some time, but not in every case.
Any suggestions if it is possible to log the activity of the relays? I did not find a regarding log yet.

I am using three DHCP relays to forward the DHCP requests of three subnets to one central DHCP server.
OPNsense is vitualized based on ESXi hypervisor - each OPNsense subnet uses its own virtual NIC  provided by ESXi.

Any hints, how to enclose the issue are highly appreciated.
Many thanks in advance!

Best regards,
WM54

[franco]

authelia and WM54

I appreciate the input, but can we avoid cluttering a topic that was solved by the original poster?

Open new threads please or find one that matches your problem.


Cheers,
Franco

[WM54]

Thanks for the hint - opened new thread.

Regards,
WM54

[phwon]

I didn't even know There is such a options like DHCP Guard.

Why not?
It is right in the GUI, well explained there and disabled by default.

Hope this helps others!

I don't think so, it is kinda to obvious.

There's always one! Top points for least valuable post of the day #yourock

[franco]

Let's not trash on each other. It's obviously obvious in hindsight as that one saying goes.

But to be frank I think this thread will help a number of people in the future running into this problem so thanks for everyone involved.


Cheers,
Franco