Seamless roaming

Qinn

...did it using the Synology assistent ;) , as promised here it is...

ds918+.jpg

Qinn

I installed docker and unifi , follow this video https://www.youtube.com/watch?v=FUfruORHRdw without de firewall tweaks, then tried to login and restored The config after it completed, I tried to login and saw that the UAP’s are disconnected. When I login From a desktop using the Software everything is nice, any idea what’s wrong?

johnpoz

Docker would normally be on their network network... Not going to be able to talk to the AP..

I really wouldn't run the controller in a docker, I would run in own VM.. Much easier to take snapshots that way when you want to update, etc. In case something goes funky.

6.2.3-25426 update 6?? Where is that?? That makes no sense.. There is no update out that I am aware of for 6.2.3..
https://www.synology.com/en-us/releaseNote/DS918+

Qinn

@johnpoz no idea john that what it reported

Qinn

@johnpoz I wanne go ahead an try using the Synology (on a different subnet 192.168.5.x then the current controller 192.168.1.x) as controller using docker, following this guys guide, without the firewall part, as my synology has no firewall running. https://lazyadmin.nl/home-network/unifi-controller-on-a-synology-nas-with-docker/

When I logged in using the ip of the synology accessing port 8443, I restored the backup then logged in and got a, "bad network" and status "disconnect". Duhhh, me still not completely grasping the unifi concept. So I figured out that the UAP has stored the ip of the controller.

From what I have read I need to ssh into both the UAP's and on the cli do:

set-inform http://ip-of-controller:8080/inform

..am I on the right track?

or is the the way to go using the UI?

Firefox_Screenshot_2020-06-11T14-41-41.038Z.png

johnpoz

Yeah for your AP and controller to be on different network you need to do L3 adoption..

Why would you want to do that? Other than making it more complex than it needs to be? Do you run segmented network now? Why do you think the AP and Controller should be on different vlans?

Docker and vlans on synology not all that simple ;)

Docker networking is its own thing to be honest.. Not sure what version of DSM that guide was using... But clicking the button to put the docker on the same network as host is no longer there..

I don't think there is an easy way in the gui to disable the nat that happens between the docker and the host network.. Unless you are a docker guru already - I would really just suggest you run your controller on VM.. This gives you way more control over pretty much everything on the controller and the network its attached too, and really easy to put a vm on a different vlan in DSM..

Qinn

@johnpoz the Synology is in the WLAN as most devices are in the WLAN and the desktop that I am running the controller software is in the LAN, of course I could change this.

No not a docker guru ;)

You advise to use a vmm running the controller, can you point me to a config to set this up?

btw you remarked ". But clicking the button to put the docker on the same network as host is no longer there.." but it is still there...
Firefox_Screenshot_2020-06-11T15-10-01.229Z.png

Qinn

@johnpoz not to push, but if you can find the time, could you point me towards an DIY how to get the controller in vmm on the synology?

johnpoz

Install whatever OS you want ubuntu, centos, debian - then install the controller package.

So does your docker get IP that your host is on when you do that? If so then it would be on the same L2 and you would be able to see your AP, etc.

Qinn

@johnpoz

The 2 nanoHD-UAP's are connected by UTP and connect to a managed switch that's connected to pfSense.

The nanoHD have 4 VLAN's

192.168.5.x - WLAN
192.168.3.x - P2P
10.0.0x - Guests
172.16.20.x - IoT's

pfSense and the nanoHD's are in the LAN with 192.168.1.X

Is it maybe an idea to give the nanoHD's an IP that is in the same subnet as the Synology namely WLAN?

johnpoz

You want the AP and the Controller in the same L2.. The problem with docker is there is normally a nat this going on.. Which are not the same L2..

If your AP and controller on not on the same L2 then you need to use L3 adoption..

example

ash-4.3# docker network inspect bridge
[
    {
        "Name": "bridge",
        "Id": "0f675293ee5c05dfffab0e87768f200646e3355732497445611ae250a0838719",
        "Created": "2020-06-26T05:22:38.90432023-05:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.17.0.0/16",
                    "Gateway": "172.17.0.1"
                }
            ]

then ip masquerade is used to match up ports on the bridge network... This i not the same L2... if docker does put this in the same L2 then it amounts to running multiple L3 on the same L2 which could sure prove problematic for L2 adoption of the AP in your controller. Are your APs adopted by your controller?

