Yes, you can route certain connections on one interface and other types on another. For example, you can have all incoming traffic originating from the Internet routed through your static IP while have all outgoing traffic originating from your home go through your dynamic IP. However, the details are extremely complex and I would recommend that you read up and understand some networking fundamentals and then go on to LARTC to get more details on how to do it in Linux.
If multiple interfaces are up there are two issues. First one is which interface has gateway and what is the interface order.
I'm assuming you're using Windows O.S. In command prompt (type "cmd" in Run window) type route print
and you should see something like this:
(the headers are in you o.s. language, mine is Turkish)
Which interface has the gateway option, actually which interface has the routing information for destination 0.0.0.0, mask 0.0.0.0 is the actual outgoing door...
{
Edit: Observe that I have a route line that is
Destination: 192.168.8.0 Mask: 255.255.248.0 and Gateway 192.168.24.2
at the bottom. That says when i need to access 192.168.8.0 network, i have to pass throug the 24.2 gateway. Besides, there are no entries in main table for 192.168.24.0 network, that was an experimental entry over another NIC
}
When you have multiple route informations for that destination {edit: 0.0.0.0} and each one is different from each other or just two different gateways, you're doomed. Network will start losing some packets...
When you have multiple route informations for that destination but one gateway for each (which is your case that your gateway will be your modem i guess, which is your dhcp server, it'll assing different ip addresses for each interface but same information for default dns and default gateway) then there is an order:
Your o.s. will treat your up and running interfaces with this ordering. So if you wireless interface is on the first line and connected, your o.s. will use that interface for network communication and vice-versa.
Best Answer
The trick is to change the network card priority so that the wireless connection remains active when a wired connection is made.
The first step is to get to the "Control Panel > Network and Internet > Network and Sharing Center" page. On the left side of that page, click the link "Change adapter settings". This should bring you to the "Control Panel > Network and Internet > Network Connections >" page.
Select the wireless connection, right-click "Properties", and provide an admin password (if necessary). This should bring you to a dialog box named [wireless connect name] Properties".
In the list box titled "This connection uses the following items:", scroll down to "Internet Protocol Version 4 (TCP/IPv4)" and select it. The "Properties" command button will enable; click it. This should bring you to a dialog box named "Internet Protocol Version 4 (TCP/IPv4) Properties".
Click the "Advanced" command button. This should bring you to a dialog box named "Advanced TCP/IP Settings".
Near the bottom of the dialog box, there should be a check box named "Automatic metric". Uncheck it. That will enable a text box named "Interface metric". Fill in a number. It needs to be larger than 1 (reserved for loopback) and the number you choose for the wired network (see below).
Click three "OK" command buttons to return to the "Control Panel > Network and Internet > Network Connections >" page.
Repeat the above for the wired connection:
Select the wired connection, and right-click "Properties" to get to the [wired connection name] Properties" dialog box.
Select the IPv4 list entry and click "Properties", and on the next dialog box click "Advanced".
Again Uncheck "Automatic metric", and fill in a number in the "Interface metric" box. It needs to be larger than 1 but smaller than the number you chose above.
I would assume that it's also possible to give the wired network higher priority than the wireless, but I didn't test that.
Comment: Some other answers asked why one would want to do this. It's not for improved throughput; I doubt that Windows could effectively divide traffic between two networks like that. Instead, it's so that the machine can be connected to two distinct networks. In my case, the wireless network goes to my ISP, and the wired network goes to my Network-Attached Storage server.
Note: I found this general idea on a How-To Geek article titled "How to Change the Priority of Wired/Wireless Network Cards in Windows". The article has screen shots, but I've included a summary in case the link goes dead, and explained it somewhat differently.