Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Usually people want to go the other direction, but I want to take our relatively fast and stable house 802.11g signal and bridge it to ethernet. I have tried using an Airport Express (the b/g flavor) and my i7 MacBook pro, both to no avail. Word is that the b/g flavor of

This flavor of Airport Express maxes at firmware 6.3 which doesn't support this kind of bridging properly. However, I expected my MacBook pro to do the job with its "Internet Sharing" feature. Alas, although my wired PC does sort of see it, it doesn't work out. Strangely, using DHCP the PC receives the same IP address as my MBP uses on the network. Less strangely, but still surprisingly, the wired ethernet port on my mac registers as the IP address of the gateway when queried with IFCONFIG.

It sort of makes sense that the mac would "pretend" to be the gateway, but the whole thing just isn't working and seems configured wrong - but all the docs I see say basically "OS X Internet Sharing: click it and go".

What do I do? Do i really have to buy more hardware, even though I have plenty of would-be candidates for bridging?

Incidentally, the host router originating the 802.11g signal is a belkin 802.11g router, and is documented to support WDS.

share|improve this question

migrated from Sep 13 '10 at 1:14

This question came from our site for professional and enthusiast programmers.

best off asking on superuser – Preet Sangha Sep 13 '10 at 1:08

The b/g AirPort Express does indeed support WDS wireless bridging, but Apple never officially supported WDS interop with third-party 802.11 gear. You might still be able to get it going, but beware that WDS requires a fair bit of manual setup:

If you want to go with the MacBook Pro situation, beware that since the MacBook Pro doesn't do bridging, you'd end up doing double NAT, which most network designers strive to avoid.

I believe Mac OS X's Internet Sharing may hard-code its NAT private address range to 10.0.2.x. If your upstream NAT gateway is set to use that range right now, but lets you change it, then change the upstream NAT gateway's private address range so it doesn't conflict with the one Mac OS X's Internet Sharing NAT feature uses.

Because the Mac will be acting as a NAT gateway and DHCP server (just on the Ethernet side, serving the PC), it's right for the PC to receive a configuration via DHCP that says it should use the Mac's NAT private (Ethernet-side) IP address as the PC's default gateway address.

share|improve this answer
I have purchased a DAP-2553 now to achieve the function the Airport Express could not. Sadly, the DAP-2553 isn't working for me either. It has a WDS, WDS+AP and Wireless Client mode. It is running firmware 1.12. I am really getting frustrated here.. the only clue I get is the DAP-2553 log keeps reading: Deauth: STA 00:11:50:59:FB:9F(reason 6). That MAC is the belkin. Am I going to be forced to buy a second DAP-2553? – Malachi Sep 21 '10 at 16:08

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .