Omada software controller cannot autofind/adopt EAP 115 via mac-docker-mbentley

Omada software controller cannot autofind/adopt EAP 115 via mac-docker-mbentley

Omada software controller cannot autofind/adopt EAP 115 via mac-docker-mbentley
Omada software controller cannot autofind/adopt EAP 115 via mac-docker-mbentley
Friday - last edited 10 hours ago
Model: EAP115  
Hardware Version: V4
Firmware Version: 5.0.5 Build 20220427 Rel. 42838(5553)

Omada controller via docker doesn't autofind EAP115, while tplin's discovery utility for macos does. Banging my head! 

I've installed mbentley's omada in local macbook m4 via docker desktop, however it neither auto find's omada EAP115 nor it adopts it if i manually add the device key. It is in preconfigure status .Suprisingly the same device gets auto detecs in my tplink's discovery tool for macos, but it doesn't get adopted. what's the solution pls.
 

note: i'm using router tplik WR850N which is connected to EAP115 via ethernet and i can connect to wifi from both router and eap. My macbook is connected to my router wifi's allthrough.Updated creds post factory reset of eap115 and changed eap's inform url to 192.168.0.108:29810.added same creds in manual device add details.  Controller Hostname/IP changed from (172.17.0.2) to (192.168.0.108)
Topology:
ISP → WR850 Router (192.168.0.1)
=>a) EAP115 (Ethernet) => IP 192.168.0.101 b) MacBook (WiFi) => 192.168.0.108 (Docker Host)
used below to run docker-omada in terminal
docker run -d \ --name omada-controller \ -v /etc/localtime:/etc/localtime:ro \ -p 8043:8043 -p 8088:8088 -p 8843:8843 -p 8880:8880 \ -p 27001:27001/udp -p 27002:27002 \ -p 29810:29810/udp -p 29811:29811 -p 29812:29812 -p 29813:29813 -p 29814:29814 \ -e SHOW_SERVER_LOGS=true \ -v ~/omada_docker//opt/tplink/EAPController/data \ -v ~/omada_docker/work:/opt/tplink/EAPController/work \ -v ~/omada_docker/logs:/opt/tplink/EAPController/logs \ mbentley/omada-controller:latest


version: "3.8"
services:
  omada-controller:
    container_name: omada-controller
    # 5.5 is the current tag as of this commen, which points to 5.5.6
    image: mbentley/omada-controller:5.5
    # restart the service if it isn't running unless manually stopped
    restart: unless-stopped
    # we can't use host network so have to explicitly define all the ports
    ports:
      - 8088:8088
      - 8043:8043
      - 8843:8843
      - 29810:29810/udp
      - 29811:29811
      - 29812:29812
      - 29813:29813
      - 29814:29814
    # create some volumes so data is saved
    volumes:
      - omada-data:/opt/tplink/EAPController/data
      - omada-logs:/opt/tplink/EAPController/logs
volumes:
  omada-data:
  omada-logs:
  0      
  0      
#1
Options
1 Accepted Solution
Re:Omada software controller cannot autofind/adopt EAP 115 via mac-docker-mbentley-Solution
Saturday - last edited 10 hours ago

  @skyscraper99 

 

you are missing some ports, try adding TCP 29815-29817

 

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:Omada software controller cannot autofind/adopt EAP 115 via mac-docker-mbentley-Solution
Saturday - last edited 10 hours ago

  @skyscraper99 

 

you are missing some ports, try adding TCP 29815-29817

 

Recommended Solution
  0  
  0  
#2
Options