Imac in one room, speaker(s) another
in [Mac Systems]
|
From: David Empson on 26 Oct 2009 00:19 Michelle Steiner <michelle(a)michelle.org> wrote: > In article <251020092008084122%nospam(a)nospam.invalid>, > nospam <nospam(a)nospam.invalid> wrote: > > > > How could I set up the D-Link 604+ router to create a wireless > > > network? > > > > google says that's an old router which only supports 802.11b and wep. > > > > you would be *far* better off hardwiring the airport express to your > > existing network and using the airport for a wifi network, particularly > > if you have the latest 802.11n version of the express. even if you have > > the older 802.11g version, you are *still* ahead. > > The problem with that is that he AE needs to be in the other room to > connect to the speakers. Upgrading to a more modern wireless router and getting the Airport Express to join its network (as I described earlier) would be the best solution. If the Airport Express creates a wireless network and the iMac is connected to both that network and the D-Link, you may be able to get it working reliably, but everything has to be configured carefully. You will effectively be setting up two separate IP networks. The D-Link and Mac form one network, and the Airport Express and Mac form a separate network. The two networks must use different ranges of IP addresses so the Mac knows which interface to use. (I'd expect the LED on the Airport Express to be blinking orange in this configuration, because it will be complaining about not having anything plugged into its Ethernet port.) The key question: what IP address range is the D-Link supplying via its DHCP server? This can be identified on the iMac by looking at System Preferences > Network > Built-in Ethernet > TCP/IP. The fields of interest are the IP address assigned to the Mac, and the subnet mask. Most routers assign addresses that start with 192.168.0 or 192.168.1, and a subnet mask of 255.255.255.0. Some assign addresses that start with 10, and a subnet mask of either 255.255.255.0 or 255.0.0.0. The subnet mask identifies how to interpret the IP addresses. The first few dot-separated numbers in the IP address (corresponding to '255's in the subnet mask) identify the network, while the last few numbers in the IP address (correpsonding to '0's in the subnet mask) identify individual computers on the network. The D-Link and iMac Ethernet must have the same "network" part of their IP addresses (which they will have if the D-Link is acting as a DHCP server). The Airport Express and iMac Airport must have the same "network" part of their addresses, but it must not be the same as the one used by the D-Link and iMac Ethernet. The Airport Express will typically be acting as a DHCP server for its network, so the main point is to configure its DHCP server to use different settings from the D-Link's DHCP server. For example, if the D-Link is using IP addresses starting with 192.168.1 and a subnet mask of 255.255.255.0, the Airport Express cannot use addresses which match that pattern, but could use 192.168.0, 192.168.2 (or higher), or 10.x.x.x. The iMac must have its network interfaces in the right order. You want Built-in Ethernet higher up the list than Airport, so that Internet traffic will go through the D-Link. You should also turn off Internet Sharing on the iMac. It will only be confusing matters. You might run into a problem where the iMac doesn't bother to acquire an IP address on its Airport network. That can be avoided by using a static IP address, but I'd rather wait to hear more details about the IP addresses you are currently using before going into further detail. -- David Empson dempson(a)actrix.gen.nz
From: David Empson on 26 Oct 2009 00:40 nospam <nospam(a)nospam.invalid> wrote: > In article <michelle-5AD66F.20321325102009(a)news.eternal-september.org>, > Michelle Steiner <michelle(a)michelle.org> wrote: > > > > > How could I set up the D-Link 604+ router to create a wireless > > > > network? > > > > > > google says that's an old router which only supports 802.11b and wep. > > > > > > you would be *far* better off hardwiring the airport express to your > > > existing network and using the airport for a wifi network, particularly > > > if you have the latest 802.11n version of the express. even if you have > > > the older 802.11g version, you are *still* ahead. > > > > The problem with that is that he AE needs to be in the other room to > > connect to the speakers. > > that would be a problem. personally, i'd get an 802.11g router to > replace the aging dlink, even if if 802.11b has sufficient bandwidth > for an audio stream (i'm not sure it actually does). It does. AirTunes uses Apple Lossless encoding, which works out to roughly 44 kHz x 2 channels x 16 bits x 0.5 average compression = 704 kbps. 802.11b can cope with that even in poor conditions, as long as the network isn't busy with other activity. -- David Empson dempson(a)actrix.gen.nz
From: David Empson on 26 Oct 2009 00:40 M-M <nospam.m-m(a)ny.more> wrote: > In article <251020092008084122%nospam(a)nospam.invalid>, > nospam <nospam(a)nospam.invalid> wrote: > > > you would be *far* better off hardwiring the airport express to your > > existing network and using the airport for a wifi network > > Right. I cannot understand why he needs to use 2 routers. The Airport Express is needed solely for its audio output capability (AirTunes). The D-Link router is the primary router for the broadband connection (using a built-in modem, I expect). The two of them need to be in different rooms, unless cables (either Ethernet or audio) are run through the wall, or something like that. -- David Empson dempson(a)actrix.gen.nz
From: Mike Rosenberg on 26 Oct 2009 08:14 Michelle Steiner <michelle(a)michelle.org> wrote: > I think that the problem may be that AirTunes requires an Airport Extreme, > Time Capsule, or another Airport Express as the router, and will not work > with any third-party wireless router. No, that's not the problem. The Express _does_ work for AirTunes streaming with non-Apple routers. -- My latest dance performance <http://www.youtube.com/watch?v=kvB98fgse-s> Mac and geek T-shirts & gifts <http://designsbymike.net/shop/mac.cgi> Prius shirts/bumper stickers <http://designsbymike.net/shop/prius.cgi>
From: Robert Montgomery on 26 Oct 2009 10:46
David Empson wrote: > Michelle Steiner <michelle(a)michelle.org> wrote: > >> In article <251020092008084122%nospam(a)nospam.invalid>, >> nospam <nospam(a)nospam.invalid> wrote: >> >>>> How could I set up the D-Link 604+ router to create a wireless >>>> network? >>> google says that's an old router which only supports 802.11b and wep. >>> >>> you would be *far* better off hardwiring the airport express to your >>> existing network and using the airport for a wifi network, particularly >>> if you have the latest 802.11n version of the express. even if you have >>> the older 802.11g version, you are *still* ahead. >> The problem with that is that he AE needs to be in the other room to >> connect to the speakers. > > Upgrading to a more modern wireless router and getting the Airport > Express to join its network (as I described earlier) would be the best > solution. > > If the Airport Express creates a wireless network and the iMac is > connected to both that network and the D-Link, you may be able to get it > working reliably, but everything has to be configured carefully. > > You will effectively be setting up two separate IP networks. The D-Link > and Mac form one network, and the Airport Express and Mac form a > separate network. The two networks must use different ranges of IP > addresses so the Mac knows which interface to use. I think I'd rather buy a new router. > > (I'd expect the LED on the Airport Express to be blinking orange in this > configuration, because it will be complaining about not having anything > plugged into its Ethernet port.) > > The key question: what IP address range is the D-Link supplying via its > DHCP server? The D-Link 604+ configuration > Advanced page for DHCP says: Starting IP address: 192.168.0.2 Ending IP address: 192.168.0.33 > This can be identified on the iMac by looking at System Preferences > > Network > Built-in Ethernet > TCP/IP. The fields of interest are the IP > address assigned to the Mac, and the subnet mask. > > Most routers assign addresses that start with 192.168.0 or 192.168.1, > and a subnet mask of 255.255.255.0. Some assign addresses that start > with 10, and a subnet mask of either 255.255.255.0 or 255.0.0.0. IP address: 192.168.0.2 Subnet mask: 255.255.255.0 Router: 192.168.0.1 > The subnet mask identifies how to interpret the IP addresses. The first > few dot-separated numbers in the IP address (corresponding to '255's in > the subnet mask) identify the network, while the last few numbers in the > IP address (correpsonding to '0's in the subnet mask) identify > individual computers on the network. > > The D-Link and iMac Ethernet must have the same "network" part of their > IP addresses (which they will have if the D-Link is acting as a DHCP > server). > > The Airport Express and iMac Airport must have the same "network" part > of their addresses, but it must not be the same as the one used by the > D-Link and iMac Ethernet. > > The Airport Express will typically be acting as a DHCP server for its > network, so the main point is to configure its DHCP server to use > different settings from the D-Link's DHCP server. > > For example, if the D-Link is using IP addresses starting with 192.168.1 > and a subnet mask of 255.255.255.0, the Airport Express cannot use > addresses which match that pattern, but could use 192.168.0, 192.168.2 > (or higher), or 10.x.x.x. > > > The iMac must have its network interfaces in the right order. You want > Built-in Ethernet higher up the list than Airport, so that Internet > traffic will go through the D-Link. > > You should also turn off Internet Sharing on the iMac. It will only be > confusing matters. > > You might run into a problem where the iMac doesn't bother to acquire an > IP address on its Airport network. That can be avoided by using a static > IP address, but I'd rather wait to hear more details about the IP > addresses you are currently using before going into further detail. > |