Hmm, the username from openvpn should be in one of the environment vars it's checking. Open a bug report at https://redmine.pfsense.org/ and we'll take a look at it to see why it isn't getting the username as expected.
@cmenning:
LAN clients can access AWS assets via private IPs using the IPSec tunnel.
So you will have set up an IPSec phase 2 between your LAN and the AWS LAN.
The same thing is necessary for the OpenVPN tunnel network and the AWS LAN to get access to the remote devices from road-warrior clients.
However, I'm not sure if multiple phase 2 are possible on AWS.
Yes, it was the firewall.
After installing Kaspersky there was "another" firewall manager above the Windows firewall.
There I had to add the subnet and add the connection to "Local LAN".
Thanks a lot!
-demux
OpenVPN itself doesn't support that.
You can make a copy of the server and keep everything the same except for the tunnel network and protocol, adjust your WAN firewall rule, and then you can pick either protocol on the client.
It wasn't a pfSense problem but a FreeNAS one.
I was run the OpenVPN client on a jail. Once I use the OpenVPN build in FreeNAS the problem has disappeared.
No. I am getting same IP results with whatismyip.host and other websites such as whatismyip.live
I am using PureVPN and visited both websites. Here are the results:
http://whatismyip.live IP results:
[image: Screen_Shot_04_19_18_at_03_27_PM.png]
http://whatismyip.host results:
[image: Screen_Shot_04_19_18_at_03_27_PM_001.png]
You need to:
add all of the remote networks each site should be able to access to the Remote Networks at those sites
be sure the OpenVPN firewall rules pass the necessary traffic into each firewall
U have show me that this setup must work and doesn't have any conflict, different instances.
jimp I will jump into the setups, 1 site is not under our management only.
I will go deep into the setup and let u know our progress.
Thanks. :)
You can't use AirVPN gateway to monitor with dpinger. You need to use an external gateway. It used to work, but something has changed either from AirVPN side or from Pfsense since 2.3.x
