Explain the difference: Modem, Router, WiFi

The way many ISPs sell services it is getting increasing confusing for consumers to understand the different components that go in to making "The Internet" work in their home.

For many people it is just a black box.

So here, I am going to try and explain the difference between a modem, a router and wifi, as well as the reasons you may want to buy one or more of these components separately.


To try and put this in to context, anyone of my generation will remember HiFi (no, not WiFi, I do mean HiFi). This is how we listened to iTunes back in the day :-)

You had components to a typical HiFi system which included things like a turntable, a tape deck, an amp, and speakers. You could buy them all in one simple cheap unit from someone like Amstrad if you wanted to, although the speakers were usually physically separate boxes connected by wires so that you could place them left and right.

Alternatively you could buy the various components and connect them together. You may buy the same make of components (i.e. from same manufacturer) but select which specific models you could afford, or you may choose to buy from different manufacturers because you feel that each was best as some areas and not others. (Ironically, some of the single board solutions where styled to look like separate boxes stacked up)

The main advantage of one box was cheapness, but you compromised choice and quality when doing this. Buying components allowed you to choose what you wanted, pick the right models that suited your tastes and budget, and get the system exactly the way you like it. It also allowed individual components to be replaced if you wanted, or of they broke.


If you are using broadband you will typically have a service from an Internet Service Provider (ISP) that runs via a phone line. This could be a normal ADSL service (the typical, up-to around 20Mb/s type services), or VDSL (the higher speed, often mis-named "fibre", services of up to around 80Mb/s). We'll ignore cable modems for now, but the principles are similar.

The modem is the bit that connects to the phone line and makes the broadband signals work on the line. Modem actually stands for Modulator/Demodulator because of what it does.

The choice of modem is mainly down to how well it works on your specific lines. Most modern modems work very well on most lines. Occasionally, on long lines, we find one make of modem will work better that another on a specific line. This is because each modem will use one of a small selection of chip sets, and each chip set has proprietary software that work well in some cases and not others.

This makes it a bit hard to pick a modem - you may not know which will be best for your line without some trial and error. In practice, for most people, there is not a lot in it as they are all pretty good.

There is, however, a key point that you have to have the modem that is right for the service. Generally a modem is either ADSL or VDSL but probably not both. Until now you would only be buying an ADSL modem as the BT VDSL services come with a modem supplied, but ISPs will now start offering wires only VDSL services. Trying to use an ADSL modem on a VDSL line will not work.

There are also other features. For VDSL there is a new vectoring feature that BT expect to launch soon, and not all modems support. For ADSL, which are almost all ADSL2 and ADSL2+ capable now, you may want AnnexM for higher uplink on the line, and not all ADSL modems do AnnexM (though, most do).

Ideally your ISP should be able to help you get the right type of modem for your services.

The modem connects to the phone line on one side (using a 4 way US style phone cable, usually via a splitter or adapter to a BT phone plug). On the other side, the modem connects to a router (using an 8 way Ethernet cable).


The next component to consider is the router. This connects to the modem. It works at a different level and provides IP (Internet Protocol) packets. It is responsible for actually logging-in to the ISP to allow your connection to work.

Often a router will have a modem built in and so you don't need a separate modem. In some cases, even if a modem is built in, you can use the router with a separate modem if you like. A good example is where the router has an ADSL modem built in, but you have a separate VDSL modem on an FTTC line so do not use the routers modem at all.

When the router and modem are separate, they are connected using an Ethernet cable (8 way connector) and use a protocol called PPPoE. It is actually possible to use PPPoE directly from most computers, e.g. a Windows or Mac laptop, connecting the laptop to the modem directly. This is really useful for testing as it lets you confirm if the modem is OK independently of the router.

Routers do vary a lot. One of the key aspects of routers is whether it supports the current Internet protocol (IPv6). Another important aspect is whether it has some sort of firewall, and if so, what sort of firewall. You can have a separate firewall if you want (yet another component). If you have Network Address Translation (NAT), that is usually in the router itself, and may mean you don't have to bother with a separate firewall.

There are a lot of subtle features that can affect the choice of router. One example is how well the router copes with re-connecting after an outage. It is so annoying for a network blip of some sort to leave you with no Internet until you reboot your router, and even worse if it is some remote, unattended, site.

The router typically connects to your home network. It may include a network switch and so have a number of 8 way Ethernet sockets. You may have it connected to a separate network switch (yet another component), or perhaps first to a firewall. If you have a separate WiFi, then that would be connected to the router or firewall via an 8 way Ethernet cable.


Wireless Internet connections are increasingly common within people's homes, replacing or supplementing the wired connections and network switches. They are very useful and found on laptops and tablets and phones.

For WiFi to work you need an Access Point (AP). This can be packaged in to a router or router/modem or connected separately. Even if your router has a WiFi AP built in, you don't have to use it - you could turn it off and buy your own separate APs.

In general, if you have a fixed desktop PC you are far better off using an Ethernet cable to connect that to your router/firewall than using WiFi. WiFi has limits on speed and latency (not good for gaming) and is subject to interference from other WiFi and non WiFi sources. It is also shared by all of the devices using it. A cable is always better.

