hstarwiki:cust:gen:unifi
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hstarwiki:cust:gen:unifi [2016-10-06 T 21:37] admin [Editing Files] |
hstarwiki:cust:gen:unifi [2019-06-02 T 22:18] (current) admin [Linux Installation] |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| * Cloud Key controller or Unifi Secure Gateway | * Cloud Key controller or Unifi Secure Gateway | ||
| **IMPORTANT** This device must be on at all times and exist on the network at all times. If it does not, the APs will will allow access with or without a password, and will do traffic shaping, but the portal will not exist. The Unifi AP's do not work like standard ubnt devices and can not be logged into via a web portal to control, though they can be accessed via ssh. | **IMPORTANT** This device must be on at all times and exist on the network at all times. If it does not, the APs will will allow access with or without a password, and will do traffic shaping, but the portal will not exist. The Unifi AP's do not work like standard ubnt devices and can not be logged into via a web portal to control, though they can be accessed via ssh. | ||
| - | ====Installation==== | + | ====Installation |
| * Setup Router and LAN. | * Setup Router and LAN. | ||
| * Router can be simple with no wifi. | * Router can be simple with no wifi. | ||
| - | * The router | + | * The router |
| - | * The subnet that is in the main router | + | * There can be 2 main kind of subnet configurations: |
| - | * the subnet that a client is on who connects | + | ** A simple |
| + | ** With Unifi routers and othe rhardware you can have a different subnet for clients | ||
| * The LAN that the Unifis are on can be any combination of Routers, switches, wireless links. | * The LAN that the Unifis are on can be any combination of Routers, switches, wireless links. | ||
| * **Important** The Ubuiquti Unifi APs are the only devices that can act as APs and be managed by the controller. You can not for instance use a loco to connect to an Unifi and keep it in bridge mode. (this is not fully tested, but apparently will not work.) | * **Important** The Ubuiquti Unifi APs are the only devices that can act as APs and be managed by the controller. You can not for instance use a loco to connect to an Unifi and keep it in bridge mode. (this is not fully tested, but apparently will not work.) | ||
| - | * Option 1: Download controller software and install on machine. | + | |
| - | * Option 2: Go to IP address of Cloud key (may need to use nmap to discover IP) and register with a ubnt account. | + | ** Option 1: Download controller software and install on machine. |
| - | | + | |
| - | ====Access Unifi Controler Configuration==== | + | ==== Linux Installation ==== |
| + | ===Manually download and install=== | ||
| + | These are simple instructions udpated in 2019 | ||
| + | to download the unifi controller software manually. You can find the link for the most current version on the website | ||
| + | wget unifiCurrent.deb | ||
| + | You should update and upgrade the repositories and packages | ||
| + | | ||
| + | sudo apt upgrade | ||
| + | Now the package can be manually installed and will perform the needed dependencies. | ||
| + | sudo dpkg -i unifi_sysvinit_all.deb | ||
| + | sudo apt install -f | ||
| + | Once installed, be sure to enabled it for startup | ||
| + | sudo systemctl enable unifi | ||
| + | There may be some other steps below that were performed AFTER these three commands listed directly above. Might take some tiral and error. | ||
| + | |||
| + | ====Other ways of installing==== | ||
| + | Here are some other ways of installing tha are either old, not fully tested, or did not work properly. | ||
| + | \\ Very good instructions are here: | ||
| + | \\ here is a summary of the type of commands you do: | ||
| + | * Add the unify repositories by creating a file in / | ||
| + | sudo nano / | ||
| + | < | ||
| + | deb http:// | ||
| + | deb http:// | ||
| + | deb http:// | ||
| + | </ | ||
| + | sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50 | ||
| + | sudo apt-get update | ||
| + | sudo apt-get install unifi | ||
| + | ====Access | ||
| The controller acts as a daemon and web host. It can be accessed either: | The controller acts as a daemon and web host. It can be accessed either: | ||
| * Windows: Click on software icon to start controller software | * Windows: Click on software icon to start controller software | ||
| * The window will say " | * The window will say " | ||
| - | * Go to: https:// | + | * Go to: https:// |
| Cloud access | Cloud access | ||
| * Go To: https:// | * Go To: https:// | ||
| Line 40: | Line 70: | ||
| * Click Unifi system you want to control | * Click Unifi system you want to control | ||
| * Click " | * Click " | ||
| - | |||
| ====Cloud Access==== | ====Cloud Access==== | ||
| - | The cloud access software can now be accessed with both the local controller software (as of 4.3) and Cloud key. This allows you to connect your controller, wherever it is, to the Ubiquiti server. You must have a registered account. You can use the same for forums. This account will be remotly | + | The cloud access software can now be accessed with both the local controller software (as of 4.3) and Cloud key. This allows you to connect your controller, wherever it is, to the Ubiquiti server. You must have a registered account. You can use the same for forums. This account will be remotely |
| ====== Unifi AP's ====== | ====== Unifi AP's ====== | ||
| Line 55: | Line 84: | ||
| Once you adopt a new unifi, it will gain the user name and password that was set up for the contoller. This is very important when doing some of the steps below | Once you adopt a new unifi, it will gain the user name and password that was set up for the contoller. This is very important when doing some of the steps below | ||
| ==== Changing Controllers ==== | ==== Changing Controllers ==== | ||
| - | If you want to move a unifi AP to a different | + | If you want to move a unifi AP to a different |
| * Setup a primary unifi controller on the desired network. Know what IP your controller is on. | * Setup a primary unifi controller on the desired network. Know what IP your controller is on. | ||
| * install temp unifi Controler on a DHCP network | * install temp unifi Controler on a DHCP network | ||
| Line 63: | Line 92: | ||
| * Go into the AP settings and change IP address to something that will work on master controller network | * Go into the AP settings and change IP address to something that will work on master controller network | ||
| * Apply | * Apply | ||
| - | * Move Unifi AP to desired network | + | * Move Unifi AP to desired network |
| * SSH into AP and run this command: | * SSH into AP and run this command: | ||
| - | * $set-inform http://[ip of master controller]: | + | * $set-inform |
| * exit | * exit | ||
| * Access Master controller | * Access Master controller | ||
| * The AP should automatically be provisioning or already adopting | * The AP should automatically be provisioning or already adopting | ||
| - | ==== Remote Reset==== | ||
| - | If you can ssh into device you can remove its adoption with some commands. THis is helpful when the device is difficult to physically reach. | ||
| - | * ssh | ||
| - | * $set-defualt | ||
| - | ==== Change Inform IP ==== | + | NOTE!! Although this method did work at one time, it also failed on a second try. It may be that you will need to set the DHCP network below the main controller but where it can ping the main controller. Then You could actually try to adopt the unifi in a more traditional sense. |
| - | An alternative way to change an AP to a different controller, when the AP has an IP that you can ssh into: | + | |
| - | * ssh into unifi AP | + | |
| - | * $set-inform http://[IP of controller]: | + | |
| You can read more here: https:// | You can read more here: https:// | ||
| - | |||
| ====== Editing Client Splash Page ====== | ====== Editing Client Splash Page ====== | ||
| ====Enable Editing==== | ====Enable Editing==== | ||
| Line 88: | Line 110: | ||
| * > Authentication > No Authentication. Here you can also set various rules such as password or hotspot for paying, but mostly we just want "No authentication" | * > Authentication > No Authentication. Here you can also set various rules such as password or hotspot for paying, but mostly we just want "No authentication" | ||
| * Settings > guest Control > Portal Customization > Override Default Templates > Check to Enable. This is the step that will create a directory and files to edit. | * Settings > guest Control > Portal Customization > Override Default Templates > Check to Enable. This is the step that will create a directory and files to edit. | ||
| + | ==== Editing index file==== | ||
| + | There is a single index.html file that holds most of the information for the different web portals. So if you want to edit the no auth page, or voucher page, you edit this. It is also important to know that there is a folder called “portal” which contains all the files needed for the web hosting. You can make a compressed version of this folder as a backup if you have multiple things you are editing. | ||
| ==== View Splash page ==== | ==== View Splash page ==== | ||
| To view the splash page even after accepting terms go to: | To view the splash page even after accepting terms go to: | ||
| Line 102: | Line 126: | ||
| Once you have access to the folder structure | Once you have access to the folder structure | ||
| - | ====Editing Files==== | + | ====== Data Locations and backup ====== |
| - | + | Most of the Main data for the unifi is located in: | |
| - | There is a single index.html file that holds most of the information | + | * Linux: / |
| - | ====== | + | ====Backup==== |
| + | Backup is simple: | ||
| + | https:// | ||
| + | \\ Basically | ||
| + | ====== | ||
| Work in progress | Work in progress | ||
| ====== Untested ====== | ====== Untested ====== | ||
| Line 118: | Line 146: | ||
| * There are many models, but the one that this link refers to is here: | * There are many models, but the one that this link refers to is here: | ||
| * http:// | * http:// | ||
| + | ====== Troubleshooting==== | ||
| + | log | ||
| + | / | ||
| + | / | ||
| + | ==== resetting configuration ==== | ||
| + | If you are having issues with login, like you forgot your password, you can reset the basic config by renaming the file that holds initial setup. Then restart the service. Here is how to do it on linux: | ||
| + | sudo mv / | ||
| + | sudo systemctl restart unifi | ||
| + | ==== Remote Reset==== | ||
| + | If you can ssh into device you can remove its adoption with some commands. THis is helpful when the device is difficult to physically reach. | ||
| + | ssh | ||
| + | set-defualt | ||
| + | ==== Isolated DHCP server ==== | ||
| + | In order to have a separate DHCP server that Clients get when attached from AP's you need the Ubiquiti "Unifi secure gateway" | ||
| + | ==== Wireless uplink and Mesh ==== | ||
| + | You can have the AP's connect to another AP for its uplink. THis is called " | ||
| + | * A and B should be adopted by the controller in the traditional unifi sense where they are both on the same subnet and connected via LAN (even if the LAN is through a wireless bridge.) | ||
| + | * Remove B from the network so it is powered, but no longer on the subnet via LAN. | ||
| + | * In the controller page, refresh until it is disconnected, | ||
| + | * Choose B. The right pane will appear | ||
| + | * choose Configure in the left pane | ||
| + | * Below, drop down " | ||
| + | * A should be listed as long as its in range. Click the Chain Icon and you are done. | ||
| + | * It will take a few minutes but that will work | ||
| + | Done! Different models might have different compatibility. You can only have 4 sub APs off of one, and sub APs can not host other sub APs. | ||
| + | ==== Wireless Uplink restrictions ==== | ||
| + | Here is a lot of information about Wireless Uplink: https:// | ||
| + | \\ With a unifi mesh device, It is important to know that the wireless uplink uses the 5ghz channel and is not available with 2ghz. So if you use an omni 2ghz, and disable 5, you will not get wireless uplink. | ||
| + | \\ Here is some information about some of the restrictions, | ||
| + | \\ https:// | ||
| + | < | ||
| + | 07-12-2017 10:43 AM | ||
| + | rebelwireless | ||
| + | UAP-AC-M units with AM-2G15-120, | ||
| + | 07-12-2017 01:30 PM | ||
| + | Dave-D | ||
| + | No: you should not use these 2.4GHz antennas as if | ||
| + | they were dual-band--they are not. If you must use | ||
| + | these, you should turn off 5GHz entirely. There will | ||
| + | be no uplink service available. | ||
| + | </ | ||
hstarwiki/cust/gen/unifi.1475789850.txt.gz · Last modified: 2017-03-03 T 17:15 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
