Re: WiFi (192.xx) & Wired (10.xx)
- From: Charles J <cj23@xxxxxxxxxxxx>
- Date: Tue, 05 Aug 2008 01:51:10 -0500
On Sun, 23 Mar 2008 16:34:35 GMT, "P.Schuman"
<pschuman_NO_SPAM_ME@xxxxxxxxxxxxx> wrote:
Here's the followup...
The DSL modem has an internal address of 10.0.0.1
and normally is just a DSL bridge with the router
actually performing all the PPPoE functions....
The DSL modem is not a router.
I've taken the WAN connection cable from my router
that normally connects to the DSL modem
and plugged it into a temp hub to gain access to the stats.
So - this temp hub has 3 connections.... (non-routed)
DSL modem - Ethernet connection
Router - WAN connection
Laptop - Ethernet connection
this works fine,
and I can bring up http://10.0.0.1 on the laptop browser
and see all the stats: DSL, ATM, Eth, and log
Next - today - I re-enabled the laptop WiFi
to see if I could have them both active...
Of course you can have both of them active.
So - I have the browser open with -> http://10.0.0.1/atmstats.html
Remember this is just a hard coded internal address for the DSL modem
and there is no routing paths beyond this since our local network is 192.xx
I open a browser tab and enter -> http://192.168.1.2
and yup - the router logon page is displayed.
So - with entering 192.xx - it figures out to use the WiFi connection
since we are on the same 192.xx segment as our WiFi IP address.
Standard routing table stuff.
Next - try a DNS address.... nope - doesn't work -
There is no way for the dual IP stacks to figure out which interface to send the
request.
Single IP stack, dual interfaces. The problem you were having is that
the default metric for wired interfaces is higher than the default
metric for wireless interfaces, so your request to reach an address on
the Internet went out the 10.x interface, where it was black holed.
Simply go to a Command Prompt and use the 'route' command to give the
wireless interface a lower metric than the wired interface.
To display your routing table, use 'route print'. To change an entry
in the table, use the 'route change' command. Use 'route /?' to see
the proper syntax.
I can't use the real DNS addresses on the Ethernet 10.xx side,
since there is no routing going on that side.
The WiFi side has all the required info and routing,
but there is no way to give one IP stack "priority" over the other IP stack.
Yes, there is a way. That's the purpose of the 'metric' variable,
described above.
But at least now I can see the DSL modem stats AND the router log at the same
time
by entering their IP addresses in the browser.
You should be able to see the DSL modem stats, the router log, and
access the Internet, all at the same time.
.
- Prev by Date: Re: Wired/Wireless Conflict
- Next by Date: Re: WGR164v5 stopped doing wireless.
- Previous by thread: WiMax power consumption
- Next by thread: AD: NEW VigSys HSDPA USB docking station - share your mobile broadband
- Index(es):
Relevant Pages
|
