AP DISCONNECTED AFTER CHANGING IP.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

AP DISCONNECTED AFTER CHANGING IP.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AP DISCONNECTED AFTER CHANGING IP.
AP DISCONNECTED AFTER CHANGING IP.
2019-08-27 14:52:30 - last edited 2019-08-27 15:00:21
Model: EAP225-Outdoor  
Hardware Version: V1
Firmware Version: 1.4.1

why my ap is disconnected after changing the ip? even when i choose the DHCP and click apply.. nothings happening.. still disconnected.. i already search everywhere for the solution.. like turning off the windows firewall and my antivirus.. but stil the same.. 

 

and this is the ip 

 

 

i just copy ip mask and gateway from the ipconfig of my laptop

 

 

hope.. there a solution here.. im using the latest version of omada controller. and reinstall it..but same result.. 

 

also i've tried to forget the AP on my controller but when i try adopting it again.. it ask me for a username and password..i tried the user and pass when logging at the omadacontroller but.. it failed.. please help..

 

 

 

  0      
  0      
#1
Options
5 Reply
Re:AP DISCONNECTED AFTER CHANGING IP.
2019-08-27 17:05:35

What's the IP of the system running Omada Controller? What's the IP of the router? Why is your default gateway in another subnet than the EAP?

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:Re:AP DISCONNECTED AFTER CHANGING IP.
2019-08-29 06:12:15
i used the same ip and subnet there.. look at the second pic..
  0  
  0  
#3
Options
Re: AP DISCONNECTED AFTER CHANGING IP.
2019-08-29 11:37:32 - last edited 2019-08-29 11:51:44

Co0LD0wN wrote

i used the same ip and subnet there.. look at the second pic..

 

EAP's static IP is 192.168.9.1, subnet is 192.168.9.0/24.

Default gateway for the EAP is 192.168.33.1, subnet is 192.168.33.0/24. This is different from EAP's subnet 192.168.9.0/24.

IP of system running Omada controller is still unknown, but can't work if inside the second subnet (unless there is a special routing).

 

Sorry, can't help, too many informations missing. Probably Error #40.

 

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options
Re:Re: AP DISCONNECTED AFTER CHANGING IP.
2019-09-01 04:48:40
thank you for that thoughts.. yeah ur right alot of info is missing.. tried pinging that ip but no respond.. also so for now im using the dynamic one.. the only problem is the ping is so unstable..
  0  
  0  
#5
Options
Re: AP DISCONNECTED AFTER CHANGING IP.
2019-09-01 12:51:04 - last edited 2019-09-01 12:52:38

Co0LD0wN wrote

yeah ur right alot of info is missing..

 

Only you could provide the missing infos about your network.

 

I assume that your router has the static IP 192.168.33.1.

 

Find free IPs in your network (only you can know which IPs are free/unused and which ones are already in use as static IPs).

 

Assign a free static IP (e.g. 192.168.33.2) to / set the default gateway (192.168.33.1) on the system running Omada Controller. If this system is a Windoze PC, be sure to disable its firewall and virus scanners. Also make sure that the system running Omada Controller is connected by wire to the network. Do not use wireless connections for the system running Omada Controller.

 

Reset the EAP to factory defaults (press its RESET button for ~7 sec.). The EAP will receive a free (dynamic) IP via DHCP from your router and will automatically be discovered by OC. Adopt the EAP. You will see its dynamic IP in the »Access Points« list. Now you can ping the EAP.

 

Either leave the EAP's IP settings set to dynamic (DHCP) or set another unused static IP for the EAP (e.g. 192.168.33.3) using Omada Controller. Also set the EAP's default gateway to the IP of your router (192.168.33.1).

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#6
Options

Information

Helpful: 0

Views: 2039

Replies: 5

Related Articles