The Physical layer turns bits into something that can travel: a voltage on copper, a pulse of light in glass, or a change in a radio wave. It has no addresses and no idea what the bits mean. That is Layer 2's job. If Layer 1 fails, every layer above it fails too.
| Bandwidth | how many bits per second the link can carry |
| Attenuation | signal loss over distance (dB); why links have max lengths |
| Noise / SNR | unwanted signal; low SNR = bit errors |
| Latency | fibre ≈ 5 µs per km one way[1] |
| Baud | symbols per second; bits/s = baud × bits per symbol |
Speed comes from two knobs: more symbols per second (baud) and more bits per symbol. Modern links pack 2 bits (PAM4) or many more (QAM) into each symbol, at the cost of needing a cleaner signal.
| Link | Signalling | Per lane | Typical use |
|---|---|---|---|
| 1000BASE-T | PAM5 over 4 copper pairs | 250 Mb/s × 4 | desktops, labs |
| 10GBASE-SR | NRZ, 850 nm light | 10 Gb/s | server to top-of-rack |
| 100GBASE-SR4 | NRZ, 4 fibre lanes | 25 Gb/s | data-centre leaf/spine |
| 400G / 800G (DR4/DR8) | PAM4, single-mode | 100 Gb/s | cloud and AI fabrics |
| 1.6T (8×200G) | PAM4 | 200 Gb/s | newest AI clusters (IEEE 802.3dj, finalising 2026)[3] |
Each medium trades distance, speed, cost and how easy it is to tap. Pick the wrong one and the link is slow or flaky no matter how good your router is.
| Medium | Max speed (typ.) | Distance | Notes |
|---|---|---|---|
| Cat5e copper | 1 Gb/s | 100 m | 100 MHz; all 4 pairs used by 1000BASE-T |
| Cat6 copper | 10 Gb/s (short) | 37–55 m at 10G | 1G to 100 m |
| Cat6A copper | 10 Gb/s | 100 m | minimum category for full-length 10GBASE-T |
| Cat8 copper | 25/40 Gb/s | 30 m | server to top-of-rack only |
| Multimode fibre (OM3/OM4) | 10G-SR | 300 / 400 m | 850 nm, cheap VCSEL lasers [26] |
| Single-mode fibre | 10G-LR … 1.6T | 10 km (LR) to oceans | 1310/1550 nm; amplified for subsea |
| Wi-Fi 7 (802.11be) | multi-gigabit | room / floor | 2.4, 5, 6 GHz; 320 MHz channels, 4096-QAM [2] |
Layer 1 devices move or regenerate signals without reading them. A switch has Layer 1 parts (its ports and optics) but makes Layer 2 decisions.
| Device | What it does | Where you see it |
|---|---|---|
| NIC PHY | chip that converts bits to line signals and back | every laptop, server, phone modem |
| Transceiver (SFP, SFP+, QSFP28, QSFP-DD, OSFP) | hot-pluggable module: electrical ↔ optical | switch and server ports, AI fabrics |
| Repeater / regenerator | boosts or cleans a weak signal | long cables, subsea amplifiers |
| Hub | repeats every bit to every port (one collision domain) | legacy; a sniffer's dream |
| Media converter | copper ↔ fibre | campus and CCTV links |
| Patch panel | passive termination point for structured cabling | network closets |
| Modem / ONT | modulates for DSL, cable or GPON fibre | your home broadband box |
When you open a website hosted abroad, your data almost certainly leaves India as light in a submarine cable, landing mostly in Mumbai and Chennai. Satellites carry only a tiny share.
Mostly accidents: trawler nets and dragging anchors in shallow water. Sharks are a myth today: the ICPC recorded no shark-caused faults in 2007–2014. Repairs need specialised cable ships, so one cut can mean days or weeks of rerouting. New capacity keeps arriving: Meta-led 2Africa landed in Mumbai in March 2025 with more than 100 Tbps [29], and content providers (Google, Meta, Microsoft, Amazon) now use about 75% of international bandwidth [30]. [5]
Training a large model splits work across thousands of GPUs that must constantly swap results. The GPUs are fast; the links between them (copper and optics) decide how fast the whole cluster really is.
"The cloud" is buildings full of servers joined by fibre. Cloud providers design their Layer 1 so that a single fire, flood, power cut or fibre cut does not take your app down, if you use it correctly.
| Provider (AWS, Azure, GCP) | You |
|---|---|
| Data-centre buildings, guards, CCTV, cages | Which regions / AZs you deploy to |
| Cabling, fibre between AZs and regions | Encrypting your data (TLS, KMS) |
| Hardware disposal and media destruction | Multi-AZ design and backups |
AWS "operates, manages and controls the components from the host operating system and virtualization layer down to the physical security of the facilities". [15]
| AWS | Mumbai ap-south-1 (3 AZs, 2016) · Hyderabad ap-south-2 (3 AZs, Nov 2022) |
| Azure | Central India, Pune (3 AZs since Dec 2021) · South India · West India |
| Google Cloud | Mumbai asia-south1 (3 zones) · Delhi asia-south2 (3 zones) |
AWS: "All data flowing across AWS Regions over the AWS global network is automatically encrypted at the physical layer before it leaves AWS secured facilities. All traffic between AZs is encrypted." [16]
Physical attacks skip firewalls entirely. They need access, not exploits, which is why red teams test locks and ports as seriously as code.
| # | Attack | How | Defence |
|---|---|---|---|
| 1 | Rogue hardware in the closet | Raspberry Pi, Bash Bunny or a cheap laptop plugged into the LAN (the DarkVishnya bank attacks); MITRE ATT&CK T1200 [20] | locked racks, badge logs, CCTV, tamper seals; 802.1X / NAC (M1035) |
| 2 | Live desk / lobby port | unused port still patched, or PoE that can power a rogue device (802.3bt: up to 90 W) [25] | shut unused ports, disable PoE where not needed, port security |
| 3 | Wi-Fi jamming | RF noise drowns the channel (denial of service). Illegal in India: up to 3 years and ₹50 lakh fine under Telecom Act 2023 s.42 [22, 23] | wired fallback for critical systems, spectrum monitoring, report to DoT/WPC |
| 4 | Malicious USB drop | infected drive left in the parking lot or lab; curiosity does the rest | block USB storage by policy, user awareness, EDR |
| 5 | Fibre tapping | bend the fibre and a clip-on coupler catches leaking light with ~1 dB loss [21] | OTDR and optical power alarms; encrypt everything (MACsec, IPsec, TLS) |
| 6 | Cable cut | anchors, trawlers, digging, or sabotage; whole regions slow down | route diversity, multiple landing stations, multi-AZ / multi-region design |