EAP245 DHCP problem
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP245 DHCP problem
Model :
Hardware Version :
Firmware Version :
ISP :
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.
Hardware Version :
Firmware Version :
ISP :
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.
