Extending a WiFi network with two Macs and a FireWire cable
12th April 2007
Last night’s Oxford Geek Night went really well, despite more than the usual flurry of problems. It’s definitely true that the more geeks there are in a room the less likely it is that the projector will work! Thankfully we got everything up and running in time for the talks to start, although it was a pretty close call.
A few of the talks needed internet access from the stage—always risky at conferences, which is why I’ve taken to recording screencasts of anything I want to demonstrate just in case there’s a problem. For the last event we hooked up a mobile phone to a laptop running an ad-hoc WiFi network, which was slow but worked fine. This time round we checked with the venue well in advance to confirm that their WiFi had been installed.
The wireless was indeed up and running, but there was one pretty significant problem: the stage was just out of range! We could pick up a network signal fine from about 10 feet away from the stage, but the layout of the building meant that the stage itself was a WiFi blackspot.
At that point the evening started feeling a bit like Apollo 13. We had a bunch of laptops, various cables (but sadly no 10 foot network cable; that’s on the list for next time) and about half an hour to go before the event kicked off. That’s when I remembered that Internet Connection Sharing under OS X has a “FireWire” option.
So here’s how to build your own WiFi repeater using two Macs and a FireWire cable:
- Connect Mac A to the existing WiFi network. Confirm with ping or a browser.
- Turn off the AirPort card on Mac B (for the moment).
- Run a FireWire cable between A and B.
- On Mac A, bring up System Preferences -> Sharing -> Internet.
- Share your connection from “AirPort” to “Built-in FireWire”.
- On Mac B, find System Preferences -> Network -> Built-in FireWire, and check that you’ve successfully connected.
- Confirm that Mac B can see the internet, using ping or a browser.
- On Mac B, browse to System Preferences -> Sharing -> Internet.
- Share your connection from “Built-in FireWire” to “AirPort”.
- Click “AirPort Options...” and set a name for the new network (and optional WEP key). This is the network that other machines will connect to.
- Hit “Start”.
All we had to do then was position our pair of laptops somewhere that was in WiFi range of both the venue network and the stage. Job done!
Except for one thing... we forgot to factor in the dampening factor of human bodies. As the area filled up the signal strength from the venue WiFi reduced, leading to intermittent network failures. The nice thing about laptops is that you can move them around, so for the talks that needed network access Nick and I stood near the door with our laptops held over our heads.
It’s a good thing the venue microphone showed up at the last minute, as our backup plan for that involved two laptops, a USB microphone, a patch in to the mixing desk and iChat AV...
We’ve started adding slides to the official site, and will hopefully soon have videos up there as well. If you took any photos at the event tag them on Flickr with oxfordgeeknight2 to have them show up on the site. Nat’s planning the next event for June or July, so subscribe to the announce-only mailing list if you want to stay informed.
More recent articles
- Things I've learned about building CLI tools in Python - 30th September 2023
- Talking Large Language Models with Rooftop Ruby - 29th September 2023
- Weeknotes: Embeddings, more embeddings and Datasette Cloud - 17th September 2023
- Build an image search engine with llm-clip, chat with models with llm chat - 12th September 2023
- LLM now provides tools for working with embeddings - 4th September 2023
- Datasette 1.0a4 and 1.0a5, plus weeknotes - 30th August 2023
- Making Large Language Models work for you - 27th August 2023
- Datasette Cloud, Datasette 1.0a3, llm-mlc and more - 16th August 2023
- How I make annotated presentations - 6th August 2023
- Weeknotes: Plugins for LLM, sqlite-utils and Datasette - 5th August 2023