Hi @William_Reid 

Thanks for posting in our business forum.

William_Reid wrote

  @Clive_A 

 

Hi there,

 

I was on the latest 2.4 release with the SDN controller running within Docker, after some reading I found out that PXE options are only exposed if running in Standalone mode.

 

As of this morning I've ditched the SDN controller, factory reset my Router as well as AP and configured those for Standalone mode.

 

This issue was still present when running the latest firmware, so I downgraded using the link you posted for 2.2.3 Build 20231201 Rel.57231 and still this doesn't work, nor do I see options for 66 and 67.

 

Not sure what else to try, here's what I have for my settings.

 

 

This was meant for the standalone users. In Controller mode, you must have the controller compatible with the options. Or it does not show up even if the firmware has supported it.

Then wait for the future controller update. I am not responsible for the controller. But the news I got is ETA V5.15.

Hi @rb5network 

Thanks for posting in our business forum.

rb5network wrote

  @Springs42 Wait, I am having the EXACT same problem. Option 66 and 67 are filled out correctly, but anytime I go to boot it finds the file, but tries to fetch it via the gateway IP. Makes absolutely zero sense.

Are you looking for the next server? It does not support it. Try the beta then. Read the previous replies.

Hi @rb5network 

Thanks for posting in our business forum.

rb5network wrote

  @Clive_A Wow, thanks for the quick reply. Yes, the next server is not correct when attempting to boot.

I was a little confused about the version revisions. I take it it's working with a beta version software for the Omada Controller?

Very unfortunate, that firmware was made for the standalone. The controller will add this, ETA V5.15. That's mentioned above.

The temp fix would be setting it in standalone mode and setting the parameters up.