Go Setup

08/17/2026

Understanding network diagnostics starts with knowing what each tool and protocol actually does.

DNS translates a domain name into an IP address.

ICMP carries network status and error messages. Ping uses ICMP Echo Request and Echo Reply to test basic IP connectivity.

Traceroute discovers Layer 3 hops by sending packets with increasing TTL values. Each router decreases TTL by one. When TTL reaches zero, the router discards the packet and returns ICMP Time Exceeded.

When reading ping results, focus on:

• Latency — round-trip time
• Packet loss — 0% is the target
• Stability — compare minimum, maximum and average

Remember:

• ICMP does not use TCP or UDP ports
• TTL is not a speed or quality score
• A successful ping confirms IP connectivity, not application availability

Quick troubleshooting order:

1. Ping the default gateway
2. Ping a public IP
3. Ping a domain name

Which test would you run first if a computer can reach its gateway but cannot resolve cisco.com?

Save this post for review and follow GoSetup for more practical networking notes.

08/16/2026

Continuing my CCNA Study Notes series with one of the most important networking concepts: the OSI Model.

The OSI Model explains how data moves through a network in seven layers.

Quick layer map:

• Layer 7 — Application services
• Layer 6 — Formatting, encryption and compression
• Layer 5 — Session management
• Layer 4 — TCP, UDP and port numbers
• Layer 3 — IP addressing and routing
• Layer 2 — MAC addresses, frames and switching
• Layer 1 — Signals, cables, fiber and radio

Encapsulation:

Data → Segment → Packet → Frame → Bits

Troubleshooting tip: start at Layer 1 and work your way up.

Slide 5 shows a simplified practical troubleshooting flow using Layers 1, 2, 3, 4 and 7. Layers 5 and 6 are not missing from the OSI Model. In everyday troubleshooting, session, encryption, certificate and data-format issues are often investigated as part of upper-layer or application troubleshooting.

No link light on a switch port—which OSI layer should you check first?

Save this post for review and follow GoSetup for more practical networking notes.

08/15/2026

Starting my CCNA Study Notes series with the foundation: Computer Network Basics.

A network connects devices so they can share data and resources.

Key points:

• A switch connects devices inside a LAN
• A router connects different IP networks
• An access point provides wireless network access
• A firewall allows or blocks traffic based on security rules
• Wi-Fi and the Internet are not the same thing

Quick memory rule:

MAC → Switch
IP → Router

Which device connects different IP networks?

Save this post for review and follow GOSETUP for more practical networking notes.

05/14/2026

The process of building a network at a new workplace using equipment found in storage: UniFi, Netgear, Eero, and TP-Link Omada.

The goal is to provide stable Wi-Fi coverage throughout the building, separate Staff and Guest networks using VLANs, configure guest access, and prepare internet failover between Xfinity and AT&T.

Even equipment from different brands can be combined into one stable infrastructure with the right network design and configuration.

VLAN ITInfrastructure GoSetup

04/03/2026

Day 1 — installation & testing ⚙️

Started a new UniFi setup today.

The system is already up and running — now moving to the final stage: wall mount and clean cable management.

Why this type of setup?

Because a proper network is not just about speed — it’s about structure.

• Network segmentation
Main devices, IoT, and guest access are separated into different networks — improving security and protecting the system.

• Load optimization
Traffic is managed and prioritized — so video calls, work devices, and streaming stay stable even under load.

• Stability over “raw speed”
Most home issues are not about internet speed, but about how the network is designed.

The goal is simple — stable Wi-Fi everywhere, without drops, buffering, or random disconnects.

Final result coming next 👌

This is how a modern home network should be designed — not just installed.

📩 Text me or submit a request online — easier for me to respond while on the job.

03/28/2026

Starlink backup internet installation completed and integrated into a UniFi network system.

Designed for homes where internet simply needs to work — for remote work, video calls, security systems, and daily use.

This setup includes:
• Primary provider (cable)
• Backup connection (Starlink)
• Automatic failover between both lines

If one connection goes down, the system switches automatically — no interruptions, no manual action.

A reliable network is something most people only think about when it fails.
This setup is built so that doesn’t happen.

If you’ve been dealing with unstable internet or just want peace of mind — feel free to reach out for a quick assessment.

02/22/2026

🧠 Home Lab in Action

Upgrading a standard light switch → into a smart one.

Old mechanical switch.
No automation. No load monitoring.

Installing Shelly Plus 1PM inside a standard electrical box
and turning a simple lighting point into part of a smart home system.

What changes:

• smartphone control
• real-time power monitoring (W / V)
• automation & scheduling
• remote access
• physical switch still works

No fancy touch panels.
No wall demolition.
Just correct wiring and clean integration.

Next step — integration with Siri or Alexa,
so a regular light becomes part of a full ecosystem.

Smart homes don’t start with expensive systems.
They start with smart engineering.

⸻







ElectricalUpgrade

02/21/2026

Distributed rack-based architecture.
Basement and attic nodes connected via backbone links.

Model:
Core — Distribution — Access

Core — routing & aggregation.
Distribution — inter-rack backbone.
Access — PoE for APs and cameras.

In this build:

• Multiple rack nodes
• Zone-based patch panels
• VLAN segmentation
• PoE budget planning
• Port reserve

Topology matters more than hardware quantity.

02/20/2026

02/18/2026

An upgrade isn’t about replacing hardware. It’s about control.

Step by step, rebuilding the system the right way.
No shortcuts. No temporary fixes. No chaos behind the rack.

What’s happening now:
• removing outdated wiring logic
• cleaning and restructuring the rack
• optimizing power distribution
• preparing the infrastructure for future load

When a network is built correctly —
it just works.
No random drops. No surprises. No stress at the worst possible time.

Every phase builds the foundation for the next one.
That’s how stable systems are created.

For upgrades or rack rebuilds, please submit an online request or send a text message — I’m often on-site and unable to take calls.

San Francisco & Bay Area.

BayAreaTech