- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
05-30-2023 05:51 PM
I recently updated and I am unable to connect from within the globalprotect 'environment'. I am not sure what to call it.
i.e.
(base) john@pcname:~$ globalprotect
>> connect
Segmentation fault (core dumped)
(base) john@pcname:~$ globalprotect
>> help
Segmentation fault (core dumped)
(base) john@pcname:~$
Trying to interact at all after just typing 'globalprotect' just ends in seg faults, no matter what command.
However, using it like this works fine:
(base) john@pcname:~$ globalprotect connect --portal address.com
Retrieving configuration...
address.com - Enter login credentials, you will be prompted for Okta Verify.
username:
Password:
Discovering network...
Enter a passcode or select an option to continue: 1 - Push. Enter '0' to abort.:
Connecting...
Connected
(base) john@pcname:~$ globalprotect show --status
GlobalProtect status: Connected
(base) john@pcname:~$ globalprotect show --version
GlobalProtect: 4.1.9-2
Copyright 2009-2018 Palo Alto Networks, Inc.
How might I troubleshoot this? I haven't been able to find anything directly related, it's been frustrating to search because I don't know how to describe these two modes in a search term.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!