ALASKA BACKSCATTER

the blog

2026-10-22 Understanding Network Models

Lately I've been thinking about redefining my hobby as not being amateur radio, home networking, or hacking, but as "amateur network engineering." After all, that really is what I like doing. I like playing with various aspects of networking tools and stacks and learning about how they work and mix together, whether that's home networking or long distance HF radio.

As I've been diving into various digital modes and networks available for amateur radio, I've found it helpful to understand the network models that exist. These models are helpful in understanding where the a part of a system operates, and you'll often see it used when describing how a system operates.

The OSI Model

This model is based around X.25 networking, the network stack that amateur packet radio (AX.25) is based off of. It's has the following layers:

  1. Physical - The hardware and (generally digital) signals.
  2. Data Link - Data transfer is controlled between two nodes.
  3. Network - How data transfer is controlled across nodes in a network.
  4. Transport - How packaged for transport.
  5. Session - How connections are established and terminated between nodes in a network.
  6. Presentation - How the data at the end destination is decoded and displayed.
  7. Application - How the user interacts with the data.

Now, this is an older model for an older network stack. It's still referenced because a lot of people learned about it when learning larger networks were just starting to take off. However, these days we use the internet protocol suite (AKA TCP/IP) for almost all of our networking, and it has a slightly different model.

The Internet Protocol Model

The IP model is a little different in that it combines a few layers from the OSI model and renames some.

  1. Physical - The hardware and signals.
  2. Data Link - Data transfer is controlled between two nodes.
  3. Internet - How the network is organized, devices are addresses, and packets are routed
  4. Transport - How data is packaged for transport and delivered across the network.
  5. Application - How the user interacts with the data.

You'll notice the session layer has been removed, since that is now controlled on the transport layer, and the presentation layer has been removed since that is now controlled on the application layer. The network layer has been renames the internet layer. So, now you've been introduced to the two mode popular models, I think it might be helpful to look at a few examples.

Examples

One thing I want to make clear before we start, these examples are not definitive, and I am still new to all the ideas I've presented so far. This means that I might have some things wrong, there might be things mixed up, and there might be a better way to explain these examples. That being said, I think these can be helpful is getting a basic understanding of how a network model applies to various networks.

Example #1: Viewing a Website

When you go to a website, the following is usually involved in the exchange:

  1. Physical signals are sent over WiFi, ethernet, coaxial cable, microwave radios, and/or fiber optics.
  2. At each change of the physical layer, the exchange is controlled in various ways to ensure no data is lost.
  3. The signals are routed from device to device on the internet layer. Each device has a unique IP address.
  4. Your device is connected to a server somewhere on the internet via TCP, your request is resolved, and the server sends you the requested data: the website!
  5. Finally, the data is decrypted (if using HTTPS), and displayed (HTTP) in your web browser.

Example #2: Packet Radio BBS

A bulletin-board system is an old method to have a basic quasi website/forum service on X.25 style networks. When you connect to an amateur radio station running a BBS, the following occurs:

  1. Your radio transmits and receives FSK modulated signals.
  2. Your radio and the receiving radio establish a connection and work out how to transfer data.
  3. If the BBS is not on that station, the receiving radio can route your traffic to the BBS station.
  4. Your data is packaged in AX.25 packets which include information about where the packet came from, where it should go, the payload, and a check sum to ensure the packet wasn't corrupted.
  5. A connection is established with the BBS station.
  6. The payload data is transformed from binary to ASCII text to be formatted by the application.
  7. Finally, the application layer, usually a terminal, where you can view the data sent by the BBS server and type in your own information to send to the server.

As you might notice, all the layers of the OSI model were used in this.

Example #3: Meshtastic Message

Meshtastic actually uses it's own network stack that is not OSI or IP based, it's an interesting example of where models are helpful, but they're not a list of boxes to check. When you send a message over Meshtastic, this is what happens:

  1. Your message is exchanged with your mesh node that then transmits signals via LoRa. LoRa manages packet framing an error detection; but Meshtastic doesn't have an OSI style data link layer (meaning a device only expects to exchange a packet and receive an acknowledgement). This limits the amount of data that can be transferred.
  2. The message is transferred across the network according to a fancy flood routing algorithm.
  3. The message is then transferred from the destination node to the destination user's device where is is decoded and displayed in the app.

As you can see, this is actually a very basic network, and in some way's that's a good thing.

Conclusion

Every network stack is quite unique, and that uniqueness breeds both function and complexity. Network models can be helpful in understanding where a function in that network lives and what its purpose is. When developing networks these models can be helpful to keep in mind, especially as you try to describe your network to others, but they are not a checklist; not every network needs every layer.

Given the variety and diaspora of networks, it's a lot to take in; especially as someone who experiments with them mostly for fun. Especially complicated is how we make these network work together cohesively to meet our goals, whether that's emergency communications, work, or just plain fun. For more discussion on networking I highly recommend the article "Rethinking Packet Networks in Amateur Radio" by Vlastimil. He share's a lot of really good and interesting thoughts about this topic.

Happy networking and 73!