Hi, I’m /koh-koo/

Bring people into a trivia game without asking everyone to install an app. The TV provides the shared display; phones provide buzzer and typed-answer inputs.

The relay coordinates players, rounds, answers, and scores. The project includes a browser TV preview so gameplay can be checked separately from the Roku application.

I deployed the game on an Ubuntu VM in my Proxmox environment and worked through installation, SSH file transfers, service updates, and connectivity checks.

Phones communicate with the relay over WebSockets. The Roku implementation uses background HTTP polling, keeping network requests separate from its display logic. Tailscale Funnel provides the public route to the homelab service.

One deployment issue made the distinction between a healthy application and a reachable service very clear. The local health endpoint responded successfully, but phones could not reach the public address.

Checking the local relay, Funnel configuration, and public DNS separately narrowed the problem: the public hostname returned NXDOMAIN while private access still worked. Public DNS resolution returned after restarting Tailscale and re-enabling Funnel.

The lesson: test each layer independently. A running process and a configured proxy are useful signals, but neither proves that a player can reach the game.

• Expanded the question pack to 120 questions, with repeat prevention within a game.
• Added a phone-based Next Question control after the reveal.
• Introduced winner celebrations, including confirmed confetti on the physical Roku TV.

Development was AI-assisted. My work included defining the experience, requesting changes, deploying updates, testing with devices, and working through infrastructure and connection problems.

The environment began with physical server setup, Cat6 cabling, and network connections. Proxmox VE provides the platform for Ubuntu Server virtual machines and LXC containers.

The lab includes storage pools, snapshots, and automated backups. These provide practical experience with managing virtual workloads and maintaining recovery options.

Linux network bridges and static IP addressing connect the workloads. OpenSSH and web interfaces provide remote management.

Couch Trivia Live runs on an Ubuntu VM in this homelab. That deployment connects virtualization practice to a real application, including service updates and connectivity troubleshooting.

The lab uses one Layer 3 core switch, two access switches, two servers, and an administrative PC. Devices are segmented into three VLANs.

Cisco IOS configuration covers access ports, trunk links, switch virtual interfaces (SVIs), and inter-VLAN routing. The core provides routing between the segmented networks.

Ping and HTTP tests check connectivity. Diagnostic commands include show vlan brief, show interfaces trunk, and show ip route, alongside Packet Tracer Simulation Mode.

This is a simulated network lab. Its focus is configuration and troubleshooting; it does not represent a production data centre deployment.

The tool processes PCAP captures and network logs. Scapy and Pandas form part of the Python analysis workflow.

The project flags anomalous activity such as port scans and denial-of-service attempts, turning traffic data into findings that can be investigated.

A flag is a starting point for investigation. Capture context and traffic patterns matter when interpreting whether activity is unexpected.

This overview reflects the project described in my résumé. Detection thresholds, model details, benchmark results, and sample findings are not documented here, so no accuracy or performance claims are made.

The survey examines MetaRoCE in the context of the networking demands of AI workloads and the limitations of RoCEv2.

Topics include Priority Flow Control (PFC), Equal-Cost Multipath (ECMP), and congestion control. The analysis also compares MetaRoCE with MRC and Ultra Ethernet.

I co-authored the survey and critical analysis at Clayton State University. This project represents research and technical synthesis, rather than an implementation of the protocol.

The paper itself is not currently attached to this portfolio. Contact me to discuss the research and my contribution.