Hello Nick, On Mon, Jun 24, 2024 at 11:28:58AM +0100, Nick Porter wrote:
On 24/06/2024 10:03, Hermann.Lauer@uni-heidelberg.de wrote:
So I never thought that I need to use "DHCP-Server-IP-Address" for the TFTP server (which is not the same as the dhcp server at our site).
What should work is, in the virtual server "listen" section, set the ipaddr or src_ipaddr to that of the DHCP server.
Then in your policy set the value of &reply:DHCP-Server-IP-Address to be the TFTP server.
thanks for the quick hint. Already found that out and it works (setting TFTP Server from a python module). Would it be resonable to exchange the order for future development to: # src_ipaddr # ipaddr # reply:DHCP-DHCP-Server-Identifier # reply:DHCP-Server-IP-Address That would allow both attributes (TFTP and DHCP Server Adress) to be dynamically setable, eg. in a python module. Thanks and greetings Hermann -- Administration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 205; 69120 Heidelberg; Tel: (06221)54-14405 Fax: -14427 Email: Hermann.Lauer@iwr.uni-heidelberg.de