"
Hello dear OPNsense Community,
I have the following problem since a few days:
Any packets sent by the OPNsense itself, the OPNsense sends with the source IP 0.0.0.0 instead of the lan interface IP. Any other packet flow works. The error probably occurred during the upgrade from version 22.4.3 to 22.10. I'm not 100% sure, because as far as I know it's not possible to downgrade from 22.10 to 22.4 (if this is somehow possible, please explain how).
You can detect the problem by sending a ping from the OPNsense to the LAN and watching it in the live view.
The source IP is always 0.0.0.0.
If you ping something in the WAN the correct WAN IP is used as source IP.
The reason why the whole behavior is so problematic in the first place is that for authentication of the users of the OpenVPN, LDAP is used. Due to the 0.0.0.0 the domain controller cannot send a response to an LDAP request and thus Home Office becomes impossible.
I have the following problem since a few days:
Any packets sent by the OPNsense itself, the OPNsense sends with the source IP 0.0.0.0 instead of the lan interface IP. Any other packet flow works. The error probably occurred during the upgrade from version 22.4.3 to 22.10. I'm not 100% sure, because as far as I know it's not possible to downgrade from 22.10 to 22.4 (if this is somehow possible, please explain how).
You can detect the problem by sending a ping from the OPNsense to the LAN and watching it in the live view.
The source IP is always 0.0.0.0.
If you ping something in the WAN the correct WAN IP is used as source IP.
The reason why the whole behavior is so problematic in the first place is that for authentication of the users of the OpenVPN, LDAP is used. Due to the 0.0.0.0 the domain controller cannot send a response to an LDAP request and thus Home Office becomes impossible.
