All,
I just recently setup the Azure P2S on our existing VNG using OpenVPN and Azure Ad Authentication. I can connect but within 5-10 minutes the client closes and I’m unable to route any where until I go into the Windows 11 VPN settings and disconnect.
I’m on Verizon 3.2. any idea where to look?
Man in a separate item but also having problems with the virtual gateway P2S if anyone has had similar issues on a mac.
I’m following the openssl docs here: https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-certificates-linux-openssl
openssl x509 -in caCert.pem -outform der | base64 -w0 && echo
base64: invalid option -- w
Usage: base64 [-Ddh] [-b num] [-i in_file] [-o out_file]
-b, --break break encoded string into num character lines
-Dd, --decode decodes input
-h, --help display this message
-i, --input input file (default: “-” for stdin)
-o, --output output file (default: “-” for stdout)
I try doing this without the -w0 but I can’t figure out what that’s even supposed to do and generate my certs and follow the rest of the steps.
At no point do I generate a rootcert.cer like show in this step, https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal#uploadfile
I just have these: caCert.pem caKey.pem userKey.pem
caCert.srl userCert.pem userReq.pem
When I validate my key with openSSL it looks fine. The different in caCert.pem and base64 decoding the openssl command above with the -w looks the same except for no being certificate/end certificate.
When I get to the step to set up the VPN on my local machine, Azure outputes a file named VpnServerRoot.cer_0 that mac doesn’t seem to recognize on click; but if I change it to .cer it seems fine; but then I can’t use that from the IKE mac VPN config or Tunnelblick.
Any help would be appreciated!