First we’ll need to ssh into the device
ssh ubnt@192.168.1.20
Next lets open up the config file
vi /tmp/system.cfg
Now search for vlan and replace the vlan id with the appropriate number
In VI you can search by hitting / and then type in vlan
After you have changed all the vlan ids, save the file with esc, wq, enter.
Now we can save the config with
cfgmtd -f /tmp/system.cfg -w && reboot
SSH into WHM server
ssh root@cpanel.host.com
Edit the following config file. Replace “website.com” with the website your enabling the shell_exec for
vi /opt/cpanel/ea-php72/root/etc/php-fpm.d/website.com.conf
Locate the following line and remove shell_exec from the list of disabled_functions
php_admin_value[disable_functions] = exec,passthru,shell_exec,system
The line should look like the following
php_admin_value[disable_functions] = exec,passthru,system
Save the file and restart the apache_php_fpm service
/scripts/restartsrv_apache_php_fpm
Change eth0 to the interface you would like to change.
SSH into EdgePoint and type in configure to get into a configuration prompt
configure
Now set interface eth0 to dhcp
set interfaces ethernet eth0 address dhcp
Delete the static IP address on eth0 if needed
delete interfaces ethernet eth0 address 192.168.1.1/24
Save changes
commit
Scenario: Remote device in a PTP configuration has been reset to factory defaults and is not connected.
Objective: Reconnect remote device and reconfigure using backup file
We’ll refer to Radio A as the radio you initially have access to
Radio B will be the remote radio that was reset.
Reinitiate temporary wireless connection
We know that the default Ubiquiti Wireless settings are
SSID=ubnt
Channel Width=20Mhz
Security=None
To reconnect the device wirelessly we can setup the Radio A as an AP with the above wireless settings.
Setup temporary network connection
Radio B should now connect wirelessly, but is going to be on a static 192.168.1.20 address. There are a handful of ways to overcome this.
Configure remote device via SSH
Open up your backup file with a text editor and copy the whole config
Once access is gained to Radio B, open up the /tmp/system.cfg file, delete all the contents and paste in the contents of the backup configuration.
Save file and write changes to radio with
/usr/etc/rc.d/rc.softrestart save
Final steps
The device should now apply the backup settings and disconnect again as it should now have the proper SSID and settings.
Restore Radio A’s settings and verify that both sides reconnect.
When applying changes over ssh you’ll need to “write” or “save” the changes. Usually you’ll edit the /tmp/system.cfg config file and then save the changes with one of the following commands.
/usr/etc/rc.d/rc.softrestart save or cfgmtd -f /tmp/system.cfg -w && reboot
rc.softrestart has some advantages. It does not require the radio to reboot when making changes to things like SNMP or the device name.
It does seem to have issues sometimes with certain changes. The following happened when attempting to replace the whole /tmp/system.cfg with a previous backup config.
XM.v6.1.8# XM.v6.1.8# /usr/etc/rc.d/rc.softrestart save ]--- /tmp/.running.cfg.972 +++ /tmp/.system.cfg.972 @@ -1,110 +1,256 @@ ... more random stuff ... Fast system script build Success. Fast syslog script build Success. Fast users script build Success. Fast poepass script build Success. Fast resolv script build Success. do_radio_fast_script: rname wifi0 Unsuported change in radio.1.dfs.status for fast update Fast radio script build failed Fixup Startup_list …Done. Welcome back! [ubnt@localhost] >
If you have issues applying changes with the softrestart, you can try it with cfgmtd. Downside is the radio does reboot.
cfgmtd -f /tmp/system.cfg -w && reboot
You could potentially take the reboot off the end of the above command, but have had random issues in the past where the only way to fix it was a physical reboot. Having the radio reboot after applying the config seems to resolve the issue
The following is a method to recover from a command that may inadvertenly make a radio go offline.
The idea is to launch a process in the background that sleeps for 5 minutes and then reboots the radio, so any changes not saved will be reverted. If the changes were successful, you’ll just need to log back in and kill the background process to keep the device from rebooting.
This can be helpful if your changing networking settings using ifconfig, trying to change routes, or something went wrong while trying to apply a system.cfg setting.
Commands
sleep 300 && reboot &
Execute whatever command you need to. i.e.
ifconfig 192.168.1.100
If your command worked you can log back into the device and search for the process id of the sleep command and kill it so the radio doesn’t reboot.
ps | grep sleep
Example output
2XC.v8.5.12# ps | grep sleep
412 admin 1636 S sleep 500
414 admin 1640 S grep sleep
2XC.v8.5.12#
Kill the pid
kill 412
The following template can be used to set the user name and passwords for cambium pmp gear. Create a new template in cnMaestro, past in the following, change the passwordEncrypted to the hash of your password and run the config.
You can get the hashed password by pulling it out of a current radio config.
{
"userParameters": {
"authenticationConfig": {
"accounts": [
{
"userName": "admin",
"level": 3,
"readOnly": false,
"passwordEncrypted": "188a934e0246ae248da19400fed83107a"
},
{
"userName": "root",
"level": 3,
"readOnly": false,
"passwordEncrypted": "188a934e0246ae248da19400fed83107a"
}
]
}
}
}
The following works for setting the snmpv3 configuration on cambium 450i 900’s. Once applied it’ll run change the SNMP settings and reboot the radio.
You’ll need to find the hashed password which can be found in a config backup.
Change the SNMP username/community as needed.
{
"userParameters": {
"snmpConfig": {
"user2Group": 0,
"snmpv3EngineId": "007000a9840a003e464e7a",
"rwAuthPasswordEncrypted": "3e5h24a694a515e81abb6b25986cea91",
"commStringROnly": "rocommunitystring2",
"user2PrivPassword": "",
"user1AuthPassword": "",
"snmpv3AuthProt": 0,
"snmpv3TrapEnable": 0,
"snmpv3PrivProt": 0,
"snmpMibPerm": 1,
"roAuthPasswordEncrypted": "3e5h24a694a515e81abb6b25986cea91",
"commStringRW": "communitystring",
"userGroup1": 0,
"user1Enable": 0,
"snmpv3SecLvl": 2,
"user2Enable": 0,
"rwUserName": "Canopy",
"roUserName": "snmpv3user",
"roPrivPasswordEncrypted": "3e5h24a694a515e81abb6b25986cea91",
"userName1": "",
"snmpPort": 161,
"rwUserEnable": 0,
"trapDomainNameAppend": 0,
"rwPrivPasswordEncrypted": "3e5h24a694a515e81abb6b25986cea91",
"user1PrivPassword": "",
"userName2": "",
"user3PrivPassword": "",
"user2AuthPassword": "",
"userName3": "",
"user3Enable": 0,
"snmpTrapPort": 162,
"user3AuthPassword": "",
"user3Group": 0,
"trapDelayAfterBootup": 5,
"snmpIpAccessFilter": [
{
"address": "192.168.0.0",
"netmask": 24
},
{
"address": "10.0.1.0",
"netmask": 24
},
{
"address": "0.0.0.0",
"netmask": 0
},
{
"address": "0.0.0.0",
"netmask": 0
},
{
"address": "0.0.0.0",
"netmask": 0
},
{
"address": "0.0.0.0",
"netmask": 0
},
{
"address": "0.0.0.0",
"netmask": 0
},
{
"address": "0.0.0.0",
"netmask": 0
},
{
"address": "0.0.0.0",
"netmask": 0
},
{
"address": "0.0.0.0",
"netmask": 0
}
],
"snmpTrapAddresses": [
"0.0.0.0",
"0.0.0.0",
"0.0.0.0",
"0.0.0.0",
"0.0.0.0",
"0.0.0.0",
"0.0.0.0",
"0.0.0.0",
"0.0.0.0",
"0.0.0.0"
]
},
}
Line numbers
Turn line numbers on
:set nu
Turn line numbers off
:set nu!
Color Scheme
:colorscheme evening
Syntax Highlighting
Turn Syntax highlighting on
:syntax on
Turn Syntax highlighting off
:syntax off
Highlight all search terms
:set hlsearch
https://vim.fandom.com/wiki/Highlight_all_search_pattern_matches
You can add the following to your ~/.vimrc in Linux or ~\.vimrc in Windows so the options are used every time you run vim.
colorscheme evening
syntax on
set hlsearch
set nu
To check if SELinux is enabled or disabled, you can us the sestatus command
sestatus
Or you can grep what is in the SELinux config
cat /etc/selinux/config | grep SELINUX=.*abled