neilphan98/hearth-http-server-tls repository overview

⁠HEARTH HTTPS Server

TLS nginx web server for the Internet/edge zone (external-facing web app).

Real-device analogue: A public-facing HTTPS web server (an Internet/DMZ site).

Protocol / ports: HTTP/HTTPS (TLS) via nginx.

⁠What it does / how it works

nginx serving the Internet-zone site over TLS; used as the external web target reached across the edge router, so IT-side flows cross a realistic perimeter.

⁠Functions

• TLS-terminated web serving
• External/Internet-zone endpoint

⁠How to use

curl -k https://<ip>/ from an IT/Internet host. Default address is the Internet zone (203.0.113.x).

⁠Use in GNS3

• Import the matching .gns3a (File > Import appliance), or docker pull neilphan98/hearth-http-server-tls:1.1.
• Drag onto your topology, wire to a switch/hub, start. Console: telnet.
• Adapters: 1. Category: guest.

IPv4 device: leave MQQ1_IP empty to auto-assign a unique IP (zero-config), or set a fixed address. Zone via HEARTH_OCTET (5 corp / 6 ot / 8 security).

⁠Default environment (per node)

MQQ1_IP=203.0.113.200
MQQ1_PREFIX=24
MQQ1_GW=203.0.113.1

Current release: 1.1 (docker pull neilphan98/hearth-http-server-tls:1.1)

Part of the HEARTH Tower commercial-building IoT/OT security testbed. Image tags are immutable per release (1.0, 1.1, ...), so updating the device list never changes nodes you already placed. See the HEARTH bundle for all devices + guides.