About Yasin Engin

I study networks by building small, documented systems.

I am a Computer Engineering student at Ondokuz Mayis University. My current work combines network automation, Go service prototypes, and laboratory experiments with Delay-Tolerant Networking and satellite-network emulation.

Explore my engineering focus GitHub LinkedIn
Yasin Engin
Implementedlinked code or configuration exists
Executedretained output from a run exists
Checkedcompared with an explicit expectation
Plannedno execution result is claimed

Current Experiment Model

From orbital inputs to emulated links and ION configuration

The diagram uses the project's controlled eight-satellite circular-reference inputs. It shows the two synchronized outputs: NetSatBench epoch events for the IP/VXLAN/NetEm path and ION contact/range information for BPv7 forwarding over the UDP-based convergence-layer adapter.

Orbit radius, a
7578.137 km
Kepler period, T
6565.301 s
Phase spacing, Δu
45°
Adjacent ISL OWLT
19.347 ms
Calibrated circular-reference model; time is accelerated for visualization. The moving marker is shown only while both displayed contacts form a path; otherwise it waits at reference ground A. This is a conceptual view, not live telemetry, CGR proof, or an operational OneWeb/Starlink result.

Study Path

From network fundamentals to research-oriented experiments

I began with routing, switching, and troubleshooting labs. I now use those foundations to study programmable infrastructure and distributed software. The common questions are practical: what state exists, who changes it, what happens when communication is interrupted, and which artifact supports a result?

I try to document each project with its assumptions, configuration, test procedure, and limits. A repository shows what was implemented; retained logs show what was executed; a result is described as checked only when it was compared with an explicit expectation or reference.

  1. Network foundationsRouting, switching, wireless, security, and troubleshooting exercises developed through CCNA/CCNP study.
  2. Network automationA Nokia SR Linux and Containerlab environment with Ansible roles and state-verification tasks.
  3. Go prototypesSmall services used to study APIs, messaging, replication, persistence, and observability.
  4. DTN and satellite emulationION-DTN and NetSatBench work on contact schedules, OWLT, link-rate inputs, and timing guards.
  5. Technical communicationTurkish videos, notes, and setup guides accompanying the lab work.

Selected Work

What the linked material currently supports

Programmable Networks

Topology files, Ansible roles, and verification tasks for a documented SR Linux and Containerlab environment.

Open the case study

Go Systems

Learning-oriented prototypes for a network inventory API, replicated storage, and message-driven services. They are not presented as production deployments.

See the system work

DTN and NetSatBench

Configuration generators, contact-plan work, physical and link calculations, and retained outputs from selected laboratory runs. Later constellation scenarios require separate revalidation.

Explore the study area

Teaching in Public

Turkish videos and notes covering network foundations, laboratory workflows, and selected software topics.

Open the video library

Current Questions

What I am trying to understand better

Evidence boundary: implemented means linked code or configuration exists; executed means retained run output exists; checked means comparison with an explicit expectation; planned means no result is claimed.

Beyond the Repository

Knowledge, compassion, and action

My longer-term direction is broader than collecting technologies. I want knowledge to become something shareable, technical work to remain connected to people, and learning to turn into useful action. That is why this portfolio includes open labs and engineering notes, but also community work and a field journal from Torino.