Subnets, Routing & Inter-Office Connectivity
Connected two branch office LANs through two routers using distinct subnets and bidirectional static routes for seamless inter-office communication.
Two offices on separate LANs cannot reach each other’s resources without routed connectivity between them.
Foundational networking delivered: addressed, routed, and verified connectivity both ways.
Each office on its own subnet with no overlap.
Each router knows the path to the remote LAN.
Two-site routed topology: distinct subnets per office, static routes on both routers forming the inter-office path.
Branch A LAN (Subnet 1) ──> Router A ══ Static Routes ══ Router B ──> Branch B LAN (Subnet 2)
branch-lan/ ├── addressing.md # Subnet plan ├── router-a.cfg # Router A routes └── router-b.cfg # Router B routes
Run active operations audits utilizing the custom sandbox telemetry receiver widget below.
Small fixed topology with no expected churn.
Static routes
Accepted manual maintenance for simplicity at this scale.
Migrate to OSPF when a third site or redundant links arrive.
Routed connectivity exposes each LAN to the other site.
One-directional connectivity after initial configuration.
Root Cause:Return route missing on one router — classic asymmetric routing oversight.
Traced pings hop by hop and found replies had no path back.
Added the missing reverse static route and re-verified both directions.
None — verification caught it before handover.
Always verify both directions; routing is a two-way contract.
Draw the addressing plan before touching any device.
Static routing is the right default until scale says otherwise.
Documented addressing saves the next engineer hours.
I would add link redundancy and OSPF as the follow-up exercise.
Audit raw repository script configurations directly inside the active terminal workspace.
Keep exploring
A routing engine simulator analyzing OSPF vs EIGRP performance under varying traffic levels and Access Control List (ACL) constraints, complete with interactive configuration widgets and raw data export.
ArchitectureConfig Inputs → Interpolation Engine → Telemetry Panels
A prototype mapping network telemetry streams to visualize delay, jitter, and packet drop trends.
ArchitectureTrigger → Telemetry Calculator → Dashboard
A distributed system architecture and orchestrator that coordinates local AI agents across multiple devices with real-time state synchronization.
ArchitectureDashboard → Master Hub (Raft) → Device Nodes → State Sync