What a network is, and the types of network
A network is two or more devices that have a way to exchange data and each have their own address; that is all. Home wifi, a company network and the internet itself are three sizes of that one idea, and what separates them is scale and who owns each piece.
- Lesson 2 of 12
- Beginner
- Free, no signup
The two sides of a home network, and the device standing between them
Your devices
the nodes of the network, each with a local address
- Phone, laptop, television and printer are all nodes
- Inside the house they talk to each other directly
- From outside they have no direct address
The outside world
the operator network and the internet beyond it
- A line you rent, not something you own
- Its faults can only be reported
- Websites see all your devices as one address
every packet leaving the house passes through this one point, and this is where responsibility changes hands
The router
both the hub of your network and its only exit
- Gives each device a local address
- Shares one public address among all of them
- In most homes it is also the modem and the access point
This drawing is one home. In an office the switch and the access point are usually separate from the router, and the border of responsibility falls elsewhere.
Last checked: Facts and tool names in this lesson are re-checked against their sources on this date.
What exactly is a network?
A network is built from three things and no more: nodes, meaning the devices that talk; links, meaning the cable or radio between them; and a protocol, meaning a shared language everyone follows plus one address per node. Two laptops with a cable between them are already a network.
Addressing is where most problems happen, not the cable. If two devices on one network do not take matching addresses, the link is healthy and nothing connects; that is exactly the case where the user says "the cable is plugged in but it does not work".
Something that gets said less often: a network has degrees. On our own server the site does not go through the network at all to talk to its database, because the setting is localhost and the connection goes through a socket on the same machine. Even when a program deliberately uses the network to talk to itself, the round trip on the machine takes 0.022 ms, while the same round trip to the first router, one cable away, is 0.252 ms. Ten times further, for a distance the eye cannot see.
So when something does not work, first decide which of those three parts is broken. Our support experience is that most "network outages" are really addressing problems or one specific device, and the cable and the antenna are innocent.

