fix(yang-push): use system-chosen source IP for NETCONF SSH

[riccardo-negri]

YANG Push notifications arrive on the anycast address (e.g. 1.1.1.45). The YANG schema fetcher was reusing that collector address as the explicit local bind address for the NETCONF SSH connection. When the NETCONF server is only reachable via the site-local unicast address (.46 or .47), the connection fails because the source IP is wrong.

Solution

Remove the explicit socket.bind(local_addr) for NETCONF SSH connections in the schema fetcher by passing None as local_address in both fetch_from_device and fetch_from_device_by_id. The Linux routing stack now selects the correct unicast source address based on the destination.

SO_BINDTODEVICE / local_interface is unchanged — interface selection still works as before.

Files changed:

• crates/yang-push/src/cache/fetcher.rs: pass None instead of Some(collector) for local_address in both NetconfSshConnectConfig::new call sites.

[Copilot]

Pull request overview

This PR fixes NETCONF SSH schema-fetch failures when YANG Push notifications arrive via an anycast collector address by no longer forcing the SSH client’s TCP socket to bind to that collector IP as its source address. Instead, it lets the OS routing stack choose an appropriate unicast source address based on the destination, while keeping interface pinning (SO_BINDTODEVICE) unchanged.

Changes:

• Pass None for local_address when building NetconfSshConnectConfig in fetch_from_device.
• Pass None for local_address when building NetconfSshConnectConfig in fetch_from_device_by_id.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.