Hi @GRL 

Thanks for posting in our business forum.

The remote site adoption and other description, are you referring to the controller being on a remote site?

GRL wrote

I have an ES205G that I am testing and will be installing at one of my remote sites.

 

I have discovered that it does not become visible on the site>devices page unless you log into its stand alone GUI and set the controller IP to where it needs to be.

 

On my main site where controller is, this is not a problem and it works immediately.

 

I have DHCP option 138 set to my controller IP on both the remote sites management vlans.

 

I think this may be because remote sites are inherently on a different IP range to the controller, so it seems to ignore the option138 setting served by the gateways at the remote sites.

 

Once logeed into standalone GUI for the switch and set its controller IP - adoption proceeds as normal.

 

Tested on a remote site adopted inside VPN and another adopted over port forward.

If it is the remote site, I think 138 does not work really well with this. If it is local, that should be fine.

  @GRL 

I did a test with ES205GP with 1.0.2 firmware, it worked fine with option 138, more and more also support option 43 but it didn't work on ES205GP.

Tested in an SD-WAN vpn tunnel.