Pi-hole/pivpn
Pi-hole/pivpn
1
0
Fork 0
mirror of https://github.com/pivpn/pivpn.git synced 2024-12-20 11:50:17 +00:00
Code Issues Projects Releases Packages Wiki Activity

Updated FAQ (markdown)

Orazio 2020-02-01 12:20:22 +01:00
parent 9583bf61c5
commit 24dfe27264
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
FAQ.md

@ -34,6 +34,7 @@ Now you are looking at udp or tcp packets coming to your Raspberry Pi on the por
6. Try to connect from your device. 6. Try to connect from your device.
7. Shortly after you should see some packets being exchanged between your Raspberry Pi and your device. 7. Shortly after you should see some packets being exchanged between your Raspberry Pi and your device.
Here's a successful conversation: Here's a successful conversation:
``` ```
@ -63,4 +64,4 @@ listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
- Check if your ISP uses Carrier-grade NAT. With CGNAT, your router gets a private IP, making port forwarding ineffective. This is mostly the norm if your router connects via 4G/LTE. If that's the case, you need to ask the ISP for a public IP. - Check if your ISP uses Carrier-grade NAT. With CGNAT, your router gets a private IP, making port forwarding ineffective. This is mostly the norm if your router connects via 4G/LTE. If that's the case, you need to ask the ISP for a public IP.
- Check if the IP in your client config matches the public IP of your Pi or that the DDNS is updated. To see the public IP of your Pi, run `curl -s https://checkip.amazonaws.com`. - Check if the IP in your client config matches the public IP of your Pi or that the DDNS is updated. To see the public IP of your Pi, run `curl -s https://checkip.amazonaws.com`.
- If you see packets coming, but no response from the Pi, it may indicate routing issues, attempts to block the connection (on either side), or poor connectivity. In all cases, try to connect from a different network. - If you see packets coming, but no response from the Pi, it may indicate routing issues, attempts to block the connection (on either side), or poor connectivity. In all cases, try to connect from a different network.
- You may have misconfigured firewall rules on your Pi, open an issue and add the output of `sudo ipables -S` and `sudo iptables -t nat -S`. - You may have misconfigured firewall rules on your Pi, open an issue and add the output of `sudo iptables -S` and `sudo iptables -t nat -S`.