Add ability to choose from what IP/IFACE you search for updates
Please add an option to allow the user to choose from what IP or interface the request for updates is outgoing. For instance, we have several BGP sessions via OpenBGPd. The search for updates always fails because it starts from a IP not allowed by our current provider for this route.
Please put a combo to choose from what IP/INTERFACE of the configured devices the request is originating from, so it can reach the pfSense repo, in the same fashion of "ping" menu. In a multi-wan scenario is difficult to choose the correct interface to reach pfSense site because the origin IP is automatic/unspecified.
Updated by Jim Pingle over 6 years ago
- Target version deleted (
The update check always has to leave the interface with the default gateway, as any traffic originating from the firewall does. Unless you add a static route to send traffic out another path. Problem is you can't static route the updates since the IP address could change depending on what we do on the server side.
Setting the source address via FETCH_BIND_ADDRESS may be possible but would need testing, though that doesn't control which interface the update leaves, only the address used for the source of the traffic.