-
-
Notifications
You must be signed in to change notification settings - Fork 17
Client Troubleshooting
Please understand that LLARP operates at the network level and that comes with inherit pros and cons, if you do not understand them please familiarize yourself with your operating system's firewall suite and IP routing tools.
LLARP operates at the network level, we do not provide you a firewall in the application, it's just an IP tunnel, the user is responsible for configuring that as the application is meant to run on a network appliance or SOHO router for consumer grade users.
For power users who want to run the client locally there is a noticeable BYO firewall which stays out of your way, (we respect system defaults, and do not attempt to change them for you, we respect your intelligence, but mainly we don't want to debug other people's system layer after we try being smart for them like other projects may).
LLARP uses a local private DNS resolver to trigger address mapping onto a user defined private IP range. This means that negative caching can get in the way. By default LLARP has a VERY low TTL to counteract this but there is only so much that can be done since it's DNS after all.
The DNS resolver defaults to 127.3.2.1:53, and can be configured to register through DBUS to systemd-resolved if needed. Check the contrib directory for relevant files.