I would suggest if you want to use your controller in a docker, and L2 adoption is not working - to use L3 adoption..

But yes generally speaking your controller and AP (managment ip) would be in the same network.. Unless your wanting to put your management IP of your AP on a vlan.. This vlan could be in the same L2 as your controller, or could be different - which again then you would need to use L3 adoption for your controller to manage your controller.

My controller and AP all run on my native vlan (untagged) 192.168.2/24 - I then have a wifi SSID that is in this vlan, this is the vlan I connect my trusted devices to... And then I have 3 other vlans (ssids) on the AP that are in different vlans 192.168.6/24, 192.168.7/24 etc..

Qinn

@johnpoz Thanks. I finally decided to move the Synology 918+ over to the LAN, so it's in the same subnet as the two UAP-nanoHD's. Then granted the WLAN subnet access to it, installed docker and the container. It's running nicely for 2 hours.

Firefox_Screenshot_2020-06-28T15-04-38.654Z.png

johnpoz

Nice.. Yeah I have added a couple dockers as of late as well ;)

I would be up for moving the controller to docker - but I also leverage that same VM as my linux box when wanting to do something I just ssh to it.. Also as vm its easier to just take snapshots when going some sort of update with controller - as mentioned I always running latest beta version..

The updatetool is slick little tool for keeping plex ratings updated with the latest numbers from imdb (runs every 12 hours).. And getting the latest ombi (plex request system) beta up was just easier to do via docker..

[INFO ] - 2020-06-28 11:23:03 @ ImdbPipeline.transformMetadata: 7670 item(s) need no update.
[INFO ] - 2020-06-28 11:23:04 @ ImdbPipeline.transformMetadata: Transforming 4 item(s)
[INFO ] - 2020-06-28 11:23:04 @ ImdbTransformer.updateMetadata: Adjust rating: 7.6 -> 8.0 for The Harvest (2)
[INFO ] - 2020-06-28 11:23:04 @ ImdbTransformer.updateMetadata: Adjust rating: 9.0 -> 8.2 for Buffy the Vampire Slayer
[INFO ] - 2020-06-28 11:23:04 @ ImdbTransformer.updateMetadata: Adjust rating: 7.5 -> 8.2 for Welcome to the Hellmouth (1)
[INFO ] - 2020-06-28 11:23:04 @ ImdbTransformer.updateMetadata: Adjust rating: 7.5 -> 7.4 for First Date
[INFO ] - 2020-06-28 11:23:04 @ ImdbTransformer.updateMetadata: (Set) Set IMDB Badge for: First Date
[INFO ] - 2020-06-28 11:23:04 @ ImdbPipeline.transformMetadata: Transformed entries for 4 items(s).

Glad you got it sorted..

edit: Looking at the unifi controller dockers I see, I don't see any on the 5.14 beta line.. So for "me" that would be a reason to just stay with using vm.

Qinn

@johnpoz From what I read here beta and docker can play well together https://www.reddit.com/r/Ubiquiti/comments/7tcyjr/unifi_beta_running_in_docker_on_synology/ maybe you wanne give it a try?

btw you are using UAP/USW Firmware 4.3.19.11295?

johnpoz

No my firmware is 5.20 told you always run the latest betas..

Qinn

@johnpoz ....did not active the early access setting in my config, thus could not see any beta's. So your on UAP/USW Firmware 5.20.0.11910 ;) btw is there any relation between the firmware and the controller version?
So could I use this beta firmware with the controller version (atag_5.13.29_13635) I have running on docker or do I need UniFi Network Controller 5.14.15, no idea if this one is available for docker?

johnpoz

You can run beta firmware with the stable controllers sure.. Its just sometimes you won't be able to do X that is in the beta firmware withou the beta contreoller.

Qinn

@johnpoz I see this Firefox_Screenshot_2020-06-30T09-44-44.362Z.png

any idea why?

johnpoz

Do you have a USG.. That is only available when you have 1 of their routers..

None of this stuff is going to show anything unless you have the stuff

Keep in mind the controller is meant to control like all of their stuff, not just AP..,

If you don't like seeing it just use your fav browser tool to hide it.

Qinn

@johnpoz you mean hide the elements? I would be nice if you could remove these widgets in the controller.