Native nftables firewall and network micro-segmentation
Separate devices into zones and choose which connections between them are allowed. The nftables firewall enforces these rules at system level. Client isolation can further restrict communication within a zone.
Isolation (Quarantine)
Default for newly connected devices
New devices enter quarantine. An administrator approves each device and assigns its zone and permitted access.
IoT / Smart Home
Cameras, sensors, vacuums, smart TVs
Outbound reach to approved vendor endpoints only. Absolute isolation from personal computers and smartphones to prevent lateral infection.
Guests
Visitors and temporary devices
A separate guest zone provides internet access and selected filtering. Firewall rules determine access to printers, NAS drives and household devices.
Trusted (LAN)
Household PCs and smartphones
Peer-to-peer LAN reach between verified devices, governed by GADNET Browser profiles and real-time anti-fraud rules.
Admin Control
Exclusive node management plane
Administrator sign-in uses passkeys, FIDO2 keys or a supported device certificate and PIN. Network rules control which devices can reach the panel.
CAKE SQM: limiting latency under load
Downloads and backups can saturate a connection and disrupt video calls. CAKE SQM helps manage traffic queues and limit latency increases. Results depend on configured limits, the connection and the route to the server.
Per-host and per-flow fairness
CAKE SQM distributes bandwidth among devices and active connections to help keep interactive traffic responsive during downloads and backups.
Tiny-packet and ACK acceleration
Prioritizes lightweight TCP ACK responses and DNS queries ahead of heavy payload chunks, keeping round-trip times snappy even when upload bandwidth is fully saturated.
DiffServ and DSCP classification
DiffServ classification sends marked voice, video and interactive traffic to the appropriate queues. Configure priorities to suit your network use.
Check the results on your connection
Compare latency before and after enabling CAKE SQM, including during uploads and downloads. Tune limits for your connection and check the results in everyday use.
>> GADNET CAKE qdisc configuration parameters
# tc qdisc add dev eth0 root cake bandwidth 920mbit diffserv4 flows ack-filter rtt 30ms
CAKE automatically hashes packet flows, isolates heavy hogs, acknowledges TCP transfers earlier via ack-filter, and ensures gaming and video packets bypass long download queues.
Unbound DNS and protection against bypass attempts
GADNET uses a local resolver and encrypts upstream queries with DoT. DNS enforcement sends ordinary lookups through the router, while configured rules restrict known public encrypted-DNS services.
Routing ordinary DNS queries through the router
With DNS enforcement enabled, UDP/TCP port 53 queries from client networks are sent to the local DNS service, even if a device specifies another server. The active policy front applies rules assigned to the device before forwarding queries.
Blocking known DoH and DoT servers
The firewall blocks configured addresses of known public DoH/DoT resolvers. DNS policies can also block their names. Enabled lists and rules define the protection scope.
Upstream DNS-over-TLS (DoT)
DoT encrypts DNS queries between the router and the upstream resolver and verifies its certificate. It conceals those queries from the network provider. Hiding the server name in a TLS connection additionally requires ECH support in the browser and website.
CERT Polska lists and RPZ policies
Enabled lists, including CERT Polska, are refreshed on a schedule and applied according to assigned policies. An RPZ rule can return NXDOMAIN for a blocked domain, preventing its address from being obtained through this DNS service. Effectiveness depends on list freshness and configuration.
>> nftables DNS interception and anti-bypass rules
DNS path: device → policy front → dnsmasq → Unbound resolver
DNS enforcement sends port 53 queries to the local service. Firewall rules and DNS policies block known public DoH/DoT endpoints. During policy-front recovery, fail-open operation maintains name resolution through dnsmasq; restoring the policy front reapplies filtering.
Banking protection and concurrent-call warnings
A banking rule can temporarily block selected communicators and recognized remote desktop tools. Recognizing a concurrent call can also trigger a push warning. Configure the rule and notifications first.
Real-time voice traffic correlation
The system analyzes active connections and data patterns associated with communicator calls, such as WhatsApp. It correlates that metadata with banking access to trigger a warning about possible manipulation.
Blocking recognized remote desktop tools
A banking-domain match can trigger a temporary block of selected remote-access domains and ports. The rule settings define the scope and duration for the device.
Dual TLS SNI verification
Visible TLS SNI provides an additional banking-domain signal alongside DNS lookups. Rules can use that signal to activate configured protection.
CERT Polska automated RPZ sync
Synchronizes continuously with the official Polish national warning feed via DNS RPZ. Known phishing portals, fake payment gateways and SMS malware domains are dropped on sight.
>> Technical deep-dive: STUN/TURN detection & AnyDesk kill rules
A banking rule reacts to a matching DNS query or visible SNI name. It activates configured domain and port blocks, while recognized call activity can trigger a push warning.
Hardware-isolated profile vault and mTLS
The Windows and Android app encrypts profile data, uses operating-system key protection and provides access to approved home services through the router’s authenticated outbound channel.
Hardware Keystore and DPAPI
Android Keystore or Windows DPAPI protects the keys used by the local profile vault. Bookmarks, history and saved credentials are stored in the app’s encrypted database.
HKDF-SHA256 and AES-256-GCM encryption
All sensitive data is encrypted using authenticated AES-256-GCM, with session keys derived via HKDF-SHA256 directly from the hardware security chip.
Authenticated access to home services
Access approved local devices (such as a private NAS panel) while away from home through an outbound authenticated relay using mutual TLS and Passkeys, keeping your router invisible.
Multi-profile sandboxing
Each household member uses a personal profile, access rules and browser data store. Separate profiles help organize use of a shared computer.
GADNET Browser is available for Windows and Android. Download release packages →
Access rules for apps, content and AI services
Choose service access and schedules. Network rules restrict selected domains and connections, while GADNET Browser applies browsing filters. HTTPS stays encrypted between the browser and website.
Mobile app CDN stream termination
Terminates native mobile app video CDN endpoints at the network boundary, stopping algorithmic autoplay loops directly at the gateway layer.
Safer search with SafeSearch
Family Safe helps apply safer settings in supported search engines. Choose filters for your child’s age and household rules to limit unsuitable results.
Granular AI endpoint scheduling
Configure granular access schedules and daily quotas for generative AI platforms (ChatGPT, Claude, Gemini, DeepSeek), dynamically toggled via in-memory RPZ policies.
Applying updated access policies
Changes to lists, rules and schedules are delivered to the appropriate system services. The administrator manages policies through the panel, and the system updates filtering configuration.
>> Technical deep-dive: SafeSearch enforcement & AI domains
SafeSearch enforcement is implemented via CNAME rewrites in Unbound (e.g. forces forcesafesearch.google.com, strict.bing.com, safe.duckduckgo.com). AI controls utilize dedicated RPZ response rules matching OpenAI, Anthropic, Google Gemini and DeepSeek endpoints, activating or deactivating based on scheduler cron jobs.