AW: AW: AW: Read Client Hostname

Matthias Mandlmeier matthias.mandlmeier at
Sat Mar 5 04:07:17 PST 2016

Nsupdate will work with my server. I can try to create a patch for this but then I need to know where the variables are set in the sources that I can trigger the hostname and send it to Bind.




-----Ursprüngliche Nachricht-----
Von: Nikos Mavrogiannopoulos [mailto:n.mavrogiannopoulos at] 
Gesendet: Samstag, 5. März 2016 10:55
An: Matthias Mandlmeier <matthias.mandlmeier at>
Cc: 'openconnect-devel' <openconnect-devel at>
Betreff: Re: AW: AW: Read Client Hostname

On Fri, 2016-03-04 at 17:35 +0100, Matthias Mandlmeier wrote:
> If I understand it correctly there is at the moment no possibility to 
> get the hostname value in the up or down scripts. If this is correct 
> does ocserv has the possibitlity to forward the DHCP Request to 
> another DHCP Server and the external DHCP Server will do the DNS 
> Update?

Would nsupdate work with your server? In that case there can be an update coming from ocserv based on the bind library:

In that case only a patch to ocserv would be needed an a testsuite.
Would you be interested to provide that patch?

> An other idea that I have if it is possible that the Up Script will be 
> executed at a later time when the Hostname is known by ocserv?

I find that appealing to call a 3rd script in the login process.

However, your request made me realise that openconnect client's hostname variable is quite arbitrarily set and is of no much use to the server. That would need some cleanup too.


More information about the openconnect-devel mailing list