fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
1.4 KiB
1.4 KiB
UniFi API firewall/ACL/DPI query report
Generated: 2026-02-06T01:39:50-08:00 Site ID: 88f7af54-98f8-306a-a1c7-c9349722b1f6 Base: https://192.168.0.1/proxy/network/integration/v1
Summary
- ACL rules: 0 (user-defined L3/L4 rules)
- Firewall zones: 6
- Traffic matching lists: 0
- DPI categories: 35
HTTP POST (RPC 405) and this API
The Official UniFi Network API exposes:
- ACL rules: L3/L4 only (protocol TCP/UDP, ports, source/dest). No HTTP method (GET vs POST).
- Firewall zones: Grouping of networks (Internal, External, etc.). No method filtering.
- Traffic matching lists: Port/IP lists. No HTTP method.
- DPI categories: Application categories for app-based blocking (e.g. "Web services"). Not method-specific.
Conclusion: The 405 Method Not Allowed for RPC POST is not configurable or visible via this API. It is likely enforced by the device's port-forward/NAT layer or a built-in proxy that does not expose HTTP-method settings in the API. To fix RPC 405: allow POST on the edge (UDM Pro UI / firmware) or use Cloudflare Tunnel for RPC (see docs/05-network/E2E_RPC_EDGE_LIMITATION.md).
Output files
acl-rules.json- ACL rules (empty if no custom rules)firewall-zones.json- Zone definitionstraffic-matching-lists.json- Port/IP listsdpi-categories.json- DPI app categorieswans.json- WAN interfaces