pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-02-08 05:56:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add image, update small items

Browse Source
This commit is contained in:
Owen
2025-12-10 18:27:25 -05:00
parent de61a00717
commit 0c2a5429d0
6 changed files with 294 additions and 305 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
manage/clients/add-client.mdx
View File

@@ -63,7 +63,7 @@ Clients can relay traffic through a Pangolin server - through Gerbil specificall
While functional, it does not always connect reliably and can fall back to relaying. We plan to work to improve the reliability over time by implementing more methods for those behind CGNAT or hard nats.
Take a look at Tailscale's recommendations [these docs](https://tailscale.com/kb/1361/firewall) for some firewall changes you might be able to make to improve hole punch reliability and performance.
Take a look at [these docs](https://tailscale.com/kb/1361/firewall) for some firewall changes you might be able to make to improve hole punch reliability and performance.
This should help to:
- Increase performance (speed/bandwidth)

16
manage/clients/install-client.mdx
View File

@@ -153,18 +153,6 @@ olm \
--endpoint https://example.com
```
### Permanent Installation
Install to your PATH (may need to run as root):
```bash
mv ./olm /usr/local/bin
```
<Note>
The quick installer will do this step for you.
</Note>
### Systemd Service
Create a basic systemd service:
@@ -285,11 +273,11 @@ Get-EventLog -LogName Application -Source "OlmWireguardService" -Newest 10
Olm creates a native tun interface. This usually requires sudo / admin permissions. Some notes:
- **Windows**: Olm will run as a service. You can use the commands described [Configure Client](/manage/clients/configure-client) to manage it. You can use this to run it in the background if needed!
- **LXC containers**: Need to be configured to allow tun access. See below.
- **LXC containers**: Need to be configured to allow tun access. On Proxmox see below.
- **Linux**: May require root privileges or specific capabilities to create tun interfaces.
- **macOS**: May require additional permissions for network interface creation.
#### LXC Container Configuration
#### LXC Proxmox
1. Create your LXC container.
2. Go to the Resources tab of the container.

8
manage/resources/private/access.mdx → manage/resources/private/authentication.mdx
View File

@@ -1,5 +1,5 @@
---
title: "Access"
title: "Authentication"
description: "Only allow access to Resources to specific users, roles, and machines"
---
@@ -11,4 +11,8 @@ Access can be granted in several ways:
* **Users:** Assign access to Resources to specific users. Only those users will gain access to the Resource when they connect.
* **Machines:** Assign access to Resources to specific machines. Only those machines will gain access to the Resource when they connect. Note that machines can not be put into roles.
When removing access to a resource, the client will automatically tear down the WireGuard tunnel to that Resource if there are no other Resources accessible on that site.
When removing access to a resource, the client will automatically tear down the WireGuard tunnel to that Resource if there are no other Resources accessible on that site.
<Frame>
<img src="/images/private_access_controls.png" centered/>
</Frame>

3
manage/sites/install-site.mdx
View File

@@ -39,9 +39,6 @@ newt \
--secret h51mmlknrvrwv8s4r1i210azhumt6isgbpyavxodibx1k2d6 \
--endpoint https://app.pangolin.net
```
<Note>
The quick installer will do this step for you.
</Note>
### Systemd Service