pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-02-25 14:26:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix links and remove proxyprotcol

Browse Source 
Ref #27
This commit is contained in:
Owen
2025-11-08 14:30:14 -08:00
parent 4ea4c2b639
commit 28c8b8845e
4 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -79,7 +79,7 @@ gerbil:
</Step>
<Step title="Configure resources">
Create [client resources](/manage/resources/client-resources.mdx) for what you would like to access through the client. For example, to SSH into a server, create a resource like `22:localhost:22`.
Create [client resources](/manage/resources/client-resources) for what you would like to access through the client. For example, to SSH into a server, create a resource like `22:localhost:22`.
</Step>
<Step title="Verify connection">
@@ -115,7 +115,7 @@ Sites have two operating modalities when accepting clients:
### Proxy Mode
When you run Newt with `--accept-clients` it will run fully in user space. This means you do not need to give the container or binary any special permissions. It will NOT create a virtual network interface on the host. Instead you should create [client resources](../resources/client-resources.mdx) in Pangolin to configure what ports clients can hit and where they should go.
When you run Newt with `--accept-clients` it will run fully in user space. This means you do not need to give the container or binary any special permissions. It will NOT create a virtual network interface on the host. Instead you should create [client resources](/resources/client-resources) in Pangolin to configure what ports clients can hit and where they should go.
### Native Mode
@@ -164,7 +164,7 @@ If you can connect to Newt (peer shows as connected in logs) but can't reach rem
1. **Check if packets reach the destination**: The connection to Newt is working, so this is likely a routing issue
2. **Verify forwarding is enabled**: Use `sysctl net.ipv4.ip_forward` to confirm it's set to 1
3. **Check iptables rules**: Ensure NAT masquerading is configured
4. **Consider using proxy mode**: [Client resources](../resources/client-resources.mdx) can be easier as Newt handles the proxying, though you'll need to address everything as the Newt IP and assign specific ports
4. **Consider using proxy mode**: [Client resources](/resources/client-resources) can be easier as Newt handles the proxying, though you'll need to address everything as the Newt IP and assign specific ports
<Note>
NAT masquerading can affect other services on the Linux instance, so be aware of potential conflicts with existing network configurations.