| Age | Commit message (Collapse) | Author |
|---|
|
Changed prompt (too strict)
|
|
Changed prompt (too strict)
|
|
|
|
there are numerous use-cases for this in models, no point to load in
models separately
|
|
Add support for PowerConnect 62xx
|
|
The pager prompt on the PowerConnect 62xx family does not have a leading space; fixed the expect regex. Also added 6224/6248 to the block ignore regex.
|
|
Add support for HP Comware SMB switches
|
|
Some SMB HP switches (V1910, V1920) run Comware, but have the CLI hidden behind a "secret" toggle - it needs to be activated by _cmdline-mode on. The password to enable it varies per model, so this patch introduces a new var, comware_cmdline to contain the password.
Unfortunately we cannot easily autodetect this, as only the "summary" command can give us the model number, but this command is paged and we cannot disable the pager until we are in the full CLI.
Tested on HP V1910-24G-POE.
|
|
|
|
Add a pre_logout for some devices
|
|
Add the Cumulus feature
|
|
Add an other post_login for some devices and a pre_logout
|
|
Add the Cumulus feature
Add Cumulus feature
|
|
ironware model improvement
|
|
|
|
hide enable secret when remove_secret is enabled
|
|
|
|
|
|
|
|
Add match for 35xx Switches, tidy up regex
|
|
Added a check for 35xx switches
Also extract only on the model number, not the suffix (P or F) as we dont need that.
|
|
Some Git libraries cant see initial commit
|
|
Using some libraries, in this case pygit2 the initial commit cannot be seen, a change and new commit fixes this.
Adding index.write appears to be a simple fix, as confirmed in this rugged issue:
https://github.com/libgit2/rugged/issues/441
|
|
PowerConnect Model not skipping some details
|
|
Some PowerConnect models were skipping fine as "Uptime" for example is shown across one line. Some models show this as a heading, and then lines for each stack member and so this was being included in the configuration. This will skip that "section" which is terminated by the next blank line.
|
|
Add Support for Cisco Devices with VSS
|
|
Devices with VSS enabled log Configuration Changes as "%SYS-SW1-5-CONFIG_I" where "SW1" is an identifier of the device in the stack that it came from. (Also added a bit of information of port numbers)
|
|
|
|
|
|
Backup full ASA configuration (include passwords)
|
|
At the old version it didn't backup things like ldap passwords, which ended up in output marked as '****'.
pre: ldap-login-password *****
now: ldap-login-password wBGqqqCY5SjZ8hY
|
|
Added support for Mikrotik RouterOS
|
|
|
|
|
|
|
|
Fix terminal length issues with older powerconnect switches
|
|
|
|
#89. Fixed by sending both commands and allowing one of them to fail.
|
|
|
|
|
|
|
|
From issue #45
|
|
|
|
|
|
Add back ability to use passwordless enable on EOS
|
|
Fix: Handle missing output file
|
|
This commit adds the ability to go into Privileged EXEC mode when no password is required by setting `enable: true`.
By default, in Arista EOS you aren't prompted for a password when entering Privileged EXEC (or privilege mode 15) mode. In PR #86, oxidized began always expecting a password.
An unquoted `true` in YAML is a boolean. So when `var(:enabled)` is `TrueClass`, we interpret this as meaning that the user wishes to go into Privileged EXEC mode and does not require a password.
|
|
If no output file is found, return nil.
Previously, it would try to find the output file by doing a recursive glob search in the config dir. It would then try to open the file for reading regardless of whether any file was found.
I ran into this when I fired up oxidized for the first time and tried to access a switch config on oxidized-web before it had a chance to collect it.
In this scenario, you get a stack trace on the switch config page (e.g. `http://oxidized.example.com:8888/node/fetch/switch-001.example.com`):
```
Puma caught this error: undefined method `join' for #<String:0x007f3a3c4283f8> (NoMethodError)
/usr/lib64/ruby/gems/2.2.0/gems/sinatra-1.4.5/lib/sinatra/show_exceptions.rb:37:in `rescue in call'
/usr/lib64/ruby/gems/2.2.0/gems/sinatra-1.4.5/lib/sinatra/show_exceptions.rb:21:in `call'
/usr/lib64/ruby/gems/2.2.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:180:in `call'
/usr/lib64/ruby/gems/2.2.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:2014:in `call'
/usr/lib64/ruby/gems/2.2.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in `block in call'
/usr/lib64/ruby/gems/2.2.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1788:in `synchronize'
/usr/lib64/ruby/gems/2.2.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in `call'
/usr/lib64/ruby/gems/2.2.0/gems/rack-1.6.0/lib/rack/urlmap.rb:66:in `block in call'
/usr/lib64/ruby/gems/2.2.0/gems/rack-1.6.0/lib/rack/urlmap.rb:50:in `each'
/usr/lib64/ruby/gems/2.2.0/gems/rack-1.6.0/lib/rack/urlmap.rb:50:in `call'
/usr/lib64/ruby/gems/2.2.0/gems/rack-1.6.0/lib/rack/builder.rb:153:in `call'
/usr/lib64/ruby/gems/2.2.0/gems/puma-2.11.1/lib/puma/server.rb:507:in `handle_request'
/usr/lib64/ruby/gems/2.2.0/gems/puma-2.11.1/lib/puma/server.rb:375:in `process_client'
/usr/lib64/ruby/gems/2.2.0/gems/puma-2.11.1/lib/puma/server.rb:262:in `block in run'
/usr/lib64/ruby/gems/2.2.0/gems/puma-2.11.1/lib/puma/thread_pool.rb:104:in `call'
/usr/lib64/ruby/gems/2.2.0/gems/puma-2.11.1/lib/puma/thread_pool.rb:104:in `block in spawn_thread'
```
|
|
|
|
fixes for EOS switches with enable secret configured
|