What is the difference between a LAN, a WAN and the internet?
The difference is scale and ownership, not technology. A LAN, a local network, is one place: a home, an office, one floor. You own it, its addresses are private, and you pay no rent for it. A WAN, a wide area network, connects several places and almost always runs on a line rented from an operator. The internet is the network of networks and has no single owner.
The practical border between the three is exactly where responsibility changes hands. Up to the home router it is yours and you fix it yourself; past the router it is something you rent and the only available move is to report it. That one sentence answers half of the arguments people have on the phone with support.
And the biggest household misunderstanding comes from here: wifi and the internet are not the same thing. A full signal icon only says the local network is healthy and your phone is talking to the router; it says nothing about the health of the operator line. That is why you can have full signal and no page opening, and why testing in the order given in the lesson on how the internet works, from near to far, gets you an answer.
Four layers, from the device itself out to the internet
-
1
The device itself
Programs talking to each other on one machine, with no packet ever leaving the network card.
-
2
The local network
A home or an office. You own it, its addresses are private, and you fix its faults yourself.
-
3
The operator network
The line you rent. From here on you can only measure and report.
-
4
The internet
The network of networks. Nobody owns it, and for that same reason nobody is solely responsible for it.
The border between the second and third layer is where responsibility passes from you to the operator. That border is contractual rather than technical, and in an office with a dedicated line it falls elsewhere.
What is actually sitting inside your home network?
Usually one box playing three roles at once. The modem turns the operator line into something your devices understand. The router decides what goes out and shares one public address among everyone. And the access point is the radio that makes the wifi. If there are network ports on the back of the box, there is a small switch inside it too.
Addresses inside the home are private, and deliberately so. Three ranges are set aside for exactly this and recorded in a document called RFC 1918: 10, 192.168, and the span from 172.16 to 172.31. Your router address is one of those. What is interesting is that our own public server has a default gateway in that same reserved span, which means even a machine that answers the world all day sits inside a local network first.
Outside the home, though, all of you are one address. The router passes the traffic of every device through a single public address, which is why a site you open cannot tell whether the request came from the phone or the laptop; they all look the same. The "my IP" you see on websites does not belong to any of your devices either, it belongs to the router.
A security consequence follows that few people notice: because devices inside the home have no direct address from outside, they are not reachable from the internet by default. That is free protection, and it is exactly what gets given away by "opening a port" or putting a device into DMZ mode.
Should you run a cable, or is wifi enough?
This question has no winner, and anyone who rules one out for you is selling something. A cable gives constant latency, is unaffected by walls and neighbours, and shares its capacity with nobody; in return it has to be run and plugged into a port. Wifi gives mobility and needs no cabling; in return it shares the air with every device around and its quality changes minute by minute.
One number is advertised everywhere and read correctly by few: the big figure on the router box is the radio rate under laboratory conditions, not the speed that reaches your device. Distance, walls, the number of devices and channel congestion each take something off it, and none of them is printed on the box.
Our position is simple: anything that is stationary and matters gets a cable. The desktop computer, the television that streams, and the machine you take video meetings on. Everything else stays wireless, and on the newer band where the device supports it, which is less crowded but passes through walls less well.
And the boundary of that advice: in a rented flat where you cannot drill, or for a laptop that moves constantly, a cable is the wrong answer. There the right work is improving the wifi itself, meaning where the router sits and which channel it uses, not pulling wire.
Cable and wifi, each for a different job
Cable
- Constant, predictable latency
- Walls and neighbours have no effect on it
- Shares its capacity with no other device
- Has to be run and plugged into a port
- For stationary work that matters: desktop, television, video meetings
Wifi
- Free movement, with no cabling at all
- The air is shared with every device around
- Its quality changes minute by minute with distance and walls
- The number on the box is the radio rate, not the speed that arrives
- For anything that moves, and for a rented flat
This comparison is for an ordinary home. Where dozens of wireless devices work in one building, channel congestion dominates and none of these lines decides on its own.
Which settings should you touch, and which not?
Three things are worth doing, and they are done once. Change the password for the router admin panel, which is not the wifi password and in most homes is still the factory value. Update the device firmware. And if your router offers a guest network, put visitors on it so they cannot reach the devices in the house.
And three things not to do merely because someone on the internet said so: opening a port, putting a device into DMZ mode, and switching off the router firewall. All three remove the free protection described in the previous section, and usually do not solve the problem they were suggested for.
A truth that security product advertising leaves out: for a home network the real danger is usually not a skilled attacker, it is the default panel password and firmware that has not been updated in years. The first takes a minute and the second takes ten, and both are more effective than anything you can buy.
The fast path, with AI
The ordinary way to deal with a home network problem is to switch the router off and on and hope. The fast way is to take four readings yourself and force the language model to judge on those four readings only. The difference is that the second way tells you which layer is broken, rather than what might be broken.
- Take your own address and the router address: <code>ipconfig</code> on Windows, <code>ip -4 addr</code> and <code>ip route</code> on Linux, network settings on macOS. The router address is the default gateway.
- Run three pings and keep the raw output of all three: the router, then <code>1.1.1.1</code>, then a name such as <code>rgb.ir</code>. Those three alone locate the border of the fault.
- Read the device model from the label on the box itself, not from the operator invoice. Similar names are common and their firmware menus are not the same.
- Hand over all three together and ask it to name only the broken layer and say which setting to look for in the manufacturer manual. If it names a menu, check it against the manufacturer own manual before touching anything.
Copy-ready recipe
You are a home network specialist. Judge only from the data below and add nothing to it.
Router model (from the label on the device): {model}
My device address: {address}
Router address (default gateway): {address}
Ping to the router:
{raw output}
Ping to 1.1.1.1:
{raw output}
Ping to a name such as rgb.ir:
{raw output}
The symptom I see: {for example, wifi is connected but no page opens}
Write three things:
1. Which layer is broken: my local network, the operator line, or name resolution. Choose one only and say which piece of data shows it.
2. One next step I can take myself, without changing any security setting.
3. If the data is not enough to decide, write which further measurement is needed.
Rule: do not guess the router menu from memory. If you do not know exactly where a setting is, write "look in the manual for this exact model".
Before you trust the output: Two things must never be pasted: the router configuration backup and the wifi password. That file usually holds the entire configuration of your home, and its diagnostic value never justifies the risk. And if the answer suggests opening a port or switching off the firewall, stop there; that suggestion almost never solves the problem and it removes the default protection of your network.
AI in this kind of work
For network concepts a language model is the best private tutor that has ever been freely available: it explains any term with an example and makes sense of a strange setting in a router panel. But the moment your specific device is involved, its memory is no substitute for the manual. The rule that works: ask the model for the concept, and the manufacturer manual for the exact location of the setting.
Tools that actually help
- Gemini Notebook Its best use is exactly this lesson: upload the PDF manual of your own router and ask the question inside that document. The answer comes from the manufacturer text, so the location of a menu is no longer a guess. It runs on a Google account, and Iran is not among the available regions.
- Claude Good for reading the raw output of commands and explaining what each line says. Iran is not on Anthropic list of supported countries, so there is no official route to sign up or pay.
- Gemini Good for translating network jargon into Persian and explaining concepts with examples. Google own page says the Gemini app works in more than 230 countries and territories, and Iran is not on that list.
Where it backfires
Two specific risks, both of which happen in this exact topic. First, the model names a menu path with complete confidence that does not exist in your device firmware; Anthropic itself calls this confident invention hallucination in its documentation and writes about reducing it, which means the vendor treats it as a real weakness rather than a rumour. Second and more dangerous, it suggests opening a port, putting a device into DMZ mode or switching off the firewall in order to "solve the problem"; those remove the same default protection the third section described, and the user usually does not know what they have agreed to. And a note about data: Google own help page for Gemini says plainly not to enter confidential information, and a router configuration backup is exactly that. For what paying for these tools looks like from Iran, see the buying guide.
Sources: Anthropic: reduce hallucinations Anthropic: supported countries Google: Gemini Apps privacy and data Google: where Gemini Apps are available
Where this advice stops
This lesson explains the network of a home and a small office, and it stops there. The network of an organisation with several branches, virtual networks that separate traffic, routing between two buildings and multi access point wireless are another world that starts with these concepts but does not end with them. One more thing is missing here on purpose: the newer generation of addressing, which is still less common in Iranian homes and needs a lesson of its own.
From our own work
Three things from our own server, all three repeatable. First, the site does not enter the network at all to talk to its database: the setting is localhost and the connection goes through a socket on the same machine, so a slow query is never a network problem. Second, on the same day we measured with ten packets: the round trip on the machine itself was 0.022 ms at the lowest and to the first router 0.252 ms at the lowest, ten times more for a distance of about one cable. Third, this same server that answers the world all day has a default gateway on a private address from the range reserved by RFC 1918, the same family of address your home router has. To see this on your own machine, ip route on Linux and ipconfig on Windows show the default gateway.
Real follow-up questions
The wifi is connected but there is no internet. What does that mean?
It means the local network is healthy and the next link is not. Your phone is talking to the router, so the signal is full, but either the operator line is down or the router could not obtain an address. Testing takes a minute: ping the router first, then a numeric address; if the first answers and the second does not, the problem is outside the house.
The address websites show me: which of my devices does it belong to?
None of them. That address belongs to your router, and every device in the house goes out behind that one address. This is why your phone and your laptop look identical from outside, and why a neighbour connected to the same network shares the same address as you.
Does a wifi repeater increase internet speed?
No. It solves a coverage problem, not a speed problem. A simple repeater has to receive each packet once and send it again, on the same channel, so the capacity of the devices behind it drops noticeably. If a part of the house has no signal a repeater makes sense; if there is signal everywhere and the speed is low, the problem is elsewhere.