WAP to WAP to 360

[xnieeufy]

Greetings, I looked around a bit but didn't see any topics addressing this exact situation.

I'll try to diagram the situation:
..... is wireless
---- is wired

Internet
|
> Belkin router/WAP
..... |
..... ..... > Linksys WAP
----- ----- |
----- ----- -----> NetGear router/WAP
----- ----- ----- |
----- ----- ----- -----> Desktop 1
----- ----- ----- -----> Desktop 2
..... ..... ..... ..... .....> Laptop 1
..... ..... ..... ..... .....> Laptop 2
..... ..... ..... ..... .....> NDS
..... ..... ..... ..... .....> PSP
----- ----- ----- -----> Linksys Switch
----- ----- ----- -----|
----- ----- ----- ----- -----> Xbox 360
----- ----- ----- ----- -----> PS2
----- ----- ----- ----- -----> GameCube
----- ----- ----- ----- -----> Onkyo Receiver

Right, I think that does it. What I'm after is to get the Xbox 360 connected to the internet. 360 ----> Switch -----> NG Router -----> Linksys WAP .....-> Belkin Router -> Internet.

I'm thinking what I have to do is use the Linksys WAP as a bridge to the Belkin and plug it into the WAN port of the NetGear router. Do these have to have different subnets, or does the firewall/NAT translation take care of that?

The Belkin is unsecured, while the NetGear is using WPA2.

Any suggestions on a different layout are welcome, although I'd prefer not to have to buy new hardware at this point.

Thanks

[xnieeufy]

Well, I tried again last night to get everything set up, but the only success I had was using a laptop to connect to the Belkin, using ICS to share that connection, and connecting the cable to the 360 through the switch. Not ideal, but it's a start.

I'm still trying to figure out how to use the WAP in place of the laptop.

[M/Q]

Sorry, I am not following your diagram. Is the LinkSys AP connected to the Belkin router?

Can you make a diagram like this?

Internet
|
>- Belkin Router
……|
……>- LinkSys AP

And so on as it would be a bit clearer, as to what you are connecting to what. I apologize, as I just am not able to follow it as is.

You will not be able to use the LinkSys AP as a bridge to the Belkin router as bridging requires two access points or bridges and usually they need to be of the same make and model.

You have enough equipment to make this work, we just need to know what you want connected to what.

[xnieeufy]

Sorry, I am not following your diagram. Is the LinkSys AP connected to the Belkin router?

Yes. Internet to Belkin Router/WAP on one floor, wireless link to Linksys WAP on another floor, Linksys WAP cabled to NetGear Router/WAP, cable to Linksys Switch in another room, cable to Xbox 360. I attempted to update the diagram.

You will not be able to use the LinkSys AP as a bridge to the Belkin router as bridging requires two access points or bridges and usually they need to be of the same make and model.

Ouch. That doesn't make much sense to me (from a "shouldn't they all play nice?" view), but I understand what you're saying. So I'd have to get another Belkin of the same make/model in order to bridge that connection, and basically toss the Linksys?

You have enough equipment to make this work, we just need to know what you want connected to what.

I have it working right now with my laptop in place of the Linksys WAP, connected to the Belkin wirelessly and using ICS to share that link over the cabled connected to the WAN port on the NetGear. PCs and Xbox 360 can connect to each other and out to the internet just fine. I'd rather not have to run my laptop in order to provide that link, though. I was hoping to use the Linksys WAP as the net link into the WAN port of the NetGear router instead.

For clarity, I provided all the various equipment in the diagram to illustrate why it's set up as it is.

Thanks for looking into this.

[M/Q]

Actually you may want to try and setup the LinkSys AP as an access point client first. It just might work, but no guarantees. The everything plays nice rule does not apply to wireless technology.

If that does not work then you need to get a Belkin AP not a wireless router and then have it act as an access point client.