Fixed IP broken AGAIN ... Lock to AP not working

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

Fixed IP broken AGAIN ... Lock to AP not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Fixed IP broken AGAIN ... Lock to AP not working
Fixed IP broken AGAIN ... Lock to AP not working
2023-05-24 13:16:47

Not much more to say on this ... You can see from the images below that neither the IP address NOR the locked AP match what is configured

 

 

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  0      
  0      
#1
Options
10 Reply
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-24 13:38:40

  @TandS 

 

Did the firmware release for the APs that enabled the "lock to ap" setting?

I can not teach anyone anything - I can only make them think - Socrates
  1  
  1  
#2
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-24 13:55:21 - last edited 2023-05-24 13:55:50

Not sure how I'm supposed to know that. I'm running the latest firmware version available and the Omada software allows the setting without any errors or warnings so I have no reason to believe that the feature wouldn't work.

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  0  
  0  
#3
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-25 10:31:55

  @TandS 

 

 

The release for the controller firmware mentions that some features require an updated device firmware.  As mentioned above this may be the case for your APs, hard to tell for sure from the screenshots.

 

 

  1  
  1  
#4
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-25 16:44:17 - last edited 2023-05-25 16:53:18

That "might" explain the Lock to AP function but if you look at my screenshot it only mentions that the device "after enabling lockto AP, clients may ..... ".  No mention about your firmware not being supported like you "now" see elsewhere in the SDN. 

Here is an example  showing a feature not currently supported which is what I would expect to see if it might not work:

 

 

And what about the Fixed IP not working again. This issue was supposedly fixed months ago but appears to have resurfaced again. Internal Quality Control on these products appear to atrocious.  I can now understand why so many people just go with Unifi products.  This might be cheaper but I guess you ultimately get what you pay for.  If I was having to rely on this for a  business it would have been ripped out and replaced months ago now.

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  0  
  0  
#5
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-26 02:25:11

  @TandS 

 

Did the fixed IP issue occur when you reboot the controller?

Have you tried other IPs beyond the DHCP pool?

Maybe rebooting the gateway can fix it.

Just striving to develop myself while helping others.
  0  
  0  
#6
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-26 12:41:21

  @Virgo 

 

Upon closer inspection I did observe that another client device was using the IP address that was "supposed" to be fixed to the client in question.

The client that was using this IP address did not have a Fixed IP address associated it to and the client with the problematic Fixed IP address had this address reservation for many weeks now.  I can only guess that one of the recent updates either to the SDN software or to the ER605 brought the issue back.

 

To try and resolve my issue I changed the Fixed IP address to the one it was "currently" assigned and then I went into my home automation applications and revised the IP address to reflect the changed one.

 

Bottom line is this should not be happening and I hope TP-Link takes this seriously and investigates as this has been an ongoing issue for many for well over a year now and should be considered basic functionality in a router.

 

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  0  
  0  
#7
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-26 18:10:27

  @TandS 

 

Wait... so is the fix IP issues... assigned a fixed IP that is WITHIN the DHCP Scope or outside the scope?

 

It works for me within the DHCP scope.  

 

Why would you enter a fixed IP (DHCP Reserve) outside the DCHP scope?  Just manually statically assign it.

 

 

I can not teach anyone anything - I can only make them think - Socrates
  0  
  0  
#8
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-05-26 18:42:05 - last edited 2023-05-26 19:33:08

It was assigned a fixed ip address within the scope of the DHCP range.

 

I have since just lowered the DHCP range and manually assigned an IP address outside the range in the hope this doesn't occur again.

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  0  
  0  
#9
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-06-04 12:55:04

  @TandS I'm facing another issue with the fixed IP on my network. It seems to be broken again. The IP address and the locked AP are not matching the configurations I've set. This problem has persisted despite the Omada Linux version being v5.9.31, R605 version 1.3.0 - Build 20230511 R.51317, SG2008P version 1.0.7 - Build 20221130 R.42340, SG2008P version 3.0.4 - Build 20221130 R.42340, and 3 x EAP245 version 5.1.0 - Build 20230104 R.79433.

  0  
  0  
#10
Options
Re:Fixed IP broken AGAIN ... Lock to AP not working
2023-06-13 00:21:23

  @TandS 

 

Same problem here with EAP650(US) v1.0 and EAP670(US) v1.0 with firmware 1.0.6

 

Lock to AP NOT WORKING

 

HOPE TPLINK WILL FIX IT ON NEXT FIRMWARE.

  0  
  0  
#11
Options

Information

Helpful: 0

Views: 799

Replies: 10

Related Articles