Wired AND Wireless Home Network, Done Right?
NiGHTS
San Diego Icrontian
Hi all,
So I've currently set up the network in our house, but am unhappy with how it's been seemingly jerryrigged for the past year and would like to fix it. I've essentially got 2 seperate home networks running, 192.168.1.xxx for wireless, 192.168.0.xxx for wired - I would like wired devices to be able to talk to wireless ones.
Before I begin, things to note:
So, I've currently got the cable modem on the second floor and a router (192.168.0.xxx) hooked up to it. This router serves the rest of the house via wall jacks. One of those jacks has a wireless router hooked up (192.168.1.xxx) to service the house wirelessly. The remaining two jacks service 2 360s and 1 computer via a switch upstairs.
I'd like everything to be on the same "network" in the house, rather than split up as they are now. A good example of what I can't do is share media from the desktop computer to an xbox on the second story, since that xbox is plugged into the wireless router with an IP of 192.168.1.xxx, while the desktop has 192.168.0.xxx.
It sounds confusing, I know. I'd draw a picture, but I'm not sure that'd even help, it really has to be seen.
Internet
|
Cable Modem
|
Router - supports WAP on floor 2, switch on floor 3 (which supports 2x 360, desktop)
|
Wireless Access Point - floor 2 > supports 1x 360 > several laptops/phones
The location of the first router prohibits me from setting up the WAP there, since it isn't in an ideal location in the house and connection really suffers for it. If that weren't the case, I wouldn't have to run 2 IPs. I'd ideally like to use the wall jacks, since they're there and wired trumps wireless for everything.
Would buying a new Wireless-N router give me the bump in connectivity and signal strength over a 4 year old b/g router? This point may be useless, though, as all the wireless devices in the house are not N-ready.
Is there a way of setting up the WAP to use 192.168.0.xxx for wireless devices so they can "talk" to 192.168.0.xxx devices?
TIA
So I've currently set up the network in our house, but am unhappy with how it's been seemingly jerryrigged for the past year and would like to fix it. I've essentially got 2 seperate home networks running, 192.168.1.xxx for wireless, 192.168.0.xxx for wired - I would like wired devices to be able to talk to wireless ones.
Before I begin, things to note:
- The house is 3 stories
- The house is prewired for CAT-5
- Wireless does not transmit well to either third or first story
So, I've currently got the cable modem on the second floor and a router (192.168.0.xxx) hooked up to it. This router serves the rest of the house via wall jacks. One of those jacks has a wireless router hooked up (192.168.1.xxx) to service the house wirelessly. The remaining two jacks service 2 360s and 1 computer via a switch upstairs.
I'd like everything to be on the same "network" in the house, rather than split up as they are now. A good example of what I can't do is share media from the desktop computer to an xbox on the second story, since that xbox is plugged into the wireless router with an IP of 192.168.1.xxx, while the desktop has 192.168.0.xxx.
It sounds confusing, I know. I'd draw a picture, but I'm not sure that'd even help, it really has to be seen.
Internet
|
Cable Modem
|
Router - supports WAP on floor 2, switch on floor 3 (which supports 2x 360, desktop)
|
Wireless Access Point - floor 2 > supports 1x 360 > several laptops/phones
The location of the first router prohibits me from setting up the WAP there, since it isn't in an ideal location in the house and connection really suffers for it. If that weren't the case, I wouldn't have to run 2 IPs. I'd ideally like to use the wall jacks, since they're there and wired trumps wireless for everything.
Would buying a new Wireless-N router give me the bump in connectivity and signal strength over a 4 year old b/g router? This point may be useless, though, as all the wireless devices in the house are not N-ready.
Is there a way of setting up the WAP to use 192.168.0.xxx for wireless devices so they can "talk" to 192.168.0.xxx devices?
TIA
0
Comments
Thanks, though.
Oh, and bridge mode on the main router really wouldn't help you here, that one NEEDS to be an actual router. You need to have bridge mode on the WAP.
I'll continue using the setup as is and just find a workaround.
Newegg has this Asus 802.11n for $50 and as a bonus DD-WRT's site reports that support for the router is WIP (some betas work with it).
You could get additional 802.11n cards for the computers that are farthest from the router.
Until recently I was testing a Trendnet wireless N router in place of WRT54G and RT-N12. But it was not reliable. I had to go back to WRT54G and bought this ASUS-RT-N12 as the AP. This combination gave much better reliability.
I have no idea how could I have done the networking without the flexibility and power of DD-WRT. Besides having the consistency (more or less depending on the hardware) of interface and options is very useful.