I recently had to deploy redeploy an old NetScreen 5GT to segregate a production LAN and create a small lab network. The production LAN has a routable IPv6 /64 prefix, delivered via a Hurricane Electric IPv6 tunnel. The lab network also required IPv6 connectivity. We also recently obtained a /48 prefix from Hurricane Electric, so I could have just assigned a /64 from that to the lab network and routed it via the 5GT. However, this 5GT gets moved around to various different networks, including trade show networks. As such, the untrust interface of the 5GT needed to be auto-configuring, so that it would obtain an IPv6 prefix from router advertisements on whichever LAN it was connected to. This also meant that assigning a /64 from our Hurricane Electric /48 prefix was out of the question.
The first step is to enable IPv6 support on your device, if it isn’t already:
set envar ipv6=yes
reset save-config yes
After restarting your device, you should find that IPv6 configuration options are available, and the web UI will also have additional pages and config options. Continue reading “Configuring NAT66 on ScreenOS”
I’ve just spent the last couple of hours trying to find a way to export the public key from a locally generated, self-signed X.509 certificate on a Juniper SRX-100 firewall. Apparently there is no Junos CLI command to do this, so after poking around the filesystem from a shell on the box, I found the location where Junos stores local certificates and key-pairs.
In the directory
/cf/var/db/certs/common you should see at least the following two subdirectories:
drwx------ 2 root wheel 512 Jul 20 16:14 key-pair
drwx------ 2 root wheel 512 Jul 20 16:16 local
In the key-pair directory you should see files for each of your key-pairs, eg. self-cert.priv. In the local directory you will find the actual certificates, eg. self-cert.cert. Both the key-pairs and certificates are stored in binary DER format, which can be read by OpenSSL and converted to the more universal base64-encoded PEM format.
Private keys should really be left alone where they are on the Juniper, but you can safely copy the certificate to other locations, since it does not contain any private key material. Simply scp the certificate file to somewhere that has the OpenSSL tools installed, then use “
openssl x509” to read the certificate:
daniel@thinkpad:~$ openssl x509 -in self-cert.cert -inform DER
There you have it folks… a base64-encoded PEM-format public certificate.
There are a couple of prerequisites before you can copy the config from a NetScreen or SSG via scp. First, obviously ssh and scp need to be enabled:
set ssh version v2
set ssh enable
set scp enable
And of course, you need to enable ssh management on the interface you’re going to connect to the device on:
set interface ethernet0 manage ssh
Once that has been done, from your PC, try the following:
scp netscreen@device-hostname:ns_sys_config ssg.cfg
And you should then have a file called ssg.cfg in that directory. Once again, simple when you know how.
It is also possible to load RSA/DSA keys against ScreenOS usernames, so that password-less login for ssh/scp can be utilised, allowing this method to form the basis of automated config backups.