- Blacklisted scanners
- —
- WAN 24h
- ...
- Active connections
- —
Infrastructure
Homelab
I maintain a homelab to support decentralized networks, personal infrastructure, and continuous learning. Below is the real-time status of my public services.
Live · via API
Everything described here runs on hardware I own and pay for, on a domestic fibre line in Valencia, Spain — not on a managed platform. The router is a MikroTik RB5009 terminating the ISP link over PPPoE with a delegated IPv6 prefix; the services sit behind it on mini PCs and a NAS, with two VPS for the parts that need to be reachable when the house is not.
The self-hosted services include a Mastodon instance, a Matrix homeserver, an AT Protocol PDS, file sync, media streaming and monitoring. Four Tor nodes run alongside them: two bridges speaking obfs4 and WebTunnel, one in Valencia and one in Alicante, and two middle relays on IONOS VPS instances, one in London and one in Madrid.
Security is one pipeline rather than a set of unrelated rules. A honeypot on the router turns a scanner's first packet into an address-list entry, nginx tarpits and pattern matches on the web tier, both feed CrowdSec, and CrowdSec drives bouncers back on the router and the reverse proxy. The counters above are what that pipeline actually stopped.
… / 3
services online
9
monitored nodes · 5 infra · 4 Tor
—
requests · 24h
—
WAN traffic · 24h
Edge Defense
router + nginxCrowdSec acts as a WAF: it analyses NGINX patterns and, together with the router honeypot, decides which IPs to block. Decisions fan out to every bouncer — NGINX, Cloudflare and the router via my cs-RouterOS-bouncer.
MikroTik honeypot + NGINX patterns → CrowdSec · WAF → bouncers (NGINX / router / Cloudflare)
- CrowdSec · blocked IPs
- —
- Requests Received (24h)
- —
- Nginx Bans
- —
Public services
Mastodon
A decentralized social network server. Part of the Fediverse.
Matrix
Secure, decentralized communication. My Server: matrix.jmrp.io
AT Protocol
My self-hosted Personal Data Server on the AT Protocol network — the identity and data behind @jmrp.io on Bluesky.
Tor Network · 4 nodes
Tor Bridge (ES0)
Pluggable transport bridge helping censored users access the Tor network from Valencia. Running obfs4 and WebTunnel.
Clients (24h)
Tor Bridge (ES1)
Pluggable transport bridge helping censored users access the Tor network from Alicante. Running obfs4 and WebTunnel.
Clients (24h)
Tor Relay (UK)
Middle relay forwarding encrypted traffic within the Tor network from United Kingdom.
Peers (24h)
Tor Relay (ES)
Middle relay forwarding encrypted traffic within the Tor network from Madrid.
Peers (24h)
Infrastructure · 5 nodes
live load · via APINGINX Edge
Reverse proxy · firewall
Matrix Homeserver
Synapse
Mastodon
Fediverse instance
TrueNAS
ZFS storage
Edge Router
MikroTik · CrowdSec