#1 SCU/Association Address Specific Socket Binding

closed
nobody
5
2007-12-25
2007-12-24
No

We have a specific use case in which a Windows 2003 server's IP interface is multi-homed (i.e., the system has more than one IP addresses assigned to a single Ethernet interface), however, we need to make sure that the traffic originating from the server to use one of the specific IP address.

This seems to be partially exposed to the "user" as TCPClient object is being passed from the calling application, but it also looks like additional mods are required in the FSM or somewhere thereabouts to get this to be coded.

I will continue to work on it and if it does work, I will post an update. If this has already been worked out, I would like to know soon.

Discussion

  • StokeMaster International

    • status: open --> closed
     
  • StokeMaster International

    Logged In: YES
    user_id=1860489
    Originator: YES

    Taking back: I have found out that this can (may) be accomplished easily without getting into the source.

    System.Net.IPAddress ip = System.Net.IPAddress.Parse("10.1.1.101"); // Let's say 10.1.1.101 is the interface address I want to use
    System.Net.IPEndPoint ep = new System.Net.IPEndPoint(ip, 123456); // 123456 is an arbitrary port, it can be any reasonable number.
    TcpClient tcp = new TcpClient(ep);
    tcp.Connect("PACS_SERVER", 104);
    Association assoc = aFact.NewRequestor(tcp);

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks