Business Community > Wireless > The AP EAP670 don't issue correct DHCP requests
< Wireless

The AP EAP670 don't issue correct DHCP requests

The AP EAP670 don't issue correct DHCP requests

The AP EAP670 don't issue correct DHCP requests
The AP EAP670 don't issue correct DHCP requests
a week ago
Model: EAP670  
Hardware Version: V1
Firmware Version: 1.3.6 Build 20260306 Rel. 14246

After upgrading the EAP670 from 1.1.1 to 1.3.6 (with OMADA 6.2.0.17) I did lose the AP.

 

After seraching I captured the trafic and find out that the AP use the default IP (192.168.0.254) and don't use the one from the DHCP server.

 

before:

the AP did the following request:

DHCP discover

the dhcp server reply with DHCP offer

the AP issue DHCP request

and the server reply with DHCP ack

 

after:

the AP did the following request:

DHCP discover

the dhcp server reply with DHCP offer

 

and loop on that!

 

I did try a factory reset and it did not change the behavior.

Updated to the 1.3.7 firmware with a laptop on the same ip range (192.168.0.1) but this don't change anything.

 

in all case it send up broadcast on UDP port 29810 with this content (with 1.3.6 firmware):

{
    "header": {
        "version": "1.3.0",
        "mac": "5C:E9:31:1D:07:BE",
        "type": 1,
        "device": "ap",
        "error": 0,
        "dest": "1d48292c25ee8f462023f91843975eaa",
        "verCap": 3
    },
    "body": {
        "deviceInfo": {
            "model": "EAP670",
            "name": "sk-ap3",
            "firmwareVersion": "1.3.6 Build 20260306 Rel. 14246",
            "modelVersion": "1.0",
            "hardwareVersion": "1.0",
            "upTime": "0 days 00:09:14",
            "cpuUti": 2,
            "memUti": 62,
            "wirelessLinked": false,
            "isFactory": false,
            "nf": [
                -95,
                -95,
                0,
                0
            ],
            "ip": "192.168.0.254",
            "mask": "255.255.255.0"
        },
        "deviceMisc": {
            "support_5g": true,
            "support_11ac": true,
            "support_lag": false,
            "supportMesh": 1,
            "customizeRegion": 276,
            "supportRoaming": 1,
            "supportDfs": 7,
            "supportCluster": 1,
            "category": "EAP",
            "modelType": "NORMAL"
        },
        "controllerSetting": {
            "controllerId": "1d48292c25ee8f462023f91843975eaa",
            "destOmadacId": "1d48292c25ee8f462023f91843975eaa"
        }
    }
}

 

A laptop on the same switch port get a correct DHCP IP.

 

What could be wrong ? And how tp downgrade to version 1.1.1 ?

Regards

 

Omada and AP are not in the same vlan. I use dhcp option 138 to allow adoption.

 

 

 

  0      
 
  0      
 
#1
Options
2 Reply
Re:The AP EAP670 don't issue correct DHCP requests
a week ago

 Hi,@net5657 

Thank you for posting on our official business forum.

 

We regret to inform you that a firmware downgrade from version 1.3.6 is currently not supported for this device. 
To help troubleshoot the issue you encountered, could you please try connecting the EAP directly to your front-end DHCP server to test whether the device can successfully obtain a valid IP address this way?
Please ensure you perform the factory reset correctly: hold down the reset button for 5 to 10 seconds to complete a full reset.

 

Additionally, to help us better investigate and diagnose your problem, we would like to collect the following information from you:

  • Details of your network topology, specifically what device the EAP is connected to upstream
  • The type of controller you use to manage the EAP, as well as the current version of your controller

Thank you very much for your cooperation.

 

  0  
  0  
#2
Options
Re:The AP EAP670 don't issue correct DHCP requests
Wednesday - last edited Wednesday

  @Jeremy_12 

 

Hello,

 

I use a Omada controller version 6.2.0.17 on debian running on a proxmox server.

 

It run on a vlan 60. IP 172.xx.60.129 (DHCP reservation)

 

The  AP is an EAP670 (EU) V1.0 with latest firmware 1.3.7 it use the default vlan (100) for admin and vlans 10,20,30,40 and 90 for ths clients  (using PPSH without radius)

It use vlan  100. IP 172.xx.128.3 (DHCP reservation)

 

The glue between network is an OPNsense device that is the central firewall and routing system. Dnsmask respond to dns and dhcp requests (with option 138 giving the omada server IP)

 

All systems are connected to an TL-SG3424P switch

 

The EAP was on port 22 with POE, trunk with vlan 10,20,30,40,90,100 and PVID as 100.

 

With EAP firmware 1.1.1 Build 20250326 this was working for more than a year. But after migrating the EAp to 1.3.6 Build 20260306 Rel. 14246 it fail to get an IP frp the dhcp firmware. Manually upgrading to 1.3.7 Build 20260306 Rel. 21567 did not change that.

 

After many attempts I found the problem!! It was the switch configuration...

With the configuration, the packets form the eap (that use the default vlan for management ) are tagged 100 on the switch and are routed to the dhcp server and it respond. That response is routed , go to the switch that send it to the EAP on tagged vlan 100. 

on the older EAP code, it did respond(default vlan or 100), but on the newer code it did no.! In fact the EAP don't know vlan 100 as the "Management VLAN is Default".

This should never have worked!! Perhaps you corrected some code on the new firmware.

 

To resolve it I have configured the switch port as link type "general" with vlan 100 as untagged and all others vlans as tagged, and so it work like a charm!

 

I hope this can help someone.

 

Regards

 

 

 

 

 

 

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 250

Replies: 2

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.