01 / THE ROLE
In this lab.
phpIPAM is a self-hosted web application with a MySQL database. Its deployment includes the web interface and a scheduled-task component. It records network information; it is not the device that routes packets or enforces firewall policy.
02 / THE CONNECTIONS
Follow the flow.
- STEP 01Network documentation
- STEP 02phpIPAM web & tasks
- STEP 03MySQL
- STEP 04Address inventory
03 / How it works
How it works.
The application stores structured information about address space and its use. Its scheduled tasks and web interface have different responsibilities. When it sits behind an HTTPS proxy, forwarded request information matters so that generated links and redirects remain consistent with the user-facing URL.
04 / Persistent data & recovery
Persistent data & recovery.
The database is the main unique state; relevant application configuration and any persistent application files must be considered with it. Network contents, API access material and exports are private and are not reproduced here.
05 / How to check it
How to check it.
Check the intended HTTPS response, application identity, redirects and authenticated application behaviour where appropriate. A login page alone does not validate inventory completeness or scheduled tasks. Record accuracy needs reconciliation against the actual infrastructure.
06 / Decisions & limits
Decisions & limits.
An address inventory is useful only when it is maintained. The lab keeps observed state distinct from documentation instead of assuming that a database entry proves an address is currently in use.