4+ Years · AWS & Data Center · Systems Administration · Weekend Developer
$ cat about.txtHi, I’m Rahul Singh Parmar—a Team Lead Network Engineer in Mumbai who builds, secures, and operates the systems behind reliable services. During the week I work across networks, infrastructure, security, Windows/Linux administration, monitoring, and data center operations. On weekends I turn operational problems into small developer tools.
- Building Home Server Heartbeat and Infrastructure Maintenance Page
- Daily work: Cisco · Brocade · Sophos · Windows Server · Linux · PRTG · Domotz
- Current path: AWS networking · PowerShell/Python automation · security engineering
- Homelab: Docker · Nextcloud · Jellyfin · Mattermost · self-hosting
- Field notes: networking, security, hardware, and programming
- Fun fact: I enjoy debugging the entire path—from a packet on the wire to the code serving the response.
daily drivers · Cisco · Sophos · Windows Server · Active Directory · Linux · PowerShell · PRTG · Docker · GitHub
open the full infrastructure + development stack
Networking: Cisco · Brocade · VLAN · DHCP · DNS · VPN · routing · switching
Security: Sophos Firewall · Sophos Endpoint · OpenVAS · Nessus · vulnerability assessment
Systems: Windows Server · Active Directory · Linux · virtualization · data center operations
Cloud: AWS · EC2 · IAM · VPC · cloud networking
Automation & development: PowerShell · Python · Java · JavaScript · SQL · Git · GitHub · Docker
Left: infrastructure focus · Right: self-assessed development expertise overlaid with live public GitHub evidence
The lab is where I practice infrastructure ownership end to end: networking, access control, storage, observability, patching, backups, failure handling, and documentation someone else can follow. The public surface runs on Glance and presents selected operational context; addresses, credentials, and control actions are deliberately kept out of this README.
Open the public homelab dashboard →
Start the incident simulation · approximately 60 seconds
INC-047 · Public users report a timeout.
Monitoring says the Docker host and application are healthy.
DNS was changed shortly before the alert.
Choose your first move:
A · Restart every container
Not yet. The application is healthy, and a restart destroys useful evidence without testing the failed path.
B · Expose the application port directly
Unsafe. This bypasses segmentation and TLS while leaving the original edge-path failure unexplained.
C · Trace DNS → TLS → reverse proxy → container
Correct. Compare the public DNS answer with the intended edge address, then test the TLS virtual host and reverse-proxy upstream independently.
Reveal the root cause
The DNS record still points to the retired edge address. Restore the intended record, verify propagation, confirm the certificate and host header, then document the rollback.
flag{trace_the_whole_path}
This game uses native GitHub disclosure controls—no JavaScript, tracking, or external runtime.
Generated locally from public GitHub data—no shared public stats service in the critical path.
|
|
|
|
Cards are regenerated from GitHub metadata; stars, forks, and primary language stay current.
C Programming · What is JAVA · Programming · Web Development
browse all 8 published notes
Hardware ·
Internet ·
Multimedia ·
Security
Web Development ·
Programming ·
What is JAVA ·
C Programming
RSS-backed and refreshed every 12 hours · cached repository asset remains visible if Hashnode is unavailable
Live Spotify activity · current track while listening, offline state when playback stops
I’m growing toward infrastructure and cloud roles where I can combine network engineering, systems, security, AWS, automation, and technical leadership. I am especially interested in teams that value engineers who can operate a service, understand its failure modes, and build the tooling that makes it more reliable.
- Learning path: VPC · EC2 · IAM · cloud networking · infrastructure security
- Public proof: Microsoft Learn achievements
- Credentials policy: verified certifications are added only with an issuer-hosted credential link
LinkedIn · GitHub · Portfolio · Hashnode · X / Twitter · Microsoft Learn
decode the signal
01100001 01110101 01110100 01101111 01101101 01100001 01110100 01100101 → automate
Each eight-bit binary group is an ASCII character. It turns an ordinary footer into a small developer interaction while reinforcing the profile’s automation theme.
Open to conversations about networks, infrastructure, cloud, security, homelabs, technical writing, and useful weekend builds.