ER605 V2 - PXE Boot not working?
I migrated from a unifi system over to a tp-link ER605 as my unifi system couldn't support my new internet connection properly.
One thing that was setup and working was pxe booting.
I've tried setting this up within the ER605 but it doesn't seem to work correctly.
It picks up the boot file correctly but even if i put the correct address into what now states the "DHCP TFTP server" it still picks up the default gateway as the tftp server and just boot loops.
Has anyone been able to get this working correctly? or is there anyway to get around it?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi everyone in this thread,
Clive_A wrote
Hi @Toast789 @mrdeadlocked @WindyBinDay @Springs42
Confirmed w/ the dev that there will be a beta for standalone to have the next server. If you are using a controller, please let me know the controller version.
Future firmware updates for the router will resolve this issue. Please patiently wait for the future firmware updates.
Here's the beta firmware for you. Please download it here: download
It adds support to the next server in standalone mode. For anyone who uses a controller, this might not be as helpful. Please wait for the future firmware of the Omada Controller.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
WallyJericho wrote
I installed firmware ER605 2.2.4 Build 20240119 Rel.44368 and TFTP server setting is still not working.
It seems that the advanced LAN settings are completely ignored.
Am I missing a vital step?
If you are not reading the thread carefully, let me point you the issue.
You are NOT using the same firmware as they do.
And my previous reply was a beta firmware provided by the download link which has expired for a long long time. (7-day)
Here's the link I created again. Note that the firmware may not include the features you see on 2.2.4 now.
In addition, the official fix to this issue will come out on V5.15(ETA). Disclaimer, this is not a guarantee but informative use.
Expired before Feb 6th: https://we.tl/t-3q5Vycz4Kl
- Copy Link
- Report Inappropriate Content
is there any config you want to share with the community? hard to tell the reason without any further info.
use DHCP option 66 and 67, are you able to make it work flawlessly?
- Copy Link
- Report Inappropriate Content
I've set the appropriate settings within the lan options which are below.
and this is what is seen on screen when trying to pxe boot
As you cans see it's picking up the default gateway when trying to use tftp
- Copy Link
- Report Inappropriate Content
In the latest firmware with the controller, you have option 66 and 67. if you don't want to test that out, that'll be fine.
(note that the controller will reset your router after adoption)
can you try setting up option 150 and dhcp tftp server? check again?
if no, not sure which option is missing causing this problem. maybe controller mode can make it work
- Copy Link
- Report Inappropriate Content
I am having the same issue, option 66 is not working.
Router: ER605 v2.0 Firmware 2.1.2
Switch: TL-SG2008P v1.0 firmware 1.0.8
Omada Software Controller: 5.9.31
But when I send a PXE request I get the gateway address instead of the TFTP server address:
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Any updates? I want to boot netboot xyz efi
- Copy Link
- Report Inappropriate Content
Hi @Toast789 @mrdeadlocked @WindyBinDay @Springs42
Toast789 wrote
Any updates? I want to boot netboot xyz efi
Thanks for posting in our business forum.
Have you double-checked your boot format?
There is a difference in the TFTP server you should access.
The standard format would be \smsboot\x64\abcd.efi
Have you set in this format and specified the path correctly?
Would love to see some screenshots from you.
- Copy Link
- Report Inappropriate Content
@Clive_A The problem is that the client doesn't get redirected to the designated TFTP server. The format for the boot/efi doesn't matter yet because the client is still being given the default gateway as the TFTP server address and not what is assigned in the DHCP Options.
- Copy Link
- Report Inappropriate Content
See this thread https://community.tp-link.com/en/business/forum/topic/641862
A beta software is coming up with next-server support.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5612
Replies: 37
Voters 0
No one has voted for it yet.