SonicWall SonicOS connection templates
The sonicwall/ folder holds three SSH templates for SonicOS, all Core and Pro. They differ in how the device logs you in. This page covers release v2.2.2.
Which template
| Template | Use for |
|---|---|
sonicwall-sonicos-ssh-noenable |
Username and password asked before the session opens |
sonicwall-sonicos-ssh-enable-banner |
The same, with a login banner to confirm with yes |
sonicwall-sonicos-ssh-noenable-nousername |
Password asked inside the session, no username prompt |
The banner template uses rConfig’s enable step for the banner: enableCmd is yes, sent to confirm the banner, rather than a privilege command.
In-band password login
Some SonicOS devices accept the SSH connection without checking the password, then ask for it inside the session:
Using username 'rconfbackup'.Password:To check, connect by hand with ssh <user>@<device>. If the password is requested after the Using username line rather than by your SSH client, use the nousername template. It sets sshInteractive: on and an empty username, so rConfig logs in at that prompt and sends only the password.
With the other two templates, such a device takes every command as a password attempt. The debug output (php artisan rconfig:download-device <id> -d) shows Access denied after each command. From rConfig Pro V8.4.2 the download is reported as a failed login; earlier versions save Access denied as the config and report success.
The nousername template needs Pro V8.4.2 or later. Older versions and Core send the username first, which the device takes as a wrong password before the real one goes through. The backup still works, but the device logs one failed login per backup, so check its lockout settings first.
The templates
rConfig-templates / sonicwall /sonicwall-sonicos-ssh-noenable.ymlView on GitHub- Protocol
- SSH, port 22
- Enable
- off
- Paging
- no cli pager session
- Status
- community-tested
- Protocol
- SSH, port 22
- Enable
- yes (accepts the banner)
- Paging
- no cli pager session
- Status
- community-tested
- Protocol
- SSH, port 22
- Login
- sshInteractive, empty username
- Paging
- no cli pager session
- Status
- untested-starter
What to put in the command group
The README suggests:
show current-config