Ability to force which IP is used by DC on Multihomed Server

WxAxGxS · Post by **WxAxGxS** » 2004-03-19 06:04

As far as I can tell, there is no way to actually tell DC which interface to use. This issue arose with the two systems I run DC on. Both have 3 IPs (3 NICs/interfaces). I want to be able to (1) choose which of these 3 IPs DC++ uses and (2) Run 2 DC++ connections from different IPs. Both of these issues stem from the fact that having DC++ on the IP uses up bandwidth... Since I have no control over which IP DC++ is using, I can't prevent it from taking up the bandwidth from, say, my game or web servers. This is a pretty big issue for me.

I think it would be a good (and rather simple) addition to DC++ that could benefit many people.

Qbert · Post by **Qbert** » 2004-03-19 07:49

WxAxGxS wrote:As far as I can tell, there is no way to actually tell DC which interface to use.

This may be true, but you don't need to tell it. You can have your OS designate the right one to it. I don't know if this is the exact name of the program for all windows versions, but for Win2k, run "route" from a command line. It can tell you the same information as "netstat -r". Use route to add a static route to the hub you want to connect to using whichever interface you want. By doing this, DC++ will automatically use the interface you want (without even knowing) and can use multiple different interfaces for different hubs (without even knowing).

WxAxGxS · Post by **WxAxGxS** » 2004-03-19 12:37

Thanks for the reply!

But, what if you are trying to connect multiple clients to the SAME ip?

Qbert · Post by **Qbert** » 2004-03-19 23:50

But, what if you are trying to connect multiple clients to the SAME ip?

My suggestion has absolutely no association to which client or how many clients you use. Whatever program you use to connect to any host, it will be first routed the way itÃ¢â‚¬â„¢s statically defined to be routed. The only limitation to this is that any and all programs will use the same interface to access the same host, but they can obviously also use a different interface to access a different host. If you want all of your programs to use say interface 1 to access a hub at host A, then just set a route for it.

WxAxGxS · Post by **WxAxGxS** » 2004-03-20 19:17

Yes, that's my problem.... I want DC #1 to use Interface 1 to go to IP 1, DC#2 to use Interface 2 to go to IP 1, and so on... :-/

Thank you for the above comment, though.. It definately helped me out for the ones that go to different IPs!

WxAxGxS · Post by **WxAxGxS** » 2004-03-25 16:29

Anyone else have any comments/opinions/help?

BSOD2600 · Post by **BSOD2600** » 2004-03-26 01:50

Only idea is to specify which adaptor you want DC++ to use, by making it the primary one. Network connections -> Advanced Menu -> Advanced. Then select the NIC and move it to the top.

Qbert · Post by **Qbert** » 2004-03-26 03:24

WxAxGxS wrote:Yes, that's my problem.... I want DC #1 to use Interface 1 to go to IP 1, DC#2 to use Interface 2 to go to IP 2, and so on... :-/

You can setup your routing table just as I've explained to accomplish this. What is the problem?

Did you not mean to designate different numbers for IP's to your post? For example, did you mean to say you want DC #1 to use Interface 1 to go to IP 1, and DC #2 to use Interface 2 to go to IP 1? Because as you've posed your circumstance, you shouldn't have any problems.

WxAxGxS · Post by **WxAxGxS** » 2004-03-26 04:35

Yeah, that's exactly what i meant and what I thought I had expressed.. Sorry if I wasn't clear enough on that.

::edit:: I just realized that I made a typo... sorry :-/ Corrected it now...

Ability to force which IP is used by DC on Multihomed Server

Ability to force which IP is used by DC on Multihomed Server

Who is online