Tell us about yourself!
Hi,From these logs neither should work. Both log sections show dropped packages. So just reading from this there is no way it works at either time. If you have followed my guide SSH is blocked from any network except the local one in this case 192.168.86.0/24 which means that your port forward with source 188.8.131.52 (I presume is the public IP of your router) should and are being blocked. If you can make your router actually NAT the port forward so it comes from it's internal IP (guessing 192.168.86.1) it should work just fine. If not change the SSH rule in the IPTABLES to accept incoming connections from 184.108.40.206 and you should be good to go./K
If you can connect to it locally even if you have the tunnel up there has to something else. Because a proper port forward sends the traffic from the routers local IP, so it should behave in the exact same manner as any other local connection. If your trying this by connecting back to your external-ip:22 over the VPN tunnel I can understand why there might be issues, other then that it should work just fine. I suggest the next step to be tracing the packages in iptables on the pi, here is a good place to start: http://adminberlin.de/iptables-debugging/
It's pretty straight forward if you search for tutorials setting up the pi as an access point (AP) and then more or less follow the steps again but against wlan0 instead of eth0.
I'm not sure I understand what you are trying to achieve here. This tutorial is for a VPN router handling several clients sharing a common connection. From your comment it sounds like your trying to use this as a VPN server or proxy which this setup doesn't include.
There are a few common issues that can cause this. You can read more here: https://openvpn.net/index.php/open-source/faq/79-client/253-tls-error-tls-key-negotiation-failed-to-occur-within-60-seconds-check-your-network-connectivity.html
Then you would have to make the Pi your main router and have configurations for what traffic should go where. It can be done but is a much more complex setup that I wouldn't do for two reasons.1. It will take a lot of maintenance and testing to make sure you don't have a DNS leak or similar that will expose your traffic.2. Depending on your internet connection the Pi isn't powerful enough to give you all the speed.
Are you sure that the printer is setup with the correct IP when you added it to windows? It might get another IP over the VPN. Try to add it again over the VPN.
Just give it a fixed IP address in the same subnet and it should work just fine. A more "sexy" approach would be to add a DHCP server to the Pi but that would require some more work.
Hi, haven't had any issues so far. Not a daily user my self to be honest. Every now and then the outgoing IP's get blocked but they usually sort it out fairly quickly.
Were are you stuck?
It might be that the android doesn't accept changes to the settings supplied by the DHCP. Try changing the config that the DHCP assigns to the clients.
If your router doesn't allow you to set specifics then you have to use a secondary DHCP.