About RobertDillow

RobertDillow · ‎04-20-2020

just running those commands give em the same error. expedition@Expedition:~$ sudo apt-get update [sudo] password for expedition: Err:22 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 Packages 403 Forbidden [IP: 91.189.95.83 80] Ign:23 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main i386 Packages Ign:24 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main Translation-en Fetched 325 kB in 8s (40.3 kB/s) Reading package lists... Done W: The repository 'https://conversionupdates.paloaltonetworks.com expedition-updates/ Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.95.83 80] E: Some index files failed to download. They have been ignored, or old ones used instead. version is still on 1.1.66.1 after this.

RobertDillow · ‎04-19-2020

so when expedition says this I should just ignore it?

RobertDillow · ‎04-15-2020

still getting these errors Building wheels for collected packages: BPA Building wheel for BPA (PEP 517) ... done Created wheel for BPA: filename=BPA-3.21.3-py3-none-any.whl size=2232529 sha256=003f3a0012f41a2d8461504fde2d5452b47869827b0cc179ec64f67687cc28cf Stored in directory: /root/.cache/pip/wheels/c3/c1/c1/03a40ae23b0210b5bfa1961f3d65264c9b62e4218ddb58d2d9 Successfully built BPA Installing collected packages: BPA Attempting uninstall: BPA Found existing installation: BPA 3.21.3 Uninstalling BPA-3.21.3: Successfully uninstalled BPA-3.21.3 Successfully installed BPA-3.21.3 expedition@Expedition:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libapache2-mod-php7.0 libpython3.6-minimal libpython3.6-stdlib php7.0 php7.0-bcmath php7.0-bz2 php7.0-cli php7.0-common php7.0-curl php7.0-gd php7.0-json php7.0-ldap php7.0-mbstring php7.0-mcrypt php7.0-mysql php7.0-opcache php7.0-readline php7.0-soap php7.0-xml php7.0-zip python3-gdbm python3.6 python3.6-minimal 23 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 16.1 kB/9,184 kB of archives. After this operation, 1,283 kB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 python3-gdbm amd64 3.6.5-3~16.04.york4 403 Forbidden [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/pool/main/p/python3-stdlib-extensions/python3-gdbm_3.6.5-3~16.04.york4_amd64.deb 403 Forbidden [IP: 91.189.95.83 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? expedition@Expedition:~$ sudo apt-get remove Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. doesn't seem to be letting me upgrade

RobertDillow · ‎04-15-2020

that worked for a good portion, still got these errors after. Err:22 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 Packages 403 Forbidden [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.95.83 80] E: Some index files failed to download. They have been ignored, or old ones used instead. The directory '/home/expedition/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. The directory '/home/expedition/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

RobertDillow · ‎04-14-2020

I run the sudo apt-get update and I get the following errors Get:1 http://security.ubuntu.com/ubuntu xenial-security/main amd64 git-man all 1:2.7.4-0ubuntu1.8 [737 kB] Err:2 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 python3.6 amd64 3.6.7-1~16.04.york3 403 Forbidden [IP: 91.189.95.83 80] Err:3 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 libpython3.6-stdlib amd64 3.6.7-1~16.04.york3 403 Forbidden [IP: 91.189.95.83 80] Get:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 git amd64 1:2.7.4-0ubuntu1.8 [3,083 kB] Err:5 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 python3.6-minimal amd64 3.6.7-1~16.04.york3 403 Forbidden [IP: 91.189.95.83 80] Err:6 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 libpython3.6-minimal amd64 3.6.7-1~16.04.york3 403 Forbidden [IP: 91.189.95.83 80] Err:7 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 python3-gdbm amd64 3.6.5-3~16.04.york4 403 Forbidden [IP: 91.189.95.83 80] Fetched 3,820 kB in 1s (3,459 kB/s) E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/pool/main/p/python3.6/python3.6_3.6.7-1~16.04.york3_amd64.deb 403 Forbidden [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/pool/main/p/python3.6/libpython3.6-stdlib_3.6.7-1~16.04.york3_amd64.deb 403 Forbidden [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/pool/main/p/python3.6/python3.6-minimal_3.6.7-1~16.04.york3_amd64.deb 403 Forbidden [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/pool/main/p/python3.6/libpython3.6-minimal_3.6.7-1~16.04.york3_amd64.deb 403 Forbidden [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/pool/main/p/python3-stdlib-extensions/python3-gdbm_3.6.5-3~16.04.york4_amd64.deb 403 Forbidden [IP: 91.189.95.83 80] My current version is 1.1.65

RobertDillow · ‎04-08-2020

If you need help with fdisk, this guide is a good start https://communities.vmware.com/thread/449261

RobertDillow · ‎02-25-2020

running the linux commands and getting the following errors. Err:22 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 Packages 403 Forbidden [IP: 91.189.95.83 80] Reading package lists... Done W: The repository 'https://conversionupdates.paloaltonetworks.com expedition-updates/ Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.95.83 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Is there an issue with the updates? stuck on 1.1.55 right now telling me that 1.1.57 are available but not able to update.

RobertDillow · ‎02-24-2020

Migrating several 5585 myself. I am not sure how the multi context would resolve into Expedition. Would think that you would build a vsys to match each context in the palo alto's themselves as a base line if that is the model you wish to continue. I would recommend getting your expedition stood up, import the 5585 and see how it looks inside there to see how the multi context are handled. Some things can't be built net new in the expedition so you might have to skeleton build your interfaces, vsys, zones and other things that you find yourself needing in the palo. If you have a Pan as mentioned in your description, you can build this in your template and push just to the pan then import that to expedition as your base line before you try to merge your rules with the base config. It has taken me a lot of tries and abandoned projects to get close to what we might want. Been at it for about 3 months now. Expedition can be forgiving so save snap points before you merge configs so you can roll back. I generally have to start over when it gets to messy. Expedition doesn't seem to do everything I want or expected, but it gives you a good idea and a starting point. Just see how your current environment translates into expedition and plan from there. Hope this gave you a direction.

RobertDillow · ‎02-24-2020

sent the email with examples. expedition does not filter, only shows unused and used on the object tab. I only found the error on export attempts. that is a valid format in the cisco asa. if you test and make a new object with a - you get a message telling that it must start with alphanumeric and can contain 0 or more alphanumeric characters, underscore, hyphen, dot, or spaces. So it has to start with a letter or number. I don't see a way to correct the 31 character limit or the - beginning.

RobertDillow · ‎02-24-2020

if there is an object group that begins with a - that is an invalid field, it will fail an api call to load it. If you manual import the config, you can bring it up but if you try to commit it, it will error out and possible reboot the palo. The 220 I have for testing has been doing this. If a name is over 31 characters this will cause another error. I have not seen anything in expedition that seems to re-mediate these issues. A reason that manual editing needs to be done on coming from the Cisco ASA is that I have to split the zones on the firewall into different vsys per the design that was implemented. I have also discovered that if have a rule to an ip address that has a nat that the rule in expedition becomes to the nat while that is not how a cisco asa works. That was confusing to find.

RobertDillow · ‎02-14-2020

This is a generic question that I haven't found a solid answer for. Expedition was sold to my upper management to be an editing tool for importing rules from our current Cisco environment to a Palo Alto firewall. Is there a way for me to edit the rules in Expedition as in deleting rules. I have to split a single context of an ASA into 7 vsys and would rather throw it all in each vsys and then clean it up so I don't forget something in a manual attempt to separate my interface rules.

RobertDillow · ‎02-14-2020

I am importing rules from a Cisco 5585 ASA in prep to move to a 5260. I have noticed that when I go through the log file from the ASA trying to clean up the objects starting with invalid characters or edit objects that exceed 31 characters that I have issue with what is imported. Example is I import 220 lines based on the count in ultra edit and Expedition shows 60 security policies. Is there a certain format that the text in the log file has to be? Anything I can check prior to import?

RobertDillow · ‎02-14-2020

This subject seems have been dropped. Through experimentation it seems that I cannot create new items that did not already exist in the base image on the palo alto that I import. If I create the Tag on my test palo and import it, it is now an option, but I still can't create a net new tag through expedition.

RobertDillow · ‎12-16-2019

thanks for the reply. I have validated that I am running the current 1.1.51. Do you need additional information?

RobertDillow · ‎12-13-2019

I have imported rules from a Cisco ASA to expedition in prep for putting them on a Palo Alto. Expedition made the zones that the rules are tied to into tags. I have tried editing the tag to the new design but I find that I can only choose an existing tag in expedition and if I try to make a new tag by just typing in the new name it generates a null tag and now the rules have 2 tags. Do I need to make the new tags in my test palo and import that config as a new baseline before I merge to generate the option of the new tag or is there a way to create new tags in expedition.

Date Registered	‎12-13-2019 01:00 PM
Date Last Visited	‎10-28-2020 04:15 PM
Total Messages Posted	15

Online Status	Offline
Date Last Visited	‎10-28-2020 04:15 PM

About RobertDillow

Re: Invalid ip addresses when upgrading

Re: Invalid ip addresses when upgrading

Re: Invalid ip addresses when upgrading

Re: Invalid ip addresses when upgrading

Invalid ip addresses when upgrading

Re: Invalid ip addresses when upgrading

Re: Invalid ip addresses when upgrading

Re: Invalid ip addresses when upgrading

Re: Invalid ip addresses when upgrading

Invalid ip addresses when upgrading

Re: Best/Easiest way to expand the storage?

Updates failing

Re: Expedition Tool To Migrate vsys

Re: Import format issue

Re: Import format issue

Use Question

Import format issue

Re: Creating new Tags in Expedition

Re: Creating new Tags in Expedition

Creating new Tags in Expedition

Strata

Prisma

Cortex

About RobertDillow