13 November 2026
Insignia's home page listed 216 supported games on November 13, 2026, and that single number says a lot about where original Xbox online play stands. Fan-run servers have turned consoles whose official services went dark into places where matches can start again. The catch is that each console gets there by a different route: a DNS change on Xbox, a DNS disc on Wii, and a Raspberry Pi pretending to be a phone exchange on Dreamcast. Here is how each works, what you need, and where to check what is actually populated.
Finding the right server and game directory
Before touching a single setting, check that your game is supported. On Xbox, Insignia's games directory states that every title currently supported by the service appears on its Games page. That makes it the authoritative list rather than a forum thread or an old wiki post that may be out of date. The home page carries a running count, and as of mid-November 2026 that count stood at 216.
The home page also works as a rough pulse check. On November 13, it showed Halo 2 as an active game with 38 online entries and an 11 / 32 active-player figure. A game being "supported" and a game having people in it right now are different things, and a glance at the activity panel tells you which one you are dealing with. If you want a match tonight, pick a title that is showing live entries rather than one that is merely on the list.
Dreamcast players have a similar reference in the FAQ at Dreamcast Live, which names Outtrigger, Phantasy Star Online v.2 and Propeller Arena among the supported games. A 2024 guide from Time Extension put the number of Dreamcast games with online play through Dreamcast Live and DreamPi at 38 at the time of writing. That is far smaller than Insignia's catalog, which fits the console's shorter life and smaller library, but it covers some of the most talked-about online games the system ever had.
The practical habit is simple. Look up the game on the project's own directory first, then look at how many people are showing as active, and only then spend an evening on setup. A correctly configured console connected to an empty lobby feels exactly like a failed configuration.
How each console reconnects to community servers
All three projects follow the same underlying idea: the console is persuaded to talk to a community-run server instead of the long-defunct official one. What differs is how much of that persuasion happens in software and how much in hardware. Xbox and Wii are the easy cases, since both rely on DNS settings. Dreamcast, which shipped with a dial-up modem, needs more.
On the original Xbox, the first step is the dashboard. Insignia's connect guide says consoles need the latest original Xbox dashboard and gives D:1.00.5960.01 as the version to check for. If your console reports something older, sort that out before anything else, because network settings will not help a machine on the wrong dashboard. Then comes DNS. The guide says the primary DNS should be 46.101.64.175, while the secondary can be either 8.8.8.8 or 1.1.1.1. The primary address is the one that matters, since it points the console at the community service. The secondary is an ordinary public resolver, so you have a choice of two.
The Wii takes a similar approach through Wiimmfi. A retro Wii online guide at whatwhatboy.com says that for the DNS-disc connection method, Wiimmfi uses primary DNS 95.217.77.181 and secondary DNS 1.1.1.1. As with Xbox, the first number is the project's own server and the second is a familiar public one. The addresses for the two projects are not interchangeable, so a common slip is carrying numbers over from one console's setup notes to another. Write the right pair down before you start, and check each digit group, because a single transposed number produces a "cannot connect" error that looks identical to a dead server.
For people who like to cross-check live activity across several communities, lobby aggregators serve as a reference point for platforms that organize online match data. Outlets such as Extra-Betting.com sit alongside the projects' own pages as a place to see how regional server lists and community hubs are categorized. Whatever you use as a secondary reference, the project's own directory remains the final word on what is supported.
Dreamcast is the odd one out. DreamPi, described in Dreamcast Live's connection guide, can run on a Raspberry Pi or on a PC through a virtual machine. The original console still thinks it is dialing out over a phone line, and DreamPi sits in the middle to catch that call and route it onto the modern internet. That is why Dreamcast setup involves hardware shopping in a way the other two do not, and why it gets its own section below.
Hardware and setup needed for DreamPi
The Pi route is the better-documented one, and the shopping list is specific. Dreamcast Live's DreamPi video tutorial, first published in 2016, spells out what is required, and the project's later written tutorial adds an important limit on which Pi you can use. Pick the model carefully, because the newest board is the one that will not work.
The items below come from those two Dreamcast Live pages and cover everything needed for the Pi route.
- A Raspberry Pi: any model works except the Raspberry Pi 5
- A Linux-compatible USB voice modem
- A line voltage inducer or telephone line simulator
- A 4GB or larger SD or microSD card
- The cables to connect the console, modem and network
Two items on that list deserve a second look. The modem has to be a voice modem and has to work under Linux, so a generic USB modem pulled from a drawer is a gamble. The line voltage inducer or telephone line simulator exists because the Dreamcast expects to see a live phone line on the other end, and without something supplying that, the console will not believe it has a connection to dial. Buyers who treat these two parts as interchangeable with anything labeled "modem" tend to lose the most time.
The PC and virtual machine option mentioned in the connection guide may suit people who do not want to dedicate a Pi to the job, though the physical modem and line-simulation question still belongs to your particular setup. If you already have a spare older Pi, the project's tutorial says it will do, as long as it is not a Pi 5. An older board that would otherwise be sitting in a box is a perfectly reasonable choice here.
Supported games and live activity snapshots
Comparing the three projects side by side shows how differently each community's catalog has developed. Insignia has the largest verified list, Dreamcast Live has a compact one with a handful of famous names, and the Wii guide documents the connection method without a game tally. The figures below are taken from the dated pages cited above, so treat them as snapshots rather than permanent numbers.
Original Xbox (Insignia) lists 216 supported games as of Nov. 13, 2026, with Halo 2 as an example active title. Dreamcast (Dreamcast Live / DreamPi) lists 38 supported games per a Sept. 2024 guide, including Outtrigger, Phantasy Star Online v.2, and Propeller Arena. Wii (Wiimmfi) figures are not given in the guide.
Read the Xbox row with a little care. The 216 figure is a count of supported titles, while Halo 2's 38 online entries and 11 / 32 active players come from a separate activity display on the same home page. Those are not the same measurement, and neither should be read as the total population of the service. The Dreamcast count is also older than the Xbox one, so the real number may have moved since the guide was written, which is a good reason to confirm against the FAQ before buying hardware for one specific game.
For anyone deciding where to start, the numbers suggest an easy order of operations. If you own an original Xbox, a dashboard check and two DNS entries get you to the largest catalog of the three. If you own a Dreamcast, budget for a voice modem, a line simulator and a compatible Pi, and pick your game from the FAQ list first. Either way, open the project's directory on the day you plan to play and see who is online before you sit down with a controller.