These are necessary conditions to use DPF in your organization. If you found that DPF is not a right system for your situation, please visit Other Solutions and see if we have a better system for you.
- Outbound connections from the network behind a firewall or NAT must be allowed. Note that this condition is true for most private networks and most firewalls are factory-configured this way.
- Firewall/NAT must be Linux netfilter based.
- So far, DPF library has been tested in the platforms listed below. More machines and platforms will be added later.
- Redhat 9 machines.
Though I tried hard to make DPF versatile, DPF does have restrictions and room for improvements.
- No multithread
- No support for nested networks
- One well-known service per private network
Currently DPF is not thread-safe.
DPF does not support nested networks. To support nested networks, DPF inagents must be cascaded together.
(Server) sockets inside the private network lease addresses from their DPF inagent. Because one inagent can rent an address to only one socket, only one instance of a well-known service is possible per inagent.