Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Airport Express WDS with third party NAT / DHCP' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Airport Express WDS with third party NAT / DHCP
Authored by: hoss on Sep 20, '04 12:30:17PM

Can't seem to get this working properly with my D-Link 624 following the directions provided above.

Has anybody else been able to get this working? I'd love to use the AirPort Express but I really don't want to run an ethernet connection to it if possible.



[ Reply to This | # ]
Airport Express WDS with third party NAT / DHCP
Authored by: matx666 on Sep 20, '04 01:34:44PM

No, me neither. I have the same Dlink-624... AirTunes works, and my stereo in the other room is happy, but the bridging trick does not work out of the box. I have not tried renaming it to the same as my dlink with the same password. Xlr8yourmac.com has a page all about different tricks and tips, but only one mention of a dlink in there. (http://www.xlr8yourmac.com/feedback/airport_express_feedback.html)



[ Reply to This | # ]
Airport Express WDS with third party NAT / DHCP
Authored by: nicol on Sep 20, '04 10:20:39PM
As it happens I was wrestling with this problem a couple of weeks ago, with a twist. Broadband comes into my house via DSL to a wireless base station (2Wire) , i.e. NOT an Apple. It runs DHCP through the air and to all devices hanging off an ethernet hub to which it is cabled.

Lessons learned after hours of experiments:

There is no easy way to get the Airport Express to extend the 2Wire network.

I have an Airport Extreme base station. I jacked it into the hub, and noted the DHCP address the 2Wire gave it. I know from experience that these addresses are highly stable once assigned.

I configured the Extreme base station to treat its own IP address as static, and to run NAT and DHCP, in the same 172.16/16 space as the 2Wire manages. Clients on the Extreme's network can't reach the outside Internet, but I can (and did) configure the Express to use the Extreme as a WDS base, and the Extreme to serve as a WDS base (that allows wireless clients, and names the Express as a remote WDS base). This established the WDS link between Extreme and Express, and I then reconfigured the Extreme (under "Network" in Airport Admin Utility) to (i) Distribute IP addresses, (ii) sharing a fixed range of IP addresses that again overlapped the 2Wire network's space.

So the trick is that remote devices (at least the Apple laptops in the house) can get an IP address from the 2Wire network when they are in range of it. Switching over to the Extreme's network they retain the IP address, and can surf the Web. The ethernet hub bridges IP traffic between the 2Wire and Extreme networks, e.g. I can scp between devices on the two networks.

So I'm not entirely sure of all the nuances involved in making this go, but here's the settings on my Extreme when the lights came on and the Express actually extended the network

"Airport"
- enable encryption (using WEP)
- channel 10
- mode 802.11b/g compatible
"Internet",
- connect using Ethernet
- configure TCP/IP using Ethernet, manually
- IP address (the one reliably given out by the 2Wire)
- submask 255.255.0.0
- Router address : (the one found on devices under the 2Wire network)
- Domain name : (the one used by the 2Wire network)
- WAN Ethernet Speed : Automatic
"Network"
- Distribute IP addresses
- Share a range of IP addresses (using only DHCP)
[I specify a range at some distance from the cluster of IP
addresses the 2Wire gives out. A /16 is a big place for a home network]
"Port Mapping"
nothing here
"Access"
nothing here
"Authentication"
nothing here
"WDS"
- enable this base station as a WDS main base station
- allow wireless clients on this base station
- the Express base station is listed as a WDS remote base station

The Express was configured to extend an Extreme, using 128 bit WEP for security. It does seem to have gotten its IP address from the Extreme base station.

So if I were to get broadband via a cable modem, my guess is that this basic schtick might work if the remote devices have IP addresses configured manually, in the address space managed by the cable modem's DHCP server. Naively running a connection through two NATs appears to be problematic and so we can't run NAT through the Extreme, but that's what the Express assistant wants to see to configure WDS. That's the only time it checks though. IP addresses are remembered mostly once assigned, and so if you can get a client a legit (from the point of view of the cable modem's IP space) address, the modem isn't going to be picky about where that address came from.

Just my $0.05 worth, YMMV.

[ Reply to This | # ]

Airport Express WDS with third party NAT / DHCP
Authored by: macwellgh on Apr 16, '05 12:52:56PM

I don't think the DI-624 is compatible with WDS.



[ Reply to This | # ]