|
Most applications aren't sensitive to particular connection devices. I know that IE and Messenger are not.
About the only way to acheive this is to - after connecting - modify the route table so that connections to certain hosts go through a particular gateway. For modems, you must connect first before doing this because most ISPs hand-out dynamic IP addresses (even many broadband providers). Some will grant you a static IP, but often times charge extra. So, until you know what your dynamically assigned IP address is, you can't modify your route table accordingly.
As far as using C# to do this, why? Modify a route table is low level, although you can do it using the route.exe command-line utility. Managed applications aren't the solution to everything, especially low-level APIs. For instance, you'll probably never see managed code used for device drivers. These drivers are typically written in C and sometimes even assembler, or at least in part.
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
Hi Heath,
I am looking for a way to create an application that matches an application for a give set of modems.
I currently have 2 modems with static IPs and all I can do is to bridge the modem so the result is that the resource networks are in common like if I had a dual CPU. It does not download faster, but while I do massiv downloads, I can still continue to navigate smoothly 
I was wondering if it is possible to do an application that can do what I just mentionned that is assigne a set of modems to a given application and for the application to use the set of modems.
I think it's possible or maybe there are tools that already exist.
I just wanted to write this in C#, just for the fun of code. As suggested "leppie", I can build the low level in C/C++ and interface in C#. But first of all, does such an application exist??? I was thinking of ISA or any other firewall, but it's not really the purpose of fire walls... 
I'm looking for such application for a while, and I was wondering to do it my self or not : 
There is no spoon.
|
|
|
|
|
Again, this works through route tables. If you don't know what a route table is, it's what routes requests to a given host through the proper gateway. Firewalls use a similar concept, only they use stateful filtering because they can - they are completely between you and your request host. You can't preempt the Windows TCP/IP stack like this. That leaves you with one option: route tables.
When you connect with multiple devices (say, two modems) each will have a different IP address. This will be your local gateway. You could modify your route table so that all requests to www.codeproject.com (209.171.52.99) go through one modem while all others are routed to the other.
This has absolutely nothing to do with the name of the application, which most often simply uses the networking APIs of the operating system.
Don't believe me? Try reading the TCP/IP specifications and check back in a few days when you're finished reading them.
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
So, an application can't be forced to use a modem or another? Then what about bridged networks???
There is no spoon.
|
|
|
|
|
Again - route tables. Take a VPN connection. When I VPN from home to the office, my route table is modified such that all connections not to my home network are routed through the VPN connection. Seriously - try reading about the subject. If you don't even understand a route table, how do you expect to even do this?
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
ok,
lets start with the begining, where can I get these informations? in the MSDN?
There is no spoon.
|
|
|
|
|
Some, yes. Others are in RFCs. Hell, ask any decent systems administrator and they'll tell you the same thing.
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
we don't have any where I work!!!
The tool I wanna do is non professional purposes, just for my brain stimulations 
There is no spoon.
|
|
|
|
|
And you've never heard of newsgroups and other forums besides those here on CodeProject?
Seriously, try reading-up on TCP/IP. I've been doing this for a very long time and speak from experience and knowledge gained by reading and participating in newsgroups and mail lists.
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
I'm going to read some articles on the MSDN...
I've just discovered newsgroups last week
I usually use codeproject and the other one I won't name here
I've been trained for local programming while doing my MCSD trainings, I never heard about Sockets and TCP/IP...
I only had theory 7 years ago about OSI and so on... it was blah blah blah... nothing concreete...
I'm looking on the MSDN for additional information. I guess there is enough for what I need to do.
There is no spoon.
|
|
|
|
|
bouli wrote:
I never heard about Sockets and TCP/IP...
 The very thing that makes the entire Internet and other networks possible? And you're studying for an MCSD?
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
I finsihed two years ago... lol it was only about Visual C++ and MSF (Microsoft Solution Framework, a kind of accelerated Merise conception of software).
When I said never heard about Socket and TCP/IP, it was not the purposes of the trainings. Even in COM/DCOM/COM+ programming trainings, we never used sockets because it was not needed.
As you know, I just started to use sockets with C# 
I have to go now...
We'll talk tomorrow.
See ya!
There is no spoon.
|
|
|
|
|
bouli wrote:
I've just discovered newsgroups last week
I've been trained for local programming while doing my MCSD trainings, I never heard about Sockets and TCP/IP...
 Nothing like biting off WAY more than you can chew!
