- Conntrack activeHosts throws netfilter query error on MIPS64 SF
- Check chains priority and ensure NetTrust Chain has high priority in the related table
- (Depends on namespace filtering and Nettrust follower agents & K8 network policies features) Kubernetes operator. Allow nettrust to be deployed and managed by a K8 operator. Nettrust can use coredns or other dns authorizers to filter the outbound traffic within the nodes
- Nettrust follower agent. In this feature Nettrust can run as a follower. While in follower mode, it will query a master agent or operator in order: fetch the configuration, use a shared authorized map.
- Nettrust K8 Network Policies. Allow Nettrust to filter traffic using K8 Network policies instead of nftables. In this mode Nettrust will not need elevated privileges
- When filtering forward chain, allow Nettrust to whitelist hosts by source network. This feature can allow the gateway where nettrust is running to allow connections to 0.0.0.0/0 that are sourced from a subnet/s and deny connections that have not been authorized for all other subnets
- Cloud provider plugin
- Add option for TLS Client authendication
- Add eBPF filtering to allow NetTrust block packets before they enter the Kenrel network stack
- Add network namespace filtering option. This can be achieved by making the firewall backend an array and loop over each time a command is executed to handle multipe namespaces
- DNS listen strikes on many invalid/block requests
- Handle IPv6 also
- Add support for reverse queries, essentially whitelisting IPs if the DNS Authorizer returns a domain back to NetTrust
- Add metrics capabilities to monitor NetTrust
- Add network statistics (e.g. how many times a host was queried) to allow alerts/notifications on certain events
- Add DNSSec
- Add IPTables Support (iptables-legacy, iptables-nft)
- Add option to use a KV store for keeping host tracking information
- Use conntrack to check and react on connections that open and are not part of NetTrust whitelisted hosts
- Conntrack Hosts & ttl metrics
- Add option to handle A/AAA zones instead of forwarding all requests
- Add option to watch for /etc/resolv.conf changes and revert back to NetTrust listening address
- Add DNS Forward loadbalance option (to allow usage of more than 1 DNS server)
- Add debug logs