There are many sorts of WiFi available, and usually have complicated codes like 802.11a, 802.11n, and so on. These are then confused by 2GHz and 5GHz options which are related to the different frequencies used and the protocols used.

I am not going to try and go in to a great deal of detail on the different types - there are far better web pages for that - the point here is that there is a choice. The choice is around budget, number of devices that the AP can handle, speed of wireless connection, compatibility with devices you have, and so on. In general the range of signal on a single AP is not so much of a choice as this is based on standards for the power used, so normally the same from one AP to another working to the same specification.

This is where buying components is a good idea - if your home has thick stone walls, or lots of floors, you will find that a WiFi signal will not work well in many parts of the house. You have to consider where to put a single WiFi Access Point for best coverage, and that may not be where the router is best located.

You can normally connect multiple APs on the same named network (the SSID) and that can work well. Devices will typically switch over automatically between the APs as you move around the house, though this can mean losing signal briefly. Each AP will normally be connected via an Ethernet cable back to your router/firewall.

It is possible to get WiFi repeaters which act as a WiFi device on your existing wireless network, and then provide further WiFi as an AP. These are not quite as good as running a separate new Ethernet cable to each AP.

One of the other annoyances with APs is reliability when working with some devices. There seems to be quite a lot of variation, with many APs needing rebooting occasionally. The two main makes I would recommend are the Apple Airport range, which seem to just work and the Ubiquity UniFi range which are ideal for wider areas needing several APs. The UniFi also have a cool feature of seamless handover between APs as you move around, as well as entry level models at a very reasonable price.

Unless you have a small house that can be covered by a single WiFi AP with no problems it is well worth getting separate APs and setting them up where you can get the best signal, cabling them each back to the router/firewall.

Update: If you get additional APs then, ideally, you need to cable them back to a network switch. This could be an Ethernet cable, and usually power to the AP. There are two other approaches that help. (1) Some APs will work with Power over Ethernet so the power can be connected by the network switch (e.g. router) and only need an Ethernet cable to the AP. This is great when the AP is best located somewhere that is not close to a power point. (2) It is possible to get Ethernet over Power adapters allowing Ethernet to use the power wiring, meaning that power at the AP elsewhere in the house can also provide the Ethernet connection via that adapter. (3) Obviously you could have Ethernet over Power to a separate power point, and there have the Ethernet over Power adapter and connect the Ethernet via a Power over Ethernet to allow just a single Ethernet from that remote power point to the AP, if that makes sense.


It is not uncommon for an ISP to provide one box which is modem, router, firewall, and WiFi AP, all in one. For a simple, cheap installation, just like the Amstrad HiFi, it may be ideal for lots of people. Another very common mix is modem and router/firewall. Until recently, the VDSL modem was usually separate from a router/firewall/WiFi box.

In many cases the standard device you are provided by your ISP may well be perfectly good. It may also be that you can use some of the components, and sensibly get a separate device for some aspect. You can usually turn off the built in WiFi and get a separate WiFi AP or set of APs if you need. You may be able to use the modem in the supplied device and configure it in bridge mode to link to a separate router/firewall. You may be able to use the supplied device router/firewall with a separate modem using PPPoE, ignoring its built in modem.

Don't be fooled

One of the reasons people are confused is some adverts from some big providers. You see providers offering the best signal or most reliable WiFi or longest reach for WiFi for the Internet Service they are selling. These are typically aspects of the WiFi AP part of the equipment they supply with their service. It is not really an aspect of the Internet Service they are selling at all, just a feature of the kit they choose to include.

You can buy service from an Internet Service Provider that provides a good Internet Service, or one that is the right price for you, and then separately buy WiFi APs that meet your specific needs to give you the best performance and reliability and range for WiFi in your home.


  1. "There is, however, a key point that you have to have the modem that is right for the service. Generally a modem is either ADSL or VDSL but probably not both"

    Most VDSL modems seem to be compatible with ADSL as well.

  2. Good article. This is a topic I regularly rant about :). A diagram showing the various components would be a useful addition, possibly with some boxes showing the components that are often packaged together.

    1. Agreed - I was thinking of making one. I may add one to this post later.

  3. It might be worth adding that a modem can be connected directly to a computer instead of being connected to a router.

    1. Like the bit that says "It is actually possible to use PPPoE directly from most computers, e.g. a Windows or Mac laptop, connecting the laptop to the modem directly. This is really useful for testing as it lets you confirm if the modem is OK independently of the router."?

  4. Even though I'm reasonably knowledgeable I'm still finding it really difficult to find "separates" with the features I need. There's no decent comparison website and most of the product reviews don't cover the feature set I need. This is where the analogy with Hifi fails - IMHO.

    So if anyone can recommend a great router that supports IPv6 properly, WiFi, VoIP, NAT (Sorry - it's for guests) and non-NATed subnets, and doesn't fall over as often as my current combination of a Wifi Router behind a Technicolor 582n, please let me know!

    1. For the router I'd say a FireBrick, but not cheap, sorry.

    2. I believe the new Drayteks support this (we've got a 5 year old Draytek Vigor 2820n which has served us pretty darn well: but no IPv6 support on the old models, the new ones do though). I've used this in residential (just two of us) and small business settings (around 20 cabled users, 10 wifi and 10 inbound VPN) with no problems.

      Price wise - they are cheaper than Firebricks (but do have less features), but more expensive than "bog-standard break after so much data" routers. It worked out cheaper for us to buy a Draytek than keep replacing cheap routers with other cheap routers.

    3. Because somebody's got to say it....
      Mikrotik RouterOS - either on x86 hardware or their own (incredibly cheap) RouterBoards: http://linitx.com/category/mikrotik-routers/200 - £36 for a five port RB750 box which does IPv4 and IPv6, statefull firewalling, NAT and manging, L2TP, PPPoE, PPTP, VLANs, scripts (and scheduling) as well as a whole load of other features. Add another £20 and you get Gigabit. The more powerful boxes will run BGP and there are wireless boxes too as well as supporting miniPCIex and USB GSM modems and so on. They have a fully-featured CLU and a nice GUI too.
      The only downside (from my POV, an upside, but you may think differently) is that you have to understand networking properly before it makes any sense to you - if you don't understand subnet masks and routing, you'll have no hope!
      I know of many people running RouterBoards behind xDSL modems with great success.

    4. I have an FB2700 at work and a Draytek 2820 at home.

      The Draytek is "fine" - generally we get along but there's nothing especially fantastic about it, and it really doesn't much like operating in any kind of network more complex than the average single subnet NAT consumer setup.

      The FB2700 is generally fantastic, but (unless I am out of date) has one huge limitation which is that (unlike just about every £30 consumer router) it doesn't have a "teleworker VPN" service.

      By "teleworker VPN" I mean something where a remote client (using the standard windows or osx vpn client, plus an IP address and some credentials) dials in, and gets assigned an IP address from the same DHCP pool used by LAN clients (presumably with some sort of proxy ARP by the router). But maybe I'm out of date on what the FB2700 sw can do these days...

    5. It now has IPsec, and will shortly handle the necessary EAP authentication to allow a typical remove device VPN. It is possible to connect to it via L2TP though, and I use that with one of our data SIMs from my iPad, giving it an IP on the home LAN via a FireBrick.

    6. Sounds good - I will look out for that!

      I do have an A&A data SIM somewhere configured to L2TP into to the office firebrick but I could never get it to do what I wanted (probably because I was guessing what I needed to do by reading the config definitions :-). When I have some free time I will dig it out of my desk drawer and ask for some proper advice in IRC...

    7. I ended up with a cisco 887 which does all that but isn't cheap (cheaper than a firebrick though!). Been through loads of routers to get there.. the Billion I had was closest but still had firmware that seemed to have never been through any QA at all (which is depressingly common for consumer routers).

      I did try routeros but its ipv6 support basically didn't work back then (no v6 over ppp, no dhcpv6, no v6 firewall..). Not sure how stable it is now.

    8. If you are using an IP on the LAN for the L2TP link you may want proxy-arp="true" on the interface or subnet for the LAN as well.

  5. RevK ref ; but Steven's comment is in plain english and much clearer to me as an audience; To be honest, for me, if I knew what PPPoE actually meant and what it actually did I'd probably not need to read your article in the first place... :S

    1. So the start of that para that says "When the router and modem are separate, they are connected using an Ethernet cable (8 way connector) and use a protocol called PPPoE. " did not help?

  6. Billion might be worth a look at. I use a Firebrick.

  7. This article is so useful, should be on the AA website

    1. The article is so useful it should be required reading for anybody calling themselves an IT engineer. I've lost count of the number of IT support companies (big and small) I've had to deal with who not only don't understand the difference between modems and routers, but don't even acknowledge the possibility that the functionality could be split over several boxes. I'll try using the HiFi analogy next time and see if that makes it easier for them!

  8. Would the humble micro filter be worth a mention? A vital component to get right, if you are on a long line.

    1. I mention it, but apparent from when they go wrong, these days they all seem to be pretty good, and much the same, IMHO.

  9. Pretty happy with my combination of Draytek Vigor 120, RouterBOARD RB750 and Cisco Aironet 1231 (yes no "n" but then none of my current wireless clients do either!). Although RouterOS did cause me grief with MSS when switching from MPoA on Be to PPPoA on Xilo.

  10. I agree that the Apple Airport range "just work", and they also support IPv6 fully. I have a couple of dual band Extremes and a single band Express and between them they handle all my wifi needs. My TG582n's wifi is disabled.

  11. An old Linksys router with OpenWRT or DDWRT would do the job, and cheaply


Comments are moderated purely to filter out obvious spam, but it means they may not show immediately.

ISO8601 is wasted

Why did we even bother? Why create ISO8601? A new API, new this year, as an industry standard, has JSON fields like this "nextAccessTim...