You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I'm seeing an issue with new machines where one can successfully install macosvpn (at least the files appear where they are supposed to and the command appears to work). I install a configuration and it never appears in Network control panel, but it will appear (only in the menu bar dropdown, not in the Network pane) if I start a new VPN interface and check the box for "Show VPN status in menu bar." Sometimes rerunning the creation script several times will work, sometimes nothing except the menu bar item workaround.
install:
#!/bin/bash
sudo sh -c "curl -L https://github.com/halo/macosvpn/releases/download/1.0.3/macosvpn > /usr/local/bin/macosvpn"
sudo chmod +x /usr/local/bin/macosvpn
echo "macosvpn command line installed"
exit 0\
Apparently something changed in 10.15.7 and Big Sur, the above behavior is seen if one tries to use macosvpn on the default "automatic" network location. Per tip by Brains on MacAdmins slack, creating a new network location and then running above command works as expected.
So I'm seeing an issue with new machines where one can successfully install macosvpn (at least the files appear where they are supposed to and the command appears to work). I install a configuration and it never appears in Network control panel, but it will appear (only in the menu bar dropdown, not in the Network pane) if I start a new VPN interface and check the box for "Show VPN status in menu bar." Sometimes rerunning the creation script several times will work, sometimes nothing except the menu bar item workaround.
install:
and I configure with this:
/usr/local/bin/macosvpn create --force --cisco CLIENT_VPN --endpoint [ip address] --username "[your full name]" --password "[your VPN password]" --sharedsecret [sharedsecret]
am I doing it wrong?
The text was updated successfully, but these errors were encountered: