Open

by Calnex

1) Use scp, sftp (or filezilla or similar) to transfer the file to the NE-ONE, once you have copied the file into the secure environment. The example below shows scp, assuming that the patch kit you received is called ne-one-patch-202204082031

scp -p ne-one-patch-202204082031 <username>@<your ne-one ip address>:

(you'll be prompted for the password for the <username> username as usual - the default is <username>)

The file is now in the home folder of the <username> user /home/<username>

2) log in to the console of your NE-ONE :

a) $ ssh <username>@<your ne-one ip address>

<username>@<your -ne-one ip address>'s password:

You get the menu:

Open

b) leave the menu with E <enter>

c) You may already have a patches folder under /ippe, check with:

<username>@NE-ONE:~$ ls -l /ippe

total 40

drwxr-xr-x 8 root root 4096 Apr 6 13:15 config

drwxr-xr-x 2 root root 4096 Apr 8 17:44 db

drwxr-xr-x 3 root root 4096 Apr 28 2021 debug_patches

drwxr-xr-x 7 root root 4096 Apr 10 19:01 filesystem

drwxr-xr-x 2 root root 4096 Feb 16 14:02 host_bin

drwxr-xr-x 9 root root 4096 Apr 27 2021 jail

drwxr-xr-x 3 root root 12288 Apr 10 19:01 logs

drwxr-xr-x 4 root root 4096 Apr 10 18:58 patches

You should see the patches folder in the list, as above.

If it is not there, create a ./patches under /ippe on your NE-ONE

<username>@NE-ONE:~$ sudo mkdir -p /ippe/patches

d) copy the ne-one-patch-202204082031 file to that folder

<username>@NE-ONE:~$ sudo cp -p ne-one-patch-202204082031 /ippe/patches

e) go the the patches folder:

<username>@NE-ONE:~$ cd /ippe/patches/

f) expand the ne-one-patch-202204082031 tarball into this folder:

<username>@NE-ONE:/ippe/patches$ sudo tar -xvzf ne-one-patch-202204082031

./bin/ipperte

./ext/Default

./ext/Expression

./ext/Generate

./ext/Labs

./ext/Service

./ext/Soft_Port

g) check that all the files are present:

<username>@NE-ONE:/ippe/patches$ ls -lR

.:

total 21368

drwxr-xr-x 2 root root 4096 Apr 10 20:02 bin

drwxr-xr-x 2 root root 4096 Apr 10 20:02 ext

-rw-rw-r-- 1 <username> <username> 21872461 Apr 10 18:49 ne-one-patch-202204082031

./bin:

total 57844

-r-sr-sr-t 1 root root 59229632 Apr 8 21:31 ipperte

./ext:

total 4632

-rwxrwxr-x 1 <username> <username> 1050496 Apr 8 17:00 Default

-rwxrwxr-x 1 <username> <username> 581704 Apr 8 17:00 Expression

-rwxrwxr-x 1 <username> <username> 342136 Apr 8 17:00 Generate

-rwxrwxr-x 1 <username> <username> 1461408 Apr 8 17:00 Labs

-rwxrwxr-x 1 <username> <username> 307448 Apr 8 17:00 Service

-rwxrwxr-x 1 <username> <username> 985192 Apr 8 17:00 Soft_Port

NOTE: The dates and times may vary a little due to timezone and clock differences, the sizes should be the same as above

h) make sure ipperte has the correct protections:

<username>@NE-ONE:~$ sudo chmod 555 /ippe/patches/bin/ipperte

i) and check the protections:

<username>@NE-ONE:/ippe/patches$ ls -l /ippe/patches/bin

total 57844

-r-xr-xr-x 1 root root 59229632 Apr 8 21:31 ipperte

<username>@NE-ONE:~$

j) enter the docker environment:

<username>@NE-ONE:~$ sudo docker exec -it ippe bash

k) enter the command to restart the ippe engine

root@NE-ONE:/# kill -1 1

l) check that the patching has taken place by looking at the ippe.log file for patching messages:

root@NE-ONE:/# grep -Eia 'ippe version|patching' /ippe/logs/ippe.log

…

2024-05-17 17:02:25.379402: PATCHING /ippe/ext/Labs
2024-05-17 17:02:25.384021: PATCHING /ippe/ext/Soft_Port
2024-05-17 17:02:25.386660: PATCHING /ippe/ext/Expression
2024-05-17 17:02:25.388602: PATCHING /ippe/ext/Generate
2024-05-17 17:02:25.390209: PATCHING /ippe/ext/Service
2024-05-17 17:02:25.391422: PATCHING /ippe/ext/Default
2024-05-17 17:02:25.394197: PATCHING restarting to patch ipperte (2024.05.000000 202405171503)
2024-05-17 17:02:25.394206: PATCHING Restarting with command: [/ippe/patches/bin/ipperte -z -d]
2024-05-17 17:02:25.450164: PATCHING /ippe/bin/ipperte from /ippe/patches/bin/ipperte
2024-05-17 17:02:25.769547: PATCHING Restarting with command: [/ippe/bin/ipperte -x -d]
2024-05-17 17:02:25.782195: PATCHING All patches have been applied
2024-05-17 17:02:25.782745: IPPE Version: 2024.05.000000

In the above output we’re looking for the PATCHING statements immediately above the last IPPE Version: - these should correspond to the files supplied.