On Tue, 11 Jul 2006 05:50:55 GMT, John Navas
<spamfilter0@navasgroup.com> wrote in
<c6e6b25njailmpdcac9pl3mln4snkap44j@4ax.com>:
>On Mon, 10 Jul 2006 22:15:28 -0700, Jeff Liebermann
><jeffl@comix.santa-cruz.ca.us> wrote in
><qub6b2164p065tbb6b4jblc19gtnhef1o1@4ax.com>:
>
>>John Navas <spamfilter0@navasgroup.com> hath wroth:
>>
>>>On 10 Jul 2006 12:29:23 -0700, ericooi@gmail.com wrote in
>>><1152559763.873836.82120@s13g2000cwa.googlegrou ps.com>:
>>>
>>>>I was wondering whether or not there was a method to auto disable my
>>>>wireless connection whenever I connect through a LAN/ethernet line?
>>>
>>>Windows will use the last connection you make.
>>
>>I beg to differ. Windoze assigns different route metrics to the
>>ethernet and wireless connections. Ethernet is considered the
>>"better" route and is used if available. See my tinkering at:
>>| http://groups.google.com/group/alt.i...de116db990c9be
I was actually partially correct -- see below.
>I beg to differ back :) -- it's not that simple. For example, I'm now
>using a Wi-Fi connection with an automatic metric of 25. See The Cable
>Guy -- April 2005, "Windows XP and Windows Server 2003 Behavior When
>Connected to Both Wired and Wireless Networks"
><http://www.microsoft.com/technet/community/columns/cableguy/cg0405.mspx>:
>
> * If there are multiple default routes with the lowest metric, choose
> the default route corresponding to the network adapter that is
> highest in the binding order.
>
>The table right below that quote is more complete than your experiments,
>with differing metrics for different interfaces. Note that:
>
>* 10BaseT has the same metric as 802.11b, resolved by binding order.
>
>That what I was thinking of, but of course my statement wasn't correct
>in the general case. [blush]
>
>* 10BaseT has a higher metric than 802.11a or 802.11g, and so won't be
>favored over wireless.
>
>* 100BaseT trumps everything else.
>
>So if the OP has 100BaseT, then it will automatically take over from
>wireless, which is what he wants. If on the other hard he has 10BaseT.
>then it won't trump 802.11a or 802.11g, and might not even trump
>802.11b.
>...
Since then it's been bugging me why Windows has automatically switched
to lower speed connections I've made, which wouldn't seem to make sense
given the above. For example, here's a route table with two Internet
connections, excellent Wi-Fi "g" at a reported 54 Mbps, and EGPRS(EDGE)
at under 200 Kbps over Bluetooth (with a virtual port speed of 460
Kbps):
|Active Routes:
|Network Destination Netmask Gateway Interface Metric
| 0.0.0.0 0.0.0.0 10.199.205.61 10.199.205.61 1
| 0.0.0.0 0.0.0.0 172.16.8.2 172.16.8.43 26
| 10.199.205.61 255.255.255.255 127.0.0.1 127.0.0.1 50
| 10.255.255.255 255.255.255.255 10.199.205.61 10.199.205.61 50
| 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
| 169.254.0.0 255.255.0.0 172.16.8.43 172.16.8.43 30
| 172.16.8.0 255.255.255.0 172.16.8.43 172.16.8.43 25
| 172.16.8.43 255.255.255.255 127.0.0.1 127.0.0.1 25
| 172.16.255.255 255.255.255.255 172.16.8.43 172.16.8.43 25
| 192.168.100.101 255.255.255.255 10.199.205.61 10.199.205.61 1
| 224.0.0.0 240.0.0.0 172.16.8.43 172.16.8.43 25
| 224.0.0.0 240.0.0.0 10.199.205.61 10.199.205.61 1
| 255.255.255.255 255.255.255.255 10.199.205.61 3 1
| 255.255.255.255 255.255.255.255 10.199.205.61 10.199.205.61 1
| 255.255.255.255 255.255.255.255 172.16.8.43 172.16.8.43 1
|Default Gateway: 10.199.205.61
Wi-Fi "g" Interface is 172.16.8.43; EGPRS Interface is 10.199.205.61
The EGPRS Metric of 1 trumps the Wi-Fi "g" Metric of 26 (note how it was
bumped up from 25 to 26), making it the Default Gateway. If I now
disconnect the EGPRS:
|Active Routes:
|Network Destination Netmask Gateway Interface Metric
| 0.0.0.0 0.0.0.0 172.16.8.2 172.16.8.43 25
| 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
| 169.254.0.0 255.255.0.0 172.16.8.43 172.16.8.43 30
| 172.16.8.0 255.255.255.0 172.16.8.43 172.16.8.43 25
| 172.16.8.43 255.255.255.255 127.0.0.1 127.0.0.1 25
| 172.16.255.255 255.255.255.255 172.16.8.43 172.16.8.43 25
| 224.0.0.0 240.0.0.0 172.16.8.43 172.16.8.43 25
| 255.255.255.255 255.255.255.255 172.16.8.43 3 1
| 255.255.255.255 255.255.255.255 172.16.8.43 172.16.8.43 1
|Default Gateway: 172.16.8.2
This behavior is what I had in mind when I originally wrote, "Windows
will use the last connection you make." It happens because EGPRS is a
Dial-Up connection. This behavior is controlled by the option "Use
default gateway on remote network" in Advanced TCP/IP Settings for
Dial-up Network Adapters.
For non-Dial-up Network Adapters, Metrics can be controlled with the
Interface Metric option in Advanced TCP/IP Settings. This would allow
the OP to do just what he wants no matter the speeds of the wireless and
wired connections.
--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>
Re: disable wireless upon ethernet connection 
Linear Mode