RageInTheMachine9532
"...a pungent, gastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
I don't know of an application that will do this either. Simply because applications don't give a damn which network their on. It's just not in an applications domain to care which devices carries its communications. Remember the OSI model? It's there for a reason and applications sit at the top of it, not down near the Network layer.
Like Heath said, about the only thing you can do is modify the route table based on the destination IP's that your apps are trying to connecting to.
RageInTheMachine9532
"...a pungent, gastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
I thought we could do this. 
So, which layers take care about the fact that an applications is forced to use a modem or another?
There is no spoon.
|
|
|
|
|
bouli wrote:
So, which layers take care about the fact that an applications is forced to use a modem or another?
None. The layers are completely seperate and independent from each other. The Application Layer doesn't have any connections to the Network Layer. It still has to go through Presentation, Session, and Transport. Each layer insulates the layers ajoining it. Don't sleep throught the OSI model next time...it comes in real handy understanding modern networking.
RageInTheMachine9532
"...a pungent, gastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Heath Stewart wrote:
Managed applications aren't the solution to everything, especially low-level APIs.
Not to go off on a tangent, but I wanted to say "exactly" to your argument. This is why debates about C/C++/ASM dying to managed code are just pointless. Managed code is great for high level RAD, but quite poor when it comes to dealing with low level code. That may change somewhat when WinFX, which is non-reliant on Win32, rolls around. But even then it'll be a matter of using the right tool for the job, and currently, managed code is not the right tool for low level API solutions.
#include "witty_sig.h"
|
|
|
|
|
To do this by applicaiton, the application has to be "aware" of the different network interfaces. As is applications like IE and MSN Messenger frankly don't know and don't care as long as the routing can contact the servers it seeks to query. For some applications, mostly server programs like IIS, this makes sense since they "bind" to specific interfaces so they provide tools to handle this. For client software this is behavior is almost meaningless.
I would say its nearly impossible to manipulate the routing to be application aware (I don't want to say it is impossible but it should be darn near impossible since it would be easy to write malicous software if you could just hijack traffic out of process). There is probably a way but it involves some serious win32 mojo to recognize what application is opening what socket and then altering the communication path accordingly.
I believe this is a case where someone is trying to solve something with software but ignoring the obvious (and distrubingly easy) hardware solution: take a modem off of the machine and place it on another and run your applications as applicable.
|
|
|
|
|
lol...
Maybe Bill can handle this, because he has the sources of Windows... 
That could be a nice extension to Longhorn Server
There is no spoon.
|
|
|
|
|
But why would you want to? Routing is a software abstraction that is there for a reason: without routing every application that wants to make a socket connection on the internet would have to enumerate and judge for themselves what network interface to use.
The cost of adding a feature like this outweighs the actual benifit. Applications need to get simpler not more complex. Adding something to Longhorn to individually route each and every process would be a control nightmare.
Your problem would be solved in half an hour by moving one modem to another machine and running the applications seperately.
|
|
|
|
|
bouli wrote:
That could be a nice extension to Longhorn Server
and an absolute bastard to troubleshoot and administer...
RageInTheMachine9532
"...a pungent, gastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
of course!!! they are here for that!!!
that could be useful for companies that have several network connections. "Bridging" is a first step... next step should be to make the applications aware of the connection to use!
There is no spoon.
|
|
|
|
|
I want to know how I can set my machines IP address in c# coding?;)
Sweet
|
|
|
|
|
There's nothing in the .NET FCL that allows you to set your machine's IP address. In fact, it's not a good idea to, anyway. It's not like some user preference that could be changed often.
In any case, such an API is not documented in the Platform SDK. Obviously there's some way to do it, but that doesn't mean it's documented.
If you want to get the machine's IP address, a simple way is like so:
string name = Environment.MachineName;
IPHostEntry host = Dns.GetHostByName(name);
foreach (IPAddress address in host.AddressList)
if (address.AddressFamily == AddressFamily.InterNetwork)
return address;
return null;This would get the IPv4 address, for example.
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
Thank you very much. 
Sweet
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
