Download the PHP package lamoni/netconf without Composer
On this page you can find all versions of the php package lamoni/netconf. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Table of contents
Download lamoni/netconf
More information about lamoni/netconf
Files in lamoni/netconf
Download lamoni/netconf
More information about lamoni/netconf
Files in lamoni/netconf
Vendor lamoni
Package netconf
Short Description A vendor-agnostic PHP NETCONF implementation
License MIT
Homepage https://github.com/lamoni/netconf
Package netconf
Short Description A vendor-agnostic PHP NETCONF implementation
License MIT
Homepage https://github.com/lamoni/netconf
Please rate this library. Is it a good library?
Informations about the package netconf
NETCONF
This is a vendor-agnostic PHP implementation of NETCONF. I developed this so I could extend a Junos (Juniper) specific NETCONF API off of it, and decided to share it publicly.
Targeted RFCs
- RFC6241 - Network Configuration Protocol (NETCONF) - https://tools.ietf.org/html/rfc6241
- RFC6242 - Using the NETCONF Protocol over Secure Shell (SSH) - https://tools.ietf.org/html/rfc6242
Dependencies
- PHP >= 5.4
- phpseclib (https://github.com/phpseclib/phpseclib)
To Do
- Attributes for sendRaw need to be sanitized correctly (https://tools.ietf.org/html/rfc6241)
- Elements with attribute naming for subtree filters need to be implemented ("6.4.8. Elements with Attribute Naming")
- Parse capabilities based on IANA list: http://www.iana.org/assignments/netconf-capability-urns/netconf-capability-urns.xhtml
Examples
Initializing NETCONF using password authentication and then sending a custom RPC call
Editing the configuration of a Junos device and committing the changes
Using NETCONF's subtree filters to get certain config
Considerations
- Namespaces?
- Heavier use of Exceptions?
- test-option: The
element MAY be specified only if the device advertises the :validate:1.1 capability (Section 8.6). - Should I be implicitly locking/unlocking the config for editConfig() (
) and commit() ( ) calls? - Should I remove the long list of arguments for argument-heavy methods and replace them with a single array?
- Pros
- it looks nicer
- allows for extension in the future without requiring heavy refactoring
- Cons
- Methods will require some extract() type code at the top, along with validation of keys passed through (abstract class that?)
- IDEs argument suggestion won't work(?)
- Pros
- XPath capability in filter?
All versions of netconf with dependencies
PHP Build Version
Package Version
The package lamoni/netconf contains the following files
Loading the files please wait ....