Quantcast
Channel: All SRX Services Gateway posts
Viewing all articles
Browse latest Browse all 17645

System Archival different then file copy via scp?

$
0
0

Hi All,

 

I'm facing a bit of an odd issue with the system archival. I've seen some posts come by about system archival, but not quite the issue i'm seeing here.

 

The setup:

SRX220 (192.168.1.1) <--> NAS (192.168.1.3)

 

The NAS is directly connected to the SRX, and everything is performing flawlessly. There are no user issues, directory issues, synology firewalls, etc.

When performing a file copy <file> scp://<user>@<ip>//<path> from the SRX to the NAS, everything seems to be fine and the file is being copied to the directory of my liking under the user of my liking. When performing a similar action with FTP, everything is fine and works also fine. However when the system archival tries to copy the configuration file to the same directory under the same user, it fails. Attached are 2 wireshark files, 1 pcap file is from the system archival, the other from the manual file copy.

 

To be sure it was not an SSH issue, I added both versions of the SSH protocol to the config. However, my preferred version would be 2. Below the necessary bits of config, with the removal of some parts.

 

<user>@<hostname>> show configuration system services
ssh {
    protocol-version [ v2 v1 ];
    client-alive-count-max 6;
    client-alive-interval 300;
}<user>@<hostname>> show configuration security ssh-known-hosts
host 192.168.1.3 {
    ecdsa-sha2-nistp256-key <key>
}<user>@<hostname>> show configuration system archival
configuration {
    transfer-on-commit;
    archive-sites {
"scp://<user of choice>@192.168.1.3//<path of choice>" password "<password of choice>"; ## SECRET-DATA
    }
}

Any feedback would be much appreciated!

 

Thanks in advance.

 

Gr,

DanVer


Viewing all articles
Browse latest Browse all 17645

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>