opsi mac address updating

[SisterOfMercy]

Is there a way to turn off the mac address updating? There is only one mac address listed per client.

However, I have a few laptops which run OpenVPN, and thus have an extra network adapter with its own mac address. Opsi updates the mac address it knows with the mac address from the TAP adapter. When the laptop is connected to the local network any netboot products fail to start, because it of course creates a file in /tftpboot/linux/pxelinux.cfg/ with the mac address of the TAP adapter.

[n.wenselowski]

Hello SisterOfMercy,

as far as I know there is only an option to let opsi update the IP address.
But you are talking about the MAC address.

What version of opsi are you running?
Did you attempt to debug the problem yourself with a high loglevel and then seeing through the logs?


With kind regards

Niko

[SisterOfMercy]

What version of opsi are you running?
Did you attempt to debug the problem yourself with a high loglevel and then seeing through the logs?

I'm running 4.0.5, of course. I have not yet tried to debug it myself, because I didn't exactly know where to start, and what causes the change in mac address. So I hoped anybody would be able to give a clue where to start.

[n.wenselowski]

Hello,

first thing would be to increase the log level for the opsiconfd (in /etc/opsi/opsiconfd.conf) to 7 and then restart the service.
Next I'd try to trigger such an update and then have a look at the logfile of the client where you experienced the change.

If you don't see enough you can increase the level to 8.
If this does not lead anywhere we could look together over one of your logs.


With kind regards

Niko

[wolfbardo]

Is there a way to turn off the mac address updating? There is only one mac address listed per client.

However, I have a few laptops which run OpenVPN, and thus have an extra network adapter with its own mac address. Opsi updates the mac address it knows with the mac address from the TAP adapter. When the laptop is connected to the local network any netboot products fail to start, because it of course creates a file in /tftpboot/linux/pxelinux.cfg/ with the mac address of the TAP adapter.

If one set opsi-client-agent=setup, the setup-script updates per default the mac address which may lead to this problem

regards,
Bardo Wolf

[SisterOfMercy]

If one set opsi-client-agent=setup, the setup-script updates per default the mac address which may lead to this problem

Ah, ok! I will look there, because you probably have something implemented to not pick a wireless mac address. I might be able to change the TAP adapter registry settings so it doesn't get picked up by the opsi-client-agent setup.