Log messages for received DHCP messages in the context of the corresponding IKE_SA about strongswan HOT 3 CLOSED

This makes it very difficult to find out to which connection these lines belong.

That's because many of these don't belong to a connection. There are simply some messages that are logged without a checked out IKE_SA, so no context can be provided to the logger plugins.

In particular sending/receiving IKE messages happens in different threads before/after IKE_SAs have been checked out/in. Same goes for the job creation based on kernel events, which happens before an SA is checked out based on that information.

The DHCP messages are currently logged by the thread that receives packets on the AF_PACKET socket, before the threads waiting for them (which run in the context of an IKE_SA) pick them up. I guess we could move them, see the 417-dhcp-log branch.

from strongswan.

I am pretty sure that a DHCP_OFFER or a DHCP_ACK do belong to a connection. Same goes for "sending packet ... to 10.145.142.13[50894]". How would strongswan know the destination address and port number?

from strongswan.

Did you read my explanation above?

from strongswan.