Xbox 360 with DD-WRT and Connect360?

[scootermaster]

First off, I have no idea if this should go in the networking, console gaming, or Apple forums, but we'll try here first.

My question is this: I have a brand-spankin' new Xbox 360 (thanks to a wonderful girlfriend). I have a Linksys router, flashed to DD-WRT (thanks to T-mobile) and I have a Hackintosh (thanks to Kaido!). The Hack runs something called Connect360 which allows me to stream files off of MacOS to the Xbox.

Connect360 works under the following scenarios: If the Xbox is plugged in to my main router (which my Hack is also plugged in to), and when it runs on my G4 Powerbook, which is connected wirelessly, and the Xbox is connected via the DD-WRT router.

The scenario I want is to be able to stream off the hack, which is connected to my main router via ethernet, with the Xbox connected wirelessly to the same router via the DD-WRT.

Xbox live, if that matters, works wirelessly through the DD-WRT. And Connect360 detects the Xbox [wirelessly]. It shows up on the software running on the hack, but the computer doesn't show up in the "computers" list on the Xbox.

Soooo, any ideas? I'm guessing it's a network thing not a software thing. The configuration is something like this:

Hack: some DHCP assigned IP, like 192.168.1.4 (ethernet)
G4: Same, but obviously not the same IP (wireless)
DD-WRT: Has an IP of 192.168.1.2 (I reset the firmware, and tried the instructions again, set it to 192.168.1.101 trying to "fix" it, and now it doesn't work it at all, but it did work previously with 192.168.1.2)
DD-WRT: is assigned a DHCP address in the range
Main Router (Same exact Linksys model, standard firmware): 192.168.1.1

Anyone have any bright ideas?

 

[her209]

Is the DD-WRT in client/repeater bridge mode?
What IP address does the XBox get when it uses DHCP to request one?
Is NAT/DHCP disabled on the DD-WRT?
Does the computer with the Connect360 have a firewall enabled?

 

[scootermaster]

Is the DD-WRT in client/repeater bridge mode?
What IP address does the XBox get when it uses DHCP to request one?
Is NAT/DHCP disabled on the DD-WRT?
Does the computer with the Connect360 have a firewall enabled?

Client bridge mode, as per these instructions: http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge#Example

I think the rounter assigned it 192.168.1.4 or something like that.

As per the above instructions, I know you explicitly turn off DHCP. I'm not sure about NAT, but I would imagine DD-WRT turns off NAT if you're in client bridge mode.

The computer with Connect360 has "allow all connections" checked in the security tab under "firewall" and does not have little snitch installed.

 

[ChAoTiCpInOy]

Try Rivet. It doesn't give as many problems as Connect360.

 

[scootermaster]

Try Rivet. It doesn't give as many problems as Connect360.

I tried Rivet. It actually shows up (after a bit) in the "test PC" section, but when I try to connect to it, it doesn't work.

I tried opening up the DMZ on the machine that has the files, and no dice.

This is weird...I know its worked before, but I feel like it worked a lonnnnng time ago.

That it works with my Powerbook connected to the same wireless network, or my desktop when the Xbox is connected to the primary router, makes me think there's some routing issues going on here. Somehow, my desktop, wired to the main router, then wirelessly to the DD-WRT, and then to the Xbox (and vice versa) just doesn't work. In terms of IPs and stuff, again, it's like this:

Desktop: 192.168.1.105
Xbox: 192.168.1.106
(all via DHCP from the main router)
DD-WRT: Client bridge, 192.168.1.4

There's another set of instructions, where the DD-WRT is in client mode (not client bridge mode) but it's a lot more confusing. The router gets a WAN IP like 192.168.1.50, but a local router IP of 192.168.2.2, with a gateway of 192.168.2.2 and a local DNS of 192.168.1.1 (the main router). And, of course, the xbox still gets the same DNS (via DHCP), but I remember having to fiddle a TON with the Xbox's network configuration to get it to work.

Any more ideas? :-( Thanks a lot for your help

 

[scootermaster]

I just tried PS3 Media Server. It works out of the box with the Xbox plugged in to the same router, but doesn't work using the DD-WRT as a wireless adapter.

So, I'm 99% sure this is a networking issue, not a software issue. Anyone have any ideas as to how I can get this working? I was hoping to use the Xbox as media extender, until I have the time/money/inclination to build a HTPC. I'm going to be really sad if it doesn't work. (Plugging them in to the same router is not feasible, as the TV where the Xbox will eventually go is downstairs).


Thanks. I'm a SadPanda(tm)

 

[JayBlay77]

In terms of IPs and stuff, again, it's like this:

Desktop: 192.168.1.105
Xbox: 192.168.1.106
(all via DHCP from the main router)
DD-WRT: Client bridge, 192.168.1.4

Now I could be completely reading this wrong, I'm having a hard time keeping your configuration straight. But it sounds like you're using the DD-WRT as your wireless adapter for the Xbox. Now I do the same thing with mine. However based on your IP's you're using two different ip addresses for the same location.

Ie the DD-WRT gets the IP address....there should be no additional config for the xbox. The xbox should adopt that ip address of the DD-WRT device. Unless the xbox just automatically grabbed a second ip and I never noticed.

But I've never done any configuration on the xbox. I configured my client by connecting it to my computer. Got it all set up and then connected to the xbox, which then adopted the configured settings.

Not at home at the moment so I can't check my actual settings, but off of memory I think that is what I have.

Hope it helps and I'll take a peek at mine when I get home.

 

[scootermaster]

Now I could be completely reading this wrong, I'm having a hard time keeping your configuration straight. But it sounds like you're using the DD-WRT as your wireless adapter for the Xbox. Now I do the same thing with mine. However based on your IP's you're using two different ip addresses for the same location.

Ie the DD-WRT gets the IP address....there should be no additional config for the xbox. The xbox should adopt that ip address of the DD-WRT device. Unless the xbox just automatically grabbed a second ip and I never noticed.

But I've never done any configuration on the xbox. I configured my client by connecting it to my computer. Got it all set up and then connected to the xbox, which then adopted the configured settings.

Not at home at the moment so I can't check my actual settings, but off of memory I think that is what I have.

Hope it helps and I'll take a peek at mine when I get home.

I'm interested in hearing your setup. Some notes:

I got it working with PS3 Media Server and Rivet (sorta), using bridge repeater mode, with the Xbox IP in the DMZ of my main router. Movies wouldn't really stream, but audio worked okay. It's still flakey. I'm not sure if the movie issue is wireless, my processor (C2D e7200, should have plenty of power) or the software.

The setup IS confusing, but according to most directions you end up with the following:

The main router's IP: 192.168.1.1
Your PC/Mac's IP: 192.168.1.105
Your Xbox's IP (assigned via the main router, via DHCP): 192.168.106
The DD-WRT's IP (hardcoded as per the directions): 192.168.1.101

I've tried killing the DHCP on the Xbox, and assigning it to 192.168.1.101, but that doesn't work, or at least it doesn't work with the current configuration. I haven't tried that with the client bridge, or bridge modes (there's directions for all three, and all three will get Xbox Live working).

So, here's the list of variables, I think:
- Main Router IP/Gateway/DNS
- Mac system IP/gateway/DNS (this shouldn't change)
- Xbox IP/Gateway/DNS
- DD-WRT IP/Gateway/DNS
- What to put in the DMZ of the main router
- What ports to open on the main router (same as above?)
- Software configuration (there's not much here, I turn off any sort of white/blacklists)

You're right in saying it would be great if the DD-WRT and the Xbox had the same address and were viewed as one entity. You'd think that client bridge mode would do that. Maybe I'll try that next, but as I said, I'm curious to see your configuration.

What's weird, is I'm pretty sure media sharing works from another device connected over 802.11 (i.e. connected to the same wireless SSID). Which makes me think the main router is having a hard time routing the "two" IPs the Xbox has. Keep in mind the main router (with stock Linksys firmware) can be flashed to DD-WRT if there's features I need there, but I doubt there is.


Thanks so much!

 

[scootermaster]

This is really driving me crazy.

Okay, so, I followed these instructions: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=45602&postdays=0&postorder=asc&start=0 (wireless repeater bridge, instead of client bridge) and for one GLORIOUS MOMENT it all worked. PS3 Media Server was serving up both some sort of Xvid DVI, as well as ripped VOB DVDs. There was no fast-foward/chapter skip with the Vobs, and the initial buffering took awhile, but it was nice.

So I go back to PS3 media server and tinker with the library, since it didn't have any of my music, and turn off the Xbox. Turn the Xbox back on, and...wait for it....

Nothing.

After another two hours of tinkering, I get it back, but I haven't done enough trials to know what combination of reseting, restarting etc is making this work. My intuitive guess is that either a). the software itself is screwy, or b). something is getting messed up with the routing tables.

Notes that may or may not be relevant:

1. When I live-monitored the DD-WRT's wan connections, for a brief moment there was both 192.168.1.107 (the Xbox) as well as 192.168.1.106 (my Mac/the server). Now, I can't seem to get anything but 192.168.1.1 (the main router).

2. Here's some debug info from PS3 Media server:

main] TRACE 12:43:57.548 Using forced address 192.168.1.106
[main] TRACE 12:43:57.550 Created socket: /192.168.1.106:5001
[Thread-3] TRACE 12:43:57.578 Starting DLNA Server on host 192.168.1.106 and port 5001...
[main] INFO 12:43:57.585 Using database URL: jdbc:h2:database/medias
[main] TRACE 12:43:57.585 Using database located at : /Applications/PS3 Media Server.app/Contents/Resources/Java/database
[main] INFO 12:43:58.229 Database file count: 2552
[main] INFO 12:43:58.229 Database version: 1.10.5
[main] TRACE 12:43:58.240 Sending ALIVE...
[main] DEBUG 12:43:58.244 Searching network interface for 192.168.1.106
[main] DEBUG 12:43:58.246 Sending message from multicast socket on network interface: name:en0 (en0) index: 5 addresses:
/192.168.1.106;

[main] DEBUG 12:43:58.246 Multicast socket is on interface: /192.168.1.106
[main] DEBUG 12:43:58.247 Socket Timeout: 0
[main] DEBUG 12:43:58.248 Socket TTL: 32
[main] TRACE 12:43:58.249 Unable to retrieve MAC address for UUID creation: using a random one...
[main] TRACE 12:43:58.250 Using following UUID: 0fdd8247-628e-4f94-8f23-c4a4b6d6ca51
[main] DEBUG 12:44:02.948 Waiting 250 milliseconds...
[main] TRACE 12:44:03.204 It's ready! You should see the server appears on XMB
[Thread-11] DEBUG 12:44:03.205 Searching network interface for 192.168.1.106
[Thread-10] TRACE 12:44:13.203 Sending ALIVE...
[Thread-10] DEBUG 12:44:13.203 Searching network interface for 192.168.1.106
[Thread-10] DEBUG 12:44:13.204 Sending message from multicast socket on network interface: name:en0 (en0) index: 5 addresses:
/192.168.1.106;

[Thread-10] DEBUG 12:44:13.204 Multicast socket is on interface: /192.168.1.106
...
...
...
Thread-11] DEBUG 12:44:17.907 Receiving a NOTIFY from [192.168.1.1:1900]
[Thread-10] TRACE 12:44:38.469 Sending ALIVE...
[Thread-10] DEBUG 12:44:38.469 Searching network interface for 192.168.1.106
[Thread-10] DEBUG 12:44:38.470 Sending message from multicast socket on network interface: name:en0 (en0) index: 5 addresses:
/192.168.1.106;

[Thread-10] DEBUG 12:44:38.470 Multicast socket is on interface: /192.168.1.106
[Thread-10] DEBUG 12:44:38.470 Socket Timeout: 0
[Thread-10] DEBUG 12:44:38.470 Socket TTL: 32
[Thread-11] DEBUG 12:44:38.470 Receiving a NOTIFY from [192.168.1.106:49163]


It does all that with the Xbox turned off. Also, when it "doesn't work", normally PS3 Media server shows that its connected to the Xbox, and the Xbox will detect the PS3 Media Server in the "PC connections" settings, but when I try and connect it will fail. Now it's worked after that before; I just go back to My Xbox and select videos/music from the server, but this time there were no computers available.

This is really driving me nuts here. Sigh.

 

[scootermaster]

Now I could be completely reading this wrong, I'm having a hard time keeping your configuration straight. But it sounds like you're using the DD-WRT as your wireless adapter for the Xbox. Now I do the same thing with mine. However based on your IP's you're using two different ip addresses for the same location.

Ie the DD-WRT gets the IP address....there should be no additional config for the xbox. The xbox should adopt that ip address of the DD-WRT device. Unless the xbox just automatically grabbed a second ip and I never noticed.

But I've never done any configuration on the xbox. I configured my client by connecting it to my computer. Got it all set up and then connected to the xbox, which then adopted the configured settings.

Not at home at the moment so I can't check my actual settings, but off of memory I think that is what I have.

Hope it helps and I'll take a peek at mine when I get home.

I've been doing more testing, and with PS3 Media Server, I can sometimes get it to work (and by "sometimes" I mean, when it works, and I shut down the Xbox and start it up again, it stops working).

I agree, it would be wonderful if there weren't four distinct IPs here (the server, the main router, the DD-WRT router and the Xbox). As a note, requests from PS3 Media server (running on 192.168.1.106) seem to come from 192.168.1.1 (the main router), not 192.168.1.107 (the xbox) or 192.168.1.2 (the DD-WRT). It'd be nice if the Xbox and the DD-WRT shared the same IP, but I'm not sure how to get that to work.

Did you get a chance to look at your configuration?

 

[JackMDS]

The Router that serve as an adapter should be put first put on a computer that is temp. of the Network and be configured to be a Wireless Bridge ( http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge ) with static IP that is out of the rnage of the main Router DHCP (like 192.168.1.222).

The Bridge must have its own core IP and it should be left alone transparent to the system. there is nothing else that you should do with it after the initial configuration.

The X-Box should get through the DHCP of the main Router its own IP (two devices on the same Network can not have the same IP).

 

[scootermaster]

The Router that serve as an adapter should be put first put on a computer that is temp. of the Network and be configured to be a Wireless Bridge ( http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge ) with static IP that is out of the rnage of the main Router DHCP (like 192.168.1.222).

The Bridge must have its own core IP and it should be left alone transparent to the system. there is nothing else that you should do with it after the initial configuration.

The X-Box should get through the DHCP of the main Router its own IP (two devices on the same Network can not have the same IP).

Trust me, this happened a lonnnnnnng time ago. It still does not work (for media streaming, Xbox live works under this scenario).

Something else is amiss.

 

[JackMDS]

It still does not work (for media streaming, Xbox live works under this scenario).
Something else is amiss.

I doubt that the AP working as a transparent Wireless card cares about the content of what is going through it

Thus that can be a starting. I.e., leaving the Card configured this way, and looking for something else.

 

[scootermaster]

I doubt that the AP working as a transparent Wireless card cares about the content of what is going through it

Thus that can be a starting. I.e., leaving the Card configured this way, and looking for something else.

Then it's either the software or something with routing at one of the endpoints. Obviously the DD-WRT doesn't care what sort of traffic is going through it, but like I've said before...I can't seem to break Xbox live. That'll work even in weird configurations where it probably shouldn't. But media streaming seems to work only when the moons are in a certain phase.

So it makes it hard to figure out what's going on.

 

[Fallen Kell]

I believe I know what your problem is. One of the issues with "Client Bridge Mode" is really the fact that it is a broken standard. The 802.11 only allows that all devices from that client bridge mode to connect using the same MAC address. Now for many things, this is not going to be a problem, but it is not following basic network laws, in that all systems on the same subnet will have a unique MAC address. Both the wireless bridge router and the device behind it (in your case, the XBox360) are using the same MAC address if you were to do a network snoop and capture that information.

This is discussed a lot in the forums over at DD-WRT. There are also issues with the current release of DD-WRT and Client Bridge Mode, and it is recommended to use one of the special builds, not the current release. For more information on this go read the DD-WRT Client Bridge Wiki page: http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge

You may need to convert from wireless bridge mode to WDS AP and WDS Client mode, however, WDS is vendor specific unfortunately (there is no IEEE standard), and thus you will need to have devices that will support WDS link between each other for this to work. WDS is also unfortunately slower than Client Bridge Mode due to extra overhead in the wireless connection. You can read more at the WDS page: http://www.dd-wrt.com/wiki/index.php/WDS

 

[scootermaster]

I believe I know what your problem is. One of the issues with "Client Bridge Mode" is really the fact that it is a broken standard. The 802.11 only allows that all devices from that client bridge mode to connect using the same MAC address. Now for many things, this is not going to be a problem, but it is not following basic network laws, in that all systems on the same subnet will have a unique MAC address. Both the wireless bridge router and the device behind it (in your case, the XBox360) are using the same MAC address if you were to do a network snoop and capture that information.

This is discussed a lot in the forums over at DD-WRT. There are also issues with the current release of DD-WRT and Client Bridge Mode, and it is recommended to use one of the special builds, not the current release. For more information on this go read the DD-WRT Client Bridge Wiki page: http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge

You may need to convert from wireless bridge mode to WDS AP and WDS Client mode, however, WDS is vendor specific unfortunately (there is no IEEE standard), and thus you will need to have devices that will support WDS link between each other for this to work. WDS is also unfortunately slower than Client Bridge Mode due to extra overhead in the wireless connection. You can read more at the WDS page: http://www.dd-wrt.com/wiki/index.php/WDS

Thank you for the information. Luckily (I hope?) both routers (the client and the host) are identical: Linksys WRT54G-TM. The host isn't flashed; the client has DD-WRT. One note: I don't need anything else connected to the DD-WRT other than the xbox. Is there some combination of MAC spoofing (which is enabled on the Linksys stock, DD-WRT and Xbox...i.e. everything) that will get the settings right?

As I said, that could be an issue if I wanted to plug other things into the DD-WRT, but just the Xbox would be fine. If I told the Xbox to have the same MAC as the DD-WRT, would that help? The other way around? Perhaps I'll have to try that next.

I'd prefer not to have to flash the host router, just because it's more work, more complicated and more risky, but if I have to, I will.

Lastly, do you know which versions of DD-WRT are the best to use?

(And for the record, I stopped using client bridge mode a long time ago, and have had the best results from using wireless repeater mode)

 

[Fallen Kell]

Most people are using the Svn11296 build for G routers in wireless bridge due to its stability. Others are using the previous V23 SP1 release and not upgrading to the V24 tree yet.

To be honest, I have found it works best if the host router is also flashed, but that is not always possible. If what you are doing works, then you might just want to stick with it. Wireless repeater mode works well on many routers, especially ones with dual-antenna (even more so if you can replace them). I have replaced my antenna with 9dbi gain ones on my base-station for better coverage in my home. I also have a 24dbi directional panel antenna which I carry in my laptop bag (along with another WRT54G that I got cheap), so that if I have a power outlet, I can usually find an open wireless network somewhere to patch into... (which was funny when one time my music professor always wondered why I had all those tech gadgets in my laptop bag until one day it saved him a lot of time by allowing him to connect the recording server to the university's wireless network from the main concert hall, where there is no wireless coverage).

 

[scootermaster]

I haven't done a lot of tinkering with WDS, but preliminary results are about the same. Apparently the WRT54G supports WDS implicitly...i.e. there's nothing you enable on it. I enabled it on the DD-WRT, and it worked once, but not since.

Any other ideas?

I'm going to explore more with things like WMC and Tversity on a Win7 install soon.

 

[fistlo]

I haven't done a lot of tinkering with WDS, but preliminary results are about the same. Apparently the WRT54G supports WDS implicitly...i.e. there's nothing you enable on it. I enabled it on the DD-WRT, and it worked once, but not since.

Any other ideas?

I'm going to explore more with things like WMC and Tversity on a Win7 install soon.

So im dealing with the exact same problem.
Two linksys WRT54G2 routers. One flashed with the DD-WRT and the other is not.

I am able to see the computer when I test the PC connection (it even recognizes connect360 or rivet) but it does not recognize it as a media center computer.

I also ended up trying WDS but it did not work and have also tried a couple other configurations.

I'm going to flash the other router tomorrow and will tell you how it goes.

 

[fistlo]

Just as a default measure I restarted the DD-WRT so that it was in default. Linked it directly to the xbox and connected to the router directly via wireless on my mac. Thus no intermediate between the Xbox and the Mac except the DD-WRT.

Had the exact same outcome. This doesn't make sense really from what everyone else has been saying... that its a transfer protocol between the two routers. I think that its the firmware supplied on the DD-WRT router thats causing the problems.