This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About gb2057
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About gb2057
11-22-2022
5Posts
1Like
0Solutions
Nov 22, 2022Last Visited
User
Activity
User
Profile
Latest posts by gb2057
| Subject | Views | Posted |
|---|---|---|
| 3429 | 10-28-2020 09:56 AM | |
| 3432 | 10-28-2020 09:53 AM | |
| 3476 | 10-27-2020 09:32 PM | |
| 2000 | 09-14-2020 11:48 AM | |
| 2238 | 09-11-2020 09:37 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 10-28-2020 09:53 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 1 Like | |||
| 1 Like | |||
| 11 Likes | |||
| 9 Likes |
Retired Member
|
by
Retired Member
|
User Badges
Community Statistics
| Member Since | 06-01-2020 06:19 PM |
| Date Last Visited | 11-22-2022 02:33 PM |
| Posts | 5 |
| Total Likes Received | 1 |
10-28-2020
09:56 AM
@lychiang fyi there was no error, nothing found in /tmp/error... I scoured the system for any logs, for all files modified in past few minutes, there was no clue in the Ubuntu system of any issue or at least I could not find anywhere to start. I thought it strange to not see any logs, because the error pop-up appears to be sent by Expedition itself, albeit there is no error message other than "Failed"
Thanks,
G
... View more
10-28-2020
09:53 AM
1 Kudo
Hi @lychiang
Thank you for the response. You are correct it was client-side, it appears a Chrome extension was causing the issue. Testing an OVA that had an earlier version (known to work) I saw I had the same issue. I started Chrome "incognito" with all extensions disabled and everything works great once again. Not sure which specific extension, but issue was definitely my client browser and not any issue with Expedition tool. I went ahead and accepted your answer as a solution since it does infer it is client-side issue and version 1.1.84 does work as expected.
Thanks again!
... View more
10-27-2020
09:32 PM
After upgrading with sudo apt-get update && sudo apt-get install expedition-beta, I can no longer import any config.
I have even tried starting from scratch with a fresh Ubunto 16.04 LTS VM. I cannot import any config -- Palo Alto for my base, nor Cisco ASA configs. Even tried same configs which had imported successfully before the update to 1.1.84, they no longer import successfully. The tool has gone from extremely useful to not usable at all.
When I select a .xml to import the Palo Alto config (or any config to import), I immediately get a blank pop-up titled "Failed"
I have scoured the system for any error logs, nothing in /tmp, or /var/log/apache2/error.log or anywhere I can find.
Any tips? Here is a screenshot:
Thanks in advance for any assistance,
G
... View more
- Tags:
- Expedition
- import
09-14-2020
11:48 AM
@BPry - Thanks for taking the time to respond with your answer. I can see you have solid experience, so I have gone ahead and accepted your response as the solution. Kudos
... View more
09-11-2020
09:37 AM
Hello to the community, First I'd like to thank everyone for contributing. The community is invaluable. I was wondering if anybody have any ideas why I always see this behavior? Reading through the discussions and doing my own research, I have seen it result showing "No rule matched" whereas my output is always just blank when no rule is matched. I enabled override on the interzone-default, and I do see the logs appear in "monitor" in the GUI. But executing test security-policy-match in CLI for the same traffic results in no output at all. Example of blank output: admin@f1-nttptc-dmz-pa(active)> test security-policy-match from DMZ to IPAM source 155.16.250.9 destination 155.16.38.141 destination-port 53 protocol 17 admin@f1-nttptc-dmz-pa(active)> I have always seen this behavior over numerous versions of PA 8.x / 9.x. Is this the expected behavior? Why do I see other posts with output results showing the helpful "No Rule Found" message? The only way I can get output from this command in CLI is if I add an explicit "deny any any" at the bottom, but this comes with its own set of issues as it overrides the default allow for "intrazone" traffic, affecting stuff like BGP, IPSec, Interface Mgmt, etc., I appreciate any feedback from others' experiences and whether this is the expected behavior? Thanks to all in advance, G
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks