ER605 V2 and EAP 235 Wall Not assigning Fixed IP
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have an EAP 235 Wall with a device connected to Eth VLan 1 port and I have assigned a fixed IP address. Whenever I restart the EAP the device is given an IP that is not the fixed one nor is it the correct Vlan, and this breaks the services running on the device. If I turn off then on again the lan port on the EAP this has no effect. The only way to get the IP correct is to go down and physically unplug the ethernet cable and the fixed IP is then assigned.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I notice in the picture the switchport is set for the LAN vlan, have you tried switching this to the IOT vlan?
Just thinking out loud, the vlan on the port would be expected to take priority over a manual setting at the client side.
- Copy Link
- Report Inappropriate Content
@Philbert hi, thanks for the reply.
The Eap has each of the physical LAN ports set to the IOT 192.168.10.x VLAN in tha advanced config and so really there should be no way for that device to get a 192.168.1.x address even if the static request is ignored. As I say it allocates to the wrong VLAN but as soon as I disconnect and reconnect the cable, it gives the correct static IP....unless I have misunderstood!
- Copy Link
- Report Inappropriate Content
Hello @andynw1 ,
Please follow the post below for the available solution.
EAP235-Wall v1 - The ETH VLAN Doesn't Work Properly After Reboot
- Copy Link
- Report Inappropriate Content
@Hank21 Hi, That beta firmware seems to have worked. I installed it then rebooted the garage EAP and the devices received their fixed IP addresses as hoped. Should I install this beta firmware onto the other to EAPs? Will there be a final release firmware upgrade as the initial issue was over a year ago and this is still beta?
Thanks
- Copy Link
- Report Inappropriate Content
Hello @andynw1 ，
andynw1 wrote
I installed it then rebooted the garage EAP and the devices received their fixed IP addresses as hoped. Should I install this beta firmware onto the other to EAPs?
This Beta firmware version is just for the BUG fixed, if your other EAP235-Wall is working properly, it is not necessary to upgrade to the Beta version.
I haven't been informed of the ETA of the new firmware for this EAP235-Wall yet, will try to push the R&D team to release the firmware shortly. If you need any further assistance with the TP-Link products, please feel free to start a thread on the community or submit a ticket email to our technical support team from here.
- Copy Link
- Report Inappropriate Content
@Hank21 Ok. The problem is I now have messages each time I open the controller saying the firmware needs upgrading as the beta is a lower number than what was there before.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 503
Replies: 6
Voters 0
No one has voted for it yet.