Skip to main content

packet-switching X.25

 X.25 is a packet-switching protocol suite developed by the ITU-T in the 1970s for wide area networking over unreliable communication links. 

It operates at the first three layers of the OSI model and was widely used for connecting remote terminals and computers over public data networks, particularly before reliable digital infrastructure became commonplace.

Architecture and Operation: X.25 uses virtual circuits to establish connections between endpoints. 

It employs three protocol layers: X.25 Packet Layer Protocol (Layer 3), LAPB (Link Access Procedure Balanced) at Layer 2, and typically operates over serial interfaces at Layer 1. 

The protocol provides both Switched Virtual Circuits (SVCs) that are established on-demand and Permanent Virtual Circuits (PVCs) that are pre-configured.

Key Features:

  • Built-in error detection and correction at multiple layers
  • Flow control to prevent buffer overflow
  • Virtual circuit multiplexing over single physical links
  • Store-and-forward packet switching
  • Comprehensive error recovery mechanisms

Cisco Configuration Example:

Router(config)# interface serial 0/0
Router(config-if)# encapsulation x25
Router(config-if)# x25 address 12345678
Router(config-if)# x25 map ip 192.168.1.2 23456789 broadcast
Router(config-if)# x25 htc 16
Router(config-if)# x25 nvc 2
Router(config-if)# ip address 192.168.1.1 255.255.255.0

This configuration sets up X.25 encapsulation with local address 12345678, maps remote IP 192.168.1.2 to X.25 address 23456789, sets highest two-way channel to 16, and allows 2 virtual circuits.

Legacy Applications: X.25 was extensively used for:

  • Bank ATM networks
  • Point-of-sale terminals
  • Airline reservation systems
  • Remote terminal access

Limitations: Despite its reliability, X.25 suffered from high latency due to extensive error checking at each hop, limited bandwidth, and complex configuration requirements.

Modern Status: X.25 has been largely replaced by Frame Relay, MPLS, and internet-based VPNs, though some legacy systems still operate in developing countries where reliable infrastructure remains challenging.

Labels:

Popular posts from this blog

How to Check if Someone is Connected to Your Machine in Linux

Picture this: you glance at your system monitor and notice your CPU is humming along even though you're not running anything demanding. Or maybe your internet feels sluggish for no obvious reason. A small, uneasy thought creeps in — is someone else on my machine right now? For Linux users, this isn't something you have to wonder about. Linux ships with a powerful set of built-in tools that let you see exactly who's connected, who's logged in, and what your network is doing at any given moment. You don't need to be a security expert to use them — you just need to know where to look. This guide walks you through the practical, no-nonsense steps to check for unauthorized connections on your Linux system, with real commands you can run right now. Why Monitoring Network Connections Matters Every device on a network — including your own Linux machine — communicates using an IP address. When another device or user connects to your system, that connection shows up as a trac...
Read more

How to Set Up a Linux Web Server and Host an HTML Page Easily

Setting up a web server on Linux means spending a fair amount of time in the terminal — Linux leans heavily on the command line rather than clicking through menus, so you'll be typing out instructions more often than not.  If you're new to this, it can feel a little intimidating at first, but the good news is you don't need to become a Linux wizard overnight. A handful of core commands will get you surprisingly far. A few you'll lean on constantly: cd — move between directories ls — see what's in the current directory mkdir — create a new folder nano or vim — edit files right there in the terminal sudo — run something with administrator privileges Get comfortable with these and you'll be able to navigate around, tweak configuration files, and install software without much trouble. You don't need to memorize everything — you just need to be confident enough to follow along with clear instructions, which is exactly what this guide aims to give you....
Read more

Linux Network Troubleshooting

If you've spent any time as a sysadmin — or honestly, just as someone who's had to fix their own home network at 11pm — you know that connectivity issues are one of the most common headaches out there. The good news is that a handful of core tools and a methodical approach can take you from "why isn't this working" to a root cause pretty quickly.  This guide walks through the essentials: configuring interfaces, managing routes, and diagnosing problems when things go sideways. Configuring Network Interfaces Your network interfaces are the actual bridge between your machine and the outside world, so getting them configured correctly is step one for any kind of reliable connectivity. Doing It Manually ifconfig is the old-school, tried-and-true tool for this on Unix-like systems. To see everything currently configured, run: ifconfig -a If you need to manually set up a specific interface — assigning an IP, a netmask, and bringing it online — it looks like this: ifconf...
Read more