tranquivox69 27 Posted ... Hi! For quite a long time I've been using this solution: https://airvpn.org/topic/15008-eddie-2103-network-lock-breaks-lan-connectivity/?do=findComment&comment=31234 instead of normal Network Lock, to preserve SMB sharing inside my network. Now, I have set up an SFTP server and had trouble with AirVPN port forwarding. I gave to one of my users my "real" IP and created a route inside Eddie to place the traffic toward his IP outside the tunnel. I opened the relevant port on my router and in Windows 10 firewall and he connected with no problem, outside the VPN. Then I experimented by removing the route in Eddie and he still can connect outside the VPN. He points to my real IP, using the port I've opened in my router and he just connects. Is this normal behaviour? Or am I open to some security risks? I did not think this was possible and I have been using AirVPN port forwarding and DDNS to access services that I did not necessarily want through the VPN since I believed that was the only way to access them. But if my real IP is available from the outside, I might reconsider.Again, admitting that this is not a security risk. Thanks to anyone chiming in. Quote Share this post Link to post