They come with a power supply that takes Ethernet and power in, and sends PoE to the AP.
Note that you can't log into a unifi AP*. You have to have a controller, which can run on FreeBSD and is in ports (it's a java application)
*well you can ssh to it, but that's only really useful to reset it or manually attach to a controller.
Install MongoDB
Install mongodb on the jail.
pkg install -y mongodb
Then set mongodb to load on system boot.
echo 'mongod_enable="YES"' >> /etc/rc.conf
[2019-02-15 13:15:12,897] <db-server> INFO db - DbServer stopped
[2019-02-15 13:16:23,653] <launcher> INFO system - ======================================================================
[2019-02-15 13:16:23,654] <launcher> INFO system - UniFi 5.9.29 (build atag_5.9.29_11384 - release) is started
[2019-02-15 13:16:23,654] <launcher> INFO system - ======================================================================
[2019-02-15 13:16:23,657] <launcher> INFO system - BASE dir:/usr/local/share/java/unifi
[2019-02-15 13:16:23,664] <launcher> INFO system - Current System IP: 192.168.1.69
[2019-02-15 13:16:23,665] <launcher> INFO system - Hostname: S07
[2019-02-15 13:16:25,865] <launcher> INFO db - waiting for db connection...
[2019-02-15 13:16:26,389] <launcher> INFO db - Connecting to mongodb://127.0.0.1:27117
[2019-02-15 13:16:32,657] <launcher> INFO db - setting mongodb features compatibility version to 3.6
[2019-02-15 13:16:32,678] <launcher> INFO db - * Factory Default * Database exists. Clean it
[2019-02-15 13:16:33,580] <launcher> INFO db - Connecting to mongodb://127.0.0.1:27117
[2019-02-15 13:16:33,603] <launcher> INFO stat - * Factory Default * Stat Database exists. Clean it
[2019-02-15 13:16:33,791] <launcher> WARN discover - unable to join multicast group 233.89.188.1 on em0 (/192.168.1.69)
[2019-02-15 13:16:33,964] <launcher> WARN system - cannot load native lib - ubnt_webrtc_jni
unifi_enable="yes"
in /etc/rc.conf. It starts its own copy of mongo automatically.Now I suddenly realize what hordes of brute-forcers are looking for. I've been wondering about this specific account for a while. I actually thought this was a default Ubuntu account or something like it.Unless things have changed the default ssh login for a new unit is ubnt for username and password.
Feb 12 19:59:30 maelcum sshd[21710]: Failed unknown for invalid user ubnt from 117.109.87.140 port 36462 ssh2
Feb 12 19:59:31 maelcum sshd[21710]: Connection closed by invalid user ubnt 117.109.87.140 port 36462 [preauth]
mongo --port 27117
to gain access or
from a browser but that only shows:-
It looks like you are trying to access MongoDB over HTTP on the native driver port.
You need to install net-mgmt/unifi5. Don't bother with mongo, the Unifi controller will do that for you. The controller will start up its own web interface that you will connect to.
HTTP Status 400 – Bad Request
Now I suddenly realize what hordes of brute-forcers are looking for. I've been wondering about this specific account for a while. I actually thought this was a default Ubuntu account or something like it.
iFirst off, you need to make sure the AP is registered with the controller
Click on the icon that looks like a target ("Devices"). Does anything show in there?
If there's an entry in there that says waiting adoption, just click the adopt button.
If there's nothing, you may need to add the AP to the controller manually. You'll need to run the two commands from my post #9 above on the AP. Once that's done it should show as waiting adoption in the controller web interface.
root@S07:~ # ssh ubnt@192.168.1.60
ubnt@192.168.1.60's password:
BusyBox v1.11.2 (2015-01-19 13:59:09 PST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
BZ.v3.2.10# mca-cli
UniFi# set-inform http://192.168.1.60:8080/inform
Adoption request sent to 'http://192.168.1.60:8080/inform'.
- please adopt it on the controller
- issue the set-inform command again
- <inform_url> will be saved after device is successfully managed
UniFi#