Search the Community
Showing results for tags 'outbound'.
Found 2 results
Hello everyone, I would like to create rules in the Windows 7 firewall so the AirVPN Edie client can work properly. Right now I have to allow all outbound connections for the client to work, which is not that secure. I want to have my Windows 7 firewall block all inbound and outbound connections unless I make a rule which allows a connection. I tried to make new rules in the Windows 7 firewall which included the AirVPN client files located in C:\Program Files\AirVPN to allow the connections but this did not work. I am fairly new to making firewall rules and using a VPN, so I need a basic explanation how to do this. Any advice would be appreciated.
On my home network, I have a public IP and run a few public services (email server, web, etc). These have no need for AirVPN. On the other hand, all of my client computers I would like to run through AirVPN (laptop when I fire it up, tablets, desktop, etc). I am thinking the easiest way to do this is to set up one box (a virtual machine) running as an alternate gateway on my network that is always connected to AirVPN. I could statically assign addresses and gateways to my servers, but then allow DHCP to route all client traffic through this alternate gateway (and thus through AirVPN). My question, has anyone done this successfully. If so how? I dont want to set up my router to connect to the VPN since I need to have services run through it from my ISPs static IP. I could run just about any flavor of linux or windows to get this to work if someone has a proven method. I found a link to a similar project on the OpenVPN site, but the directions seem to be incomplete. I build three separate VMs trying to get it working, no luck.