Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panos (Palo alto): Configuration files unusable for restores #1102

Closed
pv2b opened this issue Nov 16, 2017 · 2 comments
Closed

Panos (Palo alto): Configuration files unusable for restores #1102

pv2b opened this issue Nov 16, 2017 · 2 comments

Comments

@pv2b
Copy link
Contributor

pv2b commented Nov 16, 2017

The current Panos model outputs configuration in a "human readable" format. This is semi-useful for diffing and auditing (although the "set" output is probably better, see PR #1101)

However, it is completely impossible to load a config file in this format on a PAN OS device, meaning that what oxidized is doing is useless for "backup" purposes (only usable for configuration auditing/logging/change tracking purposes).

Some discussion on this can be found here: https://blog.webernetz.net/palo-alto-save-load-config-through-cli/

Ideally, what should be happening instead is that Oxidized should do an XML export of the configuration file and store it. This can be done through the HTTP API. This probably needs to be a completely seperate module as well... since both output in "readable" formats and "XML" format is usable for different purposes.

It's also possible to output in XML format if using the patch in PR #1101, however, I do not know if this XML format is "loadable" in the firewall... or if the better approach is to use the sanctioned HTTP APIs.

@pv2b
Copy link
Contributor Author

pv2b commented Nov 16, 2017

It would seem this is a dupe of #440. Oops. Posted the issue too soon. Can this be merged in somehow?

@laf
Copy link
Contributor

laf commented Nov 17, 2017

It can't be merged, please post your comments in #440.

@laf laf closed this as completed Nov 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants