tsonander
Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.
abiolamo
Hi there Thomas,
I have seen this issue a few times using open-VPN and I think the issue you are facing is mostly likely related to a configuration/routing error.
However to narrow this down more easily without seeing the client config, it would be helpful if you can run the task below so as to determine if traffic from client is actually making it to the VPN server in the first place. If the traffic is not getting to the VPN server, then there is no point looking at the firewall rules. So I will say to look at the issue in stages.
First ensure end-to-end routing is in place then go up the stack to check firewall rules. This will help to easily spot where the issue is
1. Run a tcpdump on the server-side to check if traffic is reaching the server network (keep a record of output and post 🙂 )
i. On VPN server run
a. “sudo tcpdump -ni any 'src net 192.168.1.0/24 or 192.168.2.0/24' and 'dst net 192.168.2.0/24 or net 192.168.1.0/24'”
2. Run from client while step is still running tcpdump (step 1) on VPN server (keep a record of output and post 🙂 )
i. From client-side run
a. “traceroute –n 192.168.2.1”
b. “traceroute –n 192.168.2.253”
c. “ping 192.168.2.253 –c 2 –w 2”
d. “ping 192.168.2.1 –c 2 –w 2”
