Skip to main content

WCF Client and multiply IP address - How to specify the IP that needs to be used

Usually, when we are developing WCF clients, we have a machine that has only one network adapter. This means that there is only one LAN network that we can use. In 99.99% of scenarios this will work perfect.
What happens when we have two or three networks adapters and each WCF client need to be use a specific one? For example we can have a private network between our machine and company network. Another one can be between our machine and internet and the last one can be a secure network between us and a partner.
For this cases, the default settings of WCF client will not work. We need to be able to specify what network we want to use for each WCF client. I looked over the firewall configuration and routing tables, but I did not found a solution on this side.
A possible solution that I found over the internet and was tested by myself also is using ServiceEndpoint.
WCF give you the possibility to create a ServiceEndpoint for each IP/URL that you want to use (on the process level). In the moment when a request is made, the ServiceEndpoint will be used to resolve the client endpoint IP.
At this level we can define a delegate that can be used to specify what IP needs to be used for each request. Because, when we create a ServiceEndpoint we specify the service endpoint address, we can have different server endpoints that will use different local IP.
The BindIPEndPontDelegate delegate is called when the client IP needs to be resolved. When the local IP is specified in the callback we need to give a valid IP address of our machine, otherwise we will end up with an error. Don’t forget that this information can be cached by WCF. Also, we don’t specify a callback, the default behavior will be used.
The code would look like this:
ServicePoint servicePoint = 
      ServicePointManager.FindServicePoint(
            new Uri("https://www.myService.com/Services/Payment/"));
servicePoint.BindIPEndPointDelegate =
                (sp, rm, retryCount) =>
                {
                                return new IPEndPoint(myIpAddress, portNumber);
                };
In the callback, we can specify any IP to be used by using IPAddress.Any.
Do you have other solutions that don’t involve writing code? Maybe doing some configuration on the local machine.    

Comments

  1. Wouldn't be easier to just add a specific route table entry for that particular case?
    (route add.. command)

    ReplyDelete
  2. do you got any solution because i am also facing same issue.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…