Does anyone know exactly how to use an airport extreme recieving mbp to run xbox live on a 360? Is there a program I need? Any input is appreciated.
^^
Thats doesn't work. It gets an IP address, as far as i can tell, sets up everything else. Establishes a link, but cant transfer anything.
im going out on a leg but I don't think the 360 supports a direct link.
im going out on a leg but I don't think the 360 supports a direct link.
You just need a cross-over cable to connect it, no need for a router.
What are my options other than the cable and trying to do this through my laptop? Keep in mind cheaper solutions maybe.
you don't need a cross over cable. you just need to configure your xbox manually. do a search for instructions on how to set up a wii with internet sharing from a mac. (i am at work, i can't) it is in the mac gaming forum.
you don't need a cross over cable. you just need to configure your xbox manually. do a search for instructions on how to set up a wii with internet sharing from a mac. (i am at work, i can't) it is in the mac gaming forum.
You just need a cross-over cable to connect it, no need for a router.
no you if you read above it doesn't work.
A cross over cable wont solve anything. The mac already takes care of it. I personally think cross over cables are total crap. They charge three times as much, and the only difference is the placement of two wires.
no you if you read above it doesn't work.
A cross over cable wont solve anything. The mac already takes care of it. I personally think cross over cables are total crap. They charge three times as much, and the only difference is the placement of two wires.
A cross-over cable will solve everything, if a straight through cable is used, the Tx and Rx for both devices would be tied together, really doing nothing. With a cross-over cable, the Tx and Rx pairs are reversed on one end, allowing, for instance, the Rx of the Mac to connect to the Tx of the Xbox, and the Tx of the Mac to connect to the Rx of the Xbox.
Your opinion is just that, an opinion, just because you think they are total crap, does not mean that it won't work.
ADD-Machine:~ Andrew$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
ether 00:16:cb:a1:ba:32
media: autoselect status: inactive
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::217:f2ff:fee7:8053%en1 prefixlen 64 scopeid 0x5
inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:17:f2:e7:80:53
media: autoselect status: active
supported media: autoselect
wlt1: flags=41<UP,RUNNING> mtu 1500
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:17:f2:ff:fe:7f:c0:cc
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
Notice that the WiFi has the IP 192.168.1.3Code:ADD-Machine:~ Andrew$ ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:16:cb:a1:ba:32 media: autoselect status: inactive supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet6 fe80::217:f2ff:fee7:8053%en1 prefixlen 64 scopeid 0x5 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:17:f2:e7:80:53 media: autoselect status: active supported media: autoselect wlt1: flags=41<UP,RUNNING> mtu 1500 fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078 lladdr 00:17:f2:ff:fe:7f:c0:cc media: autoselect <full-duplex> status: inactive supported media: autoselect <full-duplex>
with sharing enabled, the ethernet has 192.168.2.1.
So plug you xbox in, go into the terminal, and see what IP is assigned to the ethernet when sharing is enabled. Tell you xbox to use that, and then you should be up and running.
also, why is apple making people buy a modem when there is one built in... go figure...
A cross-over cable will solve everything, if a straight through cable is used, the Tx and Rx for both devices would be tied together, really doing nothing. With a cross-over cable, the Tx and Rx pairs are reversed on one end, allowing, for instance, the Rx of the Mac to connect to the Tx of the Xbox, and the Tx of the Mac to connect to the Rx of the Xbox.
Your opinion is just that, an opinion, just because you think they are total crap, does not mean that it won't work.