Lesson 3: Wi-Fi, Bluetooth, NFC, and RFID

Strong Wi-Fi bars prove one thing reasonably well: the client sees a strong enough radio signal from the access point to report it.

That is useful.

It does not prove the client received valid IP configuration, the access point has a working uplink, the gateway works, DNS works, the provider works, or the application works.

Wireless troubleshooting gets easier when you separate the radio path from everything that happens after association.

Wi-Fi begins with shared radio spectrum

At A+ depth, recognize:

• 2.4 GHz;
• 5 GHz;
• 6 GHz.

They are not interchangeable copies of the same environment.

2.4 GHz

2.4 GHz often reaches farther through obstacles and is supported by a huge number of devices.

That same popularity makes it crowded.

5 GHz

5 GHz commonly provides more channel options and higher-throughput opportunities, but effective range through obstacles is often shorter than 2.4 GHz.

6 GHz

6 GHz adds spectrum for compatible Wi-Fi generations and clients.

The client, access point, regulatory domain, and configuration all have to support it.

A 6 GHz-capable AP does not upgrade an old client by magic.

System process animation

Wi-Fi association before application traffic

A visible SSID does not prove authentication, addressing, routing, or service access.

RestartPreviousPlay sequenceNext

1. 1DiscoverThe client finds a compatible SSID and channel.
2. 2AuthenticateThe client and AP perform the security exchange.
3. 3AssociateThe AP admits the client to the wireless link.
4. 4Obtain configThe client receives valid IP configuration.
5. 5RouteTraffic crosses the gateway.
6. 6Use serviceDNS and application protocols complete.

Technician question: Which stage proves radio reachability but not network access?

Wi-Fi generations describe capabilities, not guaranteed speed

Recognize families such as:

• legacy 802.11a/b/g/n;
• 802.11ac / Wi-Fi 5;
• 802.11ax / Wi-Fi 6 and 6E;
• 802.11be / Wi-Fi 7.

A standard's maximum capability is not the speed a user will automatically receive.

Real performance depends on client capability, AP capability, channel width, interference, distance, obstacles, active clients, upstream capacity, and application behavior.

Marketing numbers are not measurements.

Channels divide shared spectrum

Wi-Fi networks use channels inside a band.

Channel availability is regulated and varies by band, country, and regulatory domain. Do not force an unsupported channel because a forum post says it is faster.

Channel selection also affects how nearby networks share airtime.

A common bad design is:

Wider channel = faster, so make every AP as wide as possible.

That can perform badly in a dense environment because each AP consumes more spectrum.

Channel width is a tradeoff between potential throughput and spectrum reuse.

Worked case: the room gets slow when everyone arrives

Evidence:

wired clients: normal
Wi-Fi association: stable
signal near AP: strong
performance with 3 clients: good
performance with 25 clients: poor
neighboring channels: heavy overlap

What becomes less likely?

A total provider outage. Wired clients are healthy.

What becomes more relevant?

• airtime contention;
• overlapping channels;
• channel width;
• AP capacity;
• client distribution across bands and APs.

The symptom changes with wireless load. That is evidence.

Security mode is part of compatibility

A client can see an SSID and still fail to join because security mode is incompatible, credentials are wrong, enterprise authentication fails, policy blocks the client, or the client does not support the required band or standard.

Visible signal is only the first layer.

Association is not IP connectivity

Consider:

SSID: connected
signal: strong
IPv4: 169.254.18.42
expected network: DHCP on 192.168.40.0/24

The radio association works.

The client did not receive expected IP configuration.

That moves the investigation above the radio layer toward DHCP, VLAN or client policy, or another configuration boundary.

Do not keep moving the laptop closer to the AP. Signal strength is not the failed mechanism.

The AP itself needs an upstream path

An access point can provide a beautiful radio signal while its Ethernet uplink is disconnected.

client
  ))) radio (((
      AP
       X  uplink failure
     switch
       ↓
    gateway

The client may associate because the AP is still powered and transmitting.

But the rest of the network is unreachable.

This is why "connected to Wi-Fi" does not mean "connected to the service I need."

Bluetooth solves a different problem

Bluetooth is commonly used for short-range personal-device connections such as headsets, keyboards, mice, speakers, controllers, and device-to-device functions.

Troubleshooting may involve:

• radio enabled or disabled;
• pairing mode;
• pairing state;
• supported profile or function;
• battery or charge;
• interference;
• OS or application selection.

A device can be paired but not selected as the active microphone or audio output.

"Paired" and "working for this application" are different claims.

NFC is near-field interaction

Near-field communication, or NFC, operates at very short range for workflows such as tap-to-pay, badges, pairing assistance, and near-field identity or access interactions.

Its very short range is part of the design.

Do not treat NFC as a long-range Wi-Fi replacement.

RFID covers a broader identification family

Radio-frequency identification, or RFID, uses tags and readers for identification and tracking workflows.

Different RFID systems operate at different ranges and frequencies depending on design.

NFC is related to RFID technology, but the terms are not interchangeable for every system.

A warehouse RFID reader and a phone's NFC tap workflow solve different practical problems.

Compare the technologies by job

Build a wireless evidence record

Using supplied fictional data, document:

• band;
• Wi-Fi generation and client capability;
• channel;
• channel width;
• regulatory-domain constraint;
• signal level;
• neighboring-channel condition;
• security mode;
• association result;
• IP configuration result;
• AP uplink state;
• one limitation of the current evidence.

Then compare one Bluetooth, NFC, and RFID scenario by purpose rather than acronym.

Before you move on

Wireless has layers too:

radio visible
  ↓
association / authentication
  ↓
IP configuration
  ↓
AP uplink
  ↓
gateway / services

Strong signal proves only the beginning of that chain.

Next we put the network services together into one fictional environment and watch what happens when one dependency fails.