ER7206 1.3.1 no Next-Server?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'd received a beta 1.3.0 in early march with Next-Server enabled.
This 1.3.1 version does not offer it. Is there a reason why? Can I ask you re-add it? It was working properly.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Submitted a ticket, and rolled back to the custom beta I'd received.
1.3.1 seems .. iffy anyway? Connectivity when using it was spotty. Sometimes connections would suddenly drop, or fail to establish. No issues on the 1.3.0 firmware I'm using.
- Copy Link
- Report Inappropriate Content
Hello @greenaar,
greenaar wrote
I'd received a beta 1.3.0 in early march with Next-Server enabled.
This 1.3.1 version does not offer it. Is there a reason why?
The 1.3.1 Beta firmware version is mainly to fix some issues based on the ER7206 V1 1.3.0 official firmware rather than functional iterations.
greenaar wrote
Can I ask you re-add it? It was working properly.
Thank you for your valuable feedback. I've recorded this to the developer team for further investigation and evaluation.
- Copy Link
- Report Inappropriate Content
@Hank21 ticket TKID230226666 resulted in a firmware build in march which was based on 1.3.0, it included the Next-Server option, and I reported back success, and the ticket was closed.
I assumed that option would get rolled into 1.3.1, as it was requested, supplied, tested, and verified. Lacking it, the ER7206 does not provide PXE boot support.
I've opened TKID230550573 to see if this can be resolved.
- Copy Link
- Report Inappropriate Content
Thanks for the update, I was wondering if 1.3.1 fixed the pxe boot next server issue as I was just about to go and test it.
I would really like to have a final resolution that enables pxe boot within omada ecosystem. I feel it so close yet seems not to be taken care of. The previous update made a push in that direction and as close as they are (messing up option 12 vs 66).... Nothing happens. Hope the final fix can be promoted to 1.3.1 soon.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 670
Replies: 4
Voters 1
