From 24dfe272643804ace83cd8d59048854332c5b5b5 Mon Sep 17 00:00:00 2001 From: Orazio Date: Sat, 1 Feb 2020 12:20:22 +0100 Subject: [PATCH] Updated FAQ (markdown) --- FAQ.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index ca4dae3..1808d6a 100644 --- a/FAQ.md +++ b/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. 7. Shortly after you should see some packets being exchanged between your Raspberry Pi and your device. + 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 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. -- 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`. \ No newline at end of file +- 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`. \ No newline at end of file