Allow for gateway configuration that would send all server connection traffic to one interface
Allow for gateway configuration that would send all server connection traffic to one interface
0 vote
On gateway servers with multiple network interfaces, provide a configuration that would allow for all the server connection traffic to be sent to one interface, all other traffic to the DVLS server and the RDM user can use whatever interface that the server routing indicates.
Our use case, we have a network configuration that allows for the production networks to be deployed behind a firewall, so recovery testing can be done without impacting production operations. The gateway server has network interfaces on the production and the recovery networks, normal routing will not handle the duplicate network addresses. So interface specific routing allows for the server connections on the recovery network.
All Comments (1)
Hi Bill,
Thank you for opening this feature request thread.
First, I’d like to share my understanding of how network interfaces are typically selected: the operating system filters the requested IP address against the subnet configured for each available interface. For example, 128.128.1.25 will use the interface with subnet 128.128.1.0/24, and 192.168.1.93 will use the interface with subnet 192.168.1.0/24. In most scenarios, Devolutions Gateway doesn’t need to specify which interface to use because the OS handles this automatically.
From your description, it sounds like you’re using the same subnet for both your disaster recovery and production networks. Is that correct? If so, I can see how this might cause complications with interface selection, and you’re right that Devolutions Gateway currently doesn’t offer a way to specify a particular interface for outgoing traffic.
I’m curious to learn more about your specific setup. You mentioned "recovery testing," so does that mean the recovery interface is typically disabled unless you’re running tests or if the production interface goes down? Also, are there any constraints that prevent you from assigning a different subnet to the recovery interface? You mentioned "recovery testing can be done without impacting production operations"; are you using two Devolutions Gateway machines: one for the recovery testing, and one (or more) for production?
Understanding these details will help us better evaluate the feasibility and scope of such a feature.
So far, I am under the impression that it’s a pretty straightforward feature to implement if you are okay with the whole instance using a single specific interface for all the outgoing traffic.
Best regards,
Benoit Cortier