Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 3 of 3
  1. #1
    Junior Member JohnDoeSmithBob is on a distinguished road
    Join Date
    Feb 2018
    Posts
    1

    EAP245 DHCP problem

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Hello.

    For my office I have bought an EAP245 AC1750 wireless access point.

    The topology on our end of the network is as such:
    - Gateway: 10.189.0.1
    - DHCP server: 10.6.0.10
    - DNS: 10.3.0.200
    - EAP245 AC1750: as assigned by the DHCP server : ip 10.189.0.235 // submask 255.255.255.0 // gw 10.189.0.1 // dns 10.3.0.200
    - Wireless clients should be in the range: 10.189.0.0/24 (at least that's what they are assigned to by the DHCP server when connected to the switch via ethernet).

    Nothing fancy (no vlan, no portal, no nothing) configured on the EAP245, just a simple SSID.

    Thing is, the AP doesn't relay DHCP requests; i.e. when wirelessly connecting to it, the clients have to manually assign ip / mask / gw / dns in order to work. For instance, if I manually set my wifi adapter to use ip 10.189.0.204, submask 255.255.255.0, gw 10.189.0.1, dns 10.3.0.200, then I can reach whatever resources on the network, internet, whatever. But without manually setting the ip (which would be very tedious if it had to be done for every client connecting to the AP), the AP doesn't relay DHCP-related requests.

    Any idea how to fix that?

    Follow-up question: I have ssh'ed to the EAP245 and I saw that the version of Busybox is quite old and doesn't have the dhcprelay applet, which would probably solve the problem right away. Is there a plan to update the firmware so we can use it, at least through ssh? If so, when can we expect it? I need an answer to that question because I'm considering sending back the EAP245 to buy whatever works out of the box instead (such as whatever cheap router of... any kind really).

    Thank you in advance for your answers.

  2. #2
    Seems like something is wrong with your AP. I have that AP and and clients have no problem receiving a DHCP IP. I don't think I had to do anything special for this to happen. Are there any firewalls or rules that might prevent the machines from accessing the DHCP server? Can you look at your DHCP server logs to see what is going on (is it even getting a request at all)?

  3. #3
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,433
    Quote Originally Posted by JohnDoeSmithBob View Post
    Any idea how to fix that?
    To respond to requests from other different broadcasts domains/subnets, the DHCP service needs to be set up in a "superscope" config. That's nothing an AP can or should handle. Either have a switch or a router relaying DHCP requests between both subnets or place a DHCP server in the same subnet the EAP and the wireless clients are in.

    I need an answer to that question because I'm considering sending back the EAP245 to buy whatever works out of the box instead (such as whatever cheap router of... any kind really).
    The EAP is just an access point, not a router. So even if it would have a DHCP relay running on EAP245 it wouldn't help much here. Beside this, the functions enabled in busybox don't depend on its version, they only depend on what functions the vendor did enable in the busybox executable.
    Last edited by R1D2; 02-10-2018 at 00:10.


 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2018 TP-LINK Technologies Co., Ltd. All rights reserved.