New commits:
commit 19f475fab2623f271b9c8e3f327f47189446834b
Merge: bc5594c8c5 aed6b1f105
Author: Andrew Cagney <[email protected]>
Date: Thu Jul 10 21:48:22 2025 -0400
Merge connections: update host addresses using resolved .nexthop
see #2301 resolve host during orient(), not extract
commit aed6b1f105f8f82dedf92c4c2b9db943de962c27
Author: Andrew Cagney <[email protected]>
Date: Thu Jul 10 15:48:12 2025 -0400
connections: pass peer's nexthop into update_hosts_from_end_host_addr()
.. instead of ferreting it from the peer's config's .nexthop
When extracting the connection, pass in the resolved value.
also remove hack setting .nexthop from the resolved nexthop
commit ff664cd36094513c579db42899ab6cc5aca248a6
Author: Andrew Cagney <[email protected]>
Date: Thu Jul 10 08:57:56 2025 -0400
connections: extract unresolved {left,right}{,nexthop}= values into struct
config ...
i.e., don't first try to resolve them. The code now looks somewhat
like:
- extract whack-message {left,right}{,nexthop} into config
- when possible perform DNS/resolution
- copy resolved values to connection proper
This sets things up for performing DNS/resolution later,
perhaps in a separate thread.
But wait...
The astute reader will notice that, after resolution, and to
preserve broken behaviour, the code needs to copy the possibly
resolved NEXTHOP back into config. Like host.addr, the value
resolved value needs to be stored in struct connection proper.
_______________________________________________
Swan-commit mailing list -- [email protected]
To unsubscribe send an email to [email protected]
