Differences

This shows you the differences between two versions of the page.

--- other:networking:opnsense:quickreferences [2021/03/23 00:34] – rodolico
+++ other:networking:opnsense:quickreferences [2025/01/10 19:59] (current) – rodolico
@@ Line 52: / Line 52: @@
 **Note**: On the rules, order is important. Any Pass rule that exists prior to this rule will negate it. For example, if you have your VPN rules before this, VPN will work from other countries. Put this as high in the list as possible.
+===== OpenVPN DNS Issues =====
+On a Chromebook, we have had an issue where making a VPN Connection using OpenVPN kills DNS. Sites can not be reached on the Chromebook while the VPN is active.
+It appears ChromeOS will kill its DNS entries when a VPN connection is made, even if no DNS is in the configuration. Once the VPN connection is stopped, DNS resumes.
+The solution is to add a DNS entry to your Road Warrior (Remote Access) vpn server.
+  - VPN | OpenVPN | Servers
+  - Select the server in question for edit
+  - Find DNS Servers (under client) and enter one or more DSN servers (by IP address)
+    - Hint: if you put a forwarding DNS server within the network you are connecting to, some Operating Systems will allow you to connect by FQDN
+    - Adding DNS Default Domain will allow you to find "acme.example.local" by simply entering "acme"
+    - Adding multiple domains separated by comma's will allow you to find the same, but across multiple domains.
+    - Putting a check mark in //Force DNS cache update// will help Windows machines to use the new server list
+    - Putting a check in //Prevent DNS leaks// will disable all other DNS servers for the duration of the VPN session (Windows only)
+    - Save, then re-export the client configuration files
+===== Admin User =====
+In many cases for small business, you want to have a user who can perform administrative functions on the router. This is an excellent alternative to supplying everyone with the root password. You can not, however, simply give all permissions, as some conflict. Following will give a group admin rights, without making them a member of the admin group and keeping the root password secure.
+  - System | Access | Groups
+  - Add new group by clicking the plus sign
+  - Create a name (I called it sysadmin), set a description, then add one or more users.
+  - Save
+  - Edit new group
+  - Edit permissions (pencil, under Assigned Privileges)
+  - Search for //All Pages// and select that (GUI All pages)
+  - Do not add or remove anything else
+  - Save
+  - The users you have added to this group can not log in, with their own credentials, and manage the router
+===== Limited access user =====
+In some cases, you need to give an end user limited rights. They need to be able to log into the router's WebUI and perform some limited functions. This will show you how to allow a user to A) change their own password and B) reboot the router.
+  - System | Access | Groups
+  - Create new group by clicking plus sign
+  - Group Name: Reboot, Description: whatever, Add users to group
+  - Click Save
+  - Edit the new group
+  - Click the pencil under //Assigned Privileges//
+  - Search for, and enable, reboot (//GUI Diagnostics: Reboot System//)
+  - Search for, and enable, password (//GUI System: User Password Manager//)
+  - Search for, and enable, login (//GUI Lobby: Login / Logout / Dashboard//)
+  - Save
+The user(s) you have as a member of this group will be able to login, change their password, and reboot the system.
 ===== Links =====
   * https://docs.opnsense.org/manual/how-tos/maxmind_geo_ip.html
   * https://docs.opnsense.org/manual/aliases.html
+  * https://forum.opnsense.org/index.php?topic=38493